Add workflow to automate backstage builds

[omrishiv]

What this does

This takes the work from https://github.com/cnoe-io/backstage-image-builder and merges it into this repository with an added Workflow file to automate building, tagging, and pushing the backstage image to ghcr. It uses the format ghcr.io/cnoe-io/backstage-app:GITSHA as the image name. This image will be built on every commit into the backstage-app repo, whether on a push to main or a PR. It also writes the image attestation to the repository for added supply chain security.

Example

https://github.com/omrishiv/backstage-app/actions/runs/9067164285

[jessesanford]

This is great. Thank you. @nabuskey I think you should probably take a look at this though.

[nabuskey]

What is this for? We are invoking the cnoe cli for no reason?

[omrishiv]

@jessesanford this is from your work; can you clarify? I just lifted it from the other repo.

[omrishiv]

I haven't thoroughly looked through the cli code, but does it use the same method as kubernetes to get a client? If that method is leveraged, it can use either the kubeconfig in the home directory or an in-cluster driven client using kubernetes service account and I believe we won't need this file.

[jessesanford]

This allows for us to just-in-time add the auth for the local Kubernetes cluster when the cnoe cli is invoked by the cnoe plugin to do perform the "verify" step. Without it, the cnoe cli invocation dies because it can't auth to the local kube.

[jessesanford]

+1 from me

[jessesanford]

This allows for us to just-in-time add the auth for the local Kubernetes cluster when the cnoe cli is invoked by the cnoe plugin to do perform the "verify" step. Without it, the cnoe cli invocation dies because it can't auth to the local kube.

[omrishiv]

@nabuskey Do you mind: https://stackoverflow.com/a/72585915

[OneCricketeer]

Is there an example of building this image with Argo Workflows and pushing into Gitea OCI registry? This would aid with faster development, I think. Ref #20

[nabuskey]

@OneCricketeer we don't have that yet. BUT we are building an example for building and pushing to the internal gitea registry as part of a workshop we are creating. It's still in WIP but is coming soon :)

If you can't wait you can probably base it off of this: https://github.com/cnoe-io/backstage-app/blob/main/.github/workflows/build-and-push.yaml

[OneCricketeer]

@nabuskey I believe I am part of that workshop 😉