Skip to main content

Kubernetes: 6. Imperative Commands

  • Imperative commands are useful in quickly creating the resources on Kubernetes
kubectl
--dry-run -> When created with this option, Kubernetes just validates the definition and does not actually create the resource
-o=yaml -> Gets the output in YAML format

kubectl run nginx-pod --image=nginx:alpine 
-> Create a pod with name nginx-pod and image nginx:alpine

kubectl run httpd --image=httpd:alpine 
-> By default, run implies run-a-pod

kubectl run redis --image=redis:alpine --labels=tier=db 
-> Create a pod with name redis and image redis:alpine and labels set to tier=db

kubectl run custom-nginx --image=nginx --port=8080 
-> Create a pod with name custom-nginx and image nginx to run on port 8080

kubectl expose pod redis --port=6379 --name=redis-service 
-> Create a service with name redis-service to expose pod named redis on service-port 6379

kubectl create deployment webapp --image=kodekloud/webapp-color --replicas=3 
-> Create a deployment with name webapp and image set with 3 replicas

kubectl create ns dev-ns
-> Create a nanespace dev-ns

kubectl create deployment redis-deploy --namespace=dev-ns --image=redis --replicas=2 
-> Create a deployment

kubectl expose pod httpd --name=httpd --type=ClusterIP --port=80 --target-port=8080 
-> Expose a pod as service of type ClusterIP on the specifed ports  
Labels:

Comments

Post a Comment

Popular posts from this blog

Kubernetes: 15. Multiple Schedulers

Custom Scheduler Kubernetes allows to create custom schedulers There can be multiple schedulers running at a same time apart from the default scheduler or A custom scheduler can replace the default kube-scheduler to become the default one So a few pods that requires additional checks apart from taints and toleration, node affinity can go through the custom scheduler before getting scheduled on the node Whereas the rest of the pods can go through the default kube-scheduler Create Custom Scheduler We can either download the kube-scheduler and run it as a service or alternatively create it using a static pod Below here we are downloading the binaries to run it The property scheduler-name is used to define the name of the scheduler, if not set then it will be defaulted to default-scheduler For your custom schedulers, update this property name to set a custom name for your scheduler For Static pods, the name can be updated directly in the pod-definition file Use kubectl create -f <pod-de...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more

Kubernetes: 8. Labels & Selectors

Labels Labels are a way of grouping the objects While Kubernetes understands the objects it create, it is easier to identify the objects by using custom labels With labels you group the objects by types (Pods, Services, ReplicaSet etc) or by Applications For a pod, labels are defined under the metadata section Selectors Selectors are used to filter the objects using labels defined on them Using kubectl and selector pods can be listed by filtering on the labels attached to them If a Selector has multiple labels, they are understood as logical AND, which means pods must match all labels. pod-definition.yaml apiVersion: v1 kind: Pod metadata:      name: myapp-pod      labels:           app: myapp           location: IN spec:      containers:      - name: nginx-container        image: nginx kubectl get pods ...
Post a Comment
Read more