External secret management integration in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Kubernetes Secret.

Kubernetes

apiVersion: v1
kind: Secret
metadata:
  name: my-secret
stringData:
  password: [1]

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

AsecretKeyRef

BexternalSecretRef

CmyPassword123

DconfigMapRef

Attempts:

3 left

💡 Hint

Common Mistakes

Using a reference like 'secretKeyRef' instead of the actual secret value.

Confusing ConfigMap references with secrets.

The stringData field requires the actual secret value, so myPassword123 is correct here.

2fill in blank

medium

Complete the ExternalSecret manifest to specify the secret store provider.

Kubernetes

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: my-external-secret
spec:
  refreshInterval: 1h
  secretStoreRef:
    name: my-secret-store
    kind: [1]

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

AClusterSecretStore

BSecret

CConfigMap

DExternalSecret

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Secret' or 'ConfigMap' as the kind, which are not secret stores.

Confusing ExternalSecret kind with secret store kind.

The secretStoreRef.kind must be ClusterSecretStore or SecretStore. Here, ClusterSecretStore is correct.

3fill in blank

hard

Fix the error in the ExternalSecret spec to correctly map the external secret key to the Kubernetes secret key.

Kubernetes

spec:
  target:
    name: my-secret
  data:
  - secretKey: password
    remoteRef:
      key: [1]

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

Adb-password

Bpassword

Cmy-secret

DsecretKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Kubernetes secret key name instead of the external secret key.

Using generic terms like 'secretKey' instead of the actual external key.

The remoteRef.key must match the key name in the external secret store, such as db-password.

4fill in blank

hard

Fill both blanks to configure the SecretStore to use AWS Secrets Manager with the correct provider and region.

Kubernetes

spec:
  provider:
    [1]:
      region: [2]

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

Aaws

Bus-west-2

Cgcp

Deurope-west1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'gcp' as provider for AWS Secrets Manager.

Using incorrect region names.

The provider for AWS Secrets Manager is aws, and the region must be a valid AWS region like us-west-2.

5fill in blank

hard

Fill all three blanks to define an ExternalSecret that fetches a secret named 'api-key' from HashiCorp Vault with the correct path and key mapping.

Kubernetes

spec:
  secretStoreRef:
    name: vault-secret-store
    kind: SecretStore
  target:
    name: vault-api-key
  data:
  - secretKey: [1]
    remoteRef:
      key: [2]
      property: [3]

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

AapiKey

Bsecret/data/api-key

Cvalue

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up secretKey and remoteRef.key values.

Using incorrect Vault paths or property names.

The Kubernetes secret key is apiKey. The Vault path is secret/data/api-key, and the property inside the secret is value.