Conversation
The first step to deprecate and remove the backend config property. It's still the only source of truth. The description in the docs is updated to explain the current behavior and planned deprecation. If it does not match the namespace from the current kubeconfig context, show a warning instructing the user to update kubeconfig. Migration guide: * If the property is not set or set to `default` in backend config and not set or set to `default` in kubeconfig, `default` is used, no action required * If the property is set to `ns-a` in both backend config and kubeconfig, `ns-a` is used, no action required * If the property is set to `ns-a` in backend config and not set or set to `ns-b` in kubeconfig, `ns-a` is used, set namespace to `ns-a` in kubeconfig to prepare for future versions * In general, it's only safe to remove the property from backend config if it is equal to `default`, which is a default value Part-of: #3857
r4victor
approved these changes
May 7, 2026
un-def
deleted the
issue_3857_deprecate_kubernetes_backend_namespace_property
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The first step to deprecate and remove the backend config property.
It's still the only source of truth.
The description in the docs is updated to explain the current behavior and planned deprecation.
If it does not match the namespace from the current kubeconfig context, show a warning instructing the user to update kubeconfig.
Migration guide:
defaultin backend config and not set or set todefaultin kubeconfig,defaultis used, no action requiredns-ain both backend config and kubeconfig,ns-ais used, no action requiredns-ain backend config and not set or set tons-bin kubeconfig,ns-ais used, set namespace tons-ain kubeconfig to prepare for future versionsdefault, which is a default valuePart-of: #3857