Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn about expiring root certificate on getting started page #6099

Closed
iamargopelter opened this issue May 6, 2021 · 2 comments · Fixed by linkerd/website#1068
Closed

Warn about expiring root certificate on getting started page #6099

iamargopelter opened this issue May 6, 2021 · 2 comments · Fixed by linkerd/website#1068

Comments

@iamargopelter
Copy link

The getting started page at https://linkerd.io/2.10/getting-started/ ends with 'Congratulations, you’re now a Linkerd user!', but doesn't warn that the control plane certificate will expire. As everything else seems automated, this has led to some unwelcome surprises.

A mention / link to the rotation procedure and/or how to set up automation in the 'next steps' segment would save headaches for new (and returning) users.

@mateiidavid
Copy link
Member

Hey @iamargopelter seems like a good suggestion to me! Would you be willing to submit a PR in linkerd2/website with the proposed changes?

@iamargopelter
Copy link
Author

Hey @mateiidavid, certainly. Submitted a PR.

kleimkuhler pushed a commit to linkerd/website that referenced this issue May 7, 2021
The getting started page does not currently mention that the Control Plane TLS credentials will ultimately expire, leading to nasty surprises a year down the line.

Adding links to the relevant documentation on the getting started page should fix this.

Fixes linkerd/linkerd2#6099

Signed-off-by: Marijn de Vlieger <[email protected]>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants