Click on "Create version" in the Marketplace UI

[maelvls]

Let's see how we "wire" the stuff we did with cloudbuild.yml and the actual solution on the Marketplace jetstack-secure-for-cert-manager.

Here are all the fields we have to fill in order to "test" our solution "live" here:

[maelvls]

From the above screenshot:

You don't have any usable tagged deployer images in your Container Registry repo. Your deployer images should reside under gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer.

Learn how  to package your application.

A version should correspond to a minor version (e.g. "1.0") according to semantic versioning  (not a patch version, such as "1.0.0"). Update the same version for patch releases, which should be backward-compatible, instead of creating a new version.

Only create versions for tags that you want in your final application (i.e. no "test" versions) since published versions cannot be immediately deleted.

So I guess we don't even have to bother with the bucket stuff, we just need to

1. Create some cluster in the project jetstack-public, let's call it cloudbuild for example:

   gcloud services enable cloudbuild.googleapis.com
   gcloud services enable container.googleapis.com
   gcloud container clusters create smoke-test --region europe-west2-b --num-nodes=1 --preemptible --workload-pool=jetstack-public.svc.id.goog

2. Run

   gcloud builds submit  --timeout 1800s --config cloudbuild.yaml \
     --substitutions _CLUSTER_NAME=cloudbuild,_CLUSTER_LOCATION=europe-west2-b,_SOLUTION_NAME:     jetstack-secure-for-cert-manager

   which should push

   gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.0.0

3. See that the blue "Create" button is now ungrayed!

[maelvls]

I ran Cloud Build on my own cluster, which succeeded. The deployer is

gcr.io/jetstack-mael-valais/jetstack-secure-for-cert-manager/deployer:1.1.0-gcm.1

I will now:

• retag and push the deployer image to gcr.io/jetstack-public/jetstack-secure-for-cert-manager and also push the moving tags "minor tag" 1.1 and "patch tag" 1.1.0:
  → ⚠️ NOTE ⚠️ THIS IS NOW DONE AS IN THE bloudbuild.yaml as of Disable retagging in cloudbuild.yaml due to the licenses requirements #33

  docker pull gcr.io/jetstack-mael-valais/jetstack-secure-for-cert-manager/deployer:1.1.0-gcm.1
  docker tag gcr.io/jetstack-mael-valais/jetstack-secure-for-cert-manager/deployer:1.1.0-gcm.1 gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1.0-gcm.1
  docker push gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1.0-gcm.1
  docker tag gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1{.0-gcm.1,}
  docker push gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1
  docker tag gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1.0{-gcm.1,}
  docker push gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1.0
  docker pull gcr.io/jetstack-mael-valais/jetstack-secure-for-cert-manager/smoke-test:1.1.0-gcm.1
  docker tag gcr.io/jetstack-mael-valais/jetstack-secure-for-cert-manager/smoke-test:1.1.0-gcm.1 gcr.io/jetstack-public/jetstack-secure-for-cert-manager/smoke-test:1.1.0-gcm.1
  docker push gcr.io/jetstack-public/jetstack-secure-for-cert-manager/smoke-test:1.1.0-gcm.1
  docker tag gcr.io/jetstack-public/jetstack-secure-for-cert-manager/smoke-test:1.1{.0-gcm.1,}
  docker push gcr.io/jetstack-public/jetstack-secure-for-cert-manager/smoke-test:1.1
  

• add the 1.1.0-gcm.1 tag to all the existing google-review tags since we will be re-using the images built by Jake with the right licences
• Press the "release" button!

[maelvls]

Here is how I filled the release information. I used the headline in this google doc as the "description" field (64 characters max)

[maelvls]

The "Deploy documentation URL" field is mandatory (see above screenshot, or in the solution release page)

Here is what Gitlab has set for their "Deploy documentation URL":

• Public Git repo: https://github.com/GoogleCloudPlatform/click-to-deploy
• Deploy documentation URL: https://github.com/GoogleCloudPlatform/click-to-deploy/blob/master/k8s/gitlab/README.md

I think we could do something similar but that would require us to make the jsp-gcm repo public:

• Public Git repo: https://github.com/jetstack/jsp-gcm
• Deploy documentation URL: https://cert-manager.io/docs/installation/google-cloud-marketplace (to be created)

Other examples:

• Unleash Enterprise (paid offering) also has the CLI deploy documentation on their README.md

  • Public Git repo: https://github.com/unleash-hosted/unleash-hosted-gcp-marketplace
  • Deploy documentation URL: https://www.unleash-hosted.com/google-cloud-marketplace ❌ this link seems to link to the UI instructions instead of the CLI instructions!
  

• Hedera Mirror Node (free) has their CLI deploy documentation in the README.md of the GCM repo

  • Public Git repo: https://github.com/hashgraph/hedera-mirror-node
  • Deploy documentation URL: https://github.com/hashgraph/hedera-mirror-node/blob/master/charts/marketplace/gcp/README.md
  

[maelvls]

I did the onboarding steps with the Unleash Enterprise (paid offering) also has the CLI deploy documentation on their README.md solution, and it is similar to the Gitlab's README.md:

• no mention of the deployer image,
• no mention of the mpdev tool either,
• just plain helm template + kubectl apply (no direct helm install)
• the service account IS created by this helm chart
• the "license key" button is the secret created for the ubbagent

trying-unleash-enterprise-on-the-google-cloud-marketplace.mp4

[maelvls]

I'll be able to press the "Release" button as soon as #22 is done.

[maelvls]

I had to re-run gcloud builds submit since we made a couple of changes (build logs).

⚠️ Note ⚠️ To update the existing 1.1 version, I had to

1. go to the solution versions
2. click on the 1.1 tag
3. wait until the spinning wheel stops
4. click on "Save" or "Update images" (not sure which one)

[maelvls]

The "Create version" has been clicked!!

• You can see the draft solution page; right now the UI deployment cannot work since the images are at gcr.io but the marketplace UI wants them to be at marketplace.gcr.io and we don't have access to this repository (images might automatically be pushed after the review of the solution)
• The UI flow does not work yet (see above point)
• The CLI flow does not work either since the "Generate license file" does not appear. We asked Google, still waiting for an answer.

The next step is to click on "Submit for review" on the admin solution page.

Closing this issue then!