Support pki file?

[AGou-ops]

This kind of kubeconfig is not recognized by headlamp.

[joaquimrocha]

Hi @AGou-ops . Can you give us more info about your setup? Mac/Linux/Windows/In-Cluster? If Linux, what Headlamp build have you installed? What is the Headlamp version you are using?

Thanks in advance.

[AGou-ops]

@joaquimrocha yes.

• MacOS 14.6.1 m1 pro chip.
• Headlamp 0.25.1

If I replace the pki file with base64 data, the cluster will connect properly.

Edit:

~/.kube/config

apiVersion: v1
clusters:
- cluster:
    certificate-authority: pki/ca.pem
    server: https://xxx.xxx.xxx.xxx:6443
  name: kubernetes80
contexts:
- context:
    cluster: kubernetes80
    user: kubernetes-admin1
  name: kubernetes-80
current-context: kubernetes-80
kind: Config
preferences: {}
users:
- name: kubernetes-admin1
  user:
    client-certificate: pki/admin.pem
    client-key: pki/admin.key

[joaquimrocha]

cc/ @knrt10

[knrt10]

Let me check. Thank you for reporting

[knrt10]

@AGou-ops Do you have access to backend? If so, can you paste logs when you try to use the file directly. I am not sure but I think the path pki/admin.pem might be the issue. Headlamp might not be able to load the path. Instead of just pki/admin.pem. Can you try changing it to absolute path from your home directory. Something like /Users/username/pathtopkifile? Please try and let me know. Thanks

[AGou-ops]

@knrt10 yes. The path and access permissions are both ok, because I can access the cluster normally via kubectl command.

`~/.kube/config`

❯ k config view
apiVersion: v1
clusters:
- cluster:
    certificate-authority: pki/ca.pem
    server: https://xxx.xxx.xxx.xxx:16443
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    user: kubernetes-admin
  name: kubernetes-admin@kubernetes
current-context: kubernetes-admin@kubernetes
kind: Config
preferences: {}
users:
- name: kubernetes-admin
  user:
    client-certificate: pki/admin.pem
    client-key: pki/admin.key
❯ k cluster-info
Kubernetes control plane is running at https://xxx.xxx.xxx.xxx:16443
CoreDNS is running at https://xxx.xxx.xxx.xxx:16443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

After changing to an absolute path, it works. So, this relative path config is not supported now?

Thanks.