Change Configuration and Secrets

The appliance’s Git repository stores the configuration it should run. Management task pages commit supported settings to that repository. Advanced operators can inspect and change it through Gitea.

Use the dedicated page for ordinary ERS, HSM, metrics, log forwarding and backup-policy tasks. Read GitOps repository ownership before editing files directly.

Understand when a Change takes Effect

  1. An accepted edit creates a Git commit.

  2. During an active cluster access lease, Management captures committed configuration, publishes it to the configured appliance registries and selects it for reconciliation.

  3. Flux applies the selected configuration and retries as needed.

  4. Verify that the affected service works for its clients.

Publication success does not prove that workloads are healthy. If a configuration causes failures, correct it with a new commit. Ordinary publication has no manual Retry or Republish control and performs no automatic rollback.

If publication fails, Management shows a failure notice with a link to the commit in Gitea. Management automatically retries temporary communication failures while cluster access is available. Invalid configuration requires a correction committed to main. The failure notice clears after a subsequent successful publication, not merely after a new commit exists.

Edit a Secret

Use a Management administrator account and keep cluster access active. Configuration may be read-only during an update.

  1. Open Appliance > Secrets.

  2. Filter by namespace or search for the required secret. Confirm its name, file path and document before opening it.

  3. Reveal only the value you need to inspect or edit. The page also offers actions to copy values and to add or remove keys.

  4. Change the intended values and select Save changes.

  5. If the page reports repository conflicts, resolve each conflicting field before saving. Review the current repository value against your intended change.

  6. Record the resulting commit identifier and verify the affected service after publication and reconciliation.

Secret edits are committed together. The editor fetches plaintext for requested fields and clears sensitive page state when cluster access changes, after a successful save, or when leaving the page. Copied values may remain in your workstation’s clipboard or clipboard history. Avoid pasting credentials into issue reports, screenshots or commit messages.

Registry and customer-monitoring settings forms do not show saved credentials again. Authorized users can reveal repository secret values in the secrets editor.

Work through Gitea

Open Gitea from the Management header and inspect the appliance repository’s main branch. Review the owning configuration files and recent commits before editing. Keep customer settings in their designated override locations, preserve encryption for secret files, and avoid live workload edits that conflict with Git.

Gitea can remain reachable without a cluster connection. Publication requires the active appliance artifact bundle. After reconnecting, check publication and runtime health to confirm that an earlier commit took effect.

For a failed change, correct the responsible configuration through Git and verify the resulting service. Reverting configuration cannot restore deleted application data. Use recovery for data restoration and troubleshooting for publication or reconciliation failures.