Troubleshooting

This section covers common issues encountered during deployment on Amazon EKS and self-managed Kubernetes environments.

AWS EKS Deployment

Check Pod Logs

For umbrella chart deployments, check logs using the shared namespace:

NAMESPACE=zilla-platform

# Control plane
kubectl logs -n $NAMESPACE -l app.kubernetes.io/component=control

# Management plane
kubectl logs -n $NAMESPACE -l app.kubernetes.io/component=management

# Console
kubectl logs -n $NAMESPACE -l app.kubernetes.io/component=console

Individual Charts:

# Control plane
kubectl logs -n zilla-platform-control -l app.kubernetes.io/component=control

# Management plane
kubectl logs -n zilla-platform-management -l app.kubernetes.io/component=management

# Console
kubectl logs -n zilla-platform-console -l app.kubernetes.io/component=console

Verify Ingress Status

kubectl get ingress -A
kubectl describe ingress -A

Common Issues

Ingress not getting an address: Ensure the AWS Load Balancer Controller is running and the IAM permissions are correct.
Pods stuck in Pending: Check if the storage class is available and EBS CSI driver is installed.
```
kubectl describe pod -n <NAMESPACE> <pod-name>
```
SSL certificate errors: Verify the ACM certificate ARN is correct and the certificate is in the same region as your cluster.
DNS resolution failures: Ensure the private hosted zone is associated with the correct VPC.

On-Prem and Local Deployment

Ingress not accessible

Ensure NGINX Ingress Controller is running:

kubectl get pods -n ingress-nginx

If not running, reinstall:

kubectl delete namespace ingress-nginx
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/cloud/deploy.yaml

Pods stuck in Pending

Check if there are resource constraints:

kubectl describe pod -n zilla-platform <pod-name>

Increase Docker Desktop resources:

Open Docker Desktop
Go to Settings → Resources
Increase CPU and Memory
Click Apply & Restart

DNS resolution issues

Verify /etc/hosts entries:

cat /etc/hosts | grep localhost

Should include:

127.0.0.1 console.localhost management.localhost control.localhost platform.localhost

Connection refused errors

Ensure the ingress controller is exposing port 80:

kubectl get svc -n ingress-nginx

The ingress-nginx-controller service should have TYPE: LoadBalancer and show localhost:80.