Menu
Test kr CLI changes on a local k3d cluster
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | kr-test |
| description | Test kr CLI changes on a local k3d cluster |
| disable-model-invocation | true |
Run a local smoke test of kr changes using k3d clusters.
Check if k3d clusters exist:
k3d cluster list
If no clusters exist, start them:
./scripts/k3d+registry/start.sh
This creates two clusters: k3d-shared and k3d-dev.
./scripts/kr init \
--context k3d-dev \
--cluster dev-app-onprem-one \
--domain k3d.kuberise.dev
./scripts/kr deploy \
--context k3d-dev \
--cluster dev-app-onprem-one \
--repo https://github.com/kuberise/kuberise.io.git \
--revision main \
--domain k3d.kuberise.dev
Check ArgoCD application status:
kubectl get applications -n argocd --context k3d-dev
Summarize:
If testing dry-run changes:
./scripts/kr deploy --dry-run \
--context k3d-dev \
--cluster dev-app-onprem-one \
--repo https://github.com/kuberise/kuberise.io.git \
--revision main \
--domain k3d.kuberise.dev
Verify the output is valid YAML (all informational messages use # comment format).
./scripts/k3d+registry/delete-all.sh
./scripts/kr (local version) not the installed kr when testing changes--cilium to kr init if neededGuide through creating a new kuberise.io release with release notes, changelog, version badge, GitHub release, and LinkedIn post
Walk through adding a new external Helm component to the kuberise platform
Scaffold a new local Helm chart and register it in the app-of-apps
Check for newer versions of external Helm charts referenced in the platform
Scaffold a new blog post for the kuberise.io website
Create a changelog entry for the kuberise.io website from RELEASE_NOTES.md