From 9d3f31a990ac8a422a4be6d64530cdf92bbea985 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Mon, 23 Oct 2017 14:04:21 -0700 Subject: [PATCH] Rephrase core group. (#6024) --- docs/concepts/overview/kubernetes-api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/overview/kubernetes-api.md b/docs/concepts/overview/kubernetes-api.md index e953a7e56a..24bfe2d01e 100644 --- a/docs/concepts/overview/kubernetes-api.md +++ b/docs/concepts/overview/kubernetes-api.md @@ -73,8 +73,8 @@ The API group is specified in a REST path and in the `apiVersion` field of a ser Currently there are several API groups in use: -1. The "core" (oftentimes called "legacy", due to not having explicit group name) group, which is at - REST path `/api/v1` and is not specified as part of the `apiVersion` field, e.g. `apiVersion: v1`. +1. The *core* group, often referred to as the *legacy group*, is at the REST path `/api/v1` and uses `apiVersion: v1`. + 1. The named groups are at REST path `/apis/$GROUP_NAME/$VERSION`, and use `apiVersion: $GROUP_NAME/$VERSION` (e.g. `apiVersion: batch/v1`). Full list of supported API groups can be seen in [Kubernetes API reference](/docs/reference/).