#FAQs

#0x00: Origin of name

Question: Why is it named k8z?

Answer: The name k8z is inspired by healthz/livez/readyz etc. k8z is short for kubernetez — shorter and easier to remember.

It historically comes from Google's internal practices. They're called "z-pages".

The reason it ends with z is to reduce collisions with actual application endpoints with the same name (like /status). See this talk for more: https://vimeo.com/173610242

Similar endpoints (at least inside Google) are /varz, /statusz, /rpcz. Services developed at Google automatically get these endpoints to export their health and metrics and there are tools that collect the exposed metrics/statuses from all the deployed services.

Open source tools like Prometheus implement this pattern (since original authors of Prometheus are also ex-Googlers) by coming to a well-known endpoint to collect metrics from your application. Similarly OpenCensus allows you to expose z-pages from your app (ideally on a different port) to diagnose problems.

#0x01: About credentials safety

Question: How do you keep my Kubernetes cluster access credentials (kubeconfig) secure?

Answer: Our application is open source, inviting everyone to examine its inner workings, including its handling of API credentials. This transparency ensures that there are no hidden functions that compromise security. You can get the source code from our GitHub repository: k8z source code on GitHub.