kubeletctl: tls: failed to find any PEM data in certificate input

tls: failed to find any PEM data in certificate input

this is all I get back… my KUBECONFIG is properly set, I daily work with it switching between several configurations

seems the kubeletctl is not handling this yaml section properly

clusters:
- cluster:
    certificate-authority-data: xyz

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 17 (10 by maintainers)

Most upvoted comments

getting the same issue

export KUBECONFIG=~/.kube/config

[] Using KUBECONFIG environment variable [] You can ignore it by modifying the KUBECONFIG environment variable, file “~/.kube/config” or use the “-i” switch 2021/02/24 18:30:23 tls: failed to find any PEM data in certificate input

hxhBrofessor on Feb 24, 2021

Quick update, the problem is because we are not supporting:

- name: arn:aws:eks: TRIMMED:cluster/TRIMMED-cluster
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - --region
      - TRIMMED
      - eks
      - get-token
      - --cluster-name
      - TRIMMED-cluster
      command: aws

We are working to support the execution of aws to get the token for EKS. Btw, by using the kubiscan-sa service account it will work:

--cacert ca.crt -s <node_ip> --token eyJhbG... pods

g3rzi on Oct 26, 2022

OK, interesting. We were able to reproduce it on EKS, we are working on it, thank you.

g3rzi on Oct 20, 2022

sorry @g3rzi …I can’t recall how and if I circumvented this… I has a specific use case in which I had to be sure I had only one configuration in there and not several as I normally do, composing the env variable KUBE_CONFIG … I’ll close it, unless someone else can provide you more info (I guess they can reopen it)

thanks for the effort spent looking into it, I feel guilty I can’t provide more info

zeph on Sep 12, 2022