We are basically integrators for Kubernetes because it is open source. And if we go further for any supported version, like Red Hat OpenShift or AWS EKS, Azure AKS. So Azure Kubernetes Service and Elastic Kubernetes Service. So that's where we are a partner as well, partner and integrator. Our clients use it mainly for application modularization or new applications in microservices, build, and deployment. So where, like, if the client was running it on a monolithic application or legacy application, and they wanted to refactor their application, we convert it to microservices. That means building those container images, and then running them on a platform like Kubernetes so that it can run across different nodes across the data center, and we can manage it. Basically, it is more of running as container images. So whenever that application requires more scale-out, features, refactoring, or application modernization, that's where we use this Kubernetes platform to run such applications.
We have clients that require us to deploy their monthly client structures in different locations, with different versions of the application running in various environments. For example, one version might be in one shop, and another version in a different shop. We create a container in Docker, and once the container is registered, any changes made can be deployed across all environments, ensuring consistency. Kubernetes handles the deployment process, ensuring everything runs smoothly. The Docker containers perform the necessary tasks for each deployment.
We use this solution to containerize applications. Some of these applications function in Jira, the local tool center. There, we push them to a centralized platform.
People are creating a company that is transforming technology and moving from legacy to container technology. So, they are to be able to develop their ability to go to the public cloud easily. They will reroute the application in containers and need to be able to manage it. One of the use cases is becoming cloud-native. They want to be cloud-dependent and cloud-dependent, so you need a new format and containers to move applications easily in any cloud. For this, you need technology to manage multi-cloud applications and balance them.
For Kubernetes, I'm mainly developing blueprints for both dedicated AKS and Azure AKS. Those are the main use cases. Currently, our dedicated AKS Blueprint is the one used in production and is fairly stable. We work on a shared AKS site use case, primarily for cost reduction and maximizing cloud investment. I'm a vendor and provider for my client. That's my main role under this group. We provide an end-to-end lifecycle, not just spinning things up but also providing other sub-components to complete the building of an AKS product. We can customize it based on client requirements.
At my company, we use Kubernetes to host our databases and applications. We work in the telecom domain, and our products use database technologies like Oracle, Postgres, and Cloudgres. We use Kubernetes to host NoSQL databases like Couchbase and Postgres and for some of our containerized applications. We are involved in multiple projects, not just a single one.
The primary use case of the solution is container orchestration for a microservices-based architecture. I worked on deployment in the cloud and on-premises.
Kubernetes is open source. It's an orchestration platform for container clusters. The solution can be deployed anywhere, such as on-premise or in the cloud.
We're using it to deploy our machine learning solutions. Every public cloud has their own version of Kubernetes. For example, Google has its own version, which is known as the Google Kubernetes Engine. AWS has its own version, which is known as the Elastic Kubernetes Services, EKS. Our entire data team is using the solution. It's between 2,000 and 3,000 people.
Senior Oracle & Cassandra Database Engineer at Bed Bath & Beyond
Real User
Top 10
2022-11-23T13:28:08Z
Nov 23, 2022
We use Kubernetes to run some content as SaaS-based applications, and there are a few more in the pipeline to migrate from the IBM MQ server and mounting to containerization.
We use Kubernetes to deploy a software solution that the company sells to enterprises. Originally, our company offered their software installed without Kubernetes, but they plan to move all future customers to Kubernetes. I would say it's extensively deployed, and they plan to increase it as much as their customer base will accept it.
We are developing some microservices for the banking sector. We are developing microservices and deploying all of them into Kubernetes. We're looking to make these projects scalable, so we are designing the policies for scaling. Also, we are deploying some front-end items. We are integrating Kubernetes on Azure, with the keyboard and storage. This means we have to use the invoice controller to properly route the request to the final destination. Also, we deploy a database, however, it's not the main goal; it's just for a backup plan as we've had some troubles with the database, which is currently in hosted in Oracle Cloud.
Kubernetes is our platform of choice for running things in production, applications, and the like. Everything we build runs on Kubernetes, it's our platform of choice. I'm the principal devs engineer.
Solutions Architect at Rapyder Cloud Solutions Pvt Ltd
Real User
2022-09-08T13:04:16Z
Sep 8, 2022
We are an IT services company, and I am part of a team of DevOps engineers deploying Kubernetes for customers. We deploy it on a virtual machine, so you can deploy it anywhere. The use case depends on the customer's deployment. For example, if the customer has microservices for lots of applications, they can use Kubernetes to segregate new microservices into different segments. They're not using a monolithic application. The same application has different components.
We use Kubernetes for hosting microservices-based applications. Kubernetes varies depending on which distribution you use. We have distributors that make these custom distributions, and I don't have any special requirements.
Practice Director, Global Infrastructure Services at Wipro Limited
Real User
2022-01-19T11:07:52Z
Jan 19, 2022
If our project requires a cloud deployment we will use a cloud provider's version of Kubernetes. For example, Azure or AWS Kubernetes Elastic Services. We try to make use of whatever is provided by the cloud providers. If the project requires an on-premise solution we use products from various vendors, such as Red Hat or other open-source products that can be downloaded and installed for free. We are using Kubernetes for container management. Kubernetes use cases are typically containerized application hosting. This is the basic use case that we do. Another use case can be deploying new application microservices which are loosely coupled and containerized using microservices-based architectures.
Senior Manager -Datacenter Planning and Operations at a comms service provider with 1,001-5,000 employees
Real User
2021-11-04T09:26:00Z
Nov 4, 2021
My primary use case of this solution is for infrastructure implementations - we allocate an EC2 instance and then define how many worker nodes are needed to run the application and the managed nodes.
Learning Manager at a educational organization with 11-50 employees
Real User
2021-10-26T16:47:49Z
Oct 26, 2021
There are many use cases. It's a concept of microservices-based architecture. You will find that Kubernetes is the most reliable solution. I work for a digital advertising company, for example. When you have advertisements that are served on the top of a website, or a sidebar or something, you fill those spaces with digital advertisements. It's a complete market product, and our end customers are media houses and advertisement agencies. We are using 600 or 700 or more microservices on microservice-based architecture, and, in order to run the microservices, we use the container-based technique as it is a much more reliable platform. It's more secure due to the use of isolation techniques. Currently, we are running an almost 190 node cluster. That is a very big cluster. This is how it is used in an advertising context: if there is a cricket game being streamed on a web portal, which has a very high viewership, a lot of companies will want to promote their ads while this particular match is playing. The portal itself is responsible for managing its streaming activity. At the same time, our company is there to display the ads on the sidebars. In such a scenario, where a high volume of people are working on some content and to handle the advertisement from the various media outlets, we need a very good auto-scaling structure. Kubernetes works well for this. At any given point in time, there is a concept for a horizontal port auto scaler based on CCP utilization. Kubernetes itself tries to increase the number of ports, which means it'll try to increase the number of instances, which are running. Another example of how we use Kubernetes is in a banking environment. In this case, they have an on-prem version. They do not have a cloud solution at all. Occasionally, there is a high volume of transactions happening. They need flexibility. They need high availability and the very beautiful thing about the Kubernetes is that, behind the scenes, these companies are doing their own development of their own applications. At any given point of time, if version one of the application is currently running in their data centers in form of Kubernetes, it is very easy for them to launch version two. If version one is running, and another version is running slowly, we can divert all the requests, which are coming to version one over to version two. The moment a customer accepts that particular product, we remove version one, and version two is ready. There is no downtime and no complexity.
We use Kubernetes as a container management solution. We use the Kubernetes solution for security analysis on Verizon's client systems. Kubernetes container services can be used for deploying applications and they can be deployed on the path layer. You deploy Kubernetes, and inside it, you deploy VMs and application containers. If you take Cloud Foundry inside the data cells, you deploy the application and data. This is how the solution operates.
Director Of Sales Marketing at a energy/utilities company with 10,001+ employees
Real User
2021-10-20T15:14:07Z
Oct 20, 2021
Our primary use case of this solution is to maintain the container orchestration. Our platform is mostly containerized and our solution needs Kubernetes because it was developed in a containerized environment. We are end-users.
Cloud Engineer at a retailer with 10,001+ employees
Real User
2021-09-30T15:27:31Z
Sep 30, 2021
Kubernetes is a container-based platform that is used for microservices-based applications. You can containerize and deploy your ports, as well as expose them over the internet, to get your applications running.
CTO at a tech services company with 11-50 employees
Real User
2021-09-10T14:04:55Z
Sep 10, 2021
If you have a lot of nodes and you want to be able to change the node that you are using, you can use Kubernetes. Kubernetes services allow users to be able to run multiple designs as well.
Solution Leader - Cloud Native and Container Platform at a tech services company with 5,001-10,000 employees
Real User
2021-06-22T20:48:05Z
Jun 22, 2021
We use this solution to orchestrate our applications. If for example, you want to use a Microservice for replication, you host it on Docker then you will need to orchestrate your application. This might include autoscaling, security, and traceability for the user.
Architect Watermanagement at a government with 5,001-10,000 employees
Real User
2021-04-07T17:37:00Z
Apr 7, 2021
We use the solution to modernize our IT landscape. We use infrastructure and platform surfaces for our data center. More recently we have added a container as a surface, which is this solution.
Kubernetes is used for cloud-native development. We deploy it to the hybrid cloud, like private in Azure and public cloud in Amazon AWS. Kubernetes is underlying, and we do not use Kubernetes directly. We use products that use underlying Kubernetes like OpenShift or Tanzu.
Multi-Cloud Consulting at a construction company with 5,001-10,000 employees
MSP
2021-01-30T06:53:00Z
Jan 30, 2021
We are not using the Google version, but the open source Kubernetes. This product can be deployed both on cloud or on-premises. Our use case is mostly for multi-services or the applications which you will try to modernize. Investors will come from monolithic applications to mostly cloud-native applications. When I say cloud-native applications, that means each service component will be part of one container. You need a container orchestration or a management platform. So Kubernetes is actually a management or an orchestration platform for containers. Basically, it works with microservice applications.
Solution Architect | Head of BizDev at Greg Solutions
Real User
2020-11-19T16:45:00Z
Nov 19, 2020
The following is a list of the cases when I prefer Kubernetes for application hosting: * Micro-services infrastructure + possible use of some service meshes, like Istio or Linkerd. * Cost efficiency; we are using Kubernetes in conjunction with AWS Spot Instances or Google Cloud preemptible VMs. * Standards-compliant infrastructures like HIPAA, PCI SOC, DSS, and ISOxxxx. * Highly-available or fault-tolerant infrastructures, due to some sort of self-recovery and self-healing. * Infrastructures with automatically scalable applications.
Co-Founder and Architect at a tech company with 1-10 employees
Real User
2020-10-08T07:25:24Z
Oct 8, 2020
The use case in this organization is basically to containerize the applications. It covers both the operational and technology side. I work in the train industry here and that is a medium-sized enterprise. I'm a cloud architect and we are customers of Kubernetes.
We are platinum partners with Oracle and we are preferred partners with Microsoft. I work for an organization which is on both sides of the coin. We are a service integrator organization. We don't have a specific loyalty, we blend in and provide the services. I'm a solutions architect.
It's a mobile phone application with a website written in Angular 8. It's a strategic microservices solution. There are a lot of containers and resources. The application is written in Java, and we are using Spring Boot, the second version. We are also using the application-gateway of Azure. If you want to do the microservices strategy, you need to split the services to the smaller work. There must be containers in Docker. There are not that many good solutions for Docker. So right now, if you need to use Docker, you choose Kubernetes because they are number one for the container orchestration solution.
We primarily use the solution for orchestration. Most of the clients we work with are enjoying the DevOps aspects of Kubernetes. They want to be able to safely and quickly deploy new applications. Others just enjoy the modern way they can deploy containers without being a DevOp company.
Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications.
It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon 15 years of experience of running production workloads at Google, combined with best-of-breed ideas and practices from the community.
We are basically integrators for Kubernetes because it is open source. And if we go further for any supported version, like Red Hat OpenShift or AWS EKS, Azure AKS. So Azure Kubernetes Service and Elastic Kubernetes Service. So that's where we are a partner as well, partner and integrator. Our clients use it mainly for application modularization or new applications in microservices, build, and deployment. So where, like, if the client was running it on a monolithic application or legacy application, and they wanted to refactor their application, we convert it to microservices. That means building those container images, and then running them on a platform like Kubernetes so that it can run across different nodes across the data center, and we can manage it. Basically, it is more of running as container images. So whenever that application requires more scale-out, features, refactoring, or application modernization, that's where we use this Kubernetes platform to run such applications.
We have clients that require us to deploy their monthly client structures in different locations, with different versions of the application running in various environments. For example, one version might be in one shop, and another version in a different shop. We create a container in Docker, and once the container is registered, any changes made can be deployed across all environments, ensuring consistency. Kubernetes handles the deployment process, ensuring everything runs smoothly. The Docker containers perform the necessary tasks for each deployment.
We use this solution to containerize applications. Some of these applications function in Jira, the local tool center. There, we push them to a centralized platform.
People are creating a company that is transforming technology and moving from legacy to container technology. So, they are to be able to develop their ability to go to the public cloud easily. They will reroute the application in containers and need to be able to manage it. One of the use cases is becoming cloud-native. They want to be cloud-dependent and cloud-dependent, so you need a new format and containers to move applications easily in any cloud. For this, you need technology to manage multi-cloud applications and balance them.
Kubernetes is used t deploy all our applications.
We use the product to manage application deployment by troubleshooting and collecting logs.
For Kubernetes, I'm mainly developing blueprints for both dedicated AKS and Azure AKS. Those are the main use cases. Currently, our dedicated AKS Blueprint is the one used in production and is fairly stable. We work on a shared AKS site use case, primarily for cost reduction and maximizing cloud investment. I'm a vendor and provider for my client. That's my main role under this group. We provide an end-to-end lifecycle, not just spinning things up but also providing other sub-components to complete the building of an AKS product. We can customize it based on client requirements.
I use the product for microservices.
At my company, we use Kubernetes to host our databases and applications. We work in the telecom domain, and our products use database technologies like Oracle, Postgres, and Cloudgres. We use Kubernetes to host NoSQL databases like Couchbase and Postgres and for some of our containerized applications. We are involved in multiple projects, not just a single one.
We use the solution to manage the containers efficiently.
The primary use case of the solution is container orchestration for a microservices-based architecture. I worked on deployment in the cloud and on-premises.
We have several use cases, but our primary use is for microservices.
Kubernetes is open source. It's an orchestration platform for container clusters. The solution can be deployed anywhere, such as on-premise or in the cloud.
This solution is used for serving DevOps.
We use Kubernetes to orchestrate the containers for deploying our Docker images to Kubernetes. I'm an Azure DevOps lead.
We're using it to deploy our machine learning solutions. Every public cloud has their own version of Kubernetes. For example, Google has its own version, which is known as the Google Kubernetes Engine. AWS has its own version, which is known as the Elastic Kubernetes Services, EKS. Our entire data team is using the solution. It's between 2,000 and 3,000 people.
We use Kubernetes to run some content as SaaS-based applications, and there are a few more in the pipeline to migrate from the IBM MQ server and mounting to containerization.
We use Kubernetes to deploy a software solution that the company sells to enterprises. Originally, our company offered their software installed without Kubernetes, but they plan to move all future customers to Kubernetes. I would say it's extensively deployed, and they plan to increase it as much as their customer base will accept it.
We are developing some microservices for the banking sector. We are developing microservices and deploying all of them into Kubernetes. We're looking to make these projects scalable, so we are designing the policies for scaling. Also, we are deploying some front-end items. We are integrating Kubernetes on Azure, with the keyboard and storage. This means we have to use the invoice controller to properly route the request to the final destination. Also, we deploy a database, however, it's not the main goal; it's just for a backup plan as we've had some troubles with the database, which is currently in hosted in Oracle Cloud.
Kubernetes is our platform of choice for running things in production, applications, and the like. Everything we build runs on Kubernetes, it's our platform of choice. I'm the principal devs engineer.
We are using the solution to deploy applications that are based on the microservices architecture.
We are an IT services company, and I am part of a team of DevOps engineers deploying Kubernetes for customers. We deploy it on a virtual machine, so you can deploy it anywhere. The use case depends on the customer's deployment. For example, if the customer has microservices for lots of applications, they can use Kubernetes to segregate new microservices into different segments. They're not using a monolithic application. The same application has different components.
I am using Kubernetes for particular projects.
Kubernetes is used to Dockerize and containerized applications.
We deploy our software solution in the Kubernetes environment.
Our setups are all Kubernetes-based. Orchestration and all of that is done through Kubernetes.
We are using it for hosting applications. Customers are hosted on the Kubernetes Service AKS.
We use Kubernetes for hosting microservices-based applications. Kubernetes varies depending on which distribution you use. We have distributors that make these custom distributions, and I don't have any special requirements.
If our project requires a cloud deployment we will use a cloud provider's version of Kubernetes. For example, Azure or AWS Kubernetes Elastic Services. We try to make use of whatever is provided by the cloud providers. If the project requires an on-premise solution we use products from various vendors, such as Red Hat or other open-source products that can be downloaded and installed for free. We are using Kubernetes for container management. Kubernetes use cases are typically containerized application hosting. This is the basic use case that we do. Another use case can be deploying new application microservices which are loosely coupled and containerized using microservices-based architectures.
My primary use case of this solution is for infrastructure implementations - we allocate an EC2 instance and then define how many worker nodes are needed to run the application and the managed nodes.
There are many use cases. It's a concept of microservices-based architecture. You will find that Kubernetes is the most reliable solution. I work for a digital advertising company, for example. When you have advertisements that are served on the top of a website, or a sidebar or something, you fill those spaces with digital advertisements. It's a complete market product, and our end customers are media houses and advertisement agencies. We are using 600 or 700 or more microservices on microservice-based architecture, and, in order to run the microservices, we use the container-based technique as it is a much more reliable platform. It's more secure due to the use of isolation techniques. Currently, we are running an almost 190 node cluster. That is a very big cluster. This is how it is used in an advertising context: if there is a cricket game being streamed on a web portal, which has a very high viewership, a lot of companies will want to promote their ads while this particular match is playing. The portal itself is responsible for managing its streaming activity. At the same time, our company is there to display the ads on the sidebars. In such a scenario, where a high volume of people are working on some content and to handle the advertisement from the various media outlets, we need a very good auto-scaling structure. Kubernetes works well for this. At any given point in time, there is a concept for a horizontal port auto scaler based on CCP utilization. Kubernetes itself tries to increase the number of ports, which means it'll try to increase the number of instances, which are running. Another example of how we use Kubernetes is in a banking environment. In this case, they have an on-prem version. They do not have a cloud solution at all. Occasionally, there is a high volume of transactions happening. They need flexibility. They need high availability and the very beautiful thing about the Kubernetes is that, behind the scenes, these companies are doing their own development of their own applications. At any given point of time, if version one of the application is currently running in their data centers in form of Kubernetes, it is very easy for them to launch version two. If version one is running, and another version is running slowly, we can divert all the requests, which are coming to version one over to version two. The moment a customer accepts that particular product, we remove version one, and version two is ready. There is no downtime and no complexity.
We use Kubernetes as a container management solution. We use the Kubernetes solution for security analysis on Verizon's client systems. Kubernetes container services can be used for deploying applications and they can be deployed on the path layer. You deploy Kubernetes, and inside it, you deploy VMs and application containers. If you take Cloud Foundry inside the data cells, you deploy the application and data. This is how the solution operates.
Our primary use case of this solution is to maintain the container orchestration. Our platform is mostly containerized and our solution needs Kubernetes because it was developed in a containerized environment. We are end-users.
We deploy microservices. We provide the screen namespaces.
Kubernetes is a container-based platform that is used for microservices-based applications. You can containerize and deploy your ports, as well as expose them over the internet, to get your applications running.
If you have a lot of nodes and you want to be able to change the node that you are using, you can use Kubernetes. Kubernetes services allow users to be able to run multiple designs as well.
We use the latest version. We use the solution for deployment purposes.
We use this solution to orchestrate our applications. If for example, you want to use a Microservice for replication, you host it on Docker then you will need to orchestrate your application. This might include autoscaling, security, and traceability for the user.
We use the solution to modernize our IT landscape. We use infrastructure and platform surfaces for our data center. More recently we have added a container as a surface, which is this solution.
Kubernetes is used for cloud-native development. We deploy it to the hybrid cloud, like private in Azure and public cloud in Amazon AWS. Kubernetes is underlying, and we do not use Kubernetes directly. We use products that use underlying Kubernetes like OpenShift or Tanzu.
Our use case of this product is for mobile banking applications. I'm the executive vice president of the company and we are customers of Kubernetes.
We are not using the Google version, but the open source Kubernetes. This product can be deployed both on cloud or on-premises. Our use case is mostly for multi-services or the applications which you will try to modernize. Investors will come from monolithic applications to mostly cloud-native applications. When I say cloud-native applications, that means each service component will be part of one container. You need a container orchestration or a management platform. So Kubernetes is actually a management or an orchestration platform for containers. Basically, it works with microservice applications.
The following is a list of the cases when I prefer Kubernetes for application hosting: * Micro-services infrastructure + possible use of some service meshes, like Istio or Linkerd. * Cost efficiency; we are using Kubernetes in conjunction with AWS Spot Instances or Google Cloud preemptible VMs. * Standards-compliant infrastructures like HIPAA, PCI SOC, DSS, and ISOxxxx. * Highly-available or fault-tolerant infrastructures, due to some sort of self-recovery and self-healing. * Infrastructures with automatically scalable applications.
We primarily use the solution for deploying containers and scheduling the jobs to the Kubernetes for our server-side deployment.
The use case in this organization is basically to containerize the applications. It covers both the operational and technology side. I work in the train industry here and that is a medium-sized enterprise. I'm a cloud architect and we are customers of Kubernetes.
I am currently learning the system, connecting the containers, and assessing the power of it.
We are platinum partners with Oracle and we are preferred partners with Microsoft. I work for an organization which is on both sides of the coin. We are a service integrator organization. We don't have a specific loyalty, we blend in and provide the services. I'm a solutions architect.
It's a mobile phone application with a website written in Angular 8. It's a strategic microservices solution. There are a lot of containers and resources. The application is written in Java, and we are using Spring Boot, the second version. We are also using the application-gateway of Azure. If you want to do the microservices strategy, you need to split the services to the smaller work. There must be containers in Docker. There are not that many good solutions for Docker. So right now, if you need to use Docker, you choose Kubernetes because they are number one for the container orchestration solution.
We primarily use the solution for orchestration. Most of the clients we work with are enjoying the DevOps aspects of Kubernetes. They want to be able to safely and quickly deploy new applications. Others just enjoy the modern way they can deploy containers without being a DevOp company.