#kubernetes - January 2022

January 2022
Mr.Devops
Mr.Devopsalmost 5 years ago
hi there - does anyone know if there’s an approved terraform provider for creating the helm operator?
Jakub
Jakubalmost 5 years ago
hi there!

anyone have experienced with EKS ? I have the problem with some nodes, on two nodes, in each 3 minutes, node is reporting that is unhealthy because of the PLEG.
I don’t know if it can help in troubleshooting but I have problem with executing command “df -h” only on those nodes - it stuck. it looks like maybe some EFS has not been mounted properly or sth like that
Franklin Lee
Franklin Leealmost 5 years ago
Will a CKA without professional experience still be able to get a job?
Mr.Devops
Mr.Devopsalmost 5 years ago
has anyone run into this error in EKS Cannot enforce AppArmor: AppArmor is not enabled on the host we’re using aws linux 2 ami. I’ve read that appArmor (by default) is supported in ubuntu and not RHEL distribution. This is causing pods to fail with status blocked
Johan
Johanalmost 5 years ago
Hi, what kind of storage drivers do you use in EKS? The new efs-csi driver is not working for us due to chown-errors.
sheldonh
sheldonhalmost 5 years ago
CLI or Go SDK kubeconfig setup for remote cluster with K8 Service Account

Anyone willing to jump on this thread and help unblock me?
Mr.Devops
Mr.Devopsalmost 5 years ago
Hi all - wondering if anyone can assist with the following error one of our pod
Readiness probe failed: Get "<http://x.x.x.x:9999/health?ready>": dial tcp x.x.x.x:9999: connect: connection refused

Readiness probe failed: HTTP probe failed with statuscode: 503

Zachary Loeber
Zachary Loeberalmost 5 years ago
https://helmwave.github.io/ <-- docker-compose for helm charts. Maybe this one was tossed out there already. Not certain if anyone has used it yet though (seems like something that could be accomplished with artful terraform depends_on constructs too))
btai
btaialmost 5 years ago
anyone using EKS and replacing the AWS VPC CNI?
rei
reialmost 5 years ago
Currently I am having issues deploying a new cluster with the latest TF EKS module cloudposse/eks-cluster/aws:0.45.0
I am getting the following "interesting" error after the nodes are up and then tf wants to set up the auth_config.
╷
│ Error: Post "<https://jsonplaceholder.typicode.com/api/v1/namespaces/kube-system/configmaps>": x509: certificate signed by unknown authority
│ 
│   with module.eks_cluster.kubernetes_config_map.aws_auth_ignore_changes[0],
│   on .terraform/modules/eks_cluster/auth.tf line 115, in resource "kubernetes_config_map" "aws_auth_ignore_changes":
│  115: resource "kubernetes_config_map" "aws_auth_ignore_changes" {
│ 

Any idea or hint what's wrong. Google or StackOverflow does not help here...