OCPBUGS-66403: Remove log exposing kubeconfig

[umohnani8]

Fixes https://issues.redhat.com/browse/OCPBUGS-66403

- What I did
MCD log on master nodes was exposing the kubeconfig in the logs. Remove that log so we are not accidentally leaking sensitive information.

- How to verify it
Ensure the MCD logs no longer have the kubeconfig text showing up in the log.

- Description for the changelog
Remove log exposing kubeconfig in MCD logs

[openshift-ci-robot]

@umohnani8: This pull request references Jira Issue OCPBUGS-66403, which is invalid:

• expected the weakness to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes https://issues.redhat.com/browse/OCPBUGS-66403

- What I did
MCD log on master nodes was exposing the kubeconfig in the logs. Remove that log so we are not accidentally leaking sensitive information.

- How to verify it
Ensure the MCD logs no longer have the kubeconfig text showing up in the log.

- Description for the changelog
Remove log exposing kubeconfig in MCD logs

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.

[umohnani8]

/jira refresh

[openshift-ci-robot]

@umohnani8: This pull request references Jira Issue OCPBUGS-66403, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

/jira refresh

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.

[umohnani8]

/retest

[isabella-janssen]

/ltgm

[openshift-ci]

@umohnani8: The following test 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/bootstrap-unit	7681165	link	false	/test bootstrap-unit

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.

[yuqi-zhang]

/ltgm

Ah, was wondering why the bot was confused, lol

/lgtm
/label acknowledge-critical-fixes-only

This is log only and should not affect any payloads

[yuqi-zhang]

nit: technically this should be the unformatted info but it shouldn't affect anything

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umohnani8, yuqi-zhang

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,yuqi-zhang]

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

[sergiordlr]

Verified using IPI on AWS

We can see in the master nodes that the certificate is not printed anymore.

I1211 09:04:25.828195    5112 update.go:2755] "Skipping kubelet restart"
I1211 09:04:25.829420    5112 update.go:2755] "Cert not found in kubeconfig. This means we need to write to disk. Subject is: openshift-kube-apiserver-operator_localhost-recovery-serving-signer@1765443589"
I1211 09:04:25.830567    5112 update.go:2755] "Skipping kubelet restart"
I1211 09:04:25.832356    5112 certificate_writer.go:224] Writing new Data to /etc/kubernetes/kubeconfig <----- THIS WAS THE OFFENDING LINE WITH THE CERTIFICATE
I1211 09:04:25.849704    5112 certificate_writer.go:294] Certificate was synced from controllerconfig resourceVersion 13783

We have executed the security e2e test cases and we we have reviewed the generated MCD logs. We haven't seen any other certificate being printed.

/label qe-approved
/verified by @sergiordlr

[openshift-ci-robot]

@umohnani8: This pull request references Jira Issue OCPBUGS-66403, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

Fixes https://issues.redhat.com/browse/OCPBUGS-66403

- What I did
MCD log on master nodes was exposing the kubeconfig in the logs. Remove that log so we are not accidentally leaking sensitive information.

- How to verify it
Ensure the MCD logs no longer have the kubeconfig text showing up in the log.

- Description for the changelog
Remove log exposing kubeconfig in MCD logs

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]

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

Details

In response to this:

Verified using IPI on AWS

We can see in the master nodes that the certificate is not printed anymore.

I1211 09:04:25.828195    5112 update.go:2755] "Skipping kubelet restart"
I1211 09:04:25.829420    5112 update.go:2755] "Cert not found in kubeconfig. This means we need to write to disk. Subject is: openshift-kube-apiserver-operator_localhost-recovery-serving-signer@1765443589"
I1211 09:04:25.830567    5112 update.go:2755] "Skipping kubelet restart"
I1211 09:04:25.832356    5112 certificate_writer.go:224] Writing new Data to /etc/kubernetes/kubeconfig <----- THIS WAS THE OFFENDING LINE WITH THE CERTIFICATE
I1211 09:04:25.849704    5112 certificate_writer.go:294] Certificate was synced from controllerconfig resourceVersion 13783

We have executed the security e2e test cases and we we have reviewed the generated MCD logs. We haven't seen any other certificate being printed.

/label qe-approved
/verified by @sergiordlr

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]

/retest-required

Remaining retests: 0 against base HEAD e2f6042 and 2 for PR HEAD 7681165 in total

[isabella-janssen]

/test e2e-aws-ovn

[openshift-ci-robot]

@umohnani8: Jira Issue Verification Checks: Jira Issue OCPBUGS-66403
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-66403 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Fixes https://issues.redhat.com/browse/OCPBUGS-66403

- What I did
MCD log on master nodes was exposing the kubeconfig in the logs. Remove that log so we are not accidentally leaking sensitive information.

- How to verify it
Ensure the MCD logs no longer have the kubeconfig text showing up in the log.

- Description for the changelog
Remove log exposing kubeconfig in MCD logs

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-merge-robot]

Fix included in accepted release 4.21.0-0.nightly-2025-12-13-080958