View and edit an app's ConfigMaps

应用配置 (Application config) reads the workloads of the selected environment and application and shows what each container really receives: environment variables, envFrom sources, volume mounts, and the contents of every ConfigMap referenced through env, envFrom, volumes or projected volumes. Init containers are included.

You can edit the text of a ConfigMap and 保存到集群 (Save to cluster). The save checks the ConfigMap’s UID and resourceVersion, so it never overwrites a newer version in the cluster.

What you see

  • ConfigMaps are found through the workload’s references, so they don’t need the app’s name or labels.
  • Text is shown per key with line numbers and syntax highlighting for YAML, JSON, TOML, Nginx and Properties/INI.
  • Secrets appear only as references. Their contents are never read.
  • Permission errors and read failures are shown in place, not as an empty page.

Edit a ConfigMap

  1. Open 应用配置 and find the ConfigMap.
  2. Click 编辑配置 (Edit config).
  3. Change the text. YAML, JSON and TOML are syntax-checked before saving.
  4. Click 保存到集群, or cancel.

If the ConfigMap was replaced or changed in the cluster since you loaded it, the save is rejected, your edits are kept, and you’re asked to refresh. Unedited keys, binary data and metadata are left exactly as they were. Immutable ConfigMaps and binary keys are read-only.

Unsaved drafts are kept in memory per connection, context, namespace and ConfigMap while you switch pages, applications or environments. They are lost when you quit or reload the app.

After saving

Saving doesn’t restart anything. Environment variables and subPath mounts need a restart — use Restart. Ordinary volume mounts are updated by the kubelet; whether the app picks up the change depends on how it reloads configuration.

Host Nginx config

If an application in project.yaml has an nginxPath such as /etc/nginx/conf.d/svc-api.conf, you can read and edit that file on the host from Nginx 配置 (Nginx config) or 应用配置.

  • The environment’s connection must use a saved SSH tunnel. The host needs Python 3, Nginx and systemd, and the SSH user needs permission to write the file and reload Nginx.
  • Only regular .conf files directly under /etc/nginx/conf.d/ are allowed. Symlinks are rejected.
  • Saving checks the file’s digest, takes a lock, replaces the file atomically, then runs nginx -t and systemctl reload nginx. If either fails, the original file is restored.
  • The result is written to the release records without the file’s contents.

Permissions

Reading ConfigMaps needs get on configmaps; saving needs get and update. See RBAC permissions.

Frequently asked questions

Can DevOpsPad show the values of my Secrets?

No. The Application config page shows where a Secret is referenced, but it never reads Secret contents.

Does saving a ConfigMap restart my app?

No. Environment variables and subPath mounts only change after a restart. Regular volume mounts update in place, and whether the app notices depends on how it reloads config.