Engineer k8s group manual

[ni9hty]

cluster.yaml changes:

• Adds a new EKSAccessEntryManualAuth resource in an {{- else }} block
• Creates an access entry for a manual IAM role (arn:aws:iam::${AWS::AccountId}:role/Manual)
• Assigns the zalando:engineer Kubernetes group to this role

poweruser-binding.yaml changes:

• Adds the zalando:engineer group as a subject in the existing RoleBinding/ClusterRoleBinding
• This grants the same permissions that okta:common/engineer has to the new zalando:engineer group

[tcondeixa]

I think we are missing 2 other places to add this new group
https://github.com/search?q=repo%3Azalando-incubator%2Fkubernetes-on-aws%20common%2Fengineer&type=code

[zalando-robot]

Deployment Checklist

This change falls under the deployment policy.

💁 Since Nov 10th, we are in the RED deployment zone. This means all changes released to production must adhere to the following requirements:

• Detailed release notes are provided in this PR’s description.
• Thorough load-testing has been performed, and is documented in the description/comment.
• Technical review: Principal Engineers or Tech Leads have green-lit your changes, and the reviewer is named in the description/comments.
• You can enable/disable the change via feature toggles, and have confirmed these toggles work as expected.
• Application Owner (Director+) approval is given about the PR, and the approver is named in the description/comments.

👉 Regardless of which boxes you click in this comment, merge/deployment will not be blocked.
Reports about deployment policy adherence will be circulated daily for Cyber-Week-relevant applications.

[ni9hty]

👍

[tcondeixa]

👍