publish container linux and windows images in quay.io

[andyzhangx]

Is your feature request related to a problem?/Why is this needed

Describe the solution you'd like in detail

Currently docker files are under here:
https://github.com/kubernetes-csi/csi-driver-smb/blob/master/pkg/smbplugin/Dockerfile
https://github.com/kubernetes-csi/csi-driver-smb/blob/master/pkg/smbplugin/Windows.Dockerfile

could refer to:
https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/release-tools/travis.yml

do you know how to do that? thanks
@wozniakjan

cc @jingxu97 @msau42

Describe alternatives you've considered

Additional context

[wozniakjan]

hi @andyzhangx, the csi-release-tools repo contains very useful documentation on how to get started - https://github.com/kubernetes-csi/csi-release-tools/.

I am not entirely sure the tooling supports windows images too, tagging @pohly as he is much more knowledgeable point of contact with regards to the csi-release-tools.

[msau42]

We're trying to move our image publishing to the k8s-infra and @jingxu97 is working on getting Windows image building working there.

[andyzhangx]

@jingxu97 do you know how can I publish the repo image to quay, it should support both windows and linux image. I am thinking whether it's appropriate to host the images on mcr.microsoft.com which I am quite familiar with.

[xing-yang]

@andyzhangx we are moving away from quay and publish images to the community infra. See issue opened here: kubernetes-csi/csi-release-tools#86

@pohly is in the process of making this change for all kubernetes-csi repos.

See this one for example: kubernetes-csi/csi-proxy#54

[pohly]

https://github.com/kubernetes-csi/node-driver-registrar is successfully publishing multi-arch images that include Windows: https://console.cloud.google.com/gcr/images/k8s-staging-csi/GLOBAL/csi-node-driver-registrar?gcrImageListsize=30&gcrImageListsort=-uploaded

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.