skills/asmayaseen/operating-k8s-local/SKILL.md
Operates local Kubernetes clusters with Minikube for development and testing. Use when setting up local K8s, deploying applications locally, or debugging K8s issues. Covers Minikube, kubectl essentials, local image loading, and networking.
npx skillsauth add aiskillstore/marketplace operating-k8s-localInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
# Start cluster with resources
minikube start --memory=8192 --cpus=4
# Enable essential addons
minikube addons enable ingress
minikube addons enable metrics-server
# Point Docker to Minikube
eval $(minikube docker-env)
# Build and deploy
docker build -t myapp:local .
kubectl apply -f k8s/
minikube start # Start with defaults
minikube start --memory=8192 --cpus=4 # With resources
minikube start --driver=docker # Specific driver
minikube status # Check status
minikube stop # Stop (preserves state)
minikube delete # Delete completely
minikube start -p my-cluster # Named cluster
minikube profile my-cluster # Switch clusters
minikube profile list # List all
minikube addons list # List available
minikube addons enable ingress # REQUIRED for external access
minikube addons enable metrics-server # For kubectl top
minikube addons enable dashboard # Web UI
minikube addons enable storage-provisioner # For PVCs
# Method 1: NodePort
minikube service my-service --url
# Method 2: LoadBalancer (requires tunnel)
minikube tunnel # Run in separate terminal
# Method 3: Port forward
kubectl port-forward svc/my-service 8080:80
# Point to Minikube's Docker
eval $(minikube docker-env)
# Build directly into Minikube
docker build -t my-app:local .
# Use imagePullPolicy: Never in manifests
# Reset to local Docker
eval $(minikube docker-env -u)
kubectl config current-context # Current context
kubectl config get-contexts # List all
kubectl config use-context minikube # Switch
kubectl config set-context --current --namespace=my-ns # Set default ns
kubectl get pods # Current namespace
kubectl get pods -A # All namespaces
kubectl get pods -o wide # With node/IP
kubectl get all # All resources
kubectl describe pod my-pod # Detailed info
kubectl get events --sort-by='.lastTimestamp' # Recent events
kubectl logs my-pod # Current logs
kubectl logs my-pod -f # Follow
kubectl logs my-pod -c container # Specific container
kubectl logs my-pod --previous # After crash
kubectl logs my-pod --tail=50 # Last 50 lines
kubectl apply -f manifest.yaml
kubectl create deployment nginx --image=nginx
kubectl create configmap my-config --from-literal=key=value
kubectl create secret generic my-secret --from-literal=password=secret
# Generate YAML
kubectl create deployment nginx --image=nginx --dry-run=client -o yaml
kubectl edit deployment my-deploy
kubectl scale deployment my-deploy --replicas=3
kubectl set image deployment/my-deploy container=image:v2
kubectl rollout restart deployment/my-deploy
kubectl exec -it my-pod -- /bin/sh # Shell into pod
kubectl exec my-pod -- env # Run command
kubectl port-forward pod/my-pod 8080:80 # Forward port
kubectl top pods # Resource usage
kubectl top nodes
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-deploy
spec:
replicas: 3
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: main
image: my-app:local
imagePullPolicy: Never # For local images
ports:
- containerPort: 8000
livenessProbe:
httpGet:
path: /health
port: 8000
initialDelaySeconds: 30
readinessProbe:
httpGet:
path: /health
port: 8000
initialDelaySeconds: 5
apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
type: ClusterIP # or NodePort, LoadBalancer
selector:
app: my-app
ports:
- port: 80
targetPort: 8000
apiVersion: v1
kind: ConfigMap
metadata:
name: my-config
data:
DATABASE_HOST: postgres
DATABASE_PORT: "5432"
---
apiVersion: v1
kind: Secret
metadata:
name: my-secret
type: Opaque
stringData:
password: mysecretpassword
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: my-ingress
spec:
ingressClassName: nginx
rules:
- host: myapp.local
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: my-service
port:
number: 80
# 1. Start Minikube
minikube start --memory=8192 --cpus=4
# 2. Enable addons
minikube addons enable ingress
minikube addons enable metrics-server
# 3. Point to Minikube Docker
eval $(minikube docker-env)
# 4. Build images
docker build -t myapp/api:local ./api
docker build -t myapp/web:local ./web
# 5. Deploy
kubectl apply -f k8s/
# 6. Access
minikube service myapp-web --url
# Or with ingress:
echo "$(minikube ip) myapp.local" | sudo tee -a /etc/hosts
# Pod not starting?
kubectl describe pod my-pod # Check Events section
# Container crashing?
kubectl logs my-pod --previous # Logs from crashed container
# Network issues?
kubectl exec -it my-pod -- nslookup my-service
kubectl exec -it my-pod -- wget -qO- http://my-service:80
# Resource issues?
kubectl top pods
kubectl top nodes
Run: python scripts/verify.py
containerizing-applications - Docker and Helm chartsdeploying-cloud-k8s - Cloud Kubernetes deploymentdevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.