make run-k8s currently suggests that it starts a usable Kubernetes development environment, but it only runs local-registry, create-kind-cluster, and build-cli. It does not deploy AR into the cluster.
That makes the target misleading for normal development and especially confusing for Helm/chart work, where the expected path is make setup-kind-cluster or make install-agentregistry.
There is a related DX gap in the same workflow: the Makefile exposes KIND_CLUSTER_NAME and KIND_NAMESPACE, but the local registry is still effectively singleton because the registry container name and port are hardcoded as kind-registry and 5001. So creating a truly separate local env is only partially supported.
Noticed while testing #445 locally.
make run-k8s currently suggests that it starts a usable Kubernetes development environment, but it only runs local-registry, create-kind-cluster, and build-cli. It does not deploy AR into the cluster.
That makes the target misleading for normal development and especially confusing for Helm/chart work, where the expected path is make setup-kind-cluster or make install-agentregistry.
There is a related DX gap in the same workflow: the Makefile exposes KIND_CLUSTER_NAME and KIND_NAMESPACE, but the local registry is still effectively singleton because the registry container name and port are hardcoded as kind-registry and 5001. So creating a truly separate local env is only partially supported.
Noticed while testing #445 locally.