mirror of https://github.com/linkerd/linkerd2.git
2bbb59b599
* Remove nginx container from mc gateway pod Fixes #5444 Replaced the nginx container with a pause container, and removed all the config boilerplate associated to nginx. The probe now targets the proxy's readiness endpoint, port 4191 path `/ready`. ## Upgrade note * @Pothulapati's feedback * @Pothulapati's feedback When multicluster gets updated in both source and target this won't cause downtime because this change only affects the probing. The `Links` will have to be re-generated of course. Til that is done, `linkerd mc gateways` will show the target cluster as not alive, but that shouldn't affect exiting connections. |
||
|---|---|---|
| .. | ||
| templates | ||
| .helmignore | ||
| Chart.yaml | ||
| NOTES.txt | ||
| README.md | ||
| README.md.gotmpl | ||
| requirements.lock | ||
| requirements.yaml | ||
| values.yaml | ||
README.md
linkerd-multicluster
The Linkerd-Multicluster extension contains resources to support multicluster linking to remote clusters
Homepage: https://linkerd.io
Quickstart and documentation
You can run Linkerd on any Kubernetes 1.16+ cluster in a matter of seconds. See the Linkerd Getting Started Guide for how.
For more comprehensive documentation, start with the Linkerd docs.
Prerequisite: Linkerd Core Control-Plane
Before installing the Linkerd Multicluster extension, The core control-plane has to be installed first by following the Linkerd Install Guide.
Adding Linkerd's Helm repository
# To add the repo for Linkerd2 stable releases:
helm repo add linkerd https://helm.linkerd.io/stable
# To add the repo for Linkerd2 edge releases:
helm repo add linkerd-edge https://helm.linkerd.io/edge
The following instructions use the linkerd repo. For installing an edge
release, just replace with linkerd-edge.
Installing the Multicluster Extension Chart
helm install linkerd/linkerd-multicluster
Get involved
- Check out Linkerd's source code at Github.
- Join Linkerd's user mailing list, developer mailing list, and announcements mailing list.
- Follow @linkerd on Twitter.
- Join the Linkerd Slack.
Requirements
Kubernetes: >=1.16.0-0
| Repository | Name | Version |
|---|---|---|
| file://../../../charts/partials | partials | 0.1.0 |
Values
| Key | Type | Default | Description |
|---|---|---|---|
| gateway | bool | true |
If the gateway component should be installed |
| gatewayName | string | "linkerd-gateway" |
The name of the gateway that will be installed |
| gatewayPort | int | 4143 |
The port on which all the gateway will accept incoming traffic |
| gatewayProbePath | string | "/ready" |
The path that will be used by remote clusters for determining whether the gateway is alive |
| gatewayProbePort | int | 4191 |
The port used for liveliness probing |
| gatewayProbeSeconds | int | 3 |
The interval (in seconds) between liveness probes |
| gatewayServiceType | string | "LoadBalancer" |
Service Type of gateway Service |
| identityTrustDomain | string | "cluster.local" |
Identity Trust Domain of the certificate authority |
| installNamespace | bool | true |
If the namespace should be installed |
| linkerdNamespace | string | "linkerd" |
Namespace of linkerd installation |
| linkerdVersion | string | "linkerdVersionValue" |
Control plane version |
| namespace | string | "linkerd-multicluster" |
Service Mirror component namespace |
| proxyOutboundPort | int | 4140 |
The port on which the proxy accepts outbound traffic |
| remoteMirrorServiceAccount | bool | true |
If the remote mirror service account should be installed |
| remoteMirrorServiceAccountName | string | "linkerd-service-mirror-remote-access-default" |
The name of the service account used to allow remote clusters to mirror local services |
Autogenerated from chart metadata using helm-docs v1.4.0