From 624a9be0bee8cd727c26d80c8ab77ec80b9be3fa Mon Sep 17 00:00:00 2001 From: ChrsMark Date: Wed, 27 Nov 2024 14:23:47 +0200 Subject: [PATCH] fix feature gate names Signed-off-by: ChrsMark --- docs/non-normative/k8s-migration.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/docs/non-normative/k8s-migration.md b/docs/non-normative/k8s-migration.md index e1baef1690..fc8c61bf17 100644 --- a/docs/non-normative/k8s-migration.md +++ b/docs/non-normative/k8s-migration.md @@ -29,12 +29,15 @@ updated to the stable K8s semantic conventions, they: Specifically for the Opentelemetry Collector: The transition will happen through two different feature gates. -One for enabling the new schema called `semconv.k8s.stable`, -and one for disabling the old schema called `semconv.k8s.legacy`. Then: - -- On alpha the old schema is enabled, while the new schema is disabled -- On beta/stable the old schema is disabled, while the new is enabled -- It is an error to disable both +One for enabling the new schema called `semconv.k8s.enableStable`, +and one for disabling the old schema called `semconv.k8s.disableLegacy`. Then: + +- On alpha the old schema is enabled by default (`semconv.k8s.disableLegacy` defaults to false), + while the new schema is disabled (`semconv.k8s.enableStable` defaults to false). +- On beta/stable the old schema is disabled by default (`semconv.k8s.disableLegacy` defaults to true), + while the new is enabled by default (`semconv.k8s.enableStable` defaults to true). +- It is an error to disable both schemas +- Both schemas can enabled with `--feature-gates=-semconv.disableLegacy,+semconv.k8s.enableStable`.