-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
3
-
False
-
None
-
False
-
SECFLOWOTL-93 - Promote Rollouts to GA
-
-
-
GitOps Scarlet - Sprint 2261, GitOps Scarlet - Sprint 3257X
Story (Required)
As a user, I wish to debug Rollouts when installed via OpenShift GitOps
Background/Approach (Required)
At present, within GitOps Must Gather (https://github.com/redhat-developer/gitops-must-gather/) we are capturing some Rollouts related artifacts. However, there are some that are still missing:
- The upstream Rollout controller logs kubernetes Events to the same Namespace as the Rollout CR is installed. We should capture all events from the Rollouts controller. For example:
[jgw@localhost-lan examples]$ kubectl get events
LAST SEEN TYPE REASON OBJECT MESSAGE
Created pod: rollout-canary-679b8b5b4c-46bnv
3s Normal RolloutAddedToInformer rollout/rollout-canary Rollout resource added to informer: openshift-gitops-operator/rollout-canary
3s Normal RolloutNotCompleted rollout/rollout-canary Rollout not completed, started update to revision 1 (679b8b5b4c)
3s Normal RolloutUpdated rollout/rollout-canary Rollout updated to revision 1
3s Normal NewReplicaSetCreated rollout/rollout-canary Created ReplicaSet rollout-canary-679b8b5b4c (revision 1)
3s Normal ScalingReplicaSet rollout/rollout-canary Scaled up ReplicaSet rollout-canary-679b8b5b4c (revision 1) from 0 to 5
3s Normal RolloutCompleted rollout/rollout-canary Rollout completed update to revision 1 (679b8b5b4c): Initial deploy
[jgw@localhost-lan examples]$
- We should also capture all of the Rollout CRs:
- analysisruns
- analysistemplates
*clusteranalysistemplates - experiments
Acceptance Criteria (Mandatory)
- The above CRs are captured by gitops must-gather output, across all Namespaces
- For each Namespace that contains a Rollout CR, Events CRs from that Namespace are captured in must-gather output
