From ad27bd7200572c3b839b969d7e46b3232dbfec54 Mon Sep 17 00:00:00 2001 From: Saylor Berman Date: Mon, 7 Aug 2023 11:15:27 -0600 Subject: [PATCH] More name changes --- docs/proposals/control-plane-config.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/proposals/control-plane-config.md b/docs/proposals/control-plane-config.md index 9f64657cf7..954f2c41bc 100644 --- a/docs/proposals/control-plane-config.md +++ b/docs/proposals/control-plane-config.md @@ -37,22 +37,23 @@ Proposed configuration CRD example: ```yaml apiVersion: gateway.nginx.org/v1alpha1 -kind: NGINXControlConfig +kind: NginxGateway metadata: - name: nkg-config + name: nginx-gateway-config namespace: nginx-gateway spec: - log: + logging: level: info ... status: + conditions: ... ``` - The CRD would be Namespace-scoped, living in the same Namespace as the controller that it applies to. - CRD is initialized and created when NKG is deployed. -- NKG references the name of this CRD via CLI arg, and only watches this CRD. If the resource doesn't exist, -then an error is logged and event created, and default values are used. +- NKG references the name of this CRD via CLI arg (`--nginx-gateway-config-name`), and only watches this CRD. + If the resource doesn't exist, then an error is logged and event created, and default values are used. - If user deletes resource, NKG logs an error and creates an event. NKG will revert to default values. This resource won't be referenced in the `parametersRef` of the GatewayClass, reserving that option for a data