feat(helm): update chart coredns to 1.37.0

[renovate]

This PR contains the following updates:

Package	Update	Change
coredns (source)	minor	1.29.0 -> 1.37.0

---

Release Notes

coredns/helm (coredns)

v1.37.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.36.2

Compare Source

v1.36.1

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.36.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.35.1

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.35.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.34.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.33.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.32.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.31.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

v1.30.0

Compare Source

CoreDNS is a DNS server that chains plugins and provides Kubernetes DNS Services

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

The given git diff reflects changes in two different files related to the upgrade of the CoreDNS Helm chart from version 1.29.0 to version 1.30.0. There are no direct security issues that can be identified purely from the diff provided, as it merely shows a version update of a software component. However, upgrading software components can introduce a range of potential security implications, depending on the changes made between versions.

Suggested Checks for Security:

1. Changelog Review: Review the changelog or release notes of CoreDNS version 1.30.0 to understand what changes have been made. This includes looking for:

   • Security patches that fix vulnerabilities present in the previous version (1.29.0).
   • Any new features or changes in behavior that could affect the security posture of the Kubernetes cluster where it's deployed.

2. Dependency Scanning: Since Helm charts can bundle other dependencies, ensure that no vulnerable dependencies are introduced in the new version. This can typically be achieved using tools designed for scanning container images or Kubernetes deployments for vulnerabilities.

3. Configuration Assessment: Evaluate any changes in the default configuration between the two versions that might need adjusting. Sometimes, newer versions change the defaults to more secure configurations, or conversely, introduce settings that might need tightening.

Fixes or additional actions cannot be accurately suggested without a detailed view of the updates in version 1.30.0 of CoreDNS and how it interacts with the specifics of the deployment environment. However, general best practices include:

1. Test in a Staging Environment: Before rolling out the update to production, test the new version in a staging environment that mirrors production closely. This helps in identifying potential issues that could affect availability or introduce vulnerabilities.

2. Backup and Rollback Plan: Ensure that you have a comprehensive backup of the existing state and a clear rollback plan in case the upgrade introduces unforeseen issues.

3. Security Practices: Employ continuous monitoring and logging to detect any anomalous behavior that could indicate a security issue post-upgrade.

Without specific insights into the changes made in CoreDNS 1.30.0 and the context of its deployment, these general security considerations and best practices are the most relevant advice that can be offered based on the provided diff.