ConfigMaps and Secrets in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a ConfigMap in microservices architecture?

A ConfigMap is a way to store non-sensitive configuration data separately from application code, allowing microservices to access configuration without rebuilding images.

beginner

How do Secrets differ from ConfigMaps?

Secrets store sensitive data like passwords or tokens in an encrypted or base64-encoded form, while ConfigMaps store non-sensitive configuration data in plain text.

intermediate

Why should sensitive data be stored in Secrets rather than ConfigMaps?

Storing sensitive data in Secrets helps protect it by restricting access and encrypting it, reducing the risk of exposure compared to ConfigMaps which are not encrypted.

intermediate

How can microservices access ConfigMaps and Secrets at runtime?

Microservices can access ConfigMaps and Secrets by mounting them as files in containers or by injecting them as environment variables during container startup.

advanced

What is a common best practice when updating ConfigMaps or Secrets in a running microservices environment?

A common best practice is to update ConfigMaps or Secrets carefully and trigger rolling restarts of microservices to reload the new configuration without downtime.

Which of the following is true about ConfigMaps?

A They cannot be updated without rebuilding the application.

B They store sensitive data encrypted by default.

C They store non-sensitive configuration data.

D They are only used for secrets like passwords.

ConfigMaps store non-sensitive configuration data separately from application code.

What is the main purpose of Secrets in microservices?

A To store container images.

B To store non-sensitive configuration.

C To store application logs.

D To store sensitive information securely.

Secrets are designed to store sensitive information like passwords and tokens securely.

How can microservices consume Secrets at runtime?

A By mounting Secrets as files or injecting as environment variables.

B By storing them in public repositories.

C By embedding them directly in the source code.

D By hardcoding them in container images.

Secrets can be accessed by mounting them as files or injecting them as environment variables.

Which practice helps safely update ConfigMaps or Secrets without downtime?

A Triggering rolling restarts of microservices.

B Ignoring updates until next deployment.

C Rebuilding container images immediately.

D Deleting and recreating all microservices.

Rolling restarts allow microservices to reload updated ConfigMaps or Secrets without downtime.

Why should sensitive data not be stored in ConfigMaps?

A Because ConfigMaps are encrypted by default.

B Because ConfigMaps are stored in plain text and less secure.

C Because ConfigMaps cannot be updated.

D Because ConfigMaps are only for logs.

ConfigMaps store data in plain text and do not provide encryption or strict access controls.

Explain the difference between ConfigMaps and Secrets in microservices and why each is important.

Think about security and configuration management.

Describe how you would update a Secret in a running microservices environment without causing downtime.

Consider safe update and reload strategies.