NO-JIRA: set ovnkube-cluster-manager as default container

[lance5890]

As we use kubectl logs -n openshift-ovn-kubernetes ovnkube-control-plane-xxx, we see the default container logs is kube-rbac-proxy, like :

kubectl logs -n openshift-ovn-kubernetes ovnkube-control-plane-7948b585d4-wc7m4 
Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, ovnkube-cluster-manager
2025-07-07T04:27:01+00:00 INFO: ovn-control-plane-metrics-certs mounted, starting kube-rbac-proxy
W0707 04:27:01.354951       1 deprecated.go:66] 
==== Removed Flag Warning ======================

logtostderr is removed in the k8s upstream and has no effect any more.

===============================================

I0707 04:27:01.356349       1 kube-rbac-proxy.go:233] Valid token audiences: 
I0707 04:27:01.356401       1 kube-rbac-proxy.go:347] Reading certificate files
I0707 04:27:01.356776       1 kube-rbac-proxy.go:395] Starting TCP socket on :9108
I0707 04:27:01.357087       1 kube-rbac-proxy.go:402] Listening securely on :9108

But most of the time we just care about the container ovnkube-cluster-manager logs , not the kube-rbac-proxy

[openshift-ci]

Hi @lance5890. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[ricky-rav]

Nice, I didn't know about this annotation! Could you apply the same changes also to bindata/network/ovn-kubernetes/managed/ovnkube-control-plane.yaml?

Bonus point:
Could we also do the same for ovnkube-node.yaml (self-hosted and managed) and set ovnkube-controller as the default container? That would be amazing.

Thanks! :)

[lance5890]

Nice, I didn't know about this annotation! Could you apply the same changes also to bindata/network/ovn-kubernetes/managed/ovnkube-control-plane.yaml?

Bonus point: Could we also do the same for ovnkube-node.yaml (self-hosted and managed) and set ovnkube-controller as the default container? That would be amazing.

Thanks! :)

that makes sense, done!

[ricky-rav]

/LGTM

[ricky-rav]

@kyrtapz PTAL

[kyrtapz]

Thanks @lance5890!
/ok-to-test
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, lance5890, ricky-rav

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kyrtapz]

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

[kyrtapz]

/retitle NO-JIRA: set ovnkube-cluster-manager as default container

[openshift-ci-robot]

@lance5890: This pull request explicitly references no jira issue.

In response to this:

As we use kubectl logs -n openshift-ovn-kubernetes ovnkube-control-plane-xxx, we see the default container logs is kube-rbac-proxy, like :

kubectl logs -n openshift-ovn-kubernetes ovnkube-control-plane-7948b585d4-wc7m4 
Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, ovnkube-cluster-manager
2025-07-07T04:27:01+00:00 INFO: ovn-control-plane-metrics-certs mounted, starting kube-rbac-proxy
W0707 04:27:01.354951       1 deprecated.go:66] 
==== Removed Flag Warning ======================

logtostderr is removed in the k8s upstream and has no effect any more.

===============================================

I0707 04:27:01.356349       1 kube-rbac-proxy.go:233] Valid token audiences: 
I0707 04:27:01.356401       1 kube-rbac-proxy.go:347] Reading certificate files
I0707 04:27:01.356776       1 kube-rbac-proxy.go:395] Starting TCP socket on :9108
I0707 04:27:01.357087       1 kube-rbac-proxy.go:402] Listening securely on :9108

But most of the time we just care about the container ovnkube-cluster-manager logs , not the kube-rbac-proxy

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.

[lance5890]

/retest

[lance5890]

/retest

[lance5890]

/retest

[lance5890]

/retest-required

[lance5890]

/retest-required

[lance5890]

/retest-required

[openshift-ci]

@lance5890: 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-azure-ovn	fe94807	link	false	/test e2e-azure-ovn
ci/prow/security	fe94807	link	false	/test security
ci/prow/e2e-aws-hypershift-ovn-kubevirt	fe94807	link	false	/test e2e-aws-hypershift-ovn-kubevirt
ci/prow/okd-scos-e2e-aws-ovn	fe94807	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-openstack-ovn	fe94807	link	false	/test e2e-openstack-ovn
ci/prow/4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade	fe94807	link	false	/test 4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade
ci/prow/4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade	fe94807	link	false	/test 4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
ci/prow/e2e-azure-ovn-upgrade	fe94807	link	true	/test e2e-azure-ovn-upgrade

Full PR test history. Your PR dashboard.

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.