I have an EKS cluster. When I deploy my container it fails to start with the following message: Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container…
strong textTill the cert-manager every pods working good as followed by aerospike docs. But while installing the operator the operator pods get crash loop backoff. Installing operator using: git clone https://github.com/aerospike/aerospike-kubernetes-operator.git git checkout 2.5.0 cd aerospike-kubernetes-operator/helm-charts helm install aerospike-kubernetes-operator ./aerospike-kubernetes-operator…
This is my eks cluster details: kubectl get all NAME READY STATUS RESTARTS AGE pod/feed-4fqdrrf-fwcc3 1/1 Running 0 64m pod/gst-7adn3njl-fg43 1/1 Running 0 71m pod/ingress-nginx-controller-f567efvef-f653dc 1/1 Running 0 9d pod/app-24dfs2d-m2fdqw 1/1 Running 0 66m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE…
When I run the command kubectl get svc from the tutorial I'm following. I get: error: You must be logged in to the server (the server has asked for the client to provide credentials). When I look at my ~/.kube/config…
while I scale down EC2 node count into zero (basically EC2 gets terminated)under each ASG of EKS cluster and scale up again , then dynamically provisioned EBS(PV) volume gets deleted , though "Delete on termination" flag is set to "No"…
I have installed the AWS Load Balancer controller on the cluster but when I create a load-balanced service it creates a network load balancer which does not work. apiVersion: v1 kind: Service metadata: name: ###### namespace: mb annotations service.beta.kubernetes.io/aws-load-balancer-ssl-cert: ########…
I have created an EKS cluster with ALB setup. I tried installing superset by following the steps provided in https://superset.apache.org/docs/installation/running-on-kubernetes/ my-values.yaml ingress: enabled: true ingressClassName: ~ annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/scheme: internet-facing alb.ingress.kubernetes.io/target-type: instance # kubernetes.io/tls-acme: "true" ## Extend timeout to…
I need to do a Target Group Binding in AWS. I am creating almost all resources using Terraform (EKS cluster, nodes, other AWS services). On top of it I am having a Kubernetes cluster of course and code written in…
I have the following situation: I want to have a Terraform configuration in which I: Create a EKS cluster Install some manifests to it using kubectl_manifest resource. So I essence, I have the following configuration: ... all the IAM stuff…
The Setup I'm building a React app that is statically served using Express. The React app is built with npm run build and the static files live in the build/ directory. Express statically serves these files with the following code…