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
Move cert-manager-release infrastructure to CNCF's GCP account #50
Comments
An alternative to porting the infrastructure would be to start fresh in a new project, which was discussed in cert-manager standup 24/09. We'll discuss this next week and decide on a path forwards. |
We got the go-ahead to move today (28/09); I'll contact the CNCF to get the ball rolling. EDIT: In response to asking for an estimate of how long it'll take:
EOW would be 01/10/2021. |
Update: they're still working on it 😄 |
Update again: they're still looking into it. The billing is definitely done, but the org move isn't. |
Update again: as far as we know the permissions are set on the jetstack side and we're waiting for the actual org move to happen. |
Update again: still continuing to chase. |
Update: given the upcoming holiday period we'll revisit in January 2022 |
Update:
We'll see if we can figure anything out on our end. |
All release infrastructure has been moved to the CNCF GCP organisation. |
CNCF have offered for us to move our
cert-manager-release
GCP project to live under the CNCF's GCP account.cert-manager-release
is currently Jetstack internal.This issue is to track that migration, and to provide a place for any discussion relating to that move.
The text was updated successfully, but these errors were encountered: