Organizing with recommended labels in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of using labels in Kubernetes?

Labels help organize and select Kubernetes objects like pods and services by attaching key-value pairs. They make managing and grouping resources easier.

beginner

Name two common recommended labels in Kubernetes.

Two common recommended labels are app.kubernetes.io/name for the application name and app.kubernetes.io/version for the version of the application.

intermediate

How do recommended labels improve collaboration in a Kubernetes environment?

Recommended labels create a common language for teams to identify and manage resources consistently, making it easier to find, filter, and understand resource roles.

beginner

What label key would you use to indicate the component within an application?

Use app.kubernetes.io/component to specify the component, such as 'frontend' or 'database', within the application.

intermediate

Why should you avoid using labels for storing large or sensitive data?

Labels are meant for small, simple key-value pairs to organize resources. Large or sensitive data can cause performance issues or security risks if stored in labels.

Which label key is recommended to specify the version of an application in Kubernetes?

A version.app.kubernetes.io

B app.kubernetes.io/version

C app.version.kubernetes.io

D kubernetes.app.version.io

The correct label key for application version is app.kubernetes.io/version.

What is the main benefit of using recommended labels in Kubernetes?

A To organize and manage resources consistently

B To store large configuration files

C To replace annotations completely

D To encrypt data inside pods

Recommended labels help organize and manage Kubernetes resources consistently across teams.

Which label would you use to indicate the part of the application a resource belongs to?

A app.kubernetes.io/component

B app.kubernetes.io/part

C app.kubernetes.io/section

D app.kubernetes.io/role

The label app.kubernetes.io/component is used to specify the component within an application.

Can labels be used to store sensitive data securely?

A Yes, if you use special label keys

B Yes, labels encrypt data automatically

C No, labels are not secure for sensitive data

D Only if combined with annotations

Labels are not designed for storing sensitive data securely and should not be used for that purpose.

Which of the following is NOT a recommended label key in Kubernetes?

A app.kubernetes.io/name

B app.kubernetes.io/instance

C app.kubernetes.io/owner

D app.kubernetes.io/large-data

app.kubernetes.io/large-data is not a recommended label key; labels should not store large data.

Explain why using recommended labels is important for organizing Kubernetes resources.

Think about how labels help find and group resources.

List at least three recommended label keys and describe what each one represents.

Focus on common labels used to identify app details.

Practice

1. What is the main purpose of using recommended labels in Kubernetes?

easy

A. To encrypt data stored in Kubernetes secrets

B. To increase the CPU and memory limits of pods

C. To automatically update Kubernetes versions

D. To organize and categorize Kubernetes objects consistently

Solution

1. Step 1: Understand what labels do in Kubernetes

   Labels are key-value pairs used to organize and select Kubernetes objects.

2. Step 2: Identify the role of recommended labels

   Recommended labels provide a standard way to name, version, and categorize resources for easier management.

3. Final Answer:

   To organize and categorize Kubernetes objects consistently -> Option D

4. Quick Check:

   Labels organize resources = A [OK]

Hint: Labels help group and find resources easily [OK]

Common Mistakes:

• Confusing labels with resource limits
• Thinking labels update Kubernetes versions
• Mixing labels with data encryption

2. Which of the following is the correct syntax to add a recommended label app.kubernetes.io/name: myapp to a pod YAML?

easy

A. metadata:
labels:
app.kubernetes.io/name: myapp

B. spec:
labels:
app.kubernetes.io/name: myapp

C. metadata:
annotations:
app.kubernetes.io/name: myapp

D. spec:
annotations:
app.kubernetes.io/name: myapp

Solution

1. Step 1: Identify where labels belong in Kubernetes YAML

   Labels are defined under metadata.labels in resource manifests.

2. Step 2: Check the options for correct placement

   metadata: labels: app.kubernetes.io/name: myapp correctly places the label under metadata.labels. Labels belong under metadata, not spec, and should use labels not annotations.

3. Final Answer:

   metadata: labels: app.kubernetes.io/name: myapp -> Option A

4. Quick Check:

   Labels go under metadata.labels = B [OK]

Hint: Labels always go under metadata.labels in YAML [OK]

Common Mistakes:

• Putting labels under spec instead of metadata
• Confusing labels with annotations
• Incorrect indentation in YAML

3. Given this pod YAML snippet, what label selector would match this pod?

metadata:
  labels:
    app.kubernetes.io/name: frontend
    app.kubernetes.io/version: v1

medium

A. app.kubernetes.io/name=backend

B. app.kubernetes.io/name=frontend

C. app.kubernetes.io/version=v2

D. app.kubernetes.io/component=frontend

Solution

1. Step 1: Read the pod's labels

   The pod has labels app.kubernetes.io/name: frontend and app.kubernetes.io/version: v1.

2. Step 2: Match the selector to the labels

   Only app.kubernetes.io/name=frontend matches the label key and value exactly. The other options use mismatched keys or values.

3. Final Answer:

   app.kubernetes.io/name=frontend -> Option B

4. Quick Check:

   Selector matches label key and value = C [OK]

Hint: Selector must exactly match label key and value [OK]

Common Mistakes:

• Using wrong label values
• Confusing label keys
• Using non-existent labels in selector

4. You applied this YAML but your pod is not selected by the service selector:

metadata:
  labels:
    app.kubernetes.io/name: frontend
spec:
  containers:
  - name: app
    image: nginx

What is the likely problem?

medium

A. The service selector does not match the pod labels

B. Labels are under spec instead of metadata

C. The container image is incorrect

D. The label key is missing the recommended prefix

Solution

1. Step 1: Check the pod labels

   The pod has label app.kubernetes.io/name: frontend under metadata.labels, which is correct.

2. Step 2: Understand why the service selector might fail

   If the service selector does not exactly match the pod's labels, the pod won't be selected. The problem is likely a mismatch in the service selector, not the pod labels or container image.

3. Final Answer:

   The service selector does not match the pod labels -> Option A

4. Quick Check:

   Selector must match pod labels = D [OK]

Hint: Service selector must exactly match pod labels [OK]

Common Mistakes:

• Assuming label keys are incorrect when they are correct
• Thinking labels belong under spec
• Blaming container image for selector issues

5. You want to organize your Kubernetes resources using recommended labels for app name, version, and component. Which set of labels should you apply to a backend service named api version v2?

hard

A. app: api
ver: v2
comp: backend

B. name: api
version: v2
component: backend

C. app.kubernetes.io/name: api
app.kubernetes.io/version: v2
app.kubernetes.io/component: backend

D. app.kubernetes.io/name: api
app.kubernetes.io/version: v1
app.kubernetes.io/component: backend

Solution

1. Step 1: Identify the recommended label keys

   Recommended labels use the prefix app.kubernetes.io/ followed by keys like name, version, and component.

2. Step 2: Match the correct values for the backend service

   The service is named api, version v2, and component backend. app.kubernetes.io/name: api app.kubernetes.io/version: v2 app.kubernetes.io/component: backend correctly uses recommended keys and values. Other options either lack the app.kubernetes.io/ prefix or use the wrong version (v1).

3. Final Answer:

   app.kubernetes.io/name: api app.kubernetes.io/version: v2 app.kubernetes.io/component: backend -> Option C

4. Quick Check:

   Use recommended keys with correct values = A [OK]

Hint: Use full recommended label keys with correct values [OK]

Common Mistakes:

• Using short or incorrect label keys
• Applying wrong version value
• Omitting the recommended prefix