kind-deploy

You can bootstrap local KCM and KOF deployments on kind clusters by following a complete dev workflow that enforces prerequisites like Go, Docker, kubectl, and htpasswd, then orchestrates KCM bootstrap, local OCI registry setup, Helm chart packaging, and mothership deployment.

Yes, you can deploy an optional Istio service mesh when bootstrapping KCM and KOF on kind clusters. The workflow includes specific optional Istio setup paths and verification steps to ensure the service mesh integrates correctly with your local development environment.

You need Go, Docker, kubectl, and htpasswd installed on your machine to set up KCM and KOF locally. These tools are strictly enforced prerequisites required to orchestrate the bootstrap process, local OCI registry setup, and Helm chart packaging on kind clusters.

Yes, the kind deployment workflow supports regional and child cluster scenarios. It provides end-to-end local deployment guidance for these configurations, allowing developers to test complex multi-cluster architectures alongside the mothership deployment.

You need a local OCI registry during kind cluster development to store and manage packaged Helm charts. The deployment workflow orchestrates local OCI registry setup alongside Helm chart packaging to ensure the mothership deployment can access required charts locally.

The best way to verify a local KOF deployment on kind is by running the specific commands and readiness checks included in the workflow guidance. These verification steps ensure your local development environment, mothership deployment, and optional Istio paths are functioning correctly.