hoping someone can help who ran into this. We recently upgraded our EKS cluster from 1.23 to 1.24 and now any new node group we create would fail with Instances failed to join the kubernetes cluster, prior to the upgrade it was working fine.
we also tried creating a new cluster going to 1.24 and that works. Something with the upgrade from 1.23 to 1.24 might be causing this...
mimoabout 3 years ago
Hey Anyone has experience with Kubespray? Is it possible to deploy a kubernetes cluster with kubespray with a specific user that has sudo permissions? Rather than default root
ememabout 3 years ago
HI everyone. Is it possible to run commands in kubernetes pod without having to override the docker entrypoint.
managedkaosabout 3 years ago
FYI...
reiabout 3 years ago
Hi there, do you know on methods or tooling to assign a Pod a specific IO load (load 1/5/15) profile? We have several pod as queue workers running across the cluster, they only need about 300m CPU and 400Mi RAM, however each Pod generate a lot of IO and compute load, hence slowing everything down. Is there any method to distribute the Pods better and not just set a high resources.requests.cpu, we do not want to waste computing power with almost empty nodes. Currently is not possible to change the software to be more performant 🤷
zadkielabout 3 years ago
Hey there 🙂
zadkielabout 3 years ago(edited)
We're using velero to snapshot PVs on GKE clusters. We have classic GCP PD, Netapp CVS CSI and GCP Filestore CSI. We're trying to use the Velero GCP plugin to backup our GCP PDs and the CSI plugin for the others. However, Velero tries to backup the GCP PDs twice, once with the CSI plugin and once with GCP plugin. Do you know a way to tell Velero to skip CSI snapshots if the PV is handled by GCP plugin (native snapshots)?
