velero-io/velero

Documentation: Dealing with K8S CA certificates

Open

#1,929 opened on Oct 2, 2019

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Go (1,550 forks)auto 404
Area/DocumentationHelp wantedIceboxReviewed Q2 2021limitation

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the problem/challenge you have

Some providers, such as Google, don't allow you to create a cluster with a specific CA (at least as far as I can tell, been looking at docs for a while). That means any restored certificates created using k8s's built in CSR tooling will not work in the new cluster.

Describe the solution you'd like

I'm suggesting/requesting that this issue be documented on the Restore Reference and Disaster Recovery pages as it may not be an obvious issue people will face. I don't think there's a way to resolve the underlying issue itself so this is really just a "heads up!" that people can be aware of when testing and documenting their Velero backup solution.

Anything else you would like to add:

If I'm wrong, then this issue becomes a request for documentation describing how to restore the cluster's CA as well.

Contributor guide