Secrets are not encrypted by default in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the default state of Kubernetes Secrets in terms of encryption?

By default, Kubernetes Secrets are stored as base64-encoded strings in etcd, but they are not encrypted at rest.

beginner

Why is it risky to rely on default Kubernetes Secrets storage?

Because Secrets are not encrypted by default, anyone with access to etcd can read sensitive data, risking data exposure.

intermediate

How can you enable encryption for Kubernetes Secrets?

You can enable encryption at rest by configuring the EncryptionConfiguration resource and updating the API server to use it.

beginner

What is the role of etcd in Kubernetes Secrets management?

etcd is the key-value store where Kubernetes stores all cluster data, including Secrets, which by default are stored unencrypted.

beginner

What is base64 encoding and does it provide security for Kubernetes Secrets?

Base64 encoding converts data into text format but does not encrypt it; it only makes data readable by systems, not secure from access.

How are Kubernetes Secrets stored by default?

A Hashed with SHA-256

B Encrypted with AES-256

C Plain text in etcd

D Base64 encoded but not encrypted

Kubernetes stores Secrets base64 encoded in etcd by default, which is not encryption.

What must you configure to encrypt Kubernetes Secrets at rest?

A EncryptionConfiguration and API server flags

B Pod Security Policies

C Network Policies

D RBAC Roles

EncryptionConfiguration resource and API server flags enable encryption of Secrets at rest.

Why is base64 encoding not enough to protect Secrets?

A It compresses data too much

B It only encodes data, does not encrypt it

C It hashes data irreversibly

D It stores data in plain text

Base64 encoding only changes data format; it does not provide confidentiality.

Where are Kubernetes Secrets stored in the cluster?

A In container file system only

B In pod environment variables only

C In etcd key-value store

D In the Kubernetes dashboard

Secrets are stored in etcd, the cluster's key-value store.

What is a simple step to improve Secrets security in Kubernetes?

A Enable encryption at rest for etcd

B Use longer base64 strings

C Store Secrets in ConfigMaps

D Disable RBAC

Enabling encryption at rest protects Secrets stored in etcd.

Explain why Kubernetes Secrets are not secure by default and how you can improve their security.

Think about how Secrets are stored and what encryption means.

Describe the role of etcd in Kubernetes Secrets management and the risks involved.

Consider where Secrets live and who can access them.

Practice

1. What is the default way Kubernetes stores Secrets?

easy

A. Hashed using SHA-256 before storage

B. As base64 encoded plain text in etcd

C. Stored in an external vault automatically

D. Encrypted with AES-256 by default

Solution

1. Step 1: Understand Kubernetes default Secret storage

   Kubernetes stores Secrets in etcd as base64 encoded strings, which is not encryption but simple encoding.

2. Step 2: Confirm encryption is not enabled by default

   Encryption at rest must be explicitly configured; by default, Secrets are not encrypted.

3. Final Answer:

   As base64 encoded plain text in etcd -> Option B

4. Quick Check:

   Default Secret storage = base64 plain text [OK]

Hint: Remember: base64 is encoding, not encryption [OK]

Common Mistakes:

• Confusing base64 encoding with encryption
• Assuming Secrets are encrypted by default
• Thinking Kubernetes uses external vault automatically

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

easy

A. Configure EncryptionConfiguration file in API server flags

B. Set encryption: true in the Secret manifest

C. Add --encryption-provider flag to kubelet

D. Use kubectl encrypt secret command

Solution

1. Step 1: Identify where encryption is configured

   Encryption at rest is enabled by configuring the API server with an EncryptionConfiguration file and passing it via flags.

2. Step 2: Verify other options are invalid

   Kubelet does not handle encryption, Secret manifests do not have encryption fields, and kubectl has no encrypt command.

3. Final Answer:

   Configure EncryptionConfiguration file in API server flags -> Option A

4. Quick Check:

   Encryption enabled via API server config [OK]

Hint: Encryption config is on API server, not kubelet or kubectl [OK]

Common Mistakes:

• Trying to encrypt Secrets via kubectl commands
• Assuming kubelet manages encryption
• Adding encryption fields in Secret YAML

3. Given this snippet from an EncryptionConfiguration file:

{
  "kind": "EncryptionConfiguration",
  "apiVersion": "apiserver.config.k8s.io/v1",
  "resources": [
    {
      "resources": ["secrets"],
      "providers": [
        {"aescbc": {"keys": [{"name": "key1", "secret": "c2VjcmV0MTIzNDU2Nzg5MDEyMzQ1Njc4OTA="}]}},
        {"identity": {}}
      ]
    }
  ]
}

What does this configuration do?

medium

A. Encrypts Secrets using AES-CBC with key1, falling back to no encryption

B. Encrypts all resources except Secrets

C. Disables encryption for Secrets

D. Encrypts Secrets using identity provider only

Solution

1. Step 1: Analyze the providers list for Secrets

   The providers list has an AES-CBC encryption provider with a key named key1, followed by identity (no encryption) as fallback.

2. Step 2: Understand the effect on Secrets

   This means Secrets are encrypted with AES-CBC using key1; if decryption fails, identity provider returns plain data.

3. Final Answer:

   Encrypts Secrets using AES-CBC with key1, falling back to no encryption -> Option A

4. Quick Check:

   Encryption config with AES-CBC + identity fallback [OK]

Hint: First provider encrypts, second is fallback identity [OK]

Common Mistakes:

• Thinking identity means encryption is disabled
• Assuming all resources are encrypted, not just Secrets
• Confusing provider order effect

4. You configured encryption for Secrets but still see base64 encoded plain text in etcd. What is the most likely cause?

medium

A. Secrets manifest missing encryption annotation

B. Encryption key is too short

C. kubectl version is outdated

D. API server was not restarted after adding EncryptionConfiguration

Solution

1. Step 1: Check if API server reload is needed

   EncryptionConfiguration changes require API server restart to take effect.

2. Step 2: Verify other options are irrelevant

   Secrets do not need annotations for encryption, kubectl version does not affect encryption, and key length would cause errors, not silent failure.

3. Final Answer:

   API server was not restarted after adding EncryptionConfiguration -> Option D

4. Quick Check:

   API server restart required for encryption config [OK]

Hint: Restart API server after config changes [OK]

Common Mistakes:

• Forgetting to restart API server
• Adding encryption annotations to Secrets
• Blaming kubectl version for encryption issues

5. You want to ensure all Secrets in your cluster are encrypted at rest. Which steps should you follow? Select the correct sequence.

hard

A. Enable encryption in kube-proxy config, restart kube-proxy, check logs

B. Add encryption field to Secret manifests, restart kubelet, verify kubectl output

C. Create EncryptionConfiguration file, update API server flags, restart API server, verify etcd data

D. Run kubectl encrypt secrets, update RBAC, restart API server

Solution

1. Step 1: Prepare EncryptionConfiguration file

   Create a file defining encryption providers for Secrets, typically AES-CBC or AES-GCM.

2. Step 2: Update API server flags and restart

   Pass the EncryptionConfiguration file path to the API server via flags and restart it to apply changes.

3. Step 3: Verify Secrets are encrypted in etcd

   Check etcd data to confirm Secrets are stored encrypted, not just base64 encoded.

4. Final Answer:

   Create EncryptionConfiguration file, update API server flags, restart API server, verify etcd data -> Option C

5. Quick Check:

   Encryption setup = config file + API server restart + verify [OK]

Hint: Encryption needs config file + API server restart + verify [OK]

Common Mistakes:

• Trying to encrypt Secrets via manifest changes
• Restarting wrong components like kubelet or kube-proxy
• Using non-existent kubectl encrypt command