-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add docs section on deploying a local pulp #42
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice as a future task to just pass in Ark creds and have the rest handled automatically, but as an initial pulp on seed support this looks good to me 👍
dd1e2e7
to
f3626ca
Compare
I realised it's actually quite easy to add those changes to the deployment script so I just put the command in there |
We could also consider a standalone Pulp server for the eventuality of multiple separate multinode environments or short lived environments. Otherwise we would be downloading 10s GiBs everytime a multinode environment is created and disposed of. Possible implementation would be some separate Terraform that creates this server. |
Maybe some TF in SKC to deploy a pulp server on their cloud? Separating it from the multinodes sounds like a good idea. It might also come in handy for in-cloud CI runners or highly secure environments where VMs have no internet access |
No description provided.