Prefixing Kubernetes Terms to Reduce Ambiguity

General Discussions
,
1

Using Kubernetes can sometimes feel like a guessing game. Terms like “Service,” “API Server,” “Scheduler,” “Job,” and “Namespace” are used everywhere in tech, and their meanings aren’t always clear when you’re working within Kubernetes. This can be confusing.

I understand these names have belonged to the industry and already have vast adoption. They also allow people to learn k8s without learning too many new terms.

  • But, to prevent confusion while using this term, how about prefixing the Kubernetes Resources with “K”.
  • We’d have “K-Service”, “K-API Server”, “K-Scheduler”, “K-Job”, “K-Namespace” etc.
  • This prefix could be optional, so that you can bring clarity as and when needed.

It’s short, simple and consistent.

Please do reply with feedback and suggestions.

2

In what context do you want to clarify? In kubernetes docs we typically capitalize them (“Service”, “Node”) and for API types we use code-format (Service, Node).

Unfortunately, we can’t change it in the actual APIs, so the best we can do is clarify when we speak.

The prefix “kube” (“kube service” or “kube node”) is pretty commonly used to disambiguate.