Base64 encoding in Secrets in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to encode the string 'password' to base64.

Kubernetes

echo -n 'password' | [1]

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

Acat

Bbase64

Cgrep

Dawk

Attempts:

3 left

💡 Hint

Common Mistakes

Using commands like cat or grep which do not encode data.

Forgetting the -n flag in echo which avoids adding a newline.

The base64 command encodes data to base64 format, which is required for Kubernetes Secrets.

2fill in blank

medium

Complete the YAML snippet to define a Kubernetes Secret with base64 encoded data.

Kubernetes

apiVersion: v1
kind: Secret
metadata:
  name: mysecret
data:
  password: [1]

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

AcGFzc3dvcmQ=

Bpassword

Cpass123

DdGVzdA==

Attempts:

3 left

💡 Hint

Common Mistakes

Putting plain text instead of base64 encoded string.

Using incorrect base64 strings.

The value for password must be base64 encoded. 'cGFzc3dvcmQ=' is the base64 encoding of 'password'.

3fill in blank

hard

Fix the error in the command to decode a base64 encoded secret value.

Kubernetes

echo 'cGFzc3dvcmQ=' | [1]

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

Abase64 --encode

Bbase64 -e

Cbase64 -d

Dbase64 --help

Attempts:

3 left

💡 Hint

Common Mistakes

Using encoding flags instead of decoding.

Not using any flag, which defaults to encoding.

The -d flag tells base64 to decode the input back to plain text.

4fill in blank

hard

Fill both blanks to create a Kubernetes Secret YAML with a base64 encoded username and password.

Kubernetes

apiVersion: v1
kind: Secret
metadata:
  name: usersecret
data:
  username: [1]
  password: [2]

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

AdXNlcg==

Buser

CcGFzc3dvcmQ=

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Using plain text instead of base64 encoded strings.

Mixing up username and password values.

The username 'user' encoded in base64 is 'dXNlcg==', and the password 'password' encoded is 'cGFzc3dvcmQ='.

5fill in blank

hard

Fill all three blanks to create a Kubernetes Secret YAML with base64 encoded keys and values.

Kubernetes

apiVersion: v1
kind: Secret
metadata:
  name: appsecret
data:
  apiKey: [1]
  token: [2]
  env: [3]

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

AYXBpS2V5MTIz

BdG9rZW5WYWx1ZQ==

CcHJvZHVjdGlvbg==

Dapikey123

Attempts:

3 left

💡 Hint

Common Mistakes

Putting plain text values instead of encoded strings.

Using incorrect base64 encodings.

'apikey123' encoded is 'YXBpS2V5MTIz', 'tokenValue' encoded is 'dG9rZW5WYWx1ZQ==', and 'production' encoded is 'cHJvZHVjdGlvbg=='.

Practice

1. What is the main reason Kubernetes Secrets use Base64 encoding for their data?

easy

A. To compress the secret data to save space

B. To encrypt the secret data for security

C. To convert binary data into text format for safe storage

D. To convert text data into binary format for faster access

Solution

1. Step 1: Understand Base64 encoding purpose

   Base64 encoding changes binary data into readable text characters so it can be stored in text files or systems.

2. Step 2: Apply to Kubernetes Secrets

   Kubernetes Secrets store sensitive data as text in YAML files, so Base64 encoding is used to safely represent binary or special characters as text.

3. Final Answer:

   To convert binary data into text format for safe storage -> Option C

4. Quick Check:

   Base64 encoding = text format for storage [OK]

Hint: Base64 makes binary data safe as text in Secrets [OK]

Common Mistakes:

• Thinking Base64 encrypts data
• Confusing Base64 with compression
• Assuming Base64 changes data speed

2. Which of the following is the correct YAML snippet for a Kubernetes Secret with a key named password and value cGFzc3dvcmQ= (Base64 encoded)?

easy

A. apiVersion: v1
kind: Secret
stringData:
password: cGFzc3dvcmQ=

