You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v5.6 Operator guide omits the namespace when updating the init SQL ConfigMap #438
The English and Chinese v5.6 Operator guides introduce hippo-init-sql in namespace ivory-operator. Later, the suggested pipeline for applying an updated SQL file uses an unqualified kubectl apply -f -. Kubectl’s active context namespace then determines where the update goes. The Operator looks up hippo-init-sql in the namespace of the IvoryCluster. English guideChinese guideOperator ConfigMap lookup
For example, consider the guide’s hippo cluster in ivory-operator while the active kubectl context uses the default namespace. With permission to apply there, the pipeline creates or updates default/hippo-init-sql and leaves the ConfigMap referenced by the cluster unchanged. This follows from the generator emitting no namespace and the apply command taking the active context namespace for resources without one. Kubectl ConfigMap generatorKubectl apply namespace handling
Please add -n ivory-operator to the kubectl apply part of the pipeline in both guides, using the same namespace as the preceding creation example. The two corrected full pages render with only that command change. The namespace behavior was verified from source.
Activity
Hanabi9248 commentedon Nov 18, 2026
/assign