OCPNODE-3880: Add criocredentialproviderconfig event handler by QiWang19 · Pull Request #5487 · openshift/machine-config-operator

QiWang19 · 2025-12-11T06:13:59Z

- What I did
Implement criocredentialprovierconfig that is used by crio-credential-provider plugin to fetch private mirror image pull secrets from the secret object.

The handler creates 97-pool-generated-credentialproviderconfig to rollout configurations to file /etc/kubernetes/credential-providers/[platform]-credential-provider.yaml .

workflow: https://github.com/openshift/enhancements/blob/master/enhancements/api-review/criocredentialproviderconfig-for-namespace-scoped-mirror-authentication.md#workflow-description
- How to verify it

create cluster CRIOCredentialProviderConfig resource, file updated with a new section name: crio-credential-provider

apiVersion: config.openshift.io/v1alpha1
kind: CRIOCredentialProviderConfig
metadata:
  name: cluster
spec:
  matchImages:
  - docker.io
  - 123456789.dkr.ecr.us-east-1.amazonaws.com
  - "*.azurecr.io"
  - gcr.io
  - "*.*.registry.io"
  - registry.io:8080/path

$ oc get mc
97-master-generated-credentialproviderconfig       f6dc328e4c370e377ea5c878aa4c0b8feeb1b181   3.5.0             2s
97-worker-generated-credentialproviderconfig       f6dc328e4c370e377ea5c878aa4c0b8feeb1b181   3.5.0             2s

$ oc describe criocredentialproviderconfig.config.openshift.io/cluster
Name:         cluster
Namespace:    
Labels:       <none>
Annotations:  <none>
API Version:  config.openshift.io/v1alpha1
Kind:         CRIOCredentialProviderConfig
Metadata:
  Creation Timestamp:  2026-02-16T21:26:17Z
  Generation:          1
  Resource Version:    42066
  UID:                 05d173ad-7b8d-4a28-afb9-b587fe565e16
Spec:
  Match Images:
    docker.io
    123456789.dkr.ecr.us-east-1.amazonaws.com
    *.azurecr.io
    gcr.io
    *.*.registry.io
    registry.io:8080/path
Status:
  Conditions:
    Last Transition Time:  2026-02-16T21:26:17Z
    Message:               Success
    Observed Generation:   1
    Reason:                MachineConfigRenderingSucceeded
    Status:                True
    Type:                  MachineConfigRendered
Events:                    <none>

sh-5.1# cat /etc/kubernetes/credential-providers/ecr-credential-provider.yaml 
apiVersion: kubelet.config.k8s.io/v1
kind: CredentialProviderConfig
providers:
- apiVersion: credentialprovider.kubelet.k8s.io/v1
  defaultCacheDuration: 12h0m0s
  matchImages:
  - '*.dkr.ecr.*.amazonaws.com'
  - '*.dkr.ecr.*.amazonaws.com.cn'
  - '*.dkr.ecr-fips.*.amazonaws.com'
  - '*.dkr.ecr.us-iso-east-1.c2s.ic.gov'
  - '*.dkr.ecr.us-isob-east-1.sc2s.sgov.gov'
  name: ecr-credential-provider
- apiVersion: credentialprovider.kubelet.k8s.io/v1
  defaultCacheDuration: 1s
  matchImages:
  - docker.io
  - 123456789.dkr.ecr.us-east-1.amazonaws.com
  - '*.azurecr.io'
  - gcr.io
  - '*.*.registry.io'
  - registry.io:8080/path
  name: crio-credential-provider
  tokenAttributes:
    cacheType: Token
    requireServiceAccount: false
    serviceAccountTokenAudience: https://kubernetes.default.svc

create namespace rolebing allow serviceaccount to get secrect in the namespace e.g. namespace:mynamespace

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: credential-provider-secret-reader
  namespace: mynamespace 
