cloudbuild: fix epoch dating on staged image tags

[BlaineEXE]

Using gcloud container images add-tag to add tags to images built and pushed to GCR was resulting in the added tags having a date of Dec. 31, 1969 (the epoch). In order to avoid tags having epoch dates, adjust the cloudbuild script to use --tag arguments for each tag.

I did a dry run of this, and I think everything looks right

GIT_TAG: hash-v0.2.0-stuff
PULL_BASE_REF: v0.2.0
PLATFORM: linux/amd64,linux/arm64
+ REPO=gcr.io/k8s-staging-sig-storage
+ CONTROLLER_IMAGE=gcr.io/k8s-staging-sig-storage/objectstorage-controller
+ SIDECAR_IMAGE=gcr.io/k8s-staging-sig-storage/objectstorage-sidecar
+ export DOCKER=/buildx-entrypoint
+ DOCKER=/buildx-entrypoint
+ export PLATFORM
+ export SIDECAR_TAG=gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:hash-v0.2.0-stuff
+ SIDECAR_TAG=gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:hash-v0.2.0-stuff
+ export CONTROLLER_TAG=gcr.io/k8s-staging-sig-storage/objectstorage-controller:hash-v0.2.0-stuff
+ CONTROLLER_TAG=gcr.io/k8s-staging-sig-storage/objectstorage-controller:hash-v0.2.0-stuff
+ ADDITIONAL_BUILD_ARGS=--push
+ ADDITIONAL_CONTROLLER_TAGS=()
+ ADDITIONAL_SIDECAR_TAGS=()
+ [[ v0.2.0 == main ]]
+ [[ v0.2.0 == release-* ]]
+ [[ v0.2.0 == controller/* ]]
+ [[ v0.2.0 == sidecar/* ]]
+ [[ v0.2.0 == \v\0\.* ]]
+ echo ' ! ! ! this is a tagged controller + sidecar release ! ! !'
 ! ! ! this is a tagged controller + sidecar release ! ! !
+ TAG=v0.2.0
+ ADDITIONAL_CONTROLLER_TAGS+=("${CONTROLLER_IMAGE}:${TAG}")
+ ADDITIONAL_SIDECAR_TAGS+=("${SIDECAR_IMAGE}:${TAG}")
+ BUILD_ARGS=--push
+ for tag in "${ADDITIONAL_CONTROLLER_TAGS[@]}"
+ BUILD_ARGS='--push --tag=gcr.io/k8s-staging-sig-storage/objectstorage-controller:v0.2.0'
+ export BUILD_ARGS
+ echo make build.controller
make build.controller
+ BUILD_ARGS=--push
+ for tag in "${ADDITIONAL_SIDECAR_TAGS[@]}"
+ BUILD_ARGS='--push --tag=gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v0.2.0'
+ export BUILD_ARGS
+ echo make build.sidecar
make build.sidecar

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BlaineEXE

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BlaineEXE]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[xing-yang]

/lgtm