You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CI for release-1.26 branch has been failing for this test since CAPZ switching to OOT credential provider PR: Cloud provider Azure e2e suite: [It] Azure Credential Provider should be able to pull private images from acr without docker secrets set explicitly [Credential] Build
What you expected to happen:
OOT credential provider works with cloud-provider-azure release-1.26.
How to reproduce it (as minimally and precisely as possible):
Test Cloud provider Azure e2e suite: [It] Azure Credential Provider should be able to pull private images from acr without docker secrets set explicitly [Credential]
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
Others:
The text was updated successfully, but these errors were encountered:
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/test-infra repository.
What happened:
CI for release-1.26 branch has been failing for this test since CAPZ switching to OOT credential provider PR:
Cloud provider Azure e2e suite: [It] Azure Credential Provider should be able to pull private images from acr without docker secrets set explicitly [Credential]
Build
What you expected to happen:
OOT credential provider works with cloud-provider-azure release-1.26.
How to reproduce it (as minimally and precisely as possible):
Test
Cloud provider Azure e2e suite: [It] Azure Credential Provider should be able to pull private images from acr without docker secrets set explicitly [Credential]
Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: