CRT Config Monitor for Ship Status #79397
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -448,6 +448,125 @@ components: | |
| - rover_group: "test-platform-ci-admins" | ||
| - service_account: "system:serviceaccount:ship-status:component-monitor" | ||
|
|
||
| - name: "Release Controller" | ||
| description: "Manages OpenShift release payloads, acceptance testing, and promotion" | ||
| ship_team: "CRT" | ||
| sub_components: | ||
| - name: "openshift-release" | ||
| description: "openshift-release.apps.ci.l2s4.p1.openshiftapps.com" | ||
| long_description: "The primary release controller for OpenShift Container Platform. Manages release payload assembly, acceptance job orchestration, and promotion of nightly and CI releases for the amd64 architecture." | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "origin-release" | ||
| description: "origin-release.apps.ci.l2s4.p1.openshiftapps.com" | ||
| long_description: "Release controller for the OKD (Origin) distribution. Manages the upstream community release pipeline separate from the downstream OCP releases." | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-arm64" | ||
| description: "openshift-release-arm64.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-multi" | ||
| description: "openshift-release-multi.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-ppc64le" | ||
| description: "openshift-release-ppc64le.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-s390x" | ||
| description: "openshift-release-s390x.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-priv" | ||
| description: "openshift-release-priv.apps.ci.l2s4.p1.openshiftapps.com" | ||
| long_description: "Handles release payloads for private/embargoed OCP content behind OAuth authentication." | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-arm64-priv" | ||
| description: "openshift-release-arm64-priv.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-multi-priv" | ||
| description: "openshift-release-multi-priv.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-ppc64le-priv" | ||
| description: "openshift-release-ppc64le-priv.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "openshift-release-s390x-priv" | ||
| description: "openshift-release-s390x-priv.apps.ci.l2s4.p1.openshiftapps.com" | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "dpcr-openshift-release" | ||
| description: "openshift-release.apps.cr.j7t7.p1.openshiftapps.com" | ||
| long_description: "Release controller instance running on the DPCR cluster, providing redundancy and serving the DPCR-hosted release pipeline." | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| owners: | ||
| - rover_group: "continuous-release-team" | ||
| - service_account: "system:serviceaccount:crt-argocd:component-monitor" | ||
|
Comment on lines
+543
to
+545
Contributor
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Check if the crt-argocd service account exists and compare with referenced component-monitor
# Look for any references to crt-argocd namespace in the codebase
rg -n 'crt-argocd' --type yaml
# Look for component-monitor service account definitions
fd -e yaml -e yml | xargs rg -l 'kind:\s*ServiceAccount' | xargs rg -A5 'name:\s*component-monitor'Repository: openshift/release Length of output: 3189 🏁 Script executed: # Search for all service accounts in crt-argocd namespace
rg -A3 'namespace:\s*crt-argocd' --type yaml | rg -B3 'kind:\s*ServiceAccount'
# Also search for any ServiceAccount definitions with crt-argocd context
fd -e yaml -e yml | xargs rg -B5 -A5 'namespace:\s*crt-argocd' | grep -A10 'ServiceAccount'
# Check if crt-argocd namespace is defined anywhere
rg 'namespace.*crt-argocd' --type yaml -B2 -A2Repository: openshift/release Length of output: 43 🏁 Script executed: # Search for all references to crt-argocd in YAML files
rg 'crt-argocd' --type yaml -B2 -A2
# Search for all ServiceAccount definitions in the codebase
fd -e yaml -e yml -exec grep -l 'kind:\s*ServiceAccount' {} \; | head -20
# Look for Release Controller and CRT related configs
rg -i 'release.*controller|continuous.*release' --type yaml -B1 -A1 | head -50Repository: openshift/release Length of output: 4665 🏁 Script executed: # Search for all ServiceAccount definitions
rg 'kind:\s*ServiceAccount' --type yaml -A2
# Look for all namespaces in serviceaccount.yaml to understand the full context
cat clusters/build-clusters/common/ship-status/serviceaccount.yaml | head -100Repository: openshift/release Length of output: 50374 🏁 Script executed: cat clusters/build-clusters/common/ship-status/serviceaccount.yamlRepository: openshift/release Length of output: 1048 Fix namespace reference for component-monitor service account. The service account referenced at lines 545 and 568 uses 🤖 Prompt for AI Agents |
||
| - name: "CRT" | ||
| description: "Services managed by the Continuous Release Tooling team" | ||
| ship_team: "CRT" | ||
| sub_components: | ||
| - name: "Backstage" | ||
| description: "backstage.dptools.openshift.org" | ||
| long_description: "Backstage provides a centralized service catalog, documentation hub, and developer portal for the OpenShift CI platform. It aggregates team information, service ownership, and technical documentation into a single interface." | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| - name: "CI-Search" | ||
| description: "search.dptools.openshift.org" | ||
| long_description: "CI-Search indexes and provides full-text search across OpenShift CI test results, build logs, and job artifacts. It integrates with Bugzilla and Jira to help developers quickly find relevant test failures and correlate them with known issues." | ||
| monitoring: | ||
| frequency: 5m | ||
| component_monitor: "crt-component-monitor" | ||
| auto_resolve: true | ||
| requires_confirmation: false | ||
| owners: | ||
| - rover_group: "continuous-release-team" | ||
| - service_account: "system:serviceaccount:crt-argocd:component-monitor" | ||
|
|
||
| tags: | ||
| - name: "ci-frontend" | ||
| description: "User-facing web interfaces for viewing CI jobs and test results" | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/release
Length of output: 449
🏁 Script executed:
Repository: openshift/release
Length of output: 3537
🏁 Script executed:
Repository: openshift/release
Length of output: 6442
Confirm that
retry_after: 5sis intentional for Release Controller and CRT services.The Release Controller entries (lines 564–624) and CRT Services entries (lines 633–639) all use
retry_after: 5s, while existing Prow monitors useretry_after: 4m(lines 8, 109). This 48× difference in retry frequency is consistent across all new entries, suggesting intentional design, but no comments explain the rationale for the difference.🤖 Prompt for AI Agents