Creating Secrets in Kubernetes - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a generic secret named mysecret with a literal key-value pair.

Kubernetes

kubectl create secret generic mysecret --from-literal=[1]

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

Afile=secret.txt

Bpassword

Cusername=admin

Dtype=opaque

Attempts:

3 left

💡 Hint

Common Mistakes

Providing only a key without a value.

Using a file name instead of a key=value pair.

The --from-literal option requires a key=value pair, such as username=admin.

2fill in blank

medium

Complete the command to create a secret from a file named config.json.

Kubernetes

kubectl create secret generic config-secret --from-file=[1]

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

Aconfig.yaml

Bconfig.json

Csecret.txt

Ddata.txt

Attempts:

3 left

💡 Hint

Common Mistakes

Using a file name that does not exist.

Confusing file extensions.

The --from-file option expects the exact file name to include in the secret.

3fill in blank

hard

Fix the error in the command to create a secret named db-secret with a literal password.

Kubernetes

kubectl create secret generic db-secret --from-literal=[1]

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

Apassword=12345

Bpassword

C12345

Dpass=12345

Attempts:

3 left

💡 Hint

Common Mistakes

Providing only the key or only the value.

Using an incorrect key name.

The --from-literal option requires a key=value format, so password=12345 is correct.

4fill in blank

hard

Fill both blanks to create a secret named api-secret from a file and specify the secret type as kubernetes.io/basic-auth.

Kubernetes

kubectl create secret generic api-secret --from-file=[1] --type=[2]

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

Aauth.txt

Bopaque

Ckubernetes.io/basic-auth

Dconfig.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong file name.

Setting the secret type incorrectly.

The file auth.txt is used with --from-file, and the secret type is set with --type=kubernetes.io/basic-auth.

5fill in blank

hard

Fill all three blanks to create a secret named token-secret from a literal token, specify the namespace dev, and set the secret type to Opaque.

Kubernetes

kubectl create secret generic token-secret --from-literal=[1] --namespace=[2] --type=[3]

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

Atoken=abc123

Bdev

COpaque

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the namespace option.

Using the wrong secret type.

Providing only the token value without a key.

The literal token is token=abc123, the namespace is dev, and the secret type is Opaque.

Practice

1. What is the main purpose of creating a Secret in Kubernetes?

easy

A. To store sensitive information like passwords and tokens securely

B. To create a backup of your application data

C. To increase the number of pods in a deployment

D. To monitor the health of your cluster nodes

Solution

1. Step 1: Understand what Secrets are for

   Secrets in Kubernetes are designed to hold sensitive data such as passwords, tokens, or keys safely.

2. Step 2: Compare options with the purpose

   Only To store sensitive information like passwords and tokens securely describes storing sensitive info securely, which matches the purpose of Secrets.

3. Final Answer:

   To store sensitive information like passwords and tokens securely -> Option A

4. Quick Check:

   Secrets store sensitive info = B [OK]

Hint: Secrets = safe storage for sensitive data [OK]

Common Mistakes:

• Confusing Secrets with backups
• Thinking Secrets manage pods or nodes
• Assuming Secrets are for monitoring

2. Which of the following is the correct command to create a generic secret named mysecret with a literal key-value pair username=admin?

easy

A. kubectl create secret generic mysecret --from-literal=username=admin

B. kubectl secret create generic mysecret --literal=username=admin

C. kubectl create secret mysecret --literal username=admin

D. kubectl create secret generic mysecret username=admin

Solution

1. Step 1: Recall the correct syntax for creating a generic secret

   The correct command uses kubectl create secret generic [name] --from-literal=key=value.

2. Step 2: Match the options with the correct syntax

   Only kubectl create secret generic mysecret --from-literal=username=admin matches the exact syntax with correct flags and order.

3. Final Answer:

   kubectl create secret generic mysecret --from-literal=username=admin -> Option A

4. Quick Check:

   Correct syntax uses --from-literal=key=value = D [OK]

Hint: Use --from-literal=key=value with create secret generic [OK]

Common Mistakes:

• Using wrong flag names like --literal
• Omitting 'generic' keyword
• Incorrect order of arguments

3. What will be the output of the command kubectl get secret mysecret -o yaml after creating a secret with kubectl create secret generic mysecret --from-literal=password=pass123?

medium

A. The secret will not appear in the output

B. The password will be shown in plain text under data field

C. The password will be base64 encoded under data field

D. An error will occur because secrets cannot be viewed

Solution

1. Step 1: Understand how Kubernetes stores secret data

   Kubernetes stores secret values base64 encoded in the data field when viewed in YAML or JSON.

2. Step 2: Analyze the command output

   The command shows the secret in YAML format with the password base64 encoded, not plain text.

3. Final Answer:

   The password will be base64 encoded under data field -> Option C

4. Quick Check:

   Secrets data is base64 encoded = A [OK]

Hint: Secrets data shown base64 encoded, not plain text [OK]

Common Mistakes:

• Expecting plain text output
• Thinking secrets are hidden completely
• Assuming error when viewing secrets

4. You tried to create a secret with the command kubectl create secret generic mysecret --from-literal password pass123 but got an error. What is the likely cause?

medium

A. You need to add --type=generic flag explicitly

B. Secret name 'mysecret' is invalid

C. The password value is too short

D. Missing '=' sign between key and value in --from-literal

Solution

1. Step 1: Check the syntax of --from-literal flag

   The correct syntax requires an '=' sign between key and value, like --from-literal=key=value.

2. Step 2: Identify the error in the command

   The command uses a space instead of '=', causing a syntax error.

3. Final Answer:

   Missing '=' sign between key and value in --from-literal -> Option D

4. Quick Check:

   --from-literal needs '=' between key and value = A [OK]

Hint: Use '=' in --from-literal key=value, no spaces [OK]

Common Mistakes:

• Using space instead of '=' in --from-literal
• Assuming secret name rules cause error
• Thinking --type=generic is mandatory

5. You want to create a secret from a file named config.txt and also add a literal key env=prod. Which command correctly does this?

hard

A. kubectl create secret generic appsecret --from-file=config.txt env=prod

B. kubectl create secret generic appsecret --from-file=config.txt --from-literal=env=prod

C. kubectl create secret generic appsecret --from-literal=config.txt --from-literal=env=prod

D. kubectl create secret generic appsecret --from-file=config.txt --literal=env=prod

Solution

1. Step 1: Understand how to add file and literal to secret

   Use --from-file=filename to add file content and --from-literal=key=value for literals.

2. Step 2: Check options for correct syntax

   kubectl create secret generic appsecret --from-file=config.txt --from-literal=env=prod correctly uses both flags with proper syntax; others misuse flags or omit '='.

3. Final Answer:

   kubectl create secret generic appsecret --from-file=config.txt --from-literal=env=prod -> Option B

4. Quick Check:

   Use --from-file and --from-literal together correctly = C [OK]

Hint: Combine --from-file and --from-literal with '=' correctly [OK]

Common Mistakes:

• Using --from-literal for file instead of --from-file
• Omitting '=' in --from-literal
• Mixing flags incorrectly