fix : update ImageUpdateAutomation to use .Changed instead of deprecated .Updated field

[Copilot]

What changed?

Updated the messageTemplate field in the ImageUpdateAutomation resource to use .Changed.Images instead of the deprecated .Updated.Images field.

Why?

The Flux image-automation-controller v1 API deprecated the .Updated template field in favor of .Changed. The CRD documentation states:

Note: The Updated template field has been removed. Use Changed instead.

Using the deprecated field could cause issues with newer versions of Flux and prevents the dev resources from properly demonstrating current best practices.

Files changed

• tools/dev-resources/image-policy/podinfo-image-update-automation.yaml

Verification

All resources in tools/dev-resources have been validated:

• ✅ All API versions are current (v1)
• ✅ Resources apply successfully to a kind cluster with Flux v2.7.2
• ✅ Resources are visible via kubectl get commands
• ✅ Kustomize build completes successfully

The resources can be applied using:

kubectl apply -k tools/dev-resources

Fixes the issue where developers using the sample deployment resources would see deprecated field usage.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 10.244.0.10
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.3
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.4
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.5
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.6
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.7
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.8
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 10.244.0.9
  • Triggering command: /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.2 --node-labels= --pod-infra-container-image=registry.k8s.io/pause:3.10.1 --provider-id=kind://docker/test-dev-resources/test-dev-resources-control-plane --runtime-cgroups=/system.slice/containerd.service (packet block)
• 1164932772709279746.1309702655845493395
  • Triggering command: /coredns -conf /etc/coredns/Corefile (dns block)
• 2130457696441284333.3075999588063013010
  • Triggering command: /coredns -conf /etc/coredns/Corefile (dns block)
• 3249526845029377753.3131220860631069716
  • Triggering command: /coredns -conf /etc/coredns/Corefile (dns block)
• 54431273706179470.1042304047230757268
  • Triggering command: /coredns -conf /etc/coredns/Corefile (dns block)
• 7960923873720595517.6501378685945402161
• 8618234498239263128.8479008927510081715
  • Triggering command: /coredns -conf /etc/coredns/Corefile (dns block)
• fluxcd.io
  • Triggering command: curl -s REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update API versions in tools/dev-resources</issue_title>
<issue_description>Short description
As a Developer I want the tools sample deployment resources to have up to date API's

Acceptance criteria
tools/dev-resources install in kind cluster and are visible in the UI running in tilt

</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #5249

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow the
Conventional Commits specification
and it looks like your proposed title needs to be adjusted.

We use the pull request title in automated release changelog updates, and would like our
changelogs to look nice.

Details:

No release type found in pull request title "fix : update ImageUpdateAutomation to use .Changed instead of deprecated .Updated field". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit