-
Story
-
Resolution: Done
-
Critical
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
-
-
-
Workload Mgmt Train 30 - 1, Workload Mgmt Train 30 - 2, Workload Mgmt Train 31 - 1, Workload Mgmt Train 31 - 2, Workload Mgmt Train 32 - 1
-
Important
-
None
Value Statement
Currently when the gitops addon is restarted, it normally takes around 3 minutes to be in fully running status. It because the gitops addon controller spends most of the time to attempt to acquire leader lease.
I0714 23:05:02.254538 1 leaderelection.go:257] attempting to acquire leader lease kube-system/gitops-addon-agent-leader.open-cluster-management.io... I0714 23:07:48.167229 1 leaderelection.go:271] successfully acquired lease kube-system/gitops-addon-agent-leader.open-cluster-management.io
We will need to improve the slowness as customers need to configure the all-namespaces setting in the addonDeploymentConfig and it requires to restart the gitops addon controller quite often.
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- is depended on by
-
ACM-18207 ACM Need option to deploy to different namespaces (not only openshift-gitops) (TP)
-
- Review
-