Commit Graph

7 Commits

Author SHA1 Message Date
Travis Beckham 5c44d98b88
Replaced relref shortcode with link render hook (#1969)
Signed-off-by: Travis Beckham <travis@buoyant.io>
2025-05-01 15:55:06 -05:00
Travis Beckham 44a87dedaf
linkerd.io rebuild (#1860) 2024-10-28 10:39:51 -05:00
Flynn 9ae1a4d3f1
Callouts for Linkerd Production Toolkit (#1596)
* Callouts for Linkerd Production Toolkit

Signed-off-by: Flynn <flynn@buoyant.io>

* lint

Signed-off-by: Flynn <flynn@buoyant.io>

* Include getting-started too.

Signed-off-by: Flynn <flynn@buoyant.io>

* Fix shortcode typo

Signed-off-by: Flynn <flynn@buoyant.io>

* Wordsmithing feedback.

Signed-off-by: Flynn <flynn@buoyant.io>

* Add LPT callouts to all versions

Signed-off-by: Flynn <flynn@buoyant.io>

---------

Signed-off-by: Flynn <flynn@buoyant.io>
Co-authored-by: Flynn <flynn@buoyant.io>
2023-04-07 13:33:01 -04:00
Phil Nichol 0e0850907d
docs: Add labels and annotations to created namespaces (#1397)
This adds the expected labels and annotations to the namespaces that automatically come with a helm installation.

Closes https://github.com/linkerd/linkerd2/issues/7298

I agree to the DCO for all the commits in this PR.
2022-09-19 09:35:41 -05:00
Eliza Weisman 2edd0626eb
update 2.12 docs to use `linkerd install --crds` before `install` (#1449)
* update 2.12 docs to use `linkerd install --crds` before `install`

The Linkerd CRDs must be installed before installing the control plane.
Most of the "Tasks" docs that require Linkerd to be installed just
reference the "Install" task, which demonstrates the use of
`install --crds`. However, some of the docs demonstrate alternative
configurations or installation methods, and actually show running the
`install` command. Many of those docs don't indicate that
`linkerd install --crds` must be run first.

This branch updates the 2.12 "Tasks" docs to show the use of
`linkerd install --crds` prior to running a `linkerd install` command. I
think I got all of them?

I didn't add `install --crds` in a couple of places where the install
command is not piped directly into `kubectl apply`. For example, in the
private docker registry documentation, we show piping `linkerd install`
into `grep` to get the docker image versions, and in that case, we are
not actually installing Linkerd into a cluster in that command example,
so the installation won't actually fail.

* update helm install instructions too
2022-08-25 12:13:05 -04:00
Eliza Weisman 89450fb283
remove needless `cat <<EOF`s in 2.12 docs (#1445)
In several places, the "Tasks" documentation shows applying a Kubernetes
manifest by `cat`ing a heredoc and piping it into `kubectl apply -f -`.
In most cases, the `cat <<EOF | kubectl apply -f -` is unneeded, and can
be simplified to just `kubectl apply -f - <<EOF`.

I didn't touch the cases where the yaml is first piped into `linkerd
inject -` and *then* into `kubectl apply`, as the cat is necessary as
the first stage in those pipelines (I think).
2022-08-25 12:07:46 -04:00
Eliza Weisman 264f7f31be
update documentation for Linkerd 2.12 (#1441)
Big bang merge of 2.12 docs into main.

Signed-off-by: Flynn <flynn@buoyant.io>
Signed-off-by: Alex Leong <alex@buoyant.io>
Signed-off-by: Matei David <matei@buoyant.io>
Co-authored-by: Alejandro Pedraza <alejandro@buoyant.io>
Co-authored-by: Matei David <matei@buoyant.io>
Co-authored-by: Oliver Gould <ver@buoyant.io>
Co-authored-by: Flynn <flynn@buoyant.io>
Co-authored-by: Flynn <kflynn@users.noreply.github.com>
Co-authored-by: Alex Leong <alex@buoyant.io>
Co-authored-by: William Morgan <william@buoyant.io>
2022-08-23 17:35:16 -07:00