Add image-build action [WIP] #12
Conversation
| push: | ||
| # Sequence of patterns matched against refs/tags | ||
| tags: | ||
| - "v*" # Push events to matching v*, i.e. v1.0, v20.15.10 |
There was a problem hiding this comment.
we may need re-consider this, eventually we'll have to onboard to ARS and they'll distribute the ECR repo to all the regions for EKS add on, it may be "automated" if we use the latest tag, we need to sync with them about this process -- not a blocker comment just sharing
There was a problem hiding this comment.
hm interesting, so I tested this, it does not work out of the box, e.g. having 2 images in repo:
- s3-csi-driver-test:v0.0.1alpha
- s3-csi-driver-test:v0.0.2alpha
it does not automatically resolve latest tag (I had a suspicion that it will):
Normal BackOff 8s kubelet Back-off pulling image "151381207180.dkr.ecr.eu-west-1.amazonaws.com/s3-csi-driver-test:latest"
but it seems like a feasible adjustment to tag image with the "greatest" v0.0.2 tag also as latest at the end of this action (it will require some shell scripting and version parsing though)
| - "v*" # Push events to matching v*, i.e. v1.0, v20.15.10 | ||
|
|
||
| env: | ||
| REGION : "us-east-1" |
Image push / release process:
https://quip-amazon.com/oVYJA1EmXaJ4/S3-CSI-Driver-basic-CI#temp:C:SPK8c350dd1b54b4b35883dee91d