Add GHA to Staging and setup EKS Access Entry for AWSAdministratorAccess PS. #129
Conversation
… container and vice versa
…to backend when using the recommended /_aws/execute-api endpoint
Various versioning cleanup and adds Github Actions do plan/deploy at least the Dev branch, plus adds EKS Access Entries for SSO admin access to the cluster.
Enable GHA for the staging branch.
|
@gtempus Could you take a look before merging to Staging? This does a number of things, but nothing too crazy: basically setups Github Actions to actually run TF Plan on PR, and TF Apply on merge, and the actual TF changes involve synchronizing the vars with actually deployed infra, while adding access to the K8s cluster using a new method. Note that with this change, merging will actually apply the TF, you can review the plan output here: https://github.com/resource-watch/api-infrastructure/actions/runs/18955004418/job/54129470211?pr=129. |
|
(I forgot to add, this was all prep to get things in a better state for updating the K8s cluster version, which is the goal) |
gtempus
left a comment
gtempus
left a comment
There was a problem hiding this comment.
Let's give it a shot, @tanderegg. Thanks for pointing me to the plan.
solomon-negusse
left a comment
solomon-negusse
left a comment
There was a problem hiding this comment.
Looks good to me @tanderegg. The eks API stuff is new to me, so just skimmed thru that for familiarity.
No description provided.