status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-15 08:14:54 +00:00
Code Issues Projects Releases Wiki Activity

proposed language about why there is no <CE>.meta.partition field

Browse Source
This commit is contained in:
trujillo-adam 2022-01-03 14:40:03 -08:00
parent 2f4fae73d1
commit 65cb869c5b
3 changed files with 89 additions and 94 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/content/docs/connect/config-entries/mesh.mdx
View File

@ -77,7 +77,6 @@ kind: Mesh
metadata:
name: mesh
namespace: default
partition: default
spec:
transparentProxy:
meshDestinationsOnly: true
@ -99,6 +98,8 @@ spec:
</Tab>
</Tabs>
Note that the Kuberetes example does not include a `partition` field. Configuration entries are applied on Kubernetes using [custom resource definitions (CRD)](/docs/k8s/crds), which can only reference their own partition.
## Available Fields
<ConfigEntryReference
@ -149,13 +150,7 @@ spec:
name: 'namespace',
enterprise: true,
description:
'Must be set tot `default`. If running Consul Open Source, the namespace is ignored (see [Kubernetes Namespaces in Consul OSS](/docs/k8s/crds#consul-oss)). If running Consul Enterprise see [Kubernetes Namespaces in Consul Enterprise](/docs/k8s/crds#consul-enterprise) for additional information.',
},
{
name: 'partition',
enterprise: true,
description:
'Specifies the admin partition in which the configuration will apply. The current partition is used if unspecified. Refer to the [Admin Partitions documentation](/docs/enterprise/admin-partitions) for details. The partitions parameter is not supported in Consul OSS.',
'Must be set to `default`. If running Consul Open Source, the namespace is ignored (see [Kubernetes Namespaces in Consul OSS](/docs/k8s/crds#consul-oss)). If running Consul Enterprise see [Kubernetes Namespaces in Consul Enterprise](/docs/k8s/crds#consul-enterprise) for additional information.',
},
],
hcl: false,

6
website/content/docs/connect/config-entries/service-defaults.mdx
View File

@ -273,7 +273,6 @@ spec:
'Specifies the name of the admin partition in which the configuration entry applies. Refer to the [Admin Partitions documentation](/docs/enterprise/admin-partitions) for additional information.',
yaml: false,
},
{
name: 'Meta',
type: 'map<string|string>: nil',
@ -353,8 +352,7 @@ spec:
{
name: 'Protocol',
type: 'string: ""',
description:
`The protocol for the upstream listener.<br><br>
description: `The protocol for the upstream listener.<br><br>
NOTE: The protocol of a service should ideally be configured via the
[\`protocol\`](/docs/connect/config-entries/service-defaults#protocol)
field of a
@ -702,7 +700,7 @@ spec:
],
},
],
}
},
]}
/>

12
website/content/docs/connect/config-entries/service-resolver.mdx
View File

@ -246,14 +246,16 @@ spec:
name: 'Namespace',
type: `string: "default"`,
enterprise: true,
description: 'Specifies the namespace in which the configuration entry will apply.',
description:
'Specifies the namespace in which the configuration entry will apply.',
yaml: false,
},
{
name: 'Partition',
type: `string: "default"`,
enterprise: true,
description: 'Specifies the admin partition in which the configuration entry will apply.',
description:
'Specifies the admin partition in which the configuration entry will apply.',
yaml: false,
},
{
@ -355,20 +357,20 @@ spec:
enterprise: true,
type: 'string: ""',
description:
'Specifies the source namespace to resolve the service from.',
'Specifies the destination namespace to resolve the service from.',
},
{
name: 'Partition',
enterprise: true,
type: 'string: ""',
description:
'Specifies the source admin partition to resolve the service from.',
'Specifies the destination admin partition to resolve the service from.',
},
{
name: 'Datacenter',
type: 'string: ""',
description:
'Specifies the source datacenter to resolve the service from.',
'Specifies the destination datacenter to resolve the service from.',
},
],
},