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

Migrate GCP CA to 1.0 #195

Closed
Tracked by #191
lukehinds opened this issue Oct 5, 2021 · 5 comments
Closed
Tracked by #191

Migrate GCP CA to 1.0 #195

lukehinds opened this issue Oct 5, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@lukehinds
Copy link
Member

Google has now implemented 1.0 with various changes, this means we need to update the googleca code to 1.0

@lukehinds lukehinds added the bug Something isn't working label Oct 5, 2021
@lukehinds lukehinds mentioned this issue Oct 5, 2021
4 tasks
@bobcallaway
Copy link
Member

@dlorenc do we need to move to a new KMS object in GCP (and do this before the signing session this Friday)?

@dlorenc
Copy link
Member

dlorenc commented Oct 5, 2021

We're still using the CA. We can create a new one whenever, but we'll need to be careful with the migration since the root is still pinned in cosign.

@lukehinds lukehinds added enhancement New feature or request and removed bug Something isn't working labels Oct 5, 2021
@lukehinds
Copy link
Member Author

We also need to be mindful of the public instance (and their chosen implementation), although we don't know what that looks like just yet.

@nsmith5
Copy link
Contributor

nsmith5 commented Jan 26, 2022

I think this is done now right? I think v1beta1 support just got deprecated as well

@dlorenc
Copy link
Member

dlorenc commented Jan 26, 2022

Yup!

@dlorenc dlorenc closed this as completed Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants