Automator: update istio@ test reference

[istio-testing]

Generated by Automator - 2025-06-15T02:01:42+00:00

[dhawton]

/retest

[AritraDey-Dev]

/retest

[dhawton]

/test doc.test.profile-none

still flaking.. not sure why.. containerd seems to indicate the curl pod started.

[istio-testing]

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
doc.test.profile-none_istio.io	e221908	link	unknown	/test doc.test.profile-none

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-sigs/prow repository. I understand the commands that are listed here.

[AritraDey-Dev]

Not appears to be a flake now...need to check the tests once

[craigbox]

Is it relevant that it's being installed with kube-inject?

+snip_apply_curl(): istioctl kube-inject --filename samples/security/spire/curl-spire.yaml
+snip_apply_curl(): kubectl apply -f -
+_wait_for_deployment default curl
+_wait_for_deployment(): local namespace=default
+_wait_for_deployment(): local name=curl
+_wait_for_deployment(): local context=
+_wait_for_deployment(): kubectl --context= -n default rollout status deployment curl --timeout 5m
+_wait_for_deployment(): echo 'Failed rollout of deployment curl in namespace default'
+_wait_for_deployment(): exit 1

I would have thought most of our examples would have had the injector running automatically

[AritraDey-Dev]

running the specific test that failed (automatic_registration_test.sh) in my local setup, I checked the logs at:

/work/out/linux_amd64/tests-setup-profile-none-460828/TestDocs/ops/integrations/spire/automatic_registration_test.sh/automatic_registration_test.sh/_test_context/automatic_registration_test.sh_output.txt
The last few lines show:

- Processing resources for Istio core.
✔ Istio core installed ⛵️
- Processing resources for Istiod.
- Processing resources for Istiod. Waiting for Deployment/istio-system/istiod
✘ Istiod encountered an error: failed to wait for resource: resources not ready after 5m0s: context deadline exceeded
  Deployment/istio-system/istiod (container failed to start: ImagePullBackOff: Back-off pulling image "istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31": ErrImagePull: rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31": failed to resolve reference "docker.io/istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31": docker.io/istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31: not found)
- Processing resources for Ingress gateways.
- Processing resources for Ingress gateways. Waiting for Deployment/istio-system/istio-ingressgateway
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: context deadline exceeded
  Deployment/istio-system/istio-ingressgateway (container failed to start: PodInitializing: )Error: failed to install manifests: 2 errors occurred:
	* failed to wait for resource: resources not ready after 5m0s: context deadline exceeded
  Deployment/istio-system/istiod (container failed to start: ImagePullBackOff: Back-off pulling image "istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31": ErrImagePull: rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31": failed to resolve reference "docker.io/istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31": docker.io/istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31: not found)
	* failed to wait for resource: resources not ready after 5m0s: context deadline exceeded
  Deployment/istio-system/istio-ingressgateway (container failed to start: PodInitializing: )

It seems the test is trying to pull the image istio/pilot:1.27-alpha.ebe60fc2d88e483f2b0bf88392b145ec7f36cb31, but it's not available. Even when I try pulling it locally using Docker, it fails with "manifest not known." So it appears this specific image tag does not exist or has not been pushed.

And the errImagebackoff error leads to another error in podInitializing.

[craigbox]

What you're seeing is a common problem with running the tests locally, but isn't the problem in this PR. You can see that Prow (our CI system) is able to pull the containers and start running but your error is that the Istio control plane can't start running at all. That suggests something different.