Skip to content

docs: keep v5.6 init SQL updates in the cluster namespace - #441

Draft
Hanabi9248 wants to merge 1 commit into
IvorySQL:v5.6from
Hanabi9248:codex/operator-init-configmap-namespace
Draft

Hanabi9248 wants to merge 1 commit into
IvorySQL:v5.6from
Hanabi9248:codex/operator-init-configmap-namespace

Conversation

@Hanabi9248

Copy link
Copy Markdown

When the current kubectl context uses another namespace, the initialization SQL update pipeline applies hippo-init-sql there. Add -n ivory-operator to the apply command in both guides, matching the worked cluster and its earlier ConfigMap creation command.

The namespace behavior was checked against the release controller and kubectl source. Both complete pages render in secure HTML5 mode, with that one command change as the only difference from each baseline HTML document. Git application and whitespace checks pass. No live Kubernetes update was performed.

Fixes #438

@github-actions

Copy link
Copy Markdown

🚀 IvorySQL-Docs Preview Ready

This branch was successfully deployed

1 active deployment
pull request — b5c04f05 Deployed Nov 18, 2026 by github-actions[bot]
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.

v5.6 Operator guide omits the namespace when updating the init SQL ConfigMap

1 participant