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

Allow overriding secretKey for kubeadm kubeconfig #408

Merged
merged 1 commit into from
Apr 18, 2024

Commits on Mar 5, 2024

  1. Allow overriding secretKey for kubeadm kubeconfig

    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 committed Mar 5, 2024
    Configuration menu
    Copy the full SHA
    294d70a View commit details
    Browse the repository at this point in the history