-
Notifications
You must be signed in to change notification settings - Fork 104
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
feat: admin kubeconfig with local service FQDN #403
Merged
Merged
Conversation
This file contains 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
Signed-off-by: Dario Tranchitella <dario@tranchitella.eu>
✅ Deploy Preview for kamaji-documentation canceled.
|
kvaps
added a commit
to aenix-io/cluster-api-control-plane-provider-kamaji
that referenced
this pull request
Feb 5, 2024
During reconciliation, the control plane provider copies the content from the secret provided by Kamaji, named <cluster>-admin-kubeconfig, into a generic Cluster API secret, <cluster>-kubeconfig, which can then be used by the bootstrap provider and other cluster components. This change introduces a new annotation, kamaji.clastix.io/kubeconfig-secret-key, for the KamajiControlPlane resource. This annotation instructs the control plane provider to read the kubeconfig from a specific key (the default one is admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: admin.svc ``` This will instruct the system to use `admin.svc` a kubeconfig with a local service FQDN (introduced by clastix/kamaji#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/cluster-api-control-plane-provider-kamaji
that referenced
this pull request
Feb 5, 2024
During reconciliation, the control plane provider copies the content from the secret provided by Kamaji, named <cluster>-admin-kubeconfig, into a generic Cluster API secret, <cluster>-kubeconfig, which can then be used by the bootstrap provider and other cluster components. This change introduces a new annotation, kamaji.clastix.io/kubeconfig-secret-key, for the KamajiControlPlane resource. This annotation instructs the control plane provider to read the kubeconfig from a specific key (the default one is admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: admin.svc ``` This will instruct the system to use `admin.svc` a kubeconfig with a local service FQDN (introduced by clastix/kamaji#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/kamaji
that referenced
this pull request
Feb 5, 2024
During reconciliation, the bootstrap provider copies the content from the secret provided by Kamaji, named `<cluster>-admin-kubeconfig` into a `cluster-info` configmap of tenant cluster, which then used by kubeadm to join nodes. This change introduces a new annotation, `kamaji.clastix.io/kubeconfig-secret-key`, for the TenantControlPlane resource. This annotation instructs kamaji to read the kubeconfig from a specific key (the default one is super-admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by clastix#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/cluster-api-control-plane-provider-kamaji
that referenced
this pull request
Feb 5, 2024
During reconciliation, the control plane provider copies the content from the secret provided by Kamaji, named <cluster>-admin-kubeconfig, into a generic Cluster API secret, <cluster>-kubeconfig, which can then be used by the bootstrap provider and other cluster components. This change introduces a new annotation, kamaji.clastix.io/kubeconfig-secret-key, for the KamajiControlPlane resource. This annotation instructs the control plane provider to read the kubeconfig from a specific key (the default one is admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by clastix/kamaji#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/kamaji
that referenced
this pull request
Feb 5, 2024
During reconciliation, the bootstrap provider copies the content from the secret provided by Kamaji, named `<cluster>-admin-kubeconfig` into a `cluster-info` configmap of tenant cluster, which then used by kubeadm to join nodes. This change introduces a new annotation, `kamaji.clastix.io/kubeconfig-secret-key`, for the TenantControlPlane resource. This annotation instructs kamaji to read the kubeconfig from a specific key (the default one is super-admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by clastix#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/kamaji
that referenced
this pull request
Mar 5, 2024
During reconciliation, the bootstrap provider copies the content from the secret provided by Kamaji, named `<cluster>-admin-kubeconfig` into a `cluster-info` configmap of tenant cluster, which then used by kubeadm to join nodes. This change introduces a new annotation, `kamaji.clastix.io/kubeconfig-secret-key`, for the TenantControlPlane resource. This annotation instructs kamaji to read the kubeconfig from a specific key (the default one is super-admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by clastix#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/kamaji
that referenced
this pull request
Mar 5, 2024
During reconciliation, the bootstrap provider copies the content from the secret provided by Kamaji, named `<cluster>-admin-kubeconfig` into a `cluster-info` configmap of tenant cluster, which then used by kubeadm to join nodes. This change introduces a new annotation, `kamaji.clastix.io/kubeconfig-secret-key`, for the TenantControlPlane resource. This annotation instructs kamaji to read the kubeconfig from a specific key (the default one is super-admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by clastix#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/kamaji
that referenced
this pull request
Mar 5, 2024
During reconciliation, the bootstrap provider copies the content from the secret provided by Kamaji, named `<cluster>-admin-kubeconfig` into a `cluster-info` configmap of tenant cluster, which then used by kubeadm to join nodes. This change introduces a new annotation, `kamaji.clastix.io/kubeconfig-secret-key`, for the TenantControlPlane resource. This annotation instructs kamaji to read the kubeconfig from a specific key (the default one is super-admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by clastix#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
prometherion
pushed a commit
that referenced
this pull request
Apr 18, 2024
During reconciliation, the bootstrap provider copies the content from the secret provided by Kamaji, named `<cluster>-admin-kubeconfig` into a `cluster-info` configmap of tenant cluster, which then used by kubeadm to join nodes. This change introduces a new annotation, `kamaji.clastix.io/kubeconfig-secret-key`, for the TenantControlPlane resource. This annotation instructs kamaji to read the kubeconfig from a specific key (the default one is super-admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: super-admin.svc ``` This will instruct the system to use `super-admin.svc` a kubeconfig with a local service FQDN (introduced by #403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/cluster-api-control-plane-provider-kamaji
that referenced
this pull request
Apr 22, 2024
During reconciliation, the control plane provider copies the content from the secret provided by Kamaji, named <cluster>-admin-kubeconfig, into a generic Cluster API secret, <cluster>-kubeconfig, which can then be used by the bootstrap provider and other cluster components. This change introduces a new annotation, kamaji.clastix.io/kubeconfig-secret-key, for the KamajiControlPlane resource. This annotation instructs the control plane provider to read the kubeconfig from a specific key (the default one is admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: admin.svc ``` This will instruct the system to use `admin.svc` a kubeconfig with a local service FQDN (introduced by clastix/kamaji#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/cluster-api-control-plane-provider-kamaji
that referenced
this pull request
Apr 22, 2024
During reconciliation, the control plane provider copies the content from the secret provided by Kamaji, named <cluster>-admin-kubeconfig, into a generic Cluster API secret, <cluster>-kubeconfig, which can then be used by the bootstrap provider and other cluster components. This change introduces a new annotation, kamaji.clastix.io/kubeconfig-secret-key, for the KamajiControlPlane resource. This annotation instructs the control plane provider to read the kubeconfig from a specific key (the default one is admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: admin.svc ``` This will instruct the system to use `admin.svc` a kubeconfig with a local service FQDN (introduced by clastix/kamaji#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
added a commit
to aenix-io/cluster-api-control-plane-provider-kamaji
that referenced
this pull request
Apr 22, 2024
During reconciliation, the control plane provider copies the content from the secret provided by Kamaji, named <cluster>-admin-kubeconfig, into a generic Cluster API secret, <cluster>-kubeconfig, which can then be used by the bootstrap provider and other cluster components. This change introduces a new annotation, kamaji.clastix.io/kubeconfig-secret-key, for the KamajiControlPlane resource. This annotation instructs the control plane provider to read the kubeconfig from a specific key (the default one is admin.conf). Example: ``` kamaji.clastix.io/kubeconfig-secret-key: admin.svc ``` This will instruct the system to use `admin.svc` a kubeconfig with a local service FQDN (introduced by clastix/kamaji#403). Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For the
admin
generated kubeconfig resources, a new key to the Secret data is added, such asadmin.conf
andadmin.svc
.The latter one is the same kubeconfig but points to the Service FQDN, which could be useful to avoid LB hops. This feature doesn't introduce breaking changes.