-
Notifications
You must be signed in to change notification settings - Fork 791
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
DNS REQUEST: add CAA record #2216
Comments
/milestone v1.23 |
/sig security |
Bumping for recency because I'd like to see the PR merged in the next week |
I have heard no response to the kubernetes.io PR merging, I think we're good to go for a similar PR for k8s.io @jimangel |
/milestone v1.24 |
@spiffxp sorry I missed this, yep, I'll get a PR in for k8s.io soon (probably after 1.23 settles down). /assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@jimangel I think we can close this. It's been exactly 30 days since we added the CAA record for |
LGTM! Thanks! |
@jimangel: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
It was requested to create CAA DNS records for k/website as a security best practices and, well, it's good to know what CAs can issue "official" certificates for public facing Kubernetes things.
More info in this PR: #1849. The PR covers kubernetes.io, not k8s.io, which we should also lock down in a similar manor.
/priority important-soon
/milestone v1.22
/cc @dims @ameukam @spiffxp @thockin
The text was updated successfully, but these errors were encountered: