Scenario 2: KAS Route Defaulting for Private Clusters

Objective: Verify the CLI correctly defaults KAS to Route strategy for Private topology, matching the behavior when --external-dns-domain is set.

Implementation: The fix adds an isPrivate parameter to GetIngressServicePublishingStrategyMapping(). When isPrivate=true, the function returns Route strategy for APIServer instead of LoadBalancer, regardless of whether --external-dns-domain is set.

Overall Scenario 2: PASS — All 4 checks verified.
StepCheckResultEvidence
1 APIServer uses Route strategy PASS "service": "APIServer", "type": "Route"
2 Ignition uses Route strategy PASS "service": "Ignition", "type": "Route"
3 Konnectivity uses Route strategy PASS "service": "Konnectivity", "type": "Route"
4 OAuthServer uses Route strategy PASS "service": "OAuthServer", "type": "Route"

Commands & Outputs

Steps 1-4: Verify all services use Route strategy

$ oc get hostedcluster brcox-100054-hc -n clusters -o jsonpath='{.spec.services}' | jq .
[
  {
    "service": "APIServer",
    "servicePublishingStrategy": {
      "type": "Route"
    }
  },
  {
    "service": "Ignition",
    "servicePublishingStrategy": {
      "type": "Route"
    }
  },
  {
    "service": "Konnectivity",
    "servicePublishingStrategy": {
      "type": "Route"
    }
  },
  {
    "service": "OAuthServer",
    "servicePublishingStrategy": {
      "type": "Route"
    }
  }
]
← Scenario 1 Scenario 3 →