Skip to content

[fix](operator) Reconcile management TLS and DDC credential delivery - #554

Open
Al-assad wants to merge 2 commits into
apache:masterfrom
Al-assad:fix/operator-management-credentials
Open

Al-assad wants to merge 2 commits into
apache:masterfrom
Al-assad:fix/operator-management-credentials

Conversation

@Al-assad

@Al-assad Al-assad commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Resolve management SQL transport from the FE configuration in DCR and DDC. An explicit false setting keeps the existing non-TLS connection behavior. When TLS is enabled, resolve its certificate Secret before opening the connection and propagate configuration and read errors.
  • For DDCs with an explicit authSecret, require that Secret and its password key. Preserve the optional username default and the initialization behavior when authSecret is unset.
  • For new DDCs with adminUser, populate the existing FE and compute-group environment variables with secretKeyRef. The operator maintains a DDC-owned Secret and a revision for credential updates. An explicit authSecret mount remains independent.

Upgrade and migration

The operator records the credential mode on the DDC. Existing deployments retain their current credential delivery across reconciliation and operator restarts. To opt in during a maintenance window, annotate the DDC with doris.apache.org/admin-credential-mode=secret. The operator prepares the Secret before applying workload templates. Apply the updated Operator RBAC with the release so it can create and update managed Secrets. Compute-group migration uses the existing DDC rollout permissions in the managed namespace (create pods/exec and delete pods). The disaggregated-operator.yaml installer supplies both. The adminUser field remains in the CR until the administrator migrates to authSecret.

Validation

  • Passed go test ./.... Credential regression tests also passed on Linux/amd64.
  • On K3s v1.34.12+k3s1, test workloads kept their existing Pods when upgrading from the pre-change master. DDCs created by Operator 24.2.0 retained their legacy credential mode. After explicit migration, FE and compute-group Pods received credentials through Secret references.
  • Verified DCR and DDC management connections against MySQL 8.4 with TLS required, including error handling for unavailable certificate Secrets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant