Secrets encryption at rest in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of enabling secrets encryption at rest in Kubernetes?

Why do Kubernetes clusters use encryption at rest for secrets?

A To automatically rotate secrets without user intervention

B To speed up the retrieval of secrets from the API server

C To allow secrets to be shared publicly without risk

D To protect secret data stored on disk from unauthorized access if the storage medium is compromised

💡 Hint

Think about what happens if someone gets physical access to the storage where secrets are saved.

Encryption at rest protects secret data stored on disk by making it unreadable without the encryption key. This prevents unauthorized users from accessing secrets even if they get access to the storage.

💻 Command Output

intermediate

What is the output of enabling encryption providers in Kubernetes API server config?

Given the following snippet in the EncryptionConfiguration file, what will be the effect on stored secrets?

apiVersion: apiserver.config.k8s.io/v1
encryptionConfig:
  resources:
  - resources:
    - secrets
    providers:
    - aescbc:
        keys:
        - name: key1
          secret: c2VjcmV0a2V5MTIzNDU2Nzg5MA==
    - identity: {}

A Secrets will be deleted automatically after encryption

B Secrets will be stored unencrypted because identity provider is last

C Secrets will be encrypted using AES-CBC with the provided key before storage

D Secrets will be encrypted using a random key each time

💡 Hint

The order of providers matters. The first provider that can encrypt is used.

The AES-CBC provider is listed first, so secrets are encrypted using AES-CBC with the given key. The identity provider is fallback and stores data unencrypted only if encryption fails.

❓ Troubleshoot

advanced

Why might secrets appear unencrypted in etcd after enabling encryption at rest?

You enabled encryption at rest for secrets in Kubernetes, but when you check etcd data, secrets appear in plain text. What could be the cause?

A The API server was not restarted after updating the encryption config

B The encryption key is too short and was rejected silently

C Secrets are always stored unencrypted in etcd regardless of config

D The kubelet is caching old secrets and showing unencrypted data

💡 Hint

Think about what is required for the API server to apply new config changes.

The API server must be restarted to load the new encryption configuration. Without restart, it continues to store secrets unencrypted.

🔀 Workflow

advanced

What is the correct order of steps to enable secrets encryption at rest in Kubernetes?

Arrange the following steps in the correct order to enable encryption at rest for secrets in a Kubernetes cluster.

A 4,1,2,3

B 1,4,2,3

C 4,2,1,3

D 1,2,4,3

💡 Hint

Think about safety first, then config, then restart, then verify.

Backing up secrets first prevents data loss. Then create the config, restart API server to apply, and finally verify encryption.

✅ Best Practice

expert

Which practice improves security when rotating encryption keys for Kubernetes secrets at rest?

You need to rotate the encryption keys used for secrets at rest. Which practice ensures minimal downtime and data safety?

A Rotate keys by changing the key name but keeping the same secret value

B Add the new key as the first provider in the EncryptionConfiguration, keep the old key as second, then restart API server

C Rotate keys by deleting all secrets and recreating them with new keys

D Remove the old key immediately and add the new key only, then restart API server

💡 Hint

Consider how Kubernetes decrypts and re-encrypts secrets during key rotation.

Adding the new key first allows the API server to encrypt new secrets with it, while still decrypting old secrets with the old key. This enables smooth rotation without data loss.

Practice

1. What is the main purpose of enabling Secrets encryption at rest in Kubernetes?

easy

A. To protect sensitive data stored in etcd from unauthorized access

B. To speed up the retrieval of Secrets from the API server

C. To allow Secrets to be shared publicly across namespaces

D. To automatically rotate Secrets without manual intervention

Solution

1. Step 1: Understand what Secrets encryption at rest means

   It means encrypting sensitive data stored on disk, specifically in etcd, to prevent unauthorized access if someone gains access to the storage.

2. Step 2: Identify the main goal of this encryption

   The goal is to protect sensitive data like passwords or tokens stored in etcd, not to speed up access or share Secrets publicly.

3. Final Answer:

   To protect sensitive data stored in etcd from unauthorized access -> Option A

4. Quick Check:

   Secrets encryption = protect data at rest [OK]

Hint: Encryption at rest means protecting stored data, not speeding access [OK]

Common Mistakes:

• Confusing encryption at rest with encryption in transit
• Thinking encryption shares Secrets publicly
• Assuming encryption automatically rotates Secrets

2. Which of the following is the correct way to enable Secrets encryption at rest in Kubernetes EncryptionConfiguration file?

easy

A. apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- resources:
- secrets
providers:
- aescbc:
keys:
- name: key1
secret:
- identity: {}

B. apiVersion: v1
kind: Secret
metadata:
name: encryption-config
stringData:
key:

C. apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- secrets
providers:
- identity: {}
- aescbc:
keys:
- name: key1
secret:

D. apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfig
resources:
- secrets
- aescbc:
keys:
- name: key1
secret:

Solution

1. Step 1: Review the correct structure of EncryptionConfiguration

   The file must have apiVersion, kind, and a resources list with nested resources and providers. The providers list includes encryption methods like aescbc and identity.

2. Step 2: Compare options for correct YAML syntax and structure

   apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration resources: - secrets providers: - identity: {} - aescbc: keys: - name: key1 secret: correctly nests resources and providers, uses aescbc with keys, and includes identity as fallback. apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration resources: - resources: - secrets providers: - aescbc: keys: - name: key1 secret: - identity: {} incorrectly nests 'resources' under 'resources'. Others have syntax errors or wrong kind names.

3. Final Answer:

   apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration resources: - secrets providers: - identity: {} - aescbc: keys: - name: key1 secret: -> Option C

4. Quick Check:

   Correct YAML structure = apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration resources: - secrets providers: - identity: {} - aescbc: keys: - name: key1 secret: [OK]

Hint: Look for 'resources' as a list of resource names and 'providers' as a list of encryption methods [OK]

Common Mistakes:

• Using wrong kind name like EncryptionConfig instead of EncryptionConfiguration
• Incorrect YAML indentation or missing nested keys
• Placing keys outside the providers list
• Nesting 'resources' under 'resources' incorrectly

3. Given this snippet from a Kubernetes API server log after enabling Secrets encryption at rest:

"Encryption provider aescbc is enabled for resource secrets"
"Using key named key1 for encryption"
"Secrets stored in etcd are now encrypted"

What is the expected effect when retrieving a Secret via kubectl get secret?

medium

A. The Secret data is shown as base64-encoded encrypted strings

B. The Secret data is automatically decrypted and shown in base64-encoded plain text

C. The Secret cannot be retrieved until manual decryption is done

D. The Secret is deleted from etcd after retrieval

Solution

1. Step 1: Understand encryption at rest vs API response

   Encryption at rest means data is encrypted in storage (etcd), but the API server decrypts it before sending to clients.

2. Step 2: Determine what kubectl get secret shows

   kubectl shows the decrypted Secret data in base64-encoded form, which is normal for Secrets, not encrypted ciphertext.

3. Final Answer:

   The Secret data is automatically decrypted and shown in base64-encoded plain text -> Option B

4. Quick Check:

   Encryption at rest decrypts before API response [OK]

Hint: Encryption at rest is transparent to kubectl output [OK]

Common Mistakes:

• Thinking Secrets remain encrypted when retrieved
• Confusing base64 encoding with encryption
• Assuming manual decryption is needed

4. You configured Secrets encryption at rest but notice that Secrets are still stored unencrypted in etcd. What is the most likely cause?

medium

A. The Secrets were created before enabling encryption and never updated

B. The encryption key is too short and rejected silently

C. The etcd cluster does not support encryption

D. The API server was not restarted after applying the encryption config

Solution

1. Step 1: Recall how encryption config is applied

   The API server must be restarted to load the new encryption configuration and apply encryption to new Secrets.

2. Step 2: Identify why Secrets remain unencrypted

   If the API server is not restarted, it continues to store Secrets unencrypted despite config changes.

3. Final Answer:

   The API server was not restarted after applying the encryption config -> Option D

4. Quick Check:

   Restart API server to apply encryption config [OK]

Hint: Always restart API server after changing encryption config [OK]

Common Mistakes:

• Assuming existing Secrets auto-encrypt without update
• Believing etcd cannot support encryption
• Ignoring the need to restart API server

5. You want to rotate the encryption key used for Secrets encryption at rest without downtime. Which approach correctly achieves this?

hard

A. Add the new key as the first provider in the encryption config, keep the old key second, then restart the API server

B. Replace the old key with the new key in the config and restart the API server immediately

C. Delete all Secrets, update the key, then recreate Secrets encrypted with the new key

D. Update the key in etcd directly without changing the API server config

Solution

1. Step 1: Understand key rotation in encryption config

   To rotate keys safely, add the new key first so new Secrets encrypt with it, and keep the old key to decrypt existing Secrets.

2. Step 2: Apply config and restart API server

   Restarting the API server loads the new config. Existing Secrets remain decryptable with the old key, allowing smooth rotation.

3. Final Answer:

   Add the new key as the first provider in the encryption config, keep the old key second, then restart the API server -> Option A

4. Quick Check:

   New key first, old key second, restart API server [OK]

Hint: New key first, old key second in config for smooth rotation [OK]

Common Mistakes:

• Replacing old key immediately causing decryption failures
• Deleting Secrets instead of rotating keys
• Modifying etcd data directly risking corruption