Secret types (Opaque, docker-registry, TLS) in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Opaque secret in Kubernetes?

An Opaque secret is the default secret type in Kubernetes. It stores arbitrary user-defined data as key-value pairs, such as passwords or tokens, in base64 encoded form.

beginner

What is the purpose of a docker-registry secret in Kubernetes?

A docker-registry secret stores credentials for accessing private container registries. It allows Kubernetes to pull private images securely using stored username, password, email, and server URL.

beginner

What does a TLS secret contain in Kubernetes?

A TLS secret contains a private key and a certificate used for TLS encryption. It is commonly used to secure communication between clients and servers inside Kubernetes.

intermediate

How do you create an Opaque secret using kubectl?

Use the command:
kubectl create secret generic my-secret --from-literal=key1=value1 --from-literal=key2=value2
This creates an Opaque secret named 'my-secret' with two key-value pairs.

beginner

Which secret type would you use to store a TLS certificate and key?

You would use the TLS secret type because it is designed to hold a certificate and private key for secure communication.

What is the default secret type in Kubernetes?

A ServiceAccountToken

B docker-registry

C TLS

D Opaque

Opaque is the default secret type used to store arbitrary key-value pairs.

Which secret type is used to store Docker registry credentials?

A docker-registry

B TLS

C Opaque

D BasicAuth

The docker-registry secret stores credentials for private container registries.

What data does a TLS secret contain?

A Certificate and private key

B Username and password

C API tokens

D Config maps

TLS secrets hold a certificate and private key for encrypted communication.

How do you create an Opaque secret with literal values?

A kubectl create secret docker-registry

B kubectl create secret generic --from-literal

C kubectl create secret tls

D kubectl create configmap

Use 'kubectl create secret generic' with --from-literal to create an Opaque secret.

Which secret type is best for storing a private key and certificate for HTTPS?

A Opaque

B docker-registry

C TLS

D BasicAuth

TLS secret type is designed for storing certificates and private keys.

Explain the differences between Opaque, docker-registry, and TLS secret types in Kubernetes.

Think about what kind of data each secret type holds and why.

Describe how you would create and use a docker-registry secret to pull a private image.

Focus on the command and how Kubernetes uses the secret.

Practice

1. Which Kubernetes secret type is best suited for storing general sensitive data like passwords or tokens?

easy

A. Opaque

B. docker-registry

C. TLS

D. ConfigMap

Solution

1. Step 1: Understand secret types

   Opaque secrets are designed to store arbitrary user-defined data such as passwords or tokens.

2. Step 2: Compare with other types

   docker-registry is for Docker credentials, TLS is for certificates, and ConfigMap is not a secret type.

3. Final Answer:

   Opaque -> Option A

4. Quick Check:

   General sensitive data = Opaque [OK]

Hint: Opaque = general secret data, docker-registry = Docker creds [OK]

Common Mistakes:

• Confusing TLS secrets with general data storage
• Using docker-registry for non-Docker secrets
• Thinking ConfigMap is a secret type

2. Which kubectl command correctly creates a docker-registry secret named myregistrykey with username user1 and password pass123?

easy

A. kubectl create secret docker-registry myregistrykey --docker-server=https://myregistry.com --docker-username=user1 --docker-password=pass123

B. kubectl create secret generic myregistrykey --docker-username=user1 --docker-password=pass123

C. kubectl create secret tls myregistrykey --docker-username=user1 --docker-password=pass123

D. kubectl create secret docker-registry myregistrykey --username=user1 --password=pass123

Solution

1. Step 1: Identify correct secret type and flags

   docker-registry secrets require the type 'docker-registry' and flags --docker-server, --docker-username and --docker-password.

2. Step 2: Check command syntax

   kubectl create secret docker-registry myregistrykey --docker-server=https://myregistry.com --docker-username=user1 --docker-password=pass123 uses correct type and flags; others use wrong types or flag names.

3. Final Answer:

   kubectl create secret docker-registry myregistrykey --docker-server=https://myregistry.com --docker-username=user1 --docker-password=pass123 -> Option A

4. Quick Check:

   docker-registry + --docker-server/--docker-username/password = correct [OK]

Hint: Use --docker-server, --docker-username and --docker-password with docker-registry type [OK]

Common Mistakes:

• Using generic secret type for docker-registry secrets
• Wrong flag names like --username instead of --docker-username
• Using TLS secret type for docker credentials

3. Given the command kubectl create secret tls mytlssecret --cert=cert.pem --key=key.pem, what will be the type of the created secret?

medium

A. Opaque

B. docker-registry

C. TLS

D. generic

Solution

1. Step 1: Analyze the command

   The command uses 'create secret tls' with certificate and key files specified.

2. Step 2: Match secret type

   Secrets created with 'tls' type store TLS certificates and keys, so the type is TLS.

3. Final Answer:

   TLS -> Option C

4. Quick Check:

   kubectl create secret tls = TLS type secret [OK]

Hint: TLS secrets use 'kubectl create secret tls' with cert and key [OK]

Common Mistakes:

• Assuming TLS secrets are Opaque
• Confusing generic secret type with TLS
• Not specifying cert and key files properly

4. You run kubectl create secret tls mytlssecret --cert=cert.pem but get an error. What is the likely cause?

medium

A. Using wrong secret type, should be opaque

B. Missing --key flag with private key file

C. Certificate file is empty

D. Secret name contains invalid characters

Solution

1. Step 1: Check required flags for TLS secret

   Creating TLS secrets requires both --cert and --key flags to specify certificate and private key files.

2. Step 2: Identify missing flag

   The command only has --cert but lacks --key, causing the error.

3. Final Answer:

   Missing --key flag with private key file -> Option B

4. Quick Check:

   Both --cert and --key required for TLS secret [OK]

Hint: TLS secrets need both --cert and --key flags [OK]

Common Mistakes:

• Omitting the --key flag when creating TLS secrets
• Using opaque type instead of TLS for certs
• Assuming secret name format causes error

5. You want to pull images from a private Docker registry in your Kubernetes cluster. Which secret type should you create and how should you use it in a Pod spec?

hard

A. Create a TLS secret and add it to the Pod's environment variables

B. Create an opaque secret and mount it as a volume in the Pod

C. Create a generic secret and specify it in the Pod's volumes section

D. Create a docker-registry secret and reference it in imagePullSecrets of the Pod

Solution

1. Step 1: Identify secret type for private Docker registry

   docker-registry secret stores Docker credentials for private registries.

2. Step 2: Use secret in Pod spec

   To allow image pull, reference the secret in the Pod's imagePullSecrets field.

3. Final Answer:

   Create a docker-registry secret and reference it in imagePullSecrets of the Pod -> Option D

4. Quick Check:

   Private Docker registry = docker-registry secret + imagePullSecrets [OK]

Hint: Use docker-registry secret with imagePullSecrets in Pod spec [OK]

Common Mistakes:

• Mounting docker-registry secrets as volumes instead of imagePullSecrets
• Using opaque or TLS secrets for Docker registry auth
• Not referencing the secret in Pod spec