Setup

1. Read cluster config: Read dev_env/.env to get:

   • DATASPOKE_DEV_KUBE_CLUSTER — kube context (e.g., docker-desktop)
   • DATASPOKE_DEV_KUBE_DATAHUB_NAMESPACE — DataHub namespace (e.g., datahub-01)
   • DATASPOKE_DEV_KUBE_DATASPOKE_NAMESPACE — DataSpoke namespace (e.g., dataspoke-01)
   • DATASPOKE_DEV_KUBE_DUMMY_DATA_NAMESPACE — Example sources namespace (e.g., dummy-data1)

2. Verify prerequisites:

bash
1kubectl version --client
2kubectl config current-context   # confirm correct context
3kubectl get nodes                 # confirm cluster access

If tools are missing or cluster is unreachable, stop and inform the user.

Execution Strategy for $ARGUMENTS

Before acting: identify the operation type from $ARGUMENTS — read, create, modify, or delete.

Read operations (safe, execute immediately):

bash
1kubectl get <type> -n <namespace>
2kubectl describe <type> <name> -n <namespace>
3kubectl logs <pod> -n <namespace> --tail=100
4kubectl get events -n <namespace> --sort-by='.lastTimestamp'
5helm status <release> -n <namespace>
6helm history <release> -n <namespace>
7helm get values <release> -n <namespace>

Create/apply operations (use dry-run first):

bash
1# Validate first
2kubectl apply -f <file.yaml> --dry-run=server
3
4# Then apply
5kubectl apply -f <file.yaml> -n <namespace>

Modify operations (confirm intent, then execute):

bash
1kubectl rollout restart deployment/<name> -n <namespace>
2helm upgrade <release> <chart> -n <namespace> -f <values.yaml>

Delete operations — always follow this safety workflow:

bash
1# 1. Confirm you're in the right context
2kubectl config current-context
3
4# 2. Describe before deleting
5kubectl describe <type> <name> -n <namespace>
6
7# 3. Delete
8kubectl delete <type> <name> -n <namespace>
9
10# 4. Verify
11kubectl get <type> -n <namespace>

Never delete namespaces. For scale-to-zero or namespace-level destructive operations, confirm with the user first.

Report Results

After every operation, summarize:

• What was executed
• What changed (before/after state if relevant)
• Any warnings, errors, or events triggered
• Suggested next steps if issues are found

For errors, consult reference.md for common causes and resolutions.

See reference.md for helm chart management, resource creation patterns, capacity planning, and error reference.