Skip to content

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

Open

Description

@Hanabi9248

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 guide Chinese guide Operator 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 generator Kubectl 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.

Generated English command Generated Chinese command

Activity

  1. Hanabi9248 commented on Nov 18, 2026

    @Hanabi9248
    Author

    /assign

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions