Postagens

Mostrando postagens de dezembro, 2023

error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"

Got this error after installing a EKS cluster on AWS. I already had the aws cli installed using apt on ubuntu 22. After some search, the solution that solved was installing manually the aws cli.  curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" unzip awscliv2.zip sudo ./aws/install

Kubernetes - apiserver advertise address

On vagrant I built a kubernetes cluster with ansible and noticed that the kubeadm init was not using the private interface created on vagrant. So to avoid that, ti changed the command with the parameter --apiserver-advertise-address to use the private ip of the master.  - name : Start the cluster   shell : kubeadm init --apiserver-advertise-address={{ inventory_hostname }} --pod-network-cidr 10.50.0.0/16 --cri-socket /run/containerd/containerd.sock   register : kubeadm_init_output   when : not file_exists.stat.exists

Kubernetes - memcache.go:265] couldn't get current server API group list

Facing the error below on Ubuntu 22.04 on vagrant. Error showing after halting and powering up the vms again. Checking the journal logs and tested was just a matter to disable swap on ubuntu. root@master:/etc/kubernetes# kubectl get pods E1212 12:55:53.292062    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused E1212 12:55:53.292515    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused E1212 12:55:53.294534    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused E1212 12:55:53.295070    1865 memcache.go:265] couldn't get current server API group list: Get "https://1