Migrated kCTF from Google Container Registry to Artifact Registry#406
Migrated kCTF from Google Container Registry to Artifact Registry#406HlynurOskar wants to merge 5 commits intogoogle:v1from
Conversation
sirdarckcat
left a comment
There was a problem hiding this comment.
Please also update
Line 98 in 4382f91
| case "${CLUSTER_TYPE}" in | ||
| gce) | ||
| IMAGE_URL="${REGISTRY}/${PROJECT}/${CHALLENGE_NAME}-${IMAGE_NAME}:${IMAGE_ID}" | ||
| IMAGE_URL="${REGISTRY}/${PROJECT}/${CLUSTER_NAME}-${CHALLENGE_NAME}/${IMAGE_NAME}:${IMAGE_ID}" |
There was a problem hiding this comment.
Is there a difference between slashes here? Maybe just add slashes too, for consistency.
There was a problem hiding this comment.
There is a significance to the slashes, it's a path that gets parsed.
Although, some want the path to be more like:
IMAGE_URL="${REGISTRY}/${PROJECT}/challenges/${CLUSTER_NAME}-${CHALLENGE_NAME}-${IMAGE_NAME}:${IMAGE_ID}"
There was a problem hiding this comment.
What if we have a dash in the cluster? Wouldn't that cause a collision?
There was a problem hiding this comment.
the registry should be shared by all challenges, so we can create it in kctf cluster create rather than managing several in kctf challenge. I used IMAGE_URL="${REGISTRY}/${PROJECT}/${CLUSTER_NAME}/${CHALLENGE_NAME}-${IMAGE_NAME}:${IMAGE_ID}"
should registry creation be part of this PR? Container Registry is shutting down very soon
Container Registry is deprecated and scheduled for shutdown. After May 15, 2024, Artifact Registry will host images for the gcr.io domain in Google Cloud projects without previous Container Registry usage. After March 18, 2025, Container Registry will be shut down.