Get the latest tech news
How to Prevent Panics
You pushed a small change to the Kubernetes cluster. It broke the production environment. You became famous in your company, but you quickly fixed the issue. Now it's time to analyse the root cause! Welcome to the post-mortem!
This is the second of a three-part series about how a missing Go test in the NGINX Ingress Controller puts thousands of Kubernetes clusters at risk. You specify the policy type ( apiKey), the place for the API key ( header or query), and the Secret’s name ( clientSecret). You run the kubectl CLI tool, pipe output to the jq app and filter the spec section.
Or read this on Hacker News