Skip to main content

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 --selector app=myapp 
-> Get pods filtered by labels

kubectl get pods --selector app=myapp,tier=frontend 
-> Get pods filtered by labels app=myapp and tier=frontend

Replica Set
  • Kubernetes also uses labels to build objects.
  • For example take a case of replica set, 
    • Labels under metadata are replicaSet labels
    • labels under template.metadata are pod labels
    • labels under selector.matchLabels are selector labels
  • Kubernetes uses the selector.matchLabels to identify which pods have to be created as defined in spec.template by matching it with spec.template.metadata.labels

replica-set-definition.yaml
apiVersion: apps/v1
kind: ReplicaSet
metadata:
    name: myapp-rs
    labels:
        app: myapp
        type: front-end

spec:
    template:
        metadata:
            name: myapp-pod
            labels:
                app: myapp
                type: front-end
            spec:
                containers:
                - name: nginx-container
                  image: nginx


    replicas: 3
    selector:
        matchLabels:
            type: front-end

Service
  • For a Service object Kubernetes matches the labels defined under spec.selector to metadata.labels as defined under pod-definition file
apiVersion: v1
kind: Service
metadata:
    name: myapp-rs
    labels:
        app: my-svc-app

spec:
    selector:
        app: myapp
    ports:
    - protocol: TCP
      port: 8080
      targetPort: 9376

Annotations
  • Annotations though sound similar to labels are to be used to store the custom information specific to object
  • With labels, you can use them to group objects or filter them with selectors
  • Annotations are custom information about the object
pod-definition.yaml
apiVersion: v1
kind: Pod
metadata:
    name: myapp-pod
    labels:
        app: myapp
        location: IN
    annotations:
        buildVersion: 1.34
        contact: am@memories.com

spec:
    containers:
    - name: nginx-container
      image: nginx
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