#Configurations

The Configurations section covers namespace-scoped configuration resources that workloads consume at runtime.

Use these pages when you need to create, review, update, or delete configuration data for applications, workloads, or cluster-side namespace resources.

#Choose the correct entry view

ConfigMaps and Secrets can be managed from different views in the new web console, but the resource itself still belongs to a concrete cluster and namespace.

• Use the Applications view when you are managing configuration for workloads in the current project scope.
• Use the Clusters view when you start from a concrete cluster and manage configuration as part of cluster-side namespace operations.

In both views, workloads can only reference ConfigMaps or Secrets from the same namespace.

#Non-sensitive configuration

Use ConfigMaps for runtime configuration that does not contain credentials or private material:

• Configuring ConfigMap

#Sensitive configuration

Use Secrets for credentials, tokens, keys, certificates, or image-pull authentication:

• Configuring Secrets

#Operational reminder

When you update or delete ConfigMaps or Secrets, review the downstream workload impact. Depending on how workloads consume the data, the change can require Pod recreation, rollout, restart, or image-pull revalidation before it fully takes effect.

Place operational guidance in the page where the action happens:

• creation and entry-scope checks belong beside the create steps
• workload-consumption checks belong beside update and delete behavior
• cluster-view differences belong next to the same capability rather than in a single appendix