publish-kubebuilder-tools: ensure we ask for a v prefix, and we check for it

Author: damdo

tools/publish-kubebuilder-tools/README.md

@@ -11,7 +11,7 @@ The archives are then optionally published to the release buck `openshift-kubebu
 
 `-pull-secret <string>`: The path to an OpenShift pull secret file that can pull from `registry.ci.openshift.org`
 `-payload <string>`: The payload image that should be used to create the artifacts. This should be from the CI stream. The format will be `registry.ci.openshift.org/ocp/release:<version>`
-`-version <string>`: The Kubernetes version to represent in the archives. This should be the Kubernetes release version from the payload, eg `1.29.1`.
+`-version <string>`: The Kubernetes version to represent in the archives. This should be the Kubernetes release version from the payload with the `v` prefix specified. eg `v1.29.1`.
 `-output-dir <string>`: A working directory to store the archives. The binaries will be extracted here and the archives will be created here.
 `-skip-upload <bool>`: Skip uploading the artifacts to the GCS bucket. This can be used if you are not authenticated to GCP.
 `-index-file <string>`: The path to the index file that should be updated with the new archives. This is optional and will default to `./envtest-releases.yaml`.

tools/publish-kubebuilder-tools/main.go

@@ -44,6 +44,11 @@ func main() {
 		panic("output is required")
 	}
 
+	// We only expect Kubernetes versions that begin with the v prefix.
+	if !strings.HasPrefix(*version, "v") {
+		panic("Kubernetes version must begin with the v prefix. Example: v1.33.2")
+	}
+
 	// Decrypt the pull secret to get the bearer token.
 	registryAuthToken, err := getRegistryAuthToken(*pullSecretFile)
 	if err != nil {