status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Remove beta tag for 1.10 features 

Remove beta tag for 1.10 features which are now GA.
This commit is contained in:
Blake Covarrubias 2021-06-22 15:04:50 -07:00 committed by Blake Covarrubias
parent 52cb3ca755
commit d9add7c2c3
5 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -15,7 +15,7 @@ The following configuration entries are supported:
- [Ingress Gateway](/docs/connect/config-entries/ingress-gateway) - defines the - [Ingress Gateway](/docs/connect/config-entries/ingress-gateway) - defines the
configuration for an ingress gateway configuration for an ingress gateway
- [Mesh](/docs/connect/config-entries/mesh) <sup>Beta</sup> - controls - [Mesh](/docs/connect/config-entries/mesh) - controls
mesh-wide configuration that applies across namespaces and federated datacenters. mesh-wide configuration that applies across namespaces and federated datacenters.
- [Proxy Defaults](/docs/connect/config-entries/proxy-defaults) - controls - [Proxy Defaults](/docs/connect/config-entries/proxy-defaults) - controls

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

@ -8,7 +8,7 @@ description: >-
Currently, only one mesh entry is supported. Currently, only one mesh entry is supported.
--- ---
# Mesh <sup>Beta</sup> # Mesh
-> **v1.10.0+:** This config entry is supported in Consul versions 1.10.0+. -> **v1.10.0+:** This config entry is supported in Consul versions 1.10.0+.

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

@ -47,7 +47,7 @@ spec:
</Tab> </Tab>
</Tabs> </Tabs>
### Upstream configuration <sup>Beta</sup> ### Upstream configuration
<Tabs> <Tabs>
<Tab heading="HCL"> <Tab heading="HCL">

8
website/content/docs/connect/registration/service-registration.mdx
View File

@ -122,7 +122,7 @@ registering a proxy instance.
instance. This is created by the application. This conflicts with `local_service_address` instance. This is created by the application. This conflicts with `local_service_address`
and `local_service_port`. This is only supported when using Envoy for the proxy. and `local_service_port`. This is only supported when using Envoy for the proxy.
- `mode` `(string: "")` <sup>Beta</sup> - One of \`direct\` or \`transparent\`. Added in v1.10.0. - `mode` `(string: "")` - One of \`direct\` or \`transparent\`. Added in v1.10.0.
- `"transparent"` - represents that inbound and outbound application traffic is being - `"transparent"` - represents that inbound and outbound application traffic is being
captured and redirected through the proxy. This mode does not enable the traffic redirection captured and redirected through the proxy. This mode does not enable the traffic redirection
itself. Instead it signals Consul to configure Envoy as if traffic is already being redirected. itself. Instead it signals Consul to configure Envoy as if traffic is already being redirected.
@ -134,7 +134,7 @@ registering a proxy instance.
2. The `service-defaults` configuration for the service. 2. The `service-defaults` configuration for the service.
3. The `global` `proxy-defaults`. 3. The `global` `proxy-defaults`.
- `transparent_proxy` `(object: {})` <sup>Beta</sup> - Specifies the configuration specific to proxies in `transparent` mode. - `transparent_proxy` `(object: {})` - Specifies the configuration specific to proxies in `transparent` mode.
The format is defined in the [Transparent Proxy Configuration Reference](#transparent-proxy-configuration-reference). The format is defined in the [Transparent Proxy Configuration Reference](#transparent-proxy-configuration-reference).
Added in v1.10.0. Added in v1.10.0.
@ -225,7 +225,7 @@ followed by documentation for each attribute.
- `mesh_gateway` `(object: {})` - Specifies the mesh gateway configuration - `mesh_gateway` `(object: {})` - Specifies the mesh gateway configuration
for this proxy. The format is defined in the [Mesh Gateway Configuration Reference](#mesh-gateway-configuration-reference). for this proxy. The format is defined in the [Mesh Gateway Configuration Reference](#mesh-gateway-configuration-reference).
### Transparent Proxy Configuration Reference <sup>Beta</sup> ### Transparent Proxy Configuration Reference
The following examples show additional configuration for transparent proxies. The following examples show additional configuration for transparent proxies.
@ -375,7 +375,7 @@ registrations](/docs/agent/services#service-definition-parameter-case).
but the proxy registration will not fail. but the proxy registration will not fail.
- `protocol` `(string: "http")` - Sets the protocol of the listener. One of `http` or `http2`. For gRPC use `http2`. - `protocol` `(string: "http")` - Sets the protocol of the listener. One of `http` or `http2`. For gRPC use `http2`.
### Unix Domain Sockets <sup>Beta</sup> ### Unix Domain Sockets
The following examples show additional configuration for Unix domain sockets. The following examples show additional configuration for Unix domain sockets.

2
website/content/docs/k8s/connect/index.mdx
View File

@ -48,7 +48,7 @@ would work on a Pod, a StatefulSet, or a DaemonSet.
This Deployment specification starts a server that responds to any This Deployment specification starts a server that responds to any
HTTP request with the static text "hello world". HTTP request with the static text "hello world".
-> **Note:** As of consul-k8s `v0.26.0-beta1` and Consul Helm `v0.32.0-beta1`, having a Kubernetes -> **Note:** As of consul-k8s `v0.26.0` and Consul Helm `v0.32.0`, having a Kubernetes
service is **required** to run services on the Consul Service Mesh. service is **required** to run services on the Consul Service Mesh.
```yaml ```yaml