Skip to content

external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0#401

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/registry.k8s.io-external-dns-external-dns-0.x
Open

external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0#401
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/registry.k8s.io-external-dns-external-dns-0.x

Conversation

@renovate

@renovate renovate Bot commented Apr 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
registry.k8s.io/external-dns/external-dns Kustomization minor v0.20.0v0.21.0

Release Notes

kubernetes-sigs/external-dns (registry.k8s.io/external-dns/external-dns)

v0.21.0

Compare Source

⚠️ Breaking Changes

🚀 Features

🐛 Bug fixes

📝 Documentation

📦 Others

📦 Docker Image

docker pull registry.k8s.io/external-dns/external-dns:v0.21.0

New Contributors

Full Changelog: kubernetes-sigs/external-dns@v0.20.0...v0.21.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 this update again.


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

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

@github-actions

github-actions Bot commented Apr 6, 2026

Copy link
Copy Markdown

Infro diff for cff331f

argocd.hashbang.sh > cloudnative-pg (0 files changed)

Details
time="2026-06-19T19:04:22Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2026-06-19T19:04:33Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."

===== apiextensions.k8s.io/CustomResourceDefinition /clusters.postgresql.cnpg.io ======
--- /tmp/argocd-diff2104067660/clusters.postgresql.cnpg.io-live.yaml
+++ /tmp/argocd-diff2104067660/clusters.postgresql.cnpg.io
@@ -5784,7 +5784,6 @@
                       procMount denotes the type of proc mount to use for the containers.
                       The default value is Default which uses the container runtime defaults for
                       readonly paths and masked paths.
-                      This requires the ProcMountType feature flag to be enabled.
                       Note that this field cannot be set when spec.os.name is windows.
                     type: string
                   readOnlyRootFilesystem:

===== apiextensions.k8s.io/CustomResourceDefinition /poolers.postgresql.cnpg.io ======
--- /tmp/argocd-diff2730429555/poolers.postgresql.cnpg.io-live.yaml
+++ /tmp/argocd-diff2730429555/poolers.postgresql.cnpg.io
@@ -2934,7 +2934,6 @@
                                     procMount denotes the type of proc mount to use for the containers.
                                     The default value is Default which uses the container runtime defaults for
                                     readonly paths and masked paths.
-                                    This requires the ProcMountType feature flag to be enabled.
                                     Note that this field cannot be set when spec.os.name is windows.
                                   type: string
                                 readOnlyRootFilesystem:
@@ -4505,7 +4504,6 @@
                                     procMount denotes the type of proc mount to use for the containers.
                                     The default value is Default which uses the container runtime defaults for
                                     readonly paths and masked paths.
-                                    This requires the ProcMountType feature flag to be enabled.
                                     Note that this field cannot be set when spec.os.name is windows.
                                   type: string
                                 readOnlyRootFilesystem:
@@ -4989,7 +4987,6 @@
                           When set to false, a new userns is created for the pod. Setting false is useful for
                           mitigating container breakout vulnerabilities even allowing users to run their
                           containers as root without actually having root privileges on the host.
-                          This field is alpha-level and is only honored by servers that enable the UserNamespacesSupport feature.
                         type: boolean
                       hostname:
                         description: |-
@@ -6159,7 +6156,6 @@
                                     procMount denotes the type of proc mount to use for the containers.
                                     The default value is Default which uses the container runtime defaults for
                                     readonly paths and masked paths.
-                                    This requires the ProcMountType feature flag to be enabled.
                                     Note that this field cannot be set when spec.os.name is windows.
                                   type: string
                                 readOnlyRootFilesystem:
@@ -6728,6 +6724,14 @@
 
                             It adds a name to it that uniquely identifies the ResourceClaim inside the Pod.
                             Containers that need access to the ResourceClaim reference it with this name.
+
+                            When the DRAWorkloadResourceClaims feature gate is enabled and this Pod
+                            belongs to a PodGroup, a PodResourceClaim is matched to a
+                            PodGroupResourceClaim if all of their fields are equal (Name,
+                            ResourceClaimName, and ResourceClaimTemplateName). A matched claim references
+                            a single ResourceClaim shared across all Pods in the PodGroup, reserved for
+                            the PodGroup in ResourceClaimStatus.ReservedFor rather than for individual
+                            Pods.
                           properties:
                             name:
                               description: |-
@@ -6753,6 +6757,16 @@
                                 generated component, will be used to form a unique name for the
                                 ResourceClaim, which will be recorded in pod.status.resourceClaimStatuses.
 
