remove kind tasks

Author: diamonwiggins

applications/mlflow/.docker/entrypoint.sh

@@ -12,53 +12,10 @@ trap 'exit 0' EXIT
 # Basic initialization
 echo "Initializing development environment..."
 
-# Function to create a Kind cluster if needed
-setup_kind_cluster() {
-  echo "Setting up Kind Kubernetes cluster..."
-  # Check if kind is installed
-  if ! command -v kind &> /dev/null; then
-    echo "Error: kind not found. Cannot create cluster."
-    return 1
-  fi
-
-  # Create a basic kind config
-  cat > /tmp/kind-config.yaml << EOF
-kind: Cluster
-apiVersion: kind.x-k8s.io/v1alpha4
-nodes:
-- role: control-plane
-  extraPortMappings:
-  - containerPort: 30080
-    hostPort: 30080
-EOF
-
-  # Create the cluster
-  echo "Creating kind cluster 'mlflow-dev'..."
-  kind create cluster --name mlflow-dev --config /tmp/kind-config.yaml --wait 2m
-
-  # Update kubeconfig
-  mkdir -p ~/.kube
-  kind get kubeconfig --name mlflow-dev > ~/.kube/config
-  chmod 600 ~/.kube/config
-  
-  echo "✅ Kind cluster 'mlflow-dev' created and configured."
-  echo "Kubernetes context set to kind-mlflow-dev"
-}
-
-# Check for kube config and offer to create kind cluster if none found
+# Check for kube config and warn if none found
 if [ ! -f ~/.kube/config ]; then
   echo "Warning: No Kubernetes config file found."
-  
-  # Check if USE_KIND is set to true
-  if [ "${USE_KIND:-}" = "true" ]; then
-    echo "USE_KIND is set, creating local Kind cluster..."
-    setup_kind_cluster
-  else
-    echo "To use a local Kind cluster, restart with:"
-    echo "USE_KIND=true task dev:shell"
-    echo ""
-    echo "Alternatively, ensure ~/.kube/config is mounted from host."
-  fi
+  echo "Ensure ~/.kube/config is mounted from host."
 else
   echo "Found Kubernetes config. Using existing configuration."
 fi
@@ -82,10 +39,10 @@ MLflow Development Environment
 - All required tools are pre-installed:
   * task, helm, kubectl, yq, jq, etc.
 - Use 'task --list' to see available tasks
-- Directories from host are mounted in /app
+- Directories from host are mounted in /workspace
 
 Kubernetes Setup:
-$(if [ "${USE_KIND:-}" = "true" ]; then echo "- Using local Kind cluster 'mlflow-dev'"; else echo "- Using host's Kubernetes config"; fi)
+- Using host's Kubernetes config
 
 Networking:
 - ${NETWORK_MODE}

applications/mlflow/DEVELOPMENT.md

@@ -13,7 +13,6 @@ Optional (for direct installation on your machine):
 - go (1.20+)
 - Helm
 - kubectl
