Secrets encryption at rest in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable encryption of Kubernetes secrets at rest by specifying the encryption provider.

Kubernetes

apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- resources:
  - secrets
  providers:
  - [1]:
      keys:
      - name: key1
        secret: <base64-encoded-secret>

Drag options to blanks, or click blank then click option'

Aaescbc

Bplaintext

Cidentity

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'plaintext' or 'identity' which do not encrypt secrets.

Leaving the provider field empty.

The aescbc provider enables AES-CBC encryption for secrets at rest in Kubernetes. Other options like plaintext or identity do not encrypt data.

2fill in blank

medium

Complete the command to restart the Kubernetes API server to apply the encryption configuration.

Kubernetes

kubectl -n kube-system delete pod -l component=[1]

Drag options to blanks, or click blank then click option'

Akube-controller-manager

Bkube-scheduler

Ckube-apiserver

Detcd

Attempts:

3 left

💡 Hint

Common Mistakes

Restarting the etcd pod instead of the API server.

Using the controller-manager or scheduler labels.

The Kubernetes API server pod must be restarted to apply the encryption configuration. The label component=kube-apiserver targets the API server pods.

3fill in blank

hard

Fix the error in the encryption configuration by choosing the correct key format for the secret.

Kubernetes

providers:
- aescbc:
    keys:
    - name: key1
      secret: [1]

Drag options to blanks, or click blank then click option'

Amy-secret-key

Bbase64encodedkey

C1234567890abcdef

DYWJjMTIzIT8kKiYoKSctPUB+

Attempts:

3 left

💡 Hint

Common Mistakes

Using plain text keys instead of base64 encoded strings.

Using incomplete or invalid base64 strings.

The secret key must be base64 encoded. Option D is a valid base64 string, while others are plain text or invalid formats.

4fill in blank

hard

Fill both blanks to complete the command that checks if secrets are encrypted in etcd by querying etcd directly.

Kubernetes

ETCDCTL_API=3 etcdctl --endpoints=[1] get /registry/secrets --prefix --keys-only | grep [2]

Drag options to blanks, or click blank then click option'

Ahttps://127.0.0.1:2379

Bdefault

Ckube-system

Dsecrets

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong etcd endpoint URL.

Filtering with incorrect keywords like 'default' or 'kube-system'.

The etcd endpoint is usually at https://127.0.0.1:2379. To filter secret keys, grep for secrets in the keys output.

5fill in blank

hard

Fill all three blanks to create a Kubernetes manifest snippet that enables encryption at rest with the 'aescbc' provider and a base64 key.

Kubernetes

apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- resources:
  - secrets
  providers:
  - [1]:
      keys:
      - name: [2]
        secret: [3]

Drag options to blanks, or click blank then click option'

Aaescbc

Bkey1

CYWJjMTIzIT8kKiYoKSctPUB+

Didentity

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'identity' as provider which disables encryption.

Using plain text instead of base64 for the secret.

This manifest enables AES-CBC encryption for secrets using a key named 'key1' with a base64 encoded secret key.

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