From b1d73bee0a32cb39b89dcbc5014e999dedef1543 Mon Sep 17 00:00:00 2001 From: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> Date: Tue, 19 Oct 2021 15:27:23 -0700 Subject: [PATCH] Apply suggestions from code review Applying some of the feedback from review Co-authored-by: Freddy Co-authored-by: David Yu --- website/content/commands/admin-partition.mdx | 6 +++--- website/content/docs/enterprise/admin-partitions.mdx | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/website/content/commands/admin-partition.mdx b/website/content/commands/admin-partition.mdx index c889eee1a5..e7c5095cf6 100644 --- a/website/content/commands/admin-partition.mdx +++ b/website/content/commands/admin-partition.mdx @@ -42,7 +42,7 @@ Usage: consul admin-partition [options] [args] Read an admin partition: - $ consul admin-partition read ns1 + $ consul admin-partition read team1 List all admin partitions: @@ -54,7 +54,7 @@ Usage: consul admin-partition [options] [args] Delete an admin partition: - $ consul admin-partition delete ns1 + $ consul admin-partition delete team1 For more examples, ask for subcommand help or view the documentation. ``` @@ -214,7 +214,7 @@ consul admin-partition delete webdev ## Admin Partition Definition -Namespaces are managed exclusively through the HTTP API and the Consul CLI. The HTTP API accepts only JSON formatted definitions while the CLI will parse either JSON or HCL. +Admin partitions are managed exclusively through the HTTP API and the Consul CLI. The HTTP API accepts only JSON formatted definitions while the CLI will parse either JSON or HCL. The following parameters are supported in admin partition defintion files: diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 5d74b2c4e0..5974572579 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -60,7 +60,7 @@ Your Consul configuration must meet the following requirements to use admin part * The agent token used by the client agent will need to allow `node:write` in the admin partition. * The `read` permission for `proxy-defaults` require `admin_partition:read` for the specific partition. The `write` permission for proxy-defaults require `mesh:write`. See [Admin Partition Rules](/docs/security/acl/acl-rules#admin-partition-rules) for additional information -* The write permissions for ingress and terminating gateways must be `operator:write`. +* The write permissions for ingress and terminating gateways must be `mesh:write`. * Existing intentions must be set to `deny` all traffic from outside the admin partition. * Wildcards (`*`) are not supported when creating intentions for admin partitions. @@ -122,7 +122,7 @@ Verify that your Consul deployment meets the [Kubernetes Requirements](#kubernet 1. Create the license secret in each cluster, e.g.: ```shell-session - kubectl create secret generic license --from-literal=key= +kubectl create secret generic license --from-file=key=[license file path i.e. ./license.hclic] ``` This step must also be completed for each workload cluster. @@ -175,7 +175,7 @@ Verify that your Consul deployment meets the [Kubernetes Requirements](#kubernet global: enabled: false enableConsulNamespaces: true - image: hashicorp/consul-enterprise:1.11.0-ent-alpha + image: hashicorp/consul-enterprise:1.11.0-ent-beta1 adminPartitions: enabled: true name: "clients" // partition name @@ -193,7 +193,7 @@ Verify that your Consul deployment meets the [Kubernetes Requirements](#kubernet secretKey: key externalServers: enabled: true - hosts: "35.192.119.38" + hosts: "35.192.119.38" # Insert External IP of LoadBalancer here tlsServerName: server.dc1.consul client: enabled: true