Olawale Olaleye

@croachrose do you mind sharing a little more details about your EKS environment? Also what does the IAM policy used by the role AWSALBIngressController_3f2bb898eae5ea79ebdb9cb3514f5ec6 looks like? Look for block like...

@croachrose from a more recent alb controller, e.g. v2.4.1 with EKS 1.22, I see tags as part of the request so that explains it. I reproduced this in the environments...

This error could occur when the node has reached the maximum pods it can schedule due to the maximum pods available for the node instance type and you try to...

EXPERIENCING THE SAME ISSUE

Attempted the same steps from another EC2 instance and didn't encounter the issue

temporary workaround was to go ahead with shrinking the image. Not the best though. ``` COPY --from=full_image / / ```

In btw, Amazon EKS Hybrid Nodes have etcd already in the managed control plane on AWS ``` k get po -n openebs | egrep -v "Running" NAME READY STATUS RESTARTS...

``` % kubectl -n openebs get svc openebs-etcd -o yaml apiVersion: v1 kind: Service metadata: annotations: meta.helm.sh/release-name: openebs meta.helm.sh/release-namespace: openebs creationTimestamp: "2025-03-21T16:31:40Z" labels: app.kubernetes.io/instance: openebs app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: etcd helm.sh/chart:...

``` % kubectl describe -n openebs svc openebs-etcd-headless Name: openebs-etcd-headless Namespace: openebs Labels: app.kubernetes.io/instance=openebs app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=etcd helm.sh/chart=etcd-8.6.0 Annotations: meta.helm.sh/release-name: openebs meta.helm.sh/release-namespace: openebs service.alpha.kubernetes.io/tolerate-unready-endpoints: true Selector: app.kubernetes.io/instance=openebs,app.kubernetes.io/name=etcd Type: ClusterIP IP Family...

``` % kg sts -n openebs NAME READY AGE openebs-etcd 0/3 62d openebs-loki 1/1 62d openebs-nats 3/3 62d ``` These are the pods ``` NAME READY STATUS RESTARTS AGE openebs-etcd-0...