Adding permission to describe EKS cluster to member infra role #5599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A reference to the issue / Description of it
ministryofjustice/analytical-platform#2454
We are building out another catalogue candidate meant to be deployed into EKS. To minimise the dependencies on MP team, we would like to build out as much infra in the MPE repository as possible. This is a request for read-level EKS permissions to allow lookups via datasources.
How does this PR fix the problem?
This gives the member infra role read-level permissions on the EKS cluster.
How has this been tested?
The local plan works because this permission is already available in the sandbox account but the deployment via GHA fails.
Deployment Plan / Instructions
This should have no impact on PROD. This adds rather than removes or restricts permissions.
Checklist (check
x
in[ ]
of list items)