OCPBUGS-60572: Use BoundServceAccountTokenVolume dy default

[lance5890]

The BoundServiceAccountTokenVolume is enabled by default

kind of post-cleanup of #355 and openshift/kubernetes#714

[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.

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.

[openshift-ci-robot]

@lance5890: This pull request references Jira Issue OCPBUGS-60572, which is invalid:

• expected the bug to target the "4.20.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:

The BoundServiceAccountTokenVolume is enabled by default

kind of post-cleanup of #355 and openshift/kubernetes#714

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]

the related pr openshift/cluster-version-operator#660 will block the upgrade

need more investigation

[lance5890]

/hold

[lance5890]

need to wait the openshift/cluster-version-operator#1225 to merge first

[tchap]

/ok-to-test

[tchap]

CVO is now ready.

/unhold

[tchap]

/jira refresh

[openshift-ci-robot]

@tchap: This pull request references Jira Issue OCPBUGS-60572, 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)

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.

[openshift-ci]

@lance5890: all tests passed!

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.

[tchap]

/lgtm

[tchap]

/verified by CI

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_cluster-kube-scheduler-operator/571/pull-ci-openshift-cluster-kube-scheduler-operator-main-e2e-aws-ovn-upgrade/1995772405519224832/artifacts/e2e-aws-ovn-upgrade/gather-extra/artifacts/inspect/namespaces/openshift-kube-scheduler-operator/core/pods.yaml

[openshift-ci-robot]

@tchap: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_cluster-kube-scheduler-operator/571/pull-ci-openshift-cluster-kube-scheduler-operator-main-e2e-aws-ovn-upgrade/1995772405519224832/artifacts/e2e-aws-ovn-upgrade/gather-extra/artifacts/inspect/namespaces/openshift-kube-scheduler-operator/core/pods.yaml

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.

[ingvagabund]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, lance5890, tchap

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 [ingvagabund]

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

[openshift-ci-robot]

@lance5890: Jira Issue Verification Checks: Jira Issue OCPBUGS-60572
✔️ 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-60572 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:

The BoundServiceAccountTokenVolume is enabled by default

kind of post-cleanup of #355 and openshift/kubernetes#714

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.