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.

Sign up for GitHub

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

Jump to bottom

CA share task #62

Open
cdenneen opened this issue Mar 9, 2022 · 2 comments
Open

CA share task #62

cdenneen opened this issue Mar 9, 2022 · 2 comments
Labels
enhancement New feature or request jira

Comments

@cdenneen
Copy link

cdenneen commented Mar 9, 2022

Use Case

Setting up new stacks to migrate existing over to will need the CA to be shared.

Describe the Solution You Would Like

Need ca to be copied over from existing to new stack prior to provisioning PE so the new infrastructure matches current CA agents are using.
@cdenneen cdenneen added the enhancement New feature or request label Mar 9, 2022
@reidmv
Copy link
Contributor

reidmv commented Apr 28, 2022 •
edited
Loading

We think the best way to handle this is to restore a previously backed-up CA onto the newly deployed cluster. Right now this approach is blocked on finishing the peadm::restore plan. puppetlabs/puppetlabs-peadm#250

@mcka1n mcka1n added the jira label Jun 13, 2022
@cdenneen
Copy link
Author

@reidmv now that peadm::restore isn't blocked any good example of adding this to a bolt plan?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request jira
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@reidmv @cdenneen @mcka1n