First prize in hand for your OpenShift Hosted Cluster

1. Access your Hosted Cluster

Upon delivery, you will be provided with two essential URLs. These vary depending on the cluster identifier.

Console OpenShift :
https://console-openshift-console.<CLUSTER_ID>.kaas.cav

API Kubernetes :
https://api.<CLUSTER_ID>.kaas.cav:443

Exemple réel :
https://console-openshift-console.hcp-ocb0007017-c3.kaas.cav

Connexion via kubeadmin :

oc login https://api.<CLUSTER_ID>.kaas.cav:443 -u kubeadmin -p <KUBEADMIN_PASSWORD>


2. Bastion Deployment

2. Bastion Deployment (Mandatory)

For security and network isolation reasons, Hosted Cluster administration must be performed via a bastion host.

The bastion host must be:

• deployed by the customer in their own VDC,
• on the same network as the Hosted Cluster workers,
• connected to the Service Zone,
• and connected to the OpenShift Zone (API, console, and system components).

Important: Without a bastion host, API access to the cluster is not possible.

Cloud Avenue does not provide a managed bastion host.

3. Connecting to the cluster from the bastion

Once connected to your bastion, you can administer your Hosted Cluster.

Option 1 : Connection via oc login

oc login https://api.<CLUSTER_ID>.kaas.cav:443 \
  -u kubeadmin \
  -p <KUBEADMIN_PASSWORD>

Option 2 : Connection via a Kubeconfig

export KUBECONFIG=~/kubeconfig-<CLUSTER_ID>.yaml
oc whoami

4. initial cluster checks

Once connected to the cluster, run the following commands to check the overall status.

Check nodes

oc get nodes -o wide

Every nodes must be in Ready state

Check ClusterOperators state

Operators must display :

• Available (disponible) = True
• Degraded (Dégradé) = False
• Progressing (Progression) = False

Check system pods

oc get pods -A

Check Operators details

oc describe clusteroperators

5. Conclusion

Your OpenShift Hosted Cluster is now:

• accessible via your bastion host,
• manageable via the API or console,
• and validated as operational through basic checks.