kubernetes

Use kubectl logs to retrieve pod logs: kubectl logs <pod-name> [-c <container-name>]. Add -A to search across all namespaces, or use --previous to view logs from a crashed container. This read-only command is safe for observability without altering cluster state.

Use safe kubectl commands: kubectl get to list resources, kubectl describe to inspect details, kubectl logs for application output, and kubectl port-forward to access services locally. These read-only operations enable full debugging while enforcing a non-destructive operational policy.

Yes, kubectl port-forward safely tunnels traffic from a local port to a pod or service: kubectl port-forward <pod-name> <local-port>:<pod-port>. This enables debugging and testing without exposing services externally or modifying cluster configuration.

Use kubectl get pods -A to list all pods across namespaces, then kubectl describe pod <pod-name> for detailed resource information including events, conditions, and configuration. These commands provide complete observability for cluster monitoring and troubleshooting.

Deletions and other destructive actions are explicitly forbidden to maintain cluster integrity. This approach enforces read-only operations focused on viewing, monitoring, and debugging resources safely without unintended modifications to running infrastructure.