Check for Windows kube-proxy images during Azure VHD build pipeline
marosset opened this issue · 1 comments
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Today (and unfortunately) the Windows kube-proxy image used by CAPI/CAPZ clusters is built and published out of https://github.com/kubernetes-sigs/sig-windows-tools.
This means that it is possible to build and publish new reference VHDs without having corresponding kube-proxy images for a given K8s patch version which can result in cluster provisioning failures or unpredictable behavior.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Until SIG-Windows has automated building / publishing of new kube-proxy images (which depends on work being doing in https://github.com/kubernetes-sigs/windows-service-proxy) we should add a check to the pipelines that build Windows VHDs to ensure that a corresponding kube-proxy image is available for the K8s patch version the VHD is being built for.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
We have a github action at https://github.com/kubernetes-sigs/sig-windows-tools/actions/workflows/test-kube-proxy-images.yaml that checks to make sure we have kube-proxy images published as new patch versions come out.
/kind feature
/sig windows
/cc @mboersma @jsturtevant
/assign