[release-4.14] OCPBUGS-63170: ccm: disable unused secure-serving port and webhook

[chrischdi]

This is an manual cherry-pick of #415

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63170, which is invalid:

• expected dependent Jira Issue OCPBUGS-63169 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

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.

In response to this:

This is an manual cherry-pick of #415

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.

[chrischdi]

/jira refresh
/label backport-risk-assessed
/lgtm
/retest-required

[openshift-ci]

@chrischdi: you cannot LGTM your own PR.

In response to this:

/jira refresh
/label backport-risk-assessed
/lgtm
/retest-required

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]

@chrischdi: This pull request references Jira Issue OCPBUGS-63170, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

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.

In response to this:

/jira refresh
/label backport-risk-assessed
/lgtm
/retest-required

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.

[chrischdi]

/jira refresh

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63170, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-63169 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-63169 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

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.

[chrischdi]

/hold

[chrischdi]

/jira refresh

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63170, which is invalid:

• expected dependent Jira Issue OCPBUGS-63169 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

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.

[chrischdi]

/jira refresh
/hold cancel

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63170, which is invalid:

• expected dependent Jira Issue OCPBUGS-63169 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.

In response to this:

/jira refresh
/hold cancel

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.

[chrischdi]

/jira refresh

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63170, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-63169 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-63169 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

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.

[damdo]

/approve
/lgtm

/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: damdo

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

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

[sunzhaohua2]

/retest

[chrischdi]

The alibaba test tries to install with a non-existing instance type:

level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: [controlPlane.platform.alibabacloud.instanceType: Invalid value: "ecs.g6.2xlarge": no available availability zones found, compute[0].platform.alibabacloud.instanceType: Invalid value: "ecs.g6.2xlarge": no available availability zones found]

[sunzhaohua2]

/verified by @sunzhaohua2 Port 10258 is no longer listening.

zhsun:aws/ $ oc exec aws-cloud-controller-manager-6b86ff9f5c-fzwvv -- ss -tlnp | grep 10258          
zhsun:aws/ $ oc exec aws-cloud-controller-manager-6b86ff9f5c-lfsjf -- ss -tlnp | grep 10258
zhsun:aws/ $ oc get clusterversion                                                                                               
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.0-0-2025-11-06-022656-test-ci-ln-hzyrjbb-latest   True        False         176m    Cluster version is 4.14.0-0-2025-11-06-022656-test-ci-ln-hzyrjbb-latest

[openshift-ci-robot]

@sunzhaohua2: This PR has been marked as verified by @sunzhaohua2 Port 10258 is no longer listening..

In response to this:

/verified by @sunzhaohua2 Port 10258 is no longer listening.

zhsun:aws/ $ oc exec aws-cloud-controller-manager-6b86ff9f5c-fzwvv -- ss -tlnp | grep 10258          
zhsun:aws/ $ oc exec aws-cloud-controller-manager-6b86ff9f5c-lfsjf -- ss -tlnp | grep 10258
zhsun:aws/ $ oc get clusterversion                                                                                               
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.0-0-2025-11-06-022656-test-ci-ln-hzyrjbb-latest   True        False         176m    Cluster version is 4.14.0-0-2025-11-06-022656-test-ci-ln-hzyrjbb-latest

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.

[chrischdi]

The alibaba test tries to install with a non-existing instance type:

level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: [controlPlane.platform.alibabacloud.instanceType: Invalid value: "ecs.g6.2xlarge": no available availability zones found, compute[0].platform.alibabacloud.instanceType: Invalid value: "ecs.g6.2xlarge": no available availability zones found]

This PR does not touch alibaba cloud.

/override e2e-alibaba-ovn

cc @damdo

[openshift-ci]

@chrischdi: chrischdi unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

In response to this:

The alibaba test tries to install with a non-existing instance type:

level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: [controlPlane.platform.alibabacloud.instanceType: Invalid value: "ecs.g6.2xlarge": no available availability zones found, compute[0].platform.alibabacloud.instanceType: Invalid value: "ecs.g6.2xlarge": no available availability zones found]

This PR does not touch alibaba cloud.

/override e2e-alibaba-ovn

cc @damdo

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]

/retest-required

Remaining retests: 0 against base HEAD a0b9c0d and 2 for PR HEAD c82f74b in total

[openshift-ci]

@chrischdi: 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/e2e-alibaba-ovn	c82f74b	link	true	/test e2e-alibaba-ovn

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.

[damdo]

/override ci/prow/e2e-alibaba-ovn

[openshift-ci]

@damdo: damdo unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

In response to this:

/override ci/prow/e2e-alibaba-ovn

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.

[chrischdi]

@elmiko / @JoelSpeed we need your help here :D