Troubleshooting¶

Common issues and solutions for Obsyk.

Operator Issues¶

Operator Pod Not Starting¶

Symptoms: Pod stuck in Pending or CrashLoopBackOff

Check pod status:

kubectl describe pod -n obsyk-system -l app=obsyk-operator

Common causes:

1. Missing credentials secret

   kubectl get secret -n obsyk-system obsyk-credentials
   

   Solution: Create the secret with correct credentials

2. Resource limits too low Check events for OOMKilled and increase memory limits

3. Image pull errors Verify network access to container registry

Cluster Shows Disconnected¶

Symptoms: Cluster status is "Disconnected" in dashboard

Check operator logs:

kubectl logs -n obsyk-system -l app=obsyk-operator --tail=100

Common causes:

1. Authentication failure
2. Look for "401" or "authentication" errors in logs
3. Verify client ID and secret are correct

4. Regenerate credentials if needed

5. Network connectivity

   kubectl exec -n obsyk-system -it $(kubectl get pod -n obsyk-system -l app=obsyk-operator -o jsonpath='{.items[0].metadata.name}') -- curl -I https://api.obsyk.ai/health
   

   Solution: Check firewall rules, proxy settings

6. TLS certificate issues

7. Ensure cluster time is synchronized
8. Check for certificate expiry errors

Missing Resources in Dashboard¶

Symptoms: Some namespaces or resources don't appear

Common causes:

1. Namespace filtering Check if namespace selector is configured:

   kubectl get cm -n obsyk-system obsyk-operator-config -o yaml
   

2. RBAC permissions Verify operator has required permissions:

   kubectl auth can-i list pods --as=system:serviceaccount:obsyk-system:obsyk-operator -A
   

3. Sync delay New resources may take a few seconds to appear. Wait and refresh.

Dashboard Issues¶

Cannot Log In¶

1. Clear browser cookies for *.obsyk.ai
2. Try incognito mode to rule out extensions
3. Check browser console for errors

Slow Loading¶

1. Large clusters with many resources may take longer
2. Check network connection to app.obsyk.ai
3. Try different browser or disable extensions

Getting Help¶

If issues persist:

1. Gather logs:

   kubectl logs -n obsyk-system -l app=obsyk-operator > operator-logs.txt
   

2. Note your cluster details:

3. Kubernetes version
4. Cloud provider

5. Operator version

6. Open an issue on GitHub with the above information