The Kubernetes Operator has been improved to allow secure access to the Kubernetes API from anywhere, using a single CRD (Custom Resource Definition) and without compromising with kube proxy and curl. This feature enables users to set up token-based RBAC (Role-Based Access Control), install the ngrok Kubernetes Operator, apply an `AgentEndpoint` resource, and then access their cluster's API remotely using ngrok. The process involves setting up authentication and authorization, reserving a domain, installing the operator, configuring environment variables, and annotating the `kubernetes` service to declare the backend as an HTTPS upstream. Users can also view K8s API requests with Traffic Inspector observability and set access control with Traffic Policy, allowing them to filter, orchestrate, and take action on traffic as it passes through the network. With this setup, users can control their clusters independent of where they are or what networks they must traverse, while adding additional security layers that simply can't be achieved with built-in options.