Why Secrets manage sensitive data in Kubernetes - Quick Recap

Recall & Review

beginner

What is a Kubernetes Secret?

A Kubernetes Secret is a special object that stores sensitive data like passwords, tokens, or keys securely, separate from application code.

beginner

Why should sensitive data be stored in Secrets instead of ConfigMaps?

Secrets are designed to store sensitive data securely with base64 encoding and can be encrypted at rest, while ConfigMaps are for non-sensitive configuration and are stored as plain text.

intermediate

How do Secrets help in managing sensitive data in Kubernetes?

Secrets keep sensitive data separate from application code and configuration, reduce the risk of accidental exposure, and allow controlled access to only authorized pods or users.

intermediate

What is one way Kubernetes protects Secrets data?

Kubernetes can encrypt Secrets data at rest in etcd, so even if someone accesses the storage, the sensitive data remains protected.

beginner

How can applications access Secrets in Kubernetes?

Applications can access Secrets by mounting them as files inside containers or by exposing them as environment variables, keeping sensitive data out of the application code.

What is the main purpose of Kubernetes Secrets?

A To manage network policies

B To store application logs

C To store sensitive data securely

D To deploy applications

Kubernetes Secrets are specifically designed to store sensitive data like passwords and tokens securely.

Which of the following is true about Kubernetes Secrets?

A They are stored as plain text in etcd by default

B They cannot be encrypted at rest

C They are used to store non-sensitive configuration

D They help separate sensitive data from application code

Secrets help keep sensitive data separate from application code to improve security.

How can Kubernetes Secrets be accessed by pods?

A Only through network requests

B By mounting as files or environment variables

C By embedding directly in application code

D By storing in ConfigMaps

Pods can access Secrets by mounting them as files or exposing them as environment variables.

Why is it risky to store sensitive data in ConfigMaps?

A ConfigMaps store data as plain text

B ConfigMaps cannot be used by pods

C ConfigMaps are encrypted by default

D ConfigMaps automatically expire

ConfigMaps store data as plain text, which is not secure for sensitive information.

What feature can Kubernetes use to protect Secrets data at rest?

A Encryption of Secrets in etcd

B Role-based access control (RBAC)

C Pod security policies

D Network segmentation

Kubernetes can encrypt Secrets stored in etcd to protect sensitive data at rest.

Explain why Kubernetes uses Secrets to manage sensitive data instead of storing it directly in application code.

Think about security and access control benefits.

Describe two ways applications can access Secrets in Kubernetes and why this is helpful.

Consider how containers get sensitive info safely.