+                                When the DRAWorkloadResourceClaims feature gate is enabled and the pod
+                                belongs to a PodGroup that defines a PodGroupResourceClaim with the same
+                                Name and ResourceClaimTemplateName, this PodResourceClaim resolves to the
+                                ResourceClaim generated for the PodGroup. All pods in the group that
+                                define an equivalent PodResourceClaim matching the
+                                PodGroupResourceClaim's Name and ResourceClaimTemplateName share the same
+                                generated ResourceClaim. ResourceClaims generated for a PodGroup are
+                                owned by the PodGroup and their lifecycles are tied to the PodGroup
+                                instead of any individual pod.
+
                                 This field is immutable and no changes will be made to the
                                 corresponding ResourceClaim by the control plane after creating the
                                 ResourceClaim.
@@ -6878,6 +6892,28 @@
                         x-kubernetes-list-map-keys:
                         - name
                         x-kubernetes-list-type: map
+                      schedulingGroup:
+                        description: |-
+                          SchedulingGroup provides a reference to the immediate scheduling runtime
+                          grouping object that this Pod belongs to.
+                          This field is used by the scheduler to identify the group and apply the
+                          correct group scheduling policies. The association with a group also
+                          impacts other lifecycle aspects of a Pod that are relevant in a wider context
+                          of scheduling like preemption, resource attachment, etc. If not specified,
+                          the Pod is treated as a single unit in all of these aspects.
+                          The group object referenced by this field may not exist at the time the
+                          Pod is created.
+                          This field is immutable, but a group object with the same name may be
+                          recreated with different policies. Doing this during pod scheduling
+                          may result in the placement not conforming to the expected policies.
+                        properties:
+                          podGroupName:
+                            description: |-
+                              PodGroupName specifies the name of the standalone PodGroup object
+                              that represents the runtime instance of this group.
+                              Must be a DNS subdomain.
+                            type: string
+                        type: object
                       securityContext:
                         description: |-
                           SecurityContext holds pod-level security attributes and common container settings.
@@ -8306,7 +8342,7 @@
                                 A failure to resolve or pull the image during pod startup will block containers from starting and may add significant latency. Failures will be retried using normal volume backoff and will be reported on the pod reason and message.
                                 The types of objects that may be mounted by this volume are defined by the container runtime implementation on a host machine and at minimum must include all valid types supported by the container image field.
                                 The OCI object gets mounted in a single directory (spec.containers[*].volumeMounts.mountPath) by merging the manifest layers in the same way as for container images.
-                                The volume will be mounted read-only (ro) and non-executable files (noexec).
+                                The volume will be mounted read-only (ro).
                                 Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath) before 1.33.
                                 The field spec.securityContext.fsGroupChangePolicy has no effect on this volume type.
                               properties:
@@ -8478,8 +8514,7 @@
                               description: |-
                                 portworxVolume represents a portworx volume attached and mounted on kubelets host machine.
                                 Deprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type
-                                are redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate
-                                is on.
+                                are redirected to the pxd.portworx.com CSI driver.
                               properties:
                                 fsType:
                                   description: |-
@@ -9302,42 +9337,6 @@
                         x-kubernetes-list-map-keys:
                         - name
                         x-kubernetes-list-type: map
-                      workloadRef:
-                        description: |-
-                          WorkloadRef provides a reference to the Workload object that this Pod belongs to.
-                          This field is used by the scheduler to identify the PodGroup and apply the
-                          correct group scheduling policies. The Workload object referenced
-                          by this field may not exist at the time the Pod is created.
-                          This field is immutable, but a Workload object with the same name
-                          may be recreated with different policies. Doing this during pod scheduling
-                          may result in the placement not conforming to the expected policies.
-                        properties:
-                          name:
-                            description: |-
-                              Name defines the name of the Workload object this Pod belongs to.
-                              Workload must be in the same namespace as the Pod.
-                              If it doesn't match any existing Workload, the Pod will remain unschedulable
-                              until a Workload object is created and observed by the kube-scheduler.
-                              It must be a DNS subdomain.
-                            type: string
-                          podGroup:
-                            description: |-
-                              PodGroup is the name of the PodGroup within the Workload that this Pod
-                              belongs to. If it doesn't match any existing PodGroup within the Workload,
-                              the Pod will remain unschedulable until the Workload object is recreated
-                              and observed by the kube-scheduler. It must be a DNS label.
-                            type: string
-                          podGroupReplicaKey:
-                            description: |-
-                              PodGroupReplicaKey specifies the replica key of the PodGroup to which this
-                              Pod belongs. It is used to distinguish pods belonging to different replicas
-                              of the same pod group. The pod group policy is applied separately to each replica.
-                              When set, it must be a DNS label.
-                            type: string
-                        required:
-                        - name
-                        - podGroup
-                        type: object
                     required:
                     - containers
                     type: object

