-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
4.14.0
-
No
-
Hypershift Sprint 243
-
1
-
Proposed
-
False
-
Description of problem:
In New Hypershift MC, on creating a HC there are some HCP pods land on default machinepool, as they don't tolerate any tainted nodes.
metrics-forwarder-775fbdfd4c-zggnj package-operator-remote-phase-manager-67c7498848-n6qsd validation-webhook-6bcf58d95b-8gzjx validation-webhook-6bcf58d95b-cxt77
MC - hs-mc-l33eosbt0
Sector - staging perf
region - us-east-2
Version-Release number of selected component (if applicable):
4.14.0-0-nightly
How reproducible:
Always
Steps to Reproduce:
1.rosa create cluster --cluster-name perf-rhcp-0010 --replicas 3 --hosted-cp --sts --mode auto -y --output json --oidc-config-id 22q95g8founghr9r81skjkhcklhemp0u --subnet-ids subnet-059cefdf652a66894,subnet-0440418e1a1b92a54,subnet-0195b49cb19610771,subnet-04a55d53b9ce9da96,subnet-0fb19a3d1133d7b3b,subnet-0c63d413d265b4af2 --properties provision_shard_id:87940a9b-5e1d-11ee-ad5b-0a580a8218cf --compute-machine-type t3a.xlarge --channel-group nightly --version 4.14.0-0.nightly-2023-09-29-231104 --properties pod_isolation_topology:true 2. Wait for them to be ready 3. check for pod placement
Actual results:
These pod will always land on default worker nodes
metrics-forwarder-775fbdfd4c-zggnj package-operator-remote-phase-manager-67c7498848-n6qsd validation-webhook-6bcf58d95b-8gzjx validation-webhook-6bcf58d95b-cxt77
Expected results:
These should be on shared non-serving worker nodes
Additional info: