(aws-eks): integration tests can't be deployed

[pahud]

Describe the bug

Integ tests in aws-eks using hashicorp/http-echo as the k8s deployment container image can't be deployed and is having the error:

Error: container has runAsNonRoot and image will run as root

This is because hashicorp/http-echo#11 and the deployment should run as 1005 described here:

https://github.com/hashicorp/http-echo/blob/672da300fbd66957bb6037e8d0369632752d1456/docker/alpine/Dockerfile#L15

Similarly, integ.eks-service-account-sdk-call can't be deployed because it's run as non-root and should be defined in the security-context of the pod as well.

Expected Behavior

integ tests integ.alb-controller.ts and integ.eks-service-account-sdk-call should be deployed

Current Behavior

integ.alb-controller.ts and integ.eks-service-account-sdk-call.ts can't be deployed

Reproduction Steps

just deploy the integ.alb-controller.ts and integ.eks-service-account-sdk-call.ts as described in the doc.

Possible Solution

define the non-user in the securityContext. i.e.

    const ingress = new kplus.Deployment(chart, 'Deployment', {
      containers: [{ 
        image: 'hashicorp/http-echo',
        args: ['-text', 'hello'],
        port: 5678,
        securityContext: {
          user: 1005,
        },
      }],
    })

Additional Information/Context

No response

CDK CLI Version

2.66.0

Framework Version

No response

Node.js Version

v16.17.0

OS

Linux

Language

Typescript

Language Version

No response

Other information

No response

[pahud]

PR underway.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.