prole/tests/test_init_kerberos_ad_forwarder_readiness.py
chrisfu ce5ff83eb4 checkpoint: improve init scripts, installer flows, and kube context handling
- Fix kube context switching for k3s single-context kubeconfigs and k3d shorthand prefixes

- Update common init/status scripts (registry, kerberos, cnpg backup, service layer, common services)

- Add Gitea init script and installer ArgoCD screen

- Add Supabase realtime probe patching plus regression tests

- Extend installer core/UI test coverage
2026-03-14 20:07:54 -07:00

20 lines
829 B
Python

from __future__ import annotations
from pathlib import Path
def test_init_kerberos_waits_for_ad_forwarder_ready_and_endpoints():
"""Regression: Kerberos test must not run against an AD forwarder Service with no endpoints.
Historically `init_kerberos.sh` would `kubectl apply` the AD forwarder Deployment/Service and then
proceed immediately (or ignore rollout failures), which could yield `kinit: Cannot contact any KDC`.
"""
text = Path("etc/init_kerberos.sh").read_text(encoding="utf-8")
assert "wait_for_ad_forwarder_ready" in text
assert "wait_for_ad_forwarder_ready \"$KRB5_AD_NAMESPACE\" \"$KRB5_AD_PROXY_NAME\" \"$KRB5_AD_SERVICE_NAME\"" in text
# Ensure we don't silently ignore readiness.
assert "rollout status deploy/${KRB5_AD_PROXY_NAME} --timeout=120s || true" not in text