Create local testing environment w/ Kind (#236)

## Summary

This PR establishes a complete local testing environment for Milo that
enables developers to quickly spin up and test the full control plane
stack locally. The implementation provides a production-like testing
environment with proper authentication, TLS certificates, and networking
configuration.

## Key Features

- **One-command setup**: task dev:setup deploys a complete Milo
environment in under 5 minutes
- **Complete control plane**: Includes etcd storage, API server,
controller manager, and webhooks
- **Production-like networking**: Uses Gateway API with Envoy Gateway
for realistic traffic routing
- **Automated certificate management**: Uses cert-manager for TLS
certificate provisioning
- **Pre-configured authentication**: Test tokens and kubeconfig for
immediate API access
- **Task automation**: Enhanced Taskfile with development workflows

## Notes

This is built on top of the changes introduced in the test-infra repo to
[add support for the envoy gateway, observability stack, and remote
taskfile support](datum-cloud/test-infra#6).

Author: scotwells

.devcontainer/devcontainer.json

@@ -21,7 +21,7 @@
 		"ghcr.io/devcontainers-extra/features/go-task": {},
 		"ghcr.io/audacioustux/devcontainers/kustomize": {},
 		"ghcr.io/devcontainers/features/node": {
-            "version": "22.14.0" 
+            "version": "22.14.0"
         },
 		"ghcr.io/devcontainers-extra/features/pulumi": {}
 	},
@@ -77,6 +77,11 @@
   		"editor.tabSize": 2
 		}
 	},
+	"containerEnv": {
+		// Allow remote task files so we can include the test-infra taskfile for
+		// test cluster management.
+		"TASK_X_REMOTE_TASKFILES": "1",
+	}
 
 	// Features to add to the dev container. More info: https://containers.dev/features.
 	// "features": {},

.dockerignore

@@ -0,0 +1,51 @@
+# Git and development files
+.git
+.gitignore
+.gitattributes
+.github/
+
+# Documentation
+*.md
+docs/
+
+# Development and test files
+.task/
+.milo/
+.claude/
+certs/
+bin/
+test/
+dev-temp/
+
+# Location the test-infra repo will be copied to by the remote taskfile.
+.test-infra
+
+# Configuration and manifests (not needed for build)
+config/
+Taskfile.yaml
+docker-compose.yaml
+
+# IDE and editor files
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS generated files
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# Temporary files
+*.tmp
+*.temp
+/tmp/
+
+# Build artifacts and caches
+node_modules/
+*.log

.gitignore

@@ -1,8 +1,13 @@
 node_modules
-test/config/zitadel/secrets/machine-key.json
 bin/
 # Generated certificates for local development
 certs/
 # Generated kubeconfig for local development
 .kube/
-.tool-versions
+
+.tool-versions
+
+# Location the test-infra repo will be copied to by the remote taskfile.
+.test-infra
+# Files used by the taskfile.
+.task

.milo/kubeconfig

@@ -0,0 +1,18 @@
+apiVersion: v1
+clusters:
+- cluster:
+    insecure-skip-tls-verify: true
+    server: https://localhost:30443
+  name: milo-test-infra
+contexts:
+- context:
+    cluster: milo-test-infra
+    user: admin
+  name: milo-test-infra
+current-context: milo-test-infra
+kind: Config
+preferences: {}
+users:
+- name: admin
+  user:
+    token: test-admin-token

README.md

@@ -27,6 +27,31 @@ help a new class of service providers gain hyperscaler advantages. We decided
 that instead of simply using the lessons we'd learned over the years to build
 our own kick-butt back office, we should make it available to others. Et voila!
 
+## Quick Start
+
+Get Milo running locally in under 5 minutes:
+
+```bash
+# Prerequisites: Docker, Kind, kubectl, and Task installed
+git clone https://github.com/datum-cloud/milo.git
+cd milo
+
+# Enable remote task files to be used
+export TASK_X_REMOTE_TASKFILES=1
+task dev:setup
+```
+
+This deploys a complete Milo environment with API server, storage, and
+controllers. Access it with:
+
+```bash
+export KUBECONFIG=.milo/kubeconfig
+kubectl get organizations
+```
+
+📚 **[Full setup guide →](docs/getting-started.md)**
+📖 **[API documentation →](docs/api/)**
+
 ## What We Prefer Not to Build
 
 Projects with such a wide surface area can engender a "build everything"
@@ -43,6 +68,7 @@ scaled vendors. Here are some examples:
 - Tax and financial compliance can be provided by Avalara, NetSuite, etc.
 
 ## What We're Starting With
+
 There are a few big "System of Record" buckets to which we think folks should
 have programmatic access, namely: contacts, accounts, products, vendors, and
 assets.