From b914d0037782ea2fdaa4592418f17ab4a4cdb68e Mon Sep 17 00:00:00 2001 From: Michael Nairn Date: Wed, 15 Nov 2023 15:41:25 +0000 Subject: [PATCH] Fix docs mgc-kuadrant-add-on-manager -> mgc-add-on-manager Remove old rbac manifests from bundle: mgc-dnsrecord-editor-role_rbac.authorization.k8s.io_v1_clusterrole.yaml mgc-dnsrecord-viewer-role_rbac.authorization.k8s.io_v1_clusterrole.yaml Doesn't look like `make bundle` removes old manifests. --- ...c.authorization.k8s.io_v1_clusterrole.yaml | 31 ------------------- ...c.authorization.k8s.io_v1_clusterrole.yaml | 27 ---------------- .../control-plane-installation.md | 4 +-- 3 files changed, 2 insertions(+), 60 deletions(-) delete mode 100644 bundle/manifests/mgc-kuadrant-dnsrecord-editor-role_rbac.authorization.k8s.io_v1_clusterrole.yaml delete mode 100644 bundle/manifests/mgc-kuadrant-dnsrecord-viewer-role_rbac.authorization.k8s.io_v1_clusterrole.yaml diff --git a/bundle/manifests/mgc-kuadrant-dnsrecord-editor-role_rbac.authorization.k8s.io_v1_clusterrole.yaml b/bundle/manifests/mgc-kuadrant-dnsrecord-editor-role_rbac.authorization.k8s.io_v1_clusterrole.yaml deleted file mode 100644 index 1265ec1c5..000000000 --- a/bundle/manifests/mgc-kuadrant-dnsrecord-editor-role_rbac.authorization.k8s.io_v1_clusterrole.yaml +++ /dev/null @@ -1,31 +0,0 @@ -apiVersion: rbac.authorization.k8s.io/v1 -kind: ClusterRole -metadata: - creationTimestamp: null - labels: - app.kubernetes.io/component: rbac - app.kubernetes.io/created-by: multicluster-gateway-controller - app.kubernetes.io/instance: dnsrecord-editor-role - app.kubernetes.io/managed-by: kustomize - app.kubernetes.io/name: clusterrole - app.kubernetes.io/part-of: multicluster-gateway-controller - name: mgc-kuadrant-dnsrecord-editor-role -rules: -- apiGroups: - - kuadrant.io - resources: - - dnsrecords - verbs: - - create - - delete - - get - - list - - patch - - update - - watch -- apiGroups: - - kuadrant.io - resources: - - dnsrecords/status - verbs: - - get diff --git a/bundle/manifests/mgc-kuadrant-dnsrecord-viewer-role_rbac.authorization.k8s.io_v1_clusterrole.yaml b/bundle/manifests/mgc-kuadrant-dnsrecord-viewer-role_rbac.authorization.k8s.io_v1_clusterrole.yaml deleted file mode 100644 index 5b029f926..000000000 --- a/bundle/manifests/mgc-kuadrant-dnsrecord-viewer-role_rbac.authorization.k8s.io_v1_clusterrole.yaml +++ /dev/null @@ -1,27 +0,0 @@ -apiVersion: rbac.authorization.k8s.io/v1 -kind: ClusterRole -metadata: - creationTimestamp: null - labels: - app.kubernetes.io/component: rbac - app.kubernetes.io/created-by: multicluster-gateway-controller - app.kubernetes.io/instance: dnsrecord-viewer-role - app.kubernetes.io/managed-by: kustomize - app.kubernetes.io/name: clusterrole - app.kubernetes.io/part-of: multicluster-gateway-controller - name: mgc-kuadrant-dnsrecord-viewer-role -rules: -- apiGroups: - - kuadrant.io - resources: - - dnsrecords - verbs: - - get - - list - - watch -- apiGroups: - - kuadrant.io - resources: - - dnsrecords/status - verbs: - - get diff --git a/docs/installation/control-plane-installation.md b/docs/installation/control-plane-installation.md index 543abeeae..38a0ae5e0 100644 --- a/docs/installation/control-plane-installation.md +++ b/docs/installation/control-plane-installation.md @@ -62,11 +62,11 @@ In addition to the MGC, this will also install the Kuadrant add-on manager and a After the configuration has been applied, you can verify that the MGC and add-on manager have been installed and are running: ```bash -kubectl wait --timeout=5m -n multicluster-gateway-controller-system deployment/mgc-controller-manager deployment/mgc-kuadrant-add-on-manager --for=condition=Available +kubectl wait --timeout=5m -n multicluster-gateway-controller-system deployment/mgc-controller-manager deployment/mgc-add-on-manager --for=condition=Available ``` ``` deployment.apps/mgc-controller-manager condition met -deployment.apps/mgc-kuadrant-add-on-manager condition met +deployment.apps/mgc-add-on-manager condition met ``` We can also verify that the `GatewayClass` has been accepted by the MGC: