Empowering Developers to Troubleshoot Kubernetes Apps
Debugging and troubleshooting Kubernetes (K8s) applications are fundamental skills for DevOps, Site Reliability Engineers (SREs), and Platform Engineers. These roles typically possess elevated permissions that enable them to access the necessary tools and resources. However, it is crucial to extend these capabilities to the organization’s developers without compromising security.
Enter self-hosted Kubeshark— a solution that allows DevOps to empower developers with collaborative and secure debugging and troubleshooting capabilities.
Unveiling Real-time Visibility
Kubeshark is a powerful tool that grants real-time, identity-aware, and cluster-wide visibility into the K8s network. It’s where all business-logic transactions execute. By providing such visibility, Kubeshark becomes a critical asset for identifying security threats and uncovering performance issues lurking within K8s.
The CLI Option: Perfect for DevOps
Kubeshark offers a command-line interface (CLI) option, leveraging kubectl access and offering a choice between port-forward and K8s proxy to launch a local dashboard.
This CLI option is particularly well-suited for DevOps who possess kubectl access and require an immediate troubleshooting solution. With Kubeshark, DevOps can start analyzing traffic within minutes, facilitating faster issue resolution.
Empowering Developers
While the CLI option benefits DevOps, there are significant advantages to enabling developers with the same debugging and troubleshooting capabilities. However, granting developers elevated access permissions can compromise security. This is where self-hosting Kubeshark becomes indispensable.
Self-hosted Kubeshark
By enabling Ingress, organizations can provide developers with a secure and performant way to access Kubeshark. Enabling Ingress exposes a web service accessible via an external IP or load-balancer. Developers can effortlessly point their web browsers to the Ingress’ IP or domain name and access Kubeshark remotely, ensuring a seamless debugging experience.
Authentication Without RBAC or Kubectl Permissions
Once Kubeshark is installed with Ingress enabled, developers can authenticate using their corporate ID, without requiring K8s credentials or kubectl access. This approach enhances security by eliminating the need to share sensitive credentials while still granting developers the debugging and troubleshooting capabilities they need.
Achieving Performance and Stability
Ingress is lightweight and guarantees a more stable experience, compared to port-forward or K8s proxy, ensuring uninterrupted debugging and troubleshooting sessions.
You can read more about how to set up Ingress in this article.
Conclusion
In conclusion, K8s debugging and troubleshooting capabilities are essential for DevOps, SREs, and platform engineers. Kubeshark delivers these capabilities by providing real-time, identity-aware, and cluster-wide visibility into the K8s network.
By self-hosting Kubeshark, DevOps can extend the same capabilities to developers and security engineers, empowering them to effectively debug and troubleshoot applications without compromising security.
By installing Kubeshark and enabling Ingress, organizations can establish a secure and performant environment where developers can access Kubeshark using their corporate ID.
Embrace the power of Kubeshark and unlock collaborative, secure debugging, and troubleshooting capabilities for your entire organization.
