Skip to content

PKG-1435: GitHub OIDC access for pmm-qa workflows to QA EKS clusters - #393

Open
nogueiraanderson wants to merge 2 commits into
mainfrom
PKG-1435-gha-pmm-qa-eks-oidc
Open

PKG-1435: GitHub OIDC access for pmm-qa workflows to QA EKS clusters#393
nogueiraanderson wants to merge 2 commits into
mainfrom
PKG-1435-gha-pmm-qa-eks-oidc

Conversation

@nogueiraanderson

Copy link
Copy Markdown
Collaborator

Feature

  • IAM role for GitHub Actions in the public percona/pmm-qa repo to reach the pmm-ha* QA EKS clusters via OIDC, no static AWS keys

Why

  • QA e2e runs need a kubeconfig for the PMM HA test clusters, and long-lived access keys in a public repo are not acceptable
  • Trust is StringEquals on explicit subjects via the shared github-oidc-role module, so fork PRs cannot assume the role
  • AWS-side permission is eks:DescribeCluster on pmm-ha* only. In-cluster authorization stays with the cluster-creating Jenkins job's access-entry stage

Tickets

- New iam-gha-pmm-qa-eks.tf: github-oidc-role module instantiation for repo:percona/pmm-qa (main + pull_request subjects)
- Permissions: eks:DescribeCluster on pmm-ha* clusters in us-east-2 only
- Kubernetes-side authorization stays with the cluster-creating Jenkins job via EKS access entries
@nogueiraanderson
nogueiraanderson requested a review from vorsel August 7, 2026 08:32
- Split cluster/pmm-ha* into explicit pmm-ha + pmm-ha-test-* resources
- State the collaborator trust boundary and the pull_request_target /
  workflow_run caveat with the audit state at introduction
- Correct the leak window to the 1h STS session and state cluster-admin
  reach including the persistent pmm-ha cluster
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant