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

GCP DNS Authorization Per Project Record #2943

Open
gerardocorea opened this issue Oct 17, 2024 · 0 comments
Open

GCP DNS Authorization Per Project Record #2943

gerardocorea opened this issue Oct 17, 2024 · 0 comments
Labels
question Further information is requested

Comments

@gerardocorea
Copy link

gerardocorea commented Oct 17, 2024

Describe your question

The gcloud command for creating a dns authorization now supports using a --type flag and using a PER_PROJECT_RECORD option. This allows for creation the same google managed certificate in mutiple projects and having a unique DNS authorization cname so google can authorize and issue the certificate for each project. In the past this was not possible because the same acme challenge cname was created with different a different data value. I don't see this as a field in the CertificateManagerDNSAuthorizationSpec type yet. What information would be needed to expose this so it can be configured when creating a CertificateManagerDNSAuthorization resource?

type: https://github.com/GoogleCloudPlatform/k8s-config-connector/blob/master/apis/certificatemanager/v1beta1/certificatemanagerdnsauthorization_types.go#L27

Citing documentation: https://cloud.google.com/certificate-manager/docs/dns-authorizations

The default DNS authorization type for a global Google-managed certificate is FIXED_RECORD. To use per-project DNS authorization, run the following command:

gcloud certificate-manager dns-authorizations create AUTHORIZATION_NAME \
    --domain="DOMAIN_NAME" \
    --type="PER_PROJECT_RECORD"
@gerardocorea gerardocorea added the question Further information is requested label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant