External secret management integration in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this command?

You have installed External Secrets Operator in your Kubernetes cluster. You run the following command to check the status of the ExternalSecret resource named db-credentials in the default namespace:

kubectl describe externalsecret db-credentials

What output will you see regarding the secret synchronization status?

A Error: Secret not found in external provider

B Status: Synced<br>Last Sync Time: 2024-06-01T12:00:00Z

C Status: Pending<br>Last Sync Time: N/A

D kubectl: error: the server doesn't have a resource type "externalsecret"

💡 Hint

Check the status section in the describe output for ExternalSecret resources.

When External Secrets Operator successfully syncs secrets from the external provider, the status shows 'Synced' with the last sync timestamp. Errors or pending states indicate issues or waiting for sync.

❓ Configuration

intermediate

Which ExternalSecret YAML correctly references a secret from AWS Secrets Manager?

You want to create an ExternalSecret resource that fetches a secret named prod/db-password from AWS Secrets Manager and stores it in a Kubernetes secret named db-password. Which YAML snippet is correct?

A

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: db-password
spec:
  secretStoreRef:
    name: aws-secret-store
    kind: SecretStore
  target:
    name: db-password
  data:
  - secretKey: password
    remoteRef:
      key: prod/db-password
      property: password

B

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: db-password
spec:
  secretStoreRef:
    name: aws-secret-store
    kind: ClusterSecretStore
  target:
    name: db-password
  dataFrom:
  - key: prod/db-password

C

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: db-password
spec:
  refreshInterval: 1h
  secretStoreRef:
    name: aws-secret-store
    kind: SecretStore
  target:
    name: db-password
  data:
  - secretKey: password
    remoteRef:
      key: prod/db-password

D

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: db-password
spec:
  secretStoreRef:
    name: aws-secret-store
    kind: SecretStore
  target:
    name: db-password
  data:
  - secretKey: password
    remoteRef:
      key: prod/db-password
      version: latest

💡 Hint

Look for the correct use of property to specify the secret field inside AWS Secrets Manager.

AWS Secrets Manager secrets often store multiple key-value pairs. The property field specifies which key to extract. Without it, the whole secret is fetched, which may not map correctly.

❓ Troubleshoot

advanced

Why does the ExternalSecret fail to sync with this error?

You see this error in the External Secrets Operator logs:

failed to get secret from provider: AccessDeniedException: User is not authorized to perform: secretsmanager:GetSecretValue

What is the most likely cause?

A The ExternalSecret resource YAML is missing the <code>refreshInterval</code> field

B The Kubernetes service account does not have permission to read secrets in the cluster

C The AWS IAM role or user used by the External Secrets Operator lacks permission to access the secret in AWS Secrets Manager

D The secret name in ExternalSecret does not match the Kubernetes secret name

💡 Hint

Check the permissions related to AWS Secrets Manager access.

The error indicates AWS denied access to get the secret value. This usually means the IAM role or user configured for the operator lacks the necessary permissions.

🔀 Workflow

advanced

What is the correct order of steps to integrate External Secrets Operator with HashiCorp Vault?

Arrange the steps in the correct order to set up External Secrets Operator to fetch secrets from HashiCorp Vault.

A 2,4,1,3

B 4,2,1,3

C 2,1,4,3

D 4,1,2,3

💡 Hint

Think about deploying the operator first, then setting Vault permissions, then configuring Kubernetes resources.

First, deploy the operator to manage ExternalSecrets. Then configure Vault policies and tokens so the operator can authenticate. Next, create the SecretStore resource with Vault details. Finally, create ExternalSecret resources to fetch secrets.

✅ Best Practice

expert

Which practice is best for securely managing external secret access in Kubernetes?

You want to ensure the External Secrets Operator accesses external secrets securely and with least privilege. Which practice is best?

A Use a single AWS IAM user with full Secrets Manager access for all namespaces and workloads.

B Disable authentication in External Secrets Operator to simplify access.

C Store AWS credentials as plain text in Kubernetes secrets and mount them to pods.

D Create separate IAM roles with minimal permissions per namespace and use Kubernetes service account annotations for role assumption.

💡 Hint

Consider the principle of least privilege and Kubernetes-native authentication methods.

Using separate IAM roles with minimal permissions per namespace and linking them to Kubernetes service accounts via annotations follows best security practices. It limits blast radius and avoids credential exposure.