Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🌱 Add TargetNamespace to cluster-template.yaml ControlPlaneEndpoint #135

Closed
christopherhein opened this issue Jun 15, 2021 · 0 comments · Fixed by #136
Closed

🌱 Add TargetNamespace to cluster-template.yaml ControlPlaneEndpoint #135

christopherhein opened this issue Jun 15, 2021 · 0 comments · Fixed by #136
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@christopherhein
Copy link
Member

User Story

As an operator I would like to get a cluster which works for vc-syncer across namespaces, so that I can sync workloads with vc-syncer.

Detailed Description

Right now with CAPN it doesn't add the namespace to the ControlPlaneEndpoint.Host which works fine in-cluster in the same namespace but isn't a valid FQDN in the certs for cross namespace traffic, al la the vc-syncer. To update this we need to add ${TARGET_NAMESPACE} from the clusterctl privder guide to the ControlPlaneEndpoint.Host for auto generation.

    host: "${CLUSTER_NAME}-apiserver.${TARGET_NAMESPACE}"

Anything else you would like to add:

Ref: #81

/kind feature
/milestone v0.1.x

@k8s-ci-robot k8s-ci-robot added this to the v0.1.x milestone Jun 15, 2021
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants