Skip to content

Verify RKE2 HA Platform Foundation

Intent

  • Purpose: Confirm that the current on-prem Kubernetes foundation is healthy and ready for GitOps-managed workloads.
  • Trigger: Pre-demo validation, post-change validation, or routine confirmation before relying on the cluster.
  • Impact: Verifies the cluster state, node readiness, kubeconfig publication, and Argo CD application health.
  • Severity: P2
  • Rollback: Verification only. If the cluster or GitOps root is unhealthy, stop downstream rollout and reconcile the relevant RKE2 or Argo state first.

Preconditions

  • The on-prem RKE2 lane has already been deployed.
  • The cluster management endpoint published in the kubeconfig is reachable.

Verify cluster state

hyops show module platform/onprem/rke2-cluster --env dev

Expected:

  • status=ok
  • cap.k8s.rke2: ready
  • kubeconfig_path is published
  • rke2_servers and rke2_agents are present

Verify node readiness

KUBECONFIG="$HOME/.hybridops/envs/dev/state/kubeconfigs/rke2.yaml" \
kubectl get nodes -o wide

Expected:

  • all control-plane nodes report Ready
  • worker nodes report Ready when present on the current lane

Verify GitOps root

hyops show module platform/k8s/argocd-bootstrap --env dev

KUBECONFIG="$HOME/.hybridops/envs/dev/state/kubeconfigs/rke2.yaml" \
kubectl -n argocd get applications

Expected:

  • platform/k8s/argocd-bootstrap is status=ok
  • cap.gitops.argocd: ready
  • the root application hyops-workloads-root is present and healthy

References