B. apiVersion: v1
kind: Secret
data:
password: cGFzc3dvcmQ=

C. apiVersion: v1
kind: Secret
secrets:
password: cGFzc3dvcmQ=

D. apiVersion: v1
kind: Secret
values:
password: cGFzc3dvcmQ=

Solution

1. Step 1: Identify correct field for Base64 data

   Kubernetes Secrets use the data field to store Base64 encoded values.

2. Step 2: Check YAML structure

   The correct YAML must have apiVersion, kind, and data with the key and Base64 value.

3. Final Answer:

   apiVersion: v1 kind: Secret data: password: cGFzc3dvcmQ= -> Option B

4. Quick Check:

   Base64 data goes under data field [OK]

Hint: Base64 values go under 'data', not 'stringData' or others [OK]

Common Mistakes:

• Using stringData for Base64 encoded values
• Wrong field names like secrets or values
• Missing apiVersion or kind fields

3. Given this command:
kubectl create secret generic mysecret --from-literal=username=admin --from-literal=password=pass123
What will be the Base64 encoded value of the password key in the Secret?

medium

A. cGFzczEyMw==

B. cGFzc3dvcmQ=

C. cGFzc3dvcmQxMjM=

D. cGFzc3dvcmQxMjM0

Solution

1. Step 1: Identify the literal value for password

   The password literal is pass123.

2. Step 2: Base64 encode 'pass123'

   Encoding 'pass123' in Base64 results in cGFzczEyMw==.

3. Final Answer:

   cGFzczEyMw== -> Option A

4. Quick Check:

   Base64('pass123') = cGFzczEyMw== [OK]

Hint: Encode exact literal value, not similar words [OK]

Common Mistakes:

• Encoding 'password' instead of 'pass123'
• Missing padding characters '=='
• Confusing similar Base64 strings

4. You created a Secret YAML with this data field:
data: apiKey: mysecretkey
What is the problem with this Secret definition?

medium

A. The value 'mysecretkey' is not Base64 encoded

B. The key 'apiKey' is invalid in Secrets

C. The data field should be named stringData

D. The Secret kind is missing

Solution

1. Step 1: Check the data field requirements

   The data field requires Base64 encoded values, not plain text.

2. Step 2: Identify the error in the value

   The value 'mysecretkey' is plain text and must be Base64 encoded before placing under data.

3. Final Answer:

   The value 'mysecretkey' is not Base64 encoded -> Option A

4. Quick Check:

   data values must be Base64 encoded [OK]

Hint: data field values must be Base64, else error [OK]

Common Mistakes:

• Putting plain text in data instead of Base64
• Confusing data with stringData field
• Ignoring required apiVersion and kind fields

5. You want to create a Kubernetes Secret from a file config.json containing JSON data. Which command correctly creates the Secret with Base64 encoding handled automatically?

hard

A. kubectl create secret generic myconfig --from-file=config.json --encode

B. kubectl create secret generic myconfig --from-literal=config.json=$(cat config.json | base64)

C. kubectl create secret generic myconfig --from-literal=config.json=config.json

D. kubectl create secret generic myconfig --from-file=config.json

Solution

1. Step 1: Understand kubectl create secret from-file option

   The --from-file option reads the file and automatically Base64 encodes its content for the Secret.

2. Step 2: Evaluate other options

   kubectl create secret generic myconfig --from-literal=config.json=$(cat config.json | base64) manually encodes but is unnecessary; kubectl create secret generic myconfig --from-literal=config.json=config.json uses literal text; kubectl create secret generic myconfig --from-file=config.json --encode uses a non-existent flag.

3. Final Answer:

   kubectl create secret generic myconfig --from-file=config.json -> Option D

4. Quick Check:

   Use --from-file to auto Base64 encode files [OK]

Hint: Use --from-file to auto Base64 encode file content [OK]

Common Mistakes:

• Manually encoding file content before command
• Using wrong flags like --encode
• Passing file name as literal string