===== coordination.k8s.io/Lease /db9c8771.cnpg.io ======
--- /tmp/argocd-diff1747653220/db9c8771.cnpg.io-live.yaml
+++ /tmp/argocd-diff1747653220/db9c8771.cnpg.io
@@ -0,0 +1,11 @@
+apiVersion: coordination.k8s.io/v1
+kind: Lease
+metadata:
+  annotations:
+    argocd.argoproj.io/tracking-id: cloudnative-pg:coordination.k8s.io/Lease:cloudnative-pg/db9c8771.cnpg.io
+  labels:
+    app.kubernetes.io/component: manager
+    app.kubernetes.io/instance: cloudnative-pg
+    app.kubernetes.io/name: cloudnative-pg
+  name: db9c8771.cnpg.io
+spec: {}

argocd.hashbang.sh > external-dns (0 files changed)

Details
time="2026-06-19T19:04:36Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2026-06-19T19:04:39Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."

===== apps/Deployment external-dns/external-dns ======
--- /tmp/argocd-diff3045691686/external-dns-live.yaml
+++ /tmp/argocd-diff3045691686/external-dns
@@ -173,11 +173,6 @@
         - --provider=aws
         - --txt-owner-id=digitalocean-hashbang
         - --txt-prefix=_owner.
-        - --source=crd
-        - --domain-filter=hashbang.sh
-        - --managed-record-types=A
-        - --managed-record-types=CNAME
-        - --managed-record-types=TXT
         env:
         - name: AWS_REGION
           value: us-west-2
@@ -188,7 +183,7 @@
             secretKeyRef:
               key: key
               name: external-dns-iam
-        image: registry.k8s.io/external-dns/external-dns:v0.20.0@sha256:ddc7f4212ed09a21024deb1f470a05240837712e74e4b9f6d1f2632ff10672e7
+        image: registry.k8s.io/external-dns/external-dns:v0.21.0@sha256:f53faaf71cb270d1ca9dce6ea0c94bfebf1a18696263487f0fbc74b9bf2bd7ff
         imagePullPolicy: IfNotPresent
         name: external-dns
         ports:

@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed Apr 24, 2026
@renovate renovate Bot closed this Apr 24, 2026
@renovate renovate Bot deleted the renovate/registry.k8s.io-external-dns-external-dns-0.x branch April 24, 2026 18:04
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 Apr 24, 2026
@renovate renovate Bot reopened this Apr 24, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch 2 times, most recently from 7c95f10 to b464c9b Compare April 24, 2026 21:51
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed May 8, 2026
@renovate renovate Bot closed this May 8, 2026
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 May 8, 2026
@renovate renovate Bot reopened this May 8, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch 2 times, most recently from b464c9b to 6782cdb Compare May 8, 2026 13:14
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed May 23, 2026
@renovate renovate Bot closed this May 23, 2026
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 May 23, 2026
@renovate renovate Bot reopened this May 23, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch 2 times, most recently from 6782cdb to f5ee37a Compare May 23, 2026 17:28
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed May 29, 2026
@renovate renovate Bot closed this May 29, 2026
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 May 29, 2026
@renovate renovate Bot reopened this May 29, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch 2 times, most recently from f5ee37a to db534fe Compare May 29, 2026 13:34
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed May 31, 2026
@renovate renovate Bot closed this May 31, 2026
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 May 31, 2026
@renovate renovate Bot reopened this May 31, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch 2 times, most recently from db534fe to c6f65cd Compare May 31, 2026 17:36
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed Jun 7, 2026
@renovate renovate Bot closed this Jun 7, 2026
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 Jun 8, 2026
@renovate renovate Bot reopened this Jun 8, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch 2 times, most recently from c6f65cd to 09fd128 Compare June 8, 2026 02:54
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed Jun 19, 2026
@renovate renovate Bot closed this Jun 19, 2026
@renovate renovate Bot changed the title external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 - autoclosed external-dns: update registry.k8s.io/external-dns/external-dns Docker tag to v0.21.0 Jun 19, 2026
@renovate renovate Bot reopened this Jun 19, 2026
@renovate renovate Bot force-pushed the renovate/registry.k8s.io-external-dns-external-dns-0.x branch from 09fd128 to 9447659 Compare June 19, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants