Change of release name and conventions

jtblin / kube2iam

kube2iam provides different AWS IAM roles for pods running on Kubernetes

BSD 3-Clause "New" or "Revised" License

1.97k stars 318 forks source link

Change of release name and conventions #315

Open paul-mesnilgrente opened 3 years ago

paul-mesnilgrente commented 3 years ago

Hi,

I'm seeing a difference between the latest two releases. The project was going for 0.10.10, 0.10.11.

And suddenly it's kube2iam-2.5.2, kube2iam-2..0.0. I couldn't find any reason for that. Where is 2.5.2 coming from? Is it still the same thing?

My main question is, is there breaking changes in the docker image kube2iam-2.6.0 and 0.10.11? I'm having issues with the arm64 architecture and I see that the latest release has support for it.

antoinedeschenes commented 3 years ago

kube2iam-* tags are for the helm chart, however no one set up a regex filter on Docker Hub to prevent building docker images at the same time

paul-mesnilgrente commented 3 years ago

What do you mean by

kube2iam-* are for the helm chart ?

when I run helm show values kube2iam/kube2iam it gives me

image:
  repository: jtblin/kube2iam
  tag: 0.10.9

Not quite sure to understand.

antoinedeschenes commented 3 years ago

The actual chart version https://github.com/jtblin/kube2iam/blob/0674908a09796246ee2309344628486d791430f6/charts/kube2iam/Chart.yaml#L3

paul-mesnilgrente commented 3 years ago

Maybe we can just stop that conversation by just answering this question. Can the kube2iam-2.6.0 docker image be used in place of the 0.10.11 one?

If not, do you think support for arm64 will happen?