feat(ci): setup CI to push scorecard, bundle images and run scorecard

[tthvo]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

---

Fixes: #227, #493
Depends on #589

Description of the change:

• Add CI to push bundle and scorecard image (if not exists) to quay.io.
• Add CI to run envtest and scorecard.

Motivation for the change:

See #227, #493

How to manually test:

See CI job status:

• https://github.com/tthvo/cryostat-operator/actions/runs/5042553727/jobs/9043312859
• https://github.com/tthvo/cryostat-operator/actions/runs/5042639850/jobs/9043480603?pr=4

Push jobs on main push is failing on my repo since it does not have access to cryostat/cryostat but build steps seems to work fine.

Others

We also need to remove checks for build Expected — Waiting for status to be reported as CI job name is changed.

[ebaron]

I've seen this action before: https://github.com/helm/kind-action. Not sure if it would make things any easier for this PR, but wanted to let you know it exists.

[tthvo]

I've seen this action before: https://github.com/helm/kind-action.

Thanks! We still need to pass in the path to config file. Tho, we can set a fixed version of kind and kubectl. Is there a version we want to set or whatever version (seems like latest) comes with ubuntu-latest is fine?

[ebaron]

One thing I noticed that's missing here is a CI image for the operator controller image. This means that any code changes aren't reflected in the bundle image, only YAML changes. We should push the operator image to ghcr.io and then pass that image to make bundle with OPERATOR_IMG.

[tthvo]

We should push the operator image to ghcr.io and then pass that image to make bundle with OPERATOR_IMG.

Do u think we should patch the manager's pod template or the operator SA with the pullImageSecret?

[tthvo]

operator-sdk run bundle is stuck waiting for the deployment to roll out. Let me try patching the deployment config before generating bundle.

https://github.com/tthvo/cryostat-operator/actions/runs/5082564293/jobs/9132453979

[tthvo]

Not the most intuitive way to patch imagePullSecrets but seems to work nicely:

Patch: 46e6741

Test run: https://github.com/tthvo/cryostat-operator/actions/runs/5083194894/jobs/9133896077

How about that?

[github-actions]

This PR/issue depends on:

• test(scorecard): enable scorecard on k8s #589
  By Dependent Issues (🤖). Happy coding!

[tthvo]

@ebaron Latest run after rebasing: https://github.com/tthvo/cryostat-operator/actions/runs/5083932753/jobs/9135558209

[ebaron]

Works well! Awesome job on getting this done @tthvo! Thank you!

[andrewazores]

This is awesome, finally knocking off a major piece of that puzzle for doing CI in a k8s environment.

[tthvo]

Niceee thanks you^^ Happy I could help with it :))