diff options
| author |  Yong Tang <yong.tang.github@outlook.com>
| 2022-02-22 06:35:16 -0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2022-02-22 09:35:16 -0500 |
| commit | d3a118e1c175eb00a0c171c2d2616dbaf39cdbba (patch) | |
| tree | 9712b3cf3de25ea3abe8d042a0949ee80d0fcc8a /plugin/kubernetes/kubernetes.go | |
| parent | 74d4e9bb1b043a3ad5699d94d74e1d7d95ef8135 (diff) | |
| download | coredns-d3a118e1c175eb00a0c171c2d2616dbaf39cdbba.tar.gz coredns-d3a118e1c175eb00a0c171c2d2616dbaf39cdbba.tar.zst coredns-d3a118e1c175eb00a0c171c2d2616dbaf39cdbba.zip | |
Avoid expose arch-specific docker image tags (#5201)
This PR tries to address the issue in 5199
where there were confusion on which image tag to use.
Because the image-specific `coredns/coredns-{arch}:version` is not usable
for all arch other than arm64, confusion happens.
This PR, for all arch-specific docker images:
1. Use `coredns/coredns:{arch}-version` (not `coredns/coredns-{arch}:version`)
so that all images remain within the same docker repo (not multiple repos).
2. Push the arch-specific image `coredns/coredns:{arch}-version` to dockerhub.
3. Create manifest-specific `coredns/coredns:version` and `coredns/coredns:latest` from arch-specific images.
4. Push `coredns/coredns:version` and `coredns/coredns:latest` to dockerhub
5. Delete arch-specific image tags `coredns/coredns:{arch}-version` from dockerhub.
This will make arch-specific image tags invisible, but the `coredns/coredns:version` and `coredns/coredns:latest`
will work as expected.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
Diffstat (limited to 'plugin/kubernetes/kubernetes.go')
0 files changed, 0 insertions, 0 deletions