rules:
- apiGroups: [""]
  resources: ["secrets"] 
  verbs: ["get", "list"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: credential-provider-secret-reader-binding
  namespace: mynamespace 
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: credential-provider-secret-reader
subjects:
  - apiGroup: rbac.authorization.k8s.io
    kind: User
    name: system:serviceaccount:mynamespace:default

Create ImageDigestMirrorSet/ImageTagMirrorSet mirror configurations
Create a pod containers.image is from mirror source registry
Check crio-credential-provider log journalctl _COMM=crio-credential on the scheduled node

- Description for the changelog

Summary by CodeRabbit

New Features
- Manage CRIO credential providers via a new CRIOCredentialProviderConfig with platform-aware credential-provider config generation and kubelet credential-provider flags on master, worker, and arbiter nodes.
Chores / Defaults
- Cluster defaults updated to add credential-provider file paths and to reload/restart kubelet when those configs change.
Security & Permissions
- Added cluster-scoped RBAC roles/bindings to allow nodes to access service account token-related operations.
Tests
- Added comprehensive unit and controller tests for CRIO credential provider create/update/merge and ignition generation.

openshift-ci · 2025-12-11T06:14:03Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

QiWang19 · 2025-12-11T06:14:07Z

/test all

QiWang19 · 2025-12-22T21:29:19Z

/test all

openshift-ci-robot · 2025-12-23T23:00:40Z

@QiWang19: This pull request references OCPNODE-3880 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

- What I did

- How to verify it

apiVersion: config.openshift.io/v1alpha1
kind: CRIOCredentialProviderConfig
metadata:
 name: cluster
spec:
 matchImages:
 - 123456789.dkr.ecr.us-east-1.amazonaws.com
 - "*.azurecr.io"
 - "*.*.registry.io"
 - registry.io:8080/path

sh-5.1# cat /etc/kubernetes/credential-providers/gcr-credential-provider.yaml 
apiVersion: kubelet.config.k8s.io/v1
kind: CredentialProviderConfig
providers:
- apiVersion: credentialprovider.kubelet.k8s.io/v1
 args:
 - get-credentials
 - --v=3
 defaultCacheDuration: 1m0s
 matchImages:
 - gcr.io
 - '*.gcr.io'
 - '*.pkg.dev'
 - container.cloud.google.com
 name: gcr-credential-provider
- apiVersion: credentialprovider.kubelet.k8s.io/v1
 defaultCacheDuration: 1s
 matchImages:
 - registry.io:8080/path
 - 123456789.dkr.ecr.us-east-1.amazonaws.com
 - '*.azurecr.io'
 - '*.*.registry.io'
 name: crio-credential-provider
 tokenAttributes:
   cacheType: Token
   requireServiceAccount: false
   serviceAccountTokenAudience: https://kubernetes.default.svc

- Description for the changelog

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

QiWang19 · 2026-01-26T15:36:25Z

/test all

QiWang19 · 2026-01-27T01:47:04Z

/test all

QiWang19 · 2026-01-27T18:43:00Z

/test all

QiWang19 · 2026-01-28T15:28:16Z

/test all

QiWang19 · 2026-02-15T16:26:15Z

/test all

QiWang19 · 2026-02-16T19:53:37Z

/test all

openshift-ci-robot · 2026-02-16T21:43:09Z

@QiWang19: This pull request references OCPNODE-3880 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

- What I did

- How to verify it

create cluster CRIOCredentialProviderConfig resource

apiVersion: config.openshift.io/v1alpha1
kind: CRIOCredentialProviderConfig
metadata:
 name: cluster
spec:
 matchImages:
 - docker.io
 - 123456789.dkr.ecr.us-east-1.amazonaws.com
 - "*.azurecr.io"
 - gcr.io
 - "*.*.registry.io"
 - registry.io:8080/path

$ oc describe criocredentialproviderconfig.config.openshift.io/cluster
Name:         cluster
Namespace:    
Labels:       <none>
Annotations:  <none>
API Version:  config.openshift.io/v1alpha1
Kind:         CRIOCredentialProviderConfig
Metadata:
 Creation Timestamp:  2026-02-16T21:26:17Z
 Generation:          1
 Resource Version:    42066
 UID:                 05d173ad-7b8d-4a28-afb9-b587fe565e16
Spec:
 Match Images:
   docker.io
   123456789.dkr.ecr.us-east-1.amazonaws.com
   *.azurecr.io
   gcr.io
   *.*.registry.io
   registry.io:8080/path
Status:
 Conditions:
   Last Transition Time:  2026-02-16T21:26:17Z
   Message:               Success
   Observed Generation:   1
   Reason:                MachineConfigRenderingSucceeded
   Status:                True
   Type:                  MachineConfigRendered
Events:                    <none>

sh-5.1# cat /etc/kubernetes/credential-providers/ecr-credential-provider.yaml 
apiVersion: kubelet.config.k8s.io/v1
kind: CredentialProviderConfig
providers:
- apiVersion: credentialprovider.kubelet.k8s.io/v1
 defaultCacheDuration: 12h0m0s
 matchImages:
 - '*.dkr.ecr.*.amazonaws.com'
 - '*.dkr.ecr.*.amazonaws.com.cn'
 - '*.dkr.ecr-fips.*.amazonaws.com'
 - '*.dkr.ecr.us-iso-east-1.c2s.ic.gov'
 - '*.dkr.ecr.us-isob-east-1.sc2s.sgov.gov'
 name: ecr-credential-provider
- apiVersion: credentialprovider.kubelet.k8s.io/v1
 defaultCacheDuration: 1s
 matchImages:
 - docker.io
 - 123456789.dkr.ecr.us-east-1.amazonaws.com
 - '*.azurecr.io'
 - gcr.io
 - '*.*.registry.io'
 - registry.io:8080/path
 name: crio-credential-provider
 tokenAttributes:
   cacheType: Token
   requireServiceAccount: false
   serviceAccountTokenAudience: https://kubernetes.default.svc

- Description for the changelog

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-02-16T22:34:05Z

@QiWang19: This pull request references OCPNODE-3880 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

- What I did

- How to verify it

create cluster CRIOCredentialProviderConfig resource

apiVersion: config.openshift.io/v1alpha1
kind: CRIOCredentialProviderConfig
metadata:
 name: cluster
spec:
 matchImages:
 - docker.io
 - 123456789.dkr.ecr.us-east-1.amazonaws.com
 - "*.azurecr.io"
 - gcr.io
 - "*.*.registry.io"
 - registry.io:8080/path

$ oc describe criocredentialproviderconfig.config.openshift.io/cluster
Name:         cluster
Namespace:    
Labels:       <none>
Annotations:  <none>
API Version:  config.openshift.io/v1alpha1
Kind:         CRIOCredentialProviderConfig
Metadata:
 Creation Timestamp:  2026-02-16T21:26:17Z
 Generation:          1
 Resource Version:    42066
 UID:                 05d173ad-7b8d-4a28-afb9-b587fe565e16
Spec:
 Match Images:
   docker.io
   123456789.dkr.ecr.us-east-1.amazonaws.com
   *.azurecr.io
   gcr.io
   *.*.registry.io
   registry.io:8080/path
Status:
 Conditions:
   Last Transition Time:  2026-02-16T21:26:17Z
   Message:               Success
   Observed Generation:   1
   Reason:                MachineConfigRenderingSucceeded
   Status:                True
   Type:                  MachineConfigRendered
Events:                    <none>

sh-5.1# cat /etc/kubernetes/credential-providers/ecr-credential-provider.yaml 
apiVersion: kubelet.config.k8s.io/v1
kind: CredentialProviderConfig
providers:
- apiVersion: credentialprovider.kubelet.k8s.io/v1
 defaultCacheDuration: 12h0m0s
 matchImages:
 - '*.dkr.ecr.*.amazonaws.com'
 - '*.dkr.ecr.*.amazonaws.com.cn'
 - '*.dkr.ecr-fips.*.amazonaws.com'
 - '*.dkr.ecr.us-iso-east-1.c2s.ic.gov'
 - '*.dkr.ecr.us-isob-east-1.sc2s.sgov.gov'
 name: ecr-credential-provider
- apiVersion: credentialprovider.kubelet.k8s.io/v1
 defaultCacheDuration: 1s
 matchImages:
 - docker.io
 - 123456789.dkr.ecr.us-east-1.amazonaws.com
 - '*.azurecr.io'
 - gcr.io
 - '*.*.registry.io'
 - registry.io:8080/path
 name: crio-credential-provider
 tokenAttributes:
   cacheType: Token
   requireServiceAccount: false
   serviceAccountTokenAudience: https://kubernetes.default.svc

create namespace rolebing e.g. namespace:mynamespace

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
 name: credential-provider-secret-reader
 namespace: mynamespace 
rules:
- apiGroups: [""]
 resources: ["secrets"] 
 verbs: ["get", "list"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
 name: credential-provider-secret-reader-binding
 namespace: mynamespace 
roleRef:
 apiGroup: rbac.authorization.k8s.io
 kind: Role
 name: credential-provider-secret-reader
subjects:
 - apiGroup: rbac.authorization.k8s.io
   kind: User
   name: system:serviceaccount:mynamespace:default

Create ImageDigestMirrorSet/ImageTagMirrorSet mirror configurations
Create a pod containers.image is from source
Check crio-credential-provider log journalctl _COMM=crio-credential on the scheduled node

- Description for the changelog

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

QiWang19 · 2026-02-16T22:34:19Z

/test all

haircommander · 2026-03-11T17:51:40Z

/lgtm

QiWang19 · 2026-03-11T22:39:17Z

/retest-required

saschagrunert · 2026-03-12T08:09:56Z

pkg/controller/container-runtime-config/container_runtime_config_controller.go

+				ctrl.syncCRIOCredentialProviderConfigStatusOnly(err, apicfgv1alpha1.ConditionTypeMachineConfigRendered, apicfgv1alpha1.ReasonMachineConfigRenderingFailed, "could not generate CRIOCredentialProvider Ignition config: %v", err)
+				return err
+			}
+			if len(overlappedEntries) > 0 {


When overlaps exist, this sets ConditionTypeValidated to False with ReasonConfigurationPartiallyApplied. If the user later removes the conflicting entries from the CR, no code path resets this condition back to True. The stale warning persists indefinitely.

Do we need to add an else branch (or an unconditional call after the loop) that sets ConditionTypeValidated to True when len(overlappedEntries) == 0?

saschagrunert · 2026-03-12T08:09:56Z

pkg/controller/container-runtime-config/container_runtime_config_controller.go

+	builtInLabelKey                      = "machineconfiguration.openshift.io/mco-built-in"
+	configMapName                        = "crio-default-container-runtime"
+	forceSyncOnUpgrade                   = "force-sync-on-upgrade"
+	genericCredProviderConfigPath        = "/etc/kubernetes/credential-providers/generic-credential-provider.yaml"


Nit: kubeletCrioImageCredProviderConfPath duplicates constants.KubeletCrioImageCredProviderConfPath from pkg/daemon/constants/constants.go. Consider using the constants package instead of redefining the value here.

saschagrunert

/lgtm

saschagrunert · 2026-03-13T10:02:35Z

/retest

QiWang19 · 2026-03-13T19:09:20Z

/verified by @QiWang19

openshift-ci-robot · 2026-03-13T19:09:33Z

@QiWang19: This PR has been marked as verified by @QiWang19.

Details

In response to this:

/verified by @QiWang19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

QiWang19 · 2026-03-14T02:14:04Z

/retest-required

QiWang19 · 2026-03-16T13:20:51Z

@isabella-janssen could you take a look?

umohnani8 · 2026-03-16T14:37:47Z

/approve

QiWang19 · 2026-03-16T19:52:24Z

/retest-required

QiWang19 · 2026-03-16T21:52:01Z

PR has a bootstrap e2e test failure that started this week. The test was passing with the previous [fix](https://github.com/QiWang19/machine-config-operator/blob/18b41eb1069358b9695019a7a9cd585ce690ea61/test/framework/envtest.go#L119-L121) but is now failing again
The failure is related to the bootstrap being run with techpreview enabled. When this feature gate is enabled, the container runtime config controller attempts to watch for TechpreviewNoUpgrade resource CRIOCredentialProviderConfig, but the test framework failed to install the CRD manifests.

QiWang19 · 2026-03-16T22:36:10Z

/retest-required

QiWang19 · 2026-03-17T00:56:16Z

rebaesd to resolve the conflict.

QiWang19 · 2026-03-17T00:58:37Z

/test bootstrap-unit

QiWang19 · 2026-03-17T02:10:13Z

/test bootstrap-unit

Signed-off-by: Qi Wang <qiwan@redhat.com>

QiWang19 · 2026-03-17T03:44:28Z

/test bootstrap-unit

QiWang19 · 2026-03-17T04:06:30Z

/verified by @QiWang19

openshift-ci-robot · 2026-03-17T04:06:42Z

@QiWang19: This PR has been marked as verified by @QiWang19.

Details

In response to this:

/verified by @QiWang19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

saschagrunert · 2026-03-17T08:44:58Z

/retest

saschagrunert · 2026-03-17T12:22:41Z

/test e2e-openstack

haircommander · 2026-03-17T14:37:17Z

/lgtm

openshift-ci · 2026-03-17T14:39:58Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, QiWang19, saschagrunert, umohnani8

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [umohnani8]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2026-03-17T15:54:29Z

@QiWang19: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-op-2of2	`b4132ef`	link	true	`/test e2e-gcp-op-2of2`
ci/prow/e2e-openstack	`f4a26aa`	link	false	`/test e2e-openstack`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 11, 2025

QiWang19 force-pushed the addcriocpcontroller branch 3 times, most recently from 865fa47 to 8a072e4 Compare December 13, 2025 06:29

QiWang19 changed the title ~~Addcriocpcontroller~~ OCPNODE-3880: Add criocredentialprovierconfig pcontroller Dec 23, 2025

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 23, 2025

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 21, 2026

QiWang19 force-pushed the addcriocpcontroller branch from 8a072e4 to 75dfbfd Compare January 26, 2026 15:35

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 26, 2026

QiWang19 force-pushed the addcriocpcontroller branch from 75dfbfd to 511fde6 Compare January 27, 2026 01:46

QiWang19 force-pushed the addcriocpcontroller branch from 511fde6 to 0ff0fe8 Compare January 27, 2026 18:42

QiWang19 force-pushed the addcriocpcontroller branch from 0ff0fe8 to 5d5008b Compare January 28, 2026 15:25

QiWang19 force-pushed the addcriocpcontroller branch from 5d5008b to 7d79743 Compare January 30, 2026 14:15

QiWang19 force-pushed the addcriocpcontroller branch 2 times, most recently from 147fbf2 to 3027d6a Compare February 15, 2026 16:17

QiWang19 force-pushed the addcriocpcontroller branch from 3027d6a to 9a477a8 Compare February 16, 2026 19:53

QiWang19 force-pushed the addcriocpcontroller branch from 9a477a8 to 58fa6bc Compare February 16, 2026 20:59

openshift-ci bot assigned haircommander Mar 11, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 11, 2026

saschagrunert reviewed Mar 12, 2026

View reviewed changes

QiWang19 force-pushed the addcriocpcontroller branch from c8f5763 to c953926 Compare March 12, 2026 18:38

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2026

QiWang19 force-pushed the addcriocpcontroller branch from c953926 to 18b41eb Compare March 12, 2026 20:38

saschagrunert approved these changes Mar 13, 2026

View reviewed changes

criocp controller

f4a26aa

Signed-off-by: Qi Wang <qiwan@redhat.com>

Conversation

QiWang19 commented Dec 11, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-ci bot commented Dec 11, 2025

Uh oh!

QiWang19 commented Dec 11, 2025

Uh oh!

QiWang19 commented Dec 22, 2025

Uh oh!

openshift-ci-robot commented Dec 23, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

QiWang19 commented Jan 26, 2026

Uh oh!

QiWang19 commented Jan 27, 2026

Uh oh!

QiWang19 commented Jan 27, 2026

Uh oh!

QiWang19 commented Jan 28, 2026

Uh oh!

QiWang19 commented Feb 15, 2026

Uh oh!

QiWang19 commented Feb 16, 2026

Uh oh!

openshift-ci-robot commented Feb 16, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 16, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

QiWang19 commented Feb 16, 2026

Uh oh!

haircommander commented Mar 11, 2026

Uh oh!

QiWang19 commented Mar 11, 2026

Uh oh!

saschagrunert Mar 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

saschagrunert Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

saschagrunert left a comment

Choose a reason for hiding this comment

Uh oh!

saschagrunert commented Mar 13, 2026

Uh oh!

QiWang19 commented Mar 13, 2026

Uh oh!

openshift-ci-robot commented Mar 13, 2026

Uh oh!

QiWang19 commented Mar 14, 2026

Uh oh!

QiWang19 commented Mar 16, 2026

Uh oh!

umohnani8 commented Mar 16, 2026

Uh oh!

QiWang19 commented Mar 16, 2026

Uh oh!

QiWang19 commented Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

QiWang19 commented Mar 16, 2026

Uh oh!

QiWang19 commented Mar 17, 2026

Uh oh!

QiWang19 commented Mar 17, 2026

Uh oh!

QiWang19 commented Mar 17, 2026

Uh oh!

QiWang19 commented Mar 17, 2026

Uh oh!

QiWang19 commented Mar 17, 2026

Uh oh!

openshift-ci-robot commented Mar 17, 2026

Uh oh!

saschagrunert commented Mar 17, 2026

QiWang19 commented Dec 11, 2025 •

edited by coderabbitai bot

Loading

openshift-ci-robot commented Dec 23, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 16, 2026 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 16, 2026 •

edited by openshift-ci bot

Loading

saschagrunert Mar 12, 2026 •

edited

Loading

QiWang19 commented Mar 16, 2026 •

edited

Loading