-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.17.0
-
Important
-
Yes
-
Installer Sprint 256
-
1
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
-
Done
Description of problem:
trying to create a private cluster got the forwarding rule, target tcp proxy and address "<infra id>-apiserver" created unexpectedly
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-06-13-084629
How reproducible:
Always
Steps to Reproduce:
1. create VPC network/subnets, and a bastion host within the VPC 2. "create install-config", and then insert network settings, "publish: Internal" and "featureSet: TechPreviewNoUpgrade" 3. "create cluster"
Actual results:
Although installation succeeds, the forwarding rule / target tcp proxy / address "<infra id>-apiserver" getting created, which are unexpected.
Expected results:
As a private cluster, there should be no the forwarding rule / target tcp proxy / address "<infra id>-apiserver".
Additional info:
FYI Flexy-install/290566/ INSTANCE_NAME_PREFIX jiwei-0614e-capi VARIABLES_LOCATION private-templates/functionality-testing/aos-4_16/ipi-on-gcp/versioned-installer-private_cluster LAUNCHER_VARS feature_set: "TechPreviewNoUpgrade" num_workers: 0 master_worker_AllInOne: "true"
- depends on
-
CORS-3296 Install Private Cluster
- Closed
- is related to
-
CORS-3296 Install Private Cluster
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update