-- [Kind](https://kind.sigs.k8s.io/) - Kubernetes in Docker (if running local Kubernetes)
 
 ## Development Workflow
 
@@ -41,13 +40,6 @@ task dev:start
 task dev:shell
 ```
 
-For development with Kind (Kubernetes in Docker), use:
-
-```bash
-# Enter the development container with Kind access
-task dev:shell:kind
-```
-
 The tasks above will:
 1. Build the development Docker image if needed
 2. Start a container with the proper mounts and environment
@@ -68,7 +60,7 @@ task helm:lint
 # Template the chart (no values overrides)
 task helm:template
 
-# Install the chart to a kind cluster
+# Install the chart to your Kubernetes cluster
 task helm:install-local
 
 # Run application tests
@@ -135,22 +127,6 @@ If you encounter issues with the container:
 - Restart it: `task dev:restart`
 - Rebuild the image if needed: `task dev:build-image`
 
-## Kubernetes Development with Kind
-
-The `dev:shell:kind` task creates a privileged container that can run Kind (Kubernetes in Docker). This allows you to:
-
-1. Create and manage a Kubernetes cluster inside the development container
-2. Test MLflow deployments in a realistic Kubernetes environment
-3. Use kubectl, helm, and other Kubernetes tools directly within the container
-
-To create a Kind cluster once inside the container:
-
-```bash
-kind create cluster --name mlflow-dev
-```
-
-This cluster can then be used to test your MLflow deployments in a Kubernetes environment that closely resembles production.
-
 ## Creating a Release
 
 When you're ready to publish your changes to the Replicated platform:
@@ -253,14 +229,6 @@ If you encounter issues with port forwarding:
 2. Try using a different port by specifying it when starting the service
 3. The development environment automatically tries ports 5000-5004 and will use the first available one
 
-### Kind Cluster Issues
-
-If you encounter issues with the Kind cluster:
-
-1. Make sure you're using the `dev:shell:kind` task which provides the necessary privileges
-2. If the cluster fails to start, try deleting it first: `kind delete cluster --name mlflow-dev`
-3. Check docker resource limits if you experience performance issues
-
 ## CI/CD Pipeline Integration
 
 For CI, we push the development image to ttl.sh with:

applications/mlflow/Taskfile.yml

@@ -94,14 +94,8 @@ tasks:
             echo "All standard ports are in use. Using a random port."
           fi
 
-          # Add privileged mode if USE_KIND is true
-          PRIVILEGED_ARG=""
-          if [ "${USE_KIND:-false}" = "true" ]; then
-            PRIVILEGED_ARG="--privileged"
-          fi
-
           # Start container with host networking for kubectl port-forward compatibility
-          CONTAINER_ID=$(docker run --name mlflow-dev-container --network host --privileged -d \
+          CONTAINER_ID=$(docker run --name mlflow-dev-container --network host -d \
             -v $(pwd):/workspace \
             -v ~/.kube:/home/devuser/.kube \
             -v ~/.helm:/home/devuser/.helm \
@@ -122,14 +116,6 @@ tasks:
           fi
         fi
 
-  dev:shell:
-    desc: Attach to development container shell
-    deps: [dev:ensure-running]
-    silent: true
-    cmds:
-      - echo "Connecting to mlflow-dev-container..."
-      - docker exec -it mlflow-dev-container /bin/bash
-
   dev:ensure-running:
     desc: Ensure the development container is running
     internal: true
@@ -145,42 +131,14 @@ tasks:
     status:
       - docker ps | grep -q "mlflow-dev-container"
 
-  dev:shell:kind:
-    desc: Start container with Kind Kubernetes cluster and attach to shell
-    deps: [dev:prepare-kind]
+  dev:shell:
+    desc: Attach to development container shell
+    deps: [dev:ensure-running]
     silent: true
     cmds:
-      - echo "Entering development container with Kind Kubernetes cluster..."
+      - echo "Connecting to mlflow-dev-container..."
       - docker exec -it mlflow-dev-container /bin/bash
 
-  dev:prepare-kind:
-    desc: Prepare the development container for Kind usage
-    internal: true
-    silent: true
-    cmds:
-      - echo "Preparing development container with Kind Kubernetes cluster..."
-      - |
-        if docker ps | grep -q "mlflow-dev-container"; then
-          echo "Container mlflow-dev-container is already running. Stopping it first..."
-          docker stop mlflow-dev-container
-          docker rm mlflow-dev-container
-        elif docker ps -a | grep -q "mlflow-dev-container"; then
-          echo "Container mlflow-dev-container exists but is not running. Removing it..."
-          docker rm mlflow-dev-container
-        fi
-        
-        # Start container with host networking and privileged mode for Kind
-        docker run --name mlflow-dev-container --network host --privileged -d \
-          -v $(pwd):/workspace \
-          -v ~/.replicated:/home/devuser/.replicated \
-          -e SHELL=/bin/bash \
-          -e HOME=/home/devuser \
-          -e USER=devuser \
-          -e USE_KIND=true \
-          -e HOST_NETWORK=true \
-          -w /workspace \
-          {{.DEV_IMAGE}} sleep infinity
-
   dev:stop:
     desc: Stop development container
     silent: true