✨ Add kubeconfig-host-override and kubeconfig-ca-file-override flags #6
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.
Summary
Some more advanced deployment scenarios for kcp-api-syncagent may require overriding the host and CA used in the REST config for the local Kubernetes cluster.
This can be the case when an OIDC trust exists between two clusters in which one cluster should run the syncagent, but another cluster is the control plane to which objects should be synced from kcp. In those situations, we want to reuse the token discovered from the container filesystem and talk to a different server which also accepts our token.
Related issue(s)
Fixes #
Release Notes