Pause EKS-A OIDC, AWS IAM, GitOps resources reconcile during upgrade
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
During upgrade, we add `paused` annotation to the EKS-A resources to disable EKS-A cluster controller reconcile for these resources. We also add `kustomize.toolkit.fluxcd.io/reconcile` to disable Flux reconcile for the same resources.
Currently only cluster, provider datacenter and provider machine configs are properly "paused". https://github.com/aws/eks-anywhere/blob/main/pkg/clustermanager/cluster_manager.go#L980
We need to potentially apply the annotation to all the other EKS-A resources:
- FluxConfig
- OIDC
- AWS IAM
- ...
https://github.com/aws/eks-anywhere/pull/3108#discussion_r953002026
**Why is this needed**:
Contributor guide
Research direction
Start with pkg/clustermanager/cluster_manager.go around line 980 and the discussion in pull request 3108. Trace how upgrade pauses cluster, provider datacenter, and provider machine configs, then identify the corresponding FluxConfig, OIDC, and AWS IAM resources that need both reconcile annotations. Done means those resources remain unreconciled throughout an upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100