-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
-
Not Selected
-
-
-
Critical
-
None
Value Statement
Use the same client used by Cluster service
Definition of Done for Engineering Story Owner (Checklist)
In long-run ARO-HCP environment
- Simulate CS using Maestro gRPC client ways
- start two Maestro gRPC clients in one pods
- each gRPC client has its own source
- each gRPC client starts its own watcher
- Simulate CS worklaod
- a maniftwork that wrapped a maniftwork that contains hypershift resources
- a maniftwork that contains a ManagedCluster
- Using server-side apply strategy
- Find the real workload in CS side to testÂ
- create -> delete -> create
- create -> delete immediately
- etc
- Scale up/down Maestro server (Maestro gRPC client reconnect behavior)
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.
- relates to
-
ACM-24312 Introduce istio into e2e environment
-
- Closed
-