luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

removed Consul requirements from documentation as it may be confusing (#15958) 

* removed Consul requirements from documentation as it may be confusing
This commit is contained in:
Michael Wilkerson 2023-01-11 21:01:30 -08:00 committed by GitHub
parent 04673cb6e4
commit d224744f6a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 11 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/connect/config-entries/exported-services.mdx
View File

@ -18,8 +18,6 @@ To configure Consul to export services contained in a Consul Enterprise admin pa
You can configure the settings defined in the `exported-services` configuration entry to apply to all namespaces in a Consul Enterprise admin partition.
## Requirements
- A 1.11.0+ Consul Enterprise binary or a 1.13.0+ Consul OSS binary.
- **Enterprise Only**: A corresponding partition that the configuration entry can export from. For example, the `exported-services` configuration entry for a partition named `frontend` requires an existing `frontend` partition.
## Usage

5
website/content/docs/connect/config-entries/ingress-gateway.mdx
View File

@ -17,11 +17,6 @@ Refer to the [Kubernetes Ingress Gateway](/docs/k8s/connect/ingress-gateways) do
For other platforms, see [Ingress Gateway](/docs/connect/gateways/ingress-gateway).
## Requirements
- Consul versions 1.8.4+ is required to use the `IngressGateway` custom resource on Kubernetes.
- Consul versions 1.8.0+ is required to use the `ingress-gateway` custom resource on all other platforms.
## Usage
1. Verify that your datacenter meets the conditions specified in the [Requirements](#requirements).

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

@ -22,12 +22,6 @@ with the [`service-defaults`](/docs/connect/config-entries/service-defaults)
configuration entry `kind` or for individual proxy instances in their [sidecar
service definitions](/docs/connect/registration/sidecar-service).
## Requirements
The following Consul binaries are supported:
* Consul 1.8.4+ on Kubernetes.
* Consul 1.5.0+ on other platforms.
## Usage
1. Verify that your datacenter meets the conditions specified in the [Requirements](#requirements).

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

@ -6,10 +6,6 @@ description: >-
---
# Service Defaults Configuration Entry
-> **v1.8.4+:** On Kubernetes, the `ServiceDefaults` custom resource is supported in Consul versions 1.8.4+.<br />
**v1.5.0+:** On other platforms, this config entry is supported in Consul versions 1.5.0+.
The `service-defaults` config entry kind (`ServiceDefaults` on Kubernetes) controls default global values for a
service, such as its protocol.

5
website/content/docs/connect/config-entries/service-router.mdx
View File

@ -18,11 +18,6 @@ service of the same name.
- Consul [service mesh connect](/docs/connect/configuration) enabled services
- Service to service communication over the protocol `http`
- Consul 1.8.4+ on Kubernetes.
- Consul 1.5.0+ on other platforms.
-> **v1.8.4+:** On Kubernetes, the `ServiceRouter` custom resource is supported in Consul versions 1.8.4+.<br />
**v1.6.0+:** On other platforms, this config entry is supported in Consul versions 1.6.0+.
## Interaction with other Config Entries