Good knowledge of the Kubernetes basic concepts and components - this exercise will be utilizing Kubernetes concepts such as Deployments, Services, Volumes, PersistentVolume, Secrets, Pods, Containers, etc. For more on Kubernetes concepts check out this documentation. - Source: dev.to / about 2 months ago
Create a deployment.yaml to define a Deployment resource. A Deployment in Kubernetes is a resource that manages and updates a group of identical pods that run our application. Ensure to substitute IP 80.85.245.188 to your VPS IP. - Source: dev.to / 3 months ago
Kubernetes Deployments Documentation. - Source: dev.to / 3 months ago
Deployments manage a set of pods and ensure your application is running in the desired state. When you use Kubernetes, you'll inevitably write a deployment at some point along the line. - Source: dev.to / 4 months ago
The above command will take us to our deployment file. We can go ahead and edit the file with information from a similar file in Kubernetes documentation at https://kubernetes.io/docs/concepts/workloads/controllers/deployment/ and also enable a port. Please note that we replaced the name of the app with sever1 and added the section for port, and protocol. As can be seen below. - Source: dev.to / 9 months ago
Kubernetes objects are the declarative definition of the requested state. For instance, the following a deployment (https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) definition is a Kubernetes object that will run four instances of the nginx container in a cluster:. - Source: dev.to / 10 months ago
I am new to kubernetes and microservices, there are 2 objects, Deployments and ReplicaSet. Source: 11 months ago
See https://kubernetes.io/docs/concepts/workloads/controllers/deployment/. Source: 11 months ago
Pod =/= deployment. You haven’t created a deployment based on the commands you showed. Look at the example yaml for deployments and you’ll see some differences from a pod spec. K8s deployment docs. Source: 11 months ago
So now, we need a Deployment for our database. Technically speaking, you could also deploy a database using a StatefulSet. Still, I'm leaving that debate for another day (or you can also check this blog in case you are curious). So let's write the deployment file and ensure it uses the proper ConfigMap and Secret. If you remember, back from our docker-compose file, the DB section used a docker volume to write... - Source: dev.to / over 1 year ago
I came across following deployment configuration in kubernetes docs:. Source: over 1 year ago
As I mentioned earlier, the rendered YAML manifests for the OpenTelemetry Demo App are available to us here. Since, for the purposes of this tutorial, we only care about the featureflagservice’s Kubernetes manifest, I’ve gone ahead and grabbed the manifest pertaining to the featureflagservice, which is made up of a Deployment and a Service, as per below. - Source: dev.to / over 1 year ago
We install the IRIS application using a Helm chart similar to that described in Automating GKE creation on CircleCI builds. For simplicity, we use deployment. That means data doesn’t persist during the pod’s restart. For persistence, you should use Statefulset or, better, Kubernetes IRIS Operator (IKO). You can find an example of IKO deployment in the iris-k8s-monitoring repository. - Source: dev.to / over 1 year ago
Zookeeper is a StatefulSet of three replicas. We need consistently named pods in the cluster. If we used a Deployment, every time a new pod was instantiated, it would be randomly name with a deployment hash suffix. - Source: dev.to / over 1 year ago
For example, the documentation for creating a deployment yaml file shows a limited set of properties and doesn't show how to pass in environment variables, etc. Https://kubernetes.io/docs/concepts/workloads/controllers/deployment/. Source: over 1 year ago
One way could be to just start with the basics: A deployment, a service, and an ingress. And when that start making sense, one can start expanding from there. Source: over 1 year ago
However, it's worth mentioning that usually you won't actually be deploying pods themselves. You'll be using other, higher-level Kubernetes resources like Deployments or DaemonSets that will create pods for you. - Source: dev.to / over 1 year ago
The YAML file sets up a Deployment named foodadvisor-backend. The deployment creates a Pod, which runs one container with your specified Docker image. - Source: dev.to / over 1 year ago
After reading thru Kubernetes documents like this, deployment , service and this I still do not have a clear idea what the purpose of service is. Source: over 1 year ago
From what I can tell in the documentation, a ReplicaSet is created when running a Deployment. It seems to support some of the same features of a ReplicationController - scale up/down and auto restart, but it's not clear if it supports rolling upgrades or autoscale. Source: almost 2 years ago
Example here: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/. Source: almost 2 years ago
Do you know an article comparing kubernetes-deploy to other products?
Suggest a link to a post with product alternatives.
This is an informative page about kubernetes-deploy. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.