mirror of https://github.com/status-im/consul.git
Merge pull request #8277 from hashicorp/je.website-maintenance-7-8-20
Update dependencies, format all files
This commit is contained in:
Jeff Escalante
GitHub
commit
338af8ac6b
|
|
@ -39,7 +39,11 @@ export default function BasicHero({
|
|||
</div>
|
||||
{links[2] && (
|
||||
<div className="third-link">
|
||||
<a href={links[2].url} rel="noopener" target="_blank">
|
||||
<a
|
||||
href={links[2].url}
|
||||
rel="noopener noreferrer"
|
||||
target="_blank"
|
||||
>
|
||||
<span className="g-type-buttons-and-standalone-links">
|
||||
{links[2].text}
|
||||
</span>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -4,7 +4,7 @@
|
|||
"version": "0.0.1",
|
||||
"author": "HashiCorp",
|
||||
"dependencies": {
|
||||
"@hashicorp/nextjs-scripts": "10.0.2",
|
||||
"@hashicorp/nextjs-scripts": "11.1.0",
|
||||
"@hashicorp/react-alert": "2.0.1",
|
||||
"@hashicorp/react-alert-banner": "3.1.0",
|
||||
"@hashicorp/react-button": "2.2.1",
|
||||
|
|
@ -36,9 +36,6 @@
|
|||
"babel-plugin-import-glob-array": "0.2.0",
|
||||
"dotenv": "8.2.0",
|
||||
"gray-matter": "4.0.2",
|
||||
"imagemin-mozjpeg": "9.0.0",
|
||||
"imagemin-optipng": "8.0.0",
|
||||
"imagemin-svgo": "8.0.0",
|
||||
"next": "9.4.4",
|
||||
"nuka-carousel": "4.7.0",
|
||||
"react": "16.13.1",
|
||||
|
|
|
|||
|
|
@ -907,7 +907,7 @@ top level object. The following selectors and filter operations are supported:
|
|||
This endpoint returns the services associated with an ingress gateway or terminating gateway.
|
||||
|
||||
| Method | Path | Produces |
|
||||
| ------ | ------------------------------ | ------------------ |
|
||||
| ------ | ------------------------------------ | ------------------ |
|
||||
| `GET` | `/catalog/gateway-services/:gateway` | `application/json` |
|
||||
|
||||
The table below shows this endpoint's support for
|
||||
|
|
@ -917,7 +917,7 @@ The table below shows this endpoint's support for
|
|||
[required ACLs](/api#authentication).
|
||||
|
||||
| Blocking Queries | Consistency Modes | Agent Caching | ACL Required |
|
||||
| ---------------- | ----------------- | ------------- | ------------------------ |
|
||||
| ---------------- | ----------------- | ------------- | -------------- |
|
||||
| `YES` | `all` | `none` | `service:read` |
|
||||
|
||||
### Parameters
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ The table below shows this endpoint's support for
|
|||
</p>
|
||||
|
||||
| Config Entry Kind | Required ACL |
|
||||
| ----------------- | ---------------- |
|
||||
| ------------------- | ---------------- |
|
||||
| ingress-gateway | `operator:write` |
|
||||
| proxy-defaults | `operator:write` |
|
||||
| service-defaults | `service:write` |
|
||||
|
|
@ -105,7 +105,7 @@ The table below shows this endpoint's support for
|
|||
<sup>1</sup> The ACL required depends on the config entry kind being read:
|
||||
|
||||
| Config Entry Kind | Required ACL |
|
||||
| ----------------- | ---------------- |
|
||||
| ------------------- | -------------- |
|
||||
| ingress-gateway | `service:read` |
|
||||
| proxy-defaults | `<none>` |
|
||||
| service-defaults | `service:read` |
|
||||
|
|
@ -172,7 +172,7 @@ The table below shows this endpoint's support for
|
|||
<sup>1</sup> The ACL required depends on the config entry kind being read:
|
||||
|
||||
| Config Entry Kind | Required ACL |
|
||||
| ----------------- | ---------------- |
|
||||
| ------------------- | -------------- |
|
||||
| ingress-gateway | `service:read` |
|
||||
| proxy-defaults | `<none>` |
|
||||
| service-defaults | `service:read` |
|
||||
|
|
@ -245,7 +245,7 @@ The table below shows this endpoint's support for
|
|||
<sup>1</sup> The ACL required depends on the config entry kind being deleted:
|
||||
|
||||
| Config Entry Kind | Required ACL |
|
||||
| ----------------- | ---------------- |
|
||||
| ------------------- | ---------------- |
|
||||
| ingress-gateway | `operator:write` |
|
||||
| proxy-defaults | `operator:write` |
|
||||
| service-defaults | `service:write` |
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ service mesh with minimal operator intervention.
|
|||
## Supported Types
|
||||
|
||||
| Types | Consul Version |
|
||||
| ----- | -------------- |
|
||||
| ------------------------------------------------- | --------------------------------- |
|
||||
| [`kubernetes`](/docs/acl/auth-methods/kubernetes) | 1.5.0+ |
|
||||
| [`jwt`](/docs/acl/auth-methods/jwt) | 1.8.0+ |
|
||||
| [`oidc`](/docs/acl/auth-methods/oidc) | 1.8.0+ <EnterpriseAlert inline /> |
|
||||
|
|
|
|||
|
|
@ -31,6 +31,7 @@ description: >-
|
|||
|
||||
A wildcard specifier provides the following properties for an ingress
|
||||
gateway:
|
||||
|
||||
- All services with the same
|
||||
[protocol](/docs/agent/config-entries/ingress-gateway#protocol) as the
|
||||
listener will be routable.
|
||||
|
|
|
|||
|
|
@ -23,6 +23,7 @@ description: >-
|
|||
See [Terminating Gateway](/docs/connect/terminating-gateway) for more information.
|
||||
|
||||
## TLS Origination
|
||||
|
||||
By specifying a path to a [CA file](/docs/agent/config-entries/terminating-gateway#cafile) connections
|
||||
from the terminating gateway will be encrypted using one-way TLS authentication. If a path to a
|
||||
[client certificate](/docs/agent/config-entries/terminating-gateway#certfile)
|
||||
|
|
@ -34,7 +35,7 @@ description: >-
|
|||
|
||||
## Wildcard service specification
|
||||
|
||||
Terminating gateways can optionally target all services within a Consul namespace by specifying a wildcard "*"
|
||||
Terminating gateways can optionally target all services within a Consul namespace by specifying a wildcard "\*"
|
||||
as the service name. Configuration options set on the wildcard act as defaults that can be overridden
|
||||
by options set on a specific service name.
|
||||
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ Intention commands commonly take positional arguments referred to as `SRC` and
|
|||
`DST` in the command documentation. These can take several forms:
|
||||
|
||||
| Format | Meaning |
|
||||
| ----------------------- | -----------------------------------------------------------------------|
|
||||
| ----------------------- | -------------------------------------------------------------------- |
|
||||
| `<service>` | the named service in the current namespace |
|
||||
| `*` | any service in the current namespace |
|
||||
| `<namespace>/<service>` | <EnterpriseAlert inline /> the named service in a specific namespace |
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ All fields are optional with a sane default.
|
|||
or `[::]` in which case this defaults to `127.0.0.1` and assumes the agent can
|
||||
dial the proxy over loopback. For more complex configurations where agent and proxy
|
||||
communicate over a bridge for example, this configuration can be used to specify
|
||||
a different *address* (but not port) for the agent to use for health checks if
|
||||
a different _address_ (but not port) for the agent to use for health checks if
|
||||
it can't talk to the proxy over localhost or it's publicly advertised port. The
|
||||
check always uses the same port that the proxy is bound to.
|
||||
|
||||
|
|
|
|||
|
|
@ -287,7 +287,6 @@ definition](/docs/connect/registration/service-registration) or
|
|||
- `max_failures` - The number of consecutive failures which cause a host to be
|
||||
removed from the load balancer.
|
||||
|
||||
|
||||
### Gateway Options
|
||||
|
||||
These fields may also be overridden explicitly in the [proxy service
|
||||
|
|
|
|||
|
|
@ -28,11 +28,11 @@ the WAN.
|
|||
|
||||
Sometimes this prerequisite is difficult or undesirable to meet:
|
||||
|
||||
* **Difficult:** The datacenters may exist in multiple Kubernetes clusters that
|
||||
- **Difficult:** The datacenters may exist in multiple Kubernetes clusters that
|
||||
unfortunately have overlapping pod IP subnets, or may exist in different
|
||||
cloud provider VPCs that have overlapping subnets.
|
||||
|
||||
* **Undesirable:** Network security teams may not approve of granting so many
|
||||
- **Undesirable:** Network security teams may not approve of granting so many
|
||||
firewall rules. When using platform autoscaling, keeping rules up to date becomes untenable.
|
||||
|
||||
Operators looking to simplify their WAN deployment and minimize the exposed
|
||||
|
|
@ -44,17 +44,16 @@ gateways](/docs/connect/mesh-gateways.html) to do so.
|
|||
There are two main kinds of communication that occur over the WAN link spanning
|
||||
the gulf between disparate Consul datacenters:
|
||||
|
||||
* **WAN gossip:** We leverage the serf and memberlist libraries to gossip
|
||||
- **WAN gossip:** We leverage the serf and memberlist libraries to gossip
|
||||
around failure detector knowledge about Consul servers in each datacenter.
|
||||
By default this operates point to point between servers over `8302/udp` with
|
||||
a fallback to `8302/tcp` (which logs a warning indicating the network is
|
||||
misconfigured).
|
||||
|
||||
* **Cross-datacenter RPCs:** Consul servers expose a special multiplexed port
|
||||
- **Cross-datacenter RPCs:** Consul servers expose a special multiplexed port
|
||||
over `8300/tcp`. Several distinct kinds of messages can be received on this
|
||||
port, such as RPC requests forwarded from servers in other datacenters.
|
||||
|
||||
|
||||
In this network topology individual Consul client agents on a LAN in one
|
||||
datacenter never need to directly dial servers in other datacenters. This
|
||||
means you could introduce a set of firewall rules prohibiting `10.0.0.0/24`
|
||||
|
|
@ -80,8 +79,7 @@ these SAN fields:
|
|||
server.<this_datacenter>.<domain> (normal)
|
||||
<node_name>.server.<this_datacenter>.<domain> (needed for wan federation)
|
||||
|
||||
This can be achieved using any number of tools, including `consul tls cert
|
||||
create` with the `-node` flag.
|
||||
This can be achieved using any number of tools, including `consul tls cert create` with the `-node` flag.
|
||||
|
||||
### Mesh Gateways
|
||||
|
||||
|
|
@ -157,7 +155,6 @@ follow this general procedure:
|
|||
resolve ACL tokens from the secondary, at which time it should be possible
|
||||
to launch the mesh gateways in the secondary datacenter.
|
||||
|
||||
|
||||
### Existing secondary
|
||||
|
||||
1. Upgrade to the desired version of the consul binary for all servers,
|
||||
|
|
@ -175,9 +172,9 @@ follow this general procedure:
|
|||
From any two datacenters joined together double check the following give you an
|
||||
expected result:
|
||||
|
||||
* Check that `consul members -wan` lists all servers in all datacenters with
|
||||
- Check that `consul members -wan` lists all servers in all datacenters with
|
||||
their _local_ ip addresses and are listed as `alive`.
|
||||
|
||||
* Ensure any API request that activates datacenter request forwarding. such as
|
||||
- Ensure any API request that activates datacenter request forwarding. such as
|
||||
[`/v1/catalog/services?dc=<OTHER_DATACENTER_NAME>`](/api/catalog.html#dc-1)
|
||||
succeeds.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,8 @@ description: >-
|
|||
# Automated Backups
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature is available in all versions of <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>.
|
||||
This feature is available in all versions of{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Consul Enterprise enables you to run
|
||||
|
|
|
|||
|
|
@ -11,7 +11,9 @@ description: >-
|
|||
# Consul Enterprise Advanced Federation
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Global Visibility, Routing, and Scale module.
|
||||
This feature requires{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>{' '}
|
||||
with the Global Visibility, Routing, and Scale module.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Consul's core federation capability uses the same gossip mechanism that is used
|
||||
|
|
|
|||
|
|
@ -8,7 +8,9 @@ description: Consul Enterprise enables data isolation with Namespaces.
|
|||
# Consul Enterprise Namespaces
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Governance and Policy module.
|
||||
This feature requires{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>{' '}
|
||||
with the Governance and Policy module.
|
||||
</EnterpriseAlert>
|
||||
|
||||
With Consul Enterprise v1.7.0, data for different users or teams
|
||||
|
|
|
|||
|
|
@ -10,7 +10,9 @@ description: |-
|
|||
# Network Segments
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Global Visibility, Routing, and Scale module.
|
||||
This feature requires{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>{' '}
|
||||
with the Global Visibility, Routing, and Scale module.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Consul Network Segments enables operators to create separate LAN gossip segments
|
||||
|
|
|
|||
|
|
@ -12,7 +12,9 @@ description: >-
|
|||
# Enhanced Read Scalability with Non-Voting Servers
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Global Visibility, Routing, and Scale module.
|
||||
This feature requires{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>{' '}
|
||||
with the Global Visibility, Routing, and Scale module.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Consul Enterprise provides the ability to scale clustered Consul servers
|
||||
|
|
|
|||
|
|
@ -10,7 +10,9 @@ description: >-
|
|||
# Redundancy Zones
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Global Visibility, Routing, and Scale module.
|
||||
This feature requires{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>{' '}
|
||||
with the Global Visibility, Routing, and Scale module.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Consul Enterprise redundancy zones provide
|
||||
|
|
|
|||
|
|
@ -11,7 +11,9 @@ description: >-
|
|||
# Sentinel in Consul
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Governance and Policy module.
|
||||
This feature requires{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>{' '}
|
||||
with the Governance and Policy module.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Sentinel policies extend the ACL system in Consul beyond static "read", "write",
|
||||
|
|
|
|||
|
|
@ -11,7 +11,8 @@ description: >-
|
|||
# Automated Upgrades
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature is available in all versions of <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>.
|
||||
This feature is available in all versions of{' '}
|
||||
<a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a>.
|
||||
</EnterpriseAlert>
|
||||
|
||||
Consul Enterprise enables the capability of automatically upgrading a cluster of Consul servers to a new
|
||||
|
|
|
|||
|
|
@ -2,10 +2,7 @@
|
|||
layout: docs
|
||||
page_title: Network Coordinates
|
||||
sidebar_title: Network Coordinates
|
||||
description: ''
|
||||
Serf uses a network tomography system to compute network coordinates for nodes in the cluster. These coordinates are useful for easily calculating the estimated network round trip time between any two nodes in the cluster. This page documents the details of this system. The core of the network tomography system us based on Vivaldi: >-
|
||||
A Decentralized Network Coordinate System, with several improvements based on
|
||||
several follow-on papers.
|
||||
description: A Decentralized Network Coordinate System, with several improvements based on several follow-on papers.
|
||||
---
|
||||
|
||||
# Network Coordinates
|
||||
|
|
|
|||
|
|
@ -792,7 +792,7 @@ and consider if they're appropriate for your deployment.
|
|||
for the mesh gateway from.
|
||||
Can be set to either: `Service`, `NodeIP`, `NodeName` or `Static`. See the behavior of each below:
|
||||
|
||||
* `Service` - Determine the address based on the service type.
|
||||
- `Service` - Determine the address based on the service type.
|
||||
|
||||
If `service.type=LoadBalancer` use the external IP or hostname of
|
||||
the service. Use the port set by `service.port`.
|
||||
|
|
@ -805,13 +805,13 @@ and consider if they're appropriate for your deployment.
|
|||
|
||||
`service.type=ExternalName` is not supported.
|
||||
|
||||
* `NodeIP` - The node IP as provided by the Kubernetes downward API.
|
||||
- `NodeIP` - The node IP as provided by the Kubernetes downward API.
|
||||
|
||||
* `NodeName` - The name of the node as provided by the Kubernetes downward
|
||||
- `NodeName` - The name of the node as provided by the Kubernetes downward
|
||||
API. This is useful if the node names are DNS entries that
|
||||
are routable from other datacenters.
|
||||
|
||||
* `Static` - Use the address hardcoded in `meshGateway.wanAddress.static`.
|
||||
- `Static` - Use the address hardcoded in `meshGateway.wanAddress.static`.
|
||||
|
||||
- `port` ((#v-meshgateway-wanaddress-port)) (`integer: 443`) - Port that gets registered for WAN traffic.
|
||||
If source is set to "Service" then this setting will have no effect.
|
||||
|
|
|
|||
|
|
@ -195,16 +195,14 @@ export default function HomePage() {
|
|||
title: 'Getting Started',
|
||||
category: 'Step-by-Step Guides',
|
||||
time: '48 mins',
|
||||
link:
|
||||
'https://learn.hashicorp.com/consul/getting-started/install',
|
||||
link: 'https://learn.hashicorp.com/consul/getting-started/install',
|
||||
image: require('./img/learn/getting-started.svg?url'),
|
||||
},
|
||||
{
|
||||
title: 'Run Consul on Kubernetes',
|
||||
category: 'Step-by-Step Guides',
|
||||
time: '142 mins',
|
||||
link:
|
||||
'https://learn.hashicorp.com/consul/kubernetes/minikube',
|
||||
link: 'https://learn.hashicorp.com/consul/kubernetes/minikube',
|
||||
image: require('./img/learn/kubernetes.svg?url'),
|
||||
},
|
||||
]}
|
||||
|
|
|
|||
Loading…
Reference in New Issue