-
Notifications
You must be signed in to change notification settings - Fork 15
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
Bump CoreDNS to 1.11.4 #148
Conversation
There have been several security fixes since v1.8.7 which was released in January 2022. For example, CVE-2022-27191 and CVE-2022-28948 were mentioned in version v1.9.3 and security issues discovered in an audit were fixed in v1.9.2. There were also plenty of bugfixes done in the last 2.5 years.
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.
Hi @IngmarStein
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Friendly ping |
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.
Tested this on dev here, and resolving including .local seems to work as before! In the past we did had regression on CoreDNS updates, so we definitely want this for a couple of days in beta before letting loose 😅
LGTM. Thanks for the PR 🙏
There have been several security fixes since v1.8.7 which was released in January 2022. For example, CVE-2022-27191 and CVE-2022-28948 were mentioned in version v1.9.3 and security issues discovered in an audit were fixed in v1.9.2. There were also plenty of bugfixes done in the last 2.5 years.