create yaml manifests

[Raboo]

Describe the problem/challenge you have I want to treat my BuildKit backend as a persistent application to always have a running BuildKit in my k8s cluster. So I want to avoid having kubectl buildkit create and kubectl buildkit rm as a part of peoples workflows causing potentially a multitude of forgotten BuildKit deployments running in my k8s cluster since I share it with other people.

However I do not want to have a persistent application running that is setup from some cli command like kubectl buildkit create in a my-k8s-cluster-setup.sh. I do prefer to have it in a GitOps pipeline that manages the state of my k8s. So it would be great if there was a --yaml-output or a --dry-run command to kubectl buildkit create that creates/outputs Kubernetes YAML manifests of what it intends to apply in my cluster. That way I can take those files and put them in my pipeline.

My end goal will be to have one persistently running deployment of BuildKit with HPA for auto-scaling workers.

Description of the solution you'd like A --yaml-output or a --dry-run command to kubectl buildkit create that creates/outputs Kubernetes YAML manifests of what it intends to apply in my cluster.

Vote on this request

This is an invitation to the community to vote on issues. Use the "smiley face" up to the right of this comment to vote.

• :+1: "This project will be more useful if this feature were added"
• :-1: "This feature will not enhance the project in a meaningful way"

[dhiltgen]

Great suggestion! This would be a nice feature to add.

As a workaround until we get this implemented you can use kubectl get -o yaml deployment buildkit > buildkit.yaml (possibly with a little sanitizing of the results if necessary for your setup)

[Raboo]

Sure I could kubectl get all to retrieve all resources in a namespace as a workaround. But it requires a bunch of sanitizing as you said and it just feels that it would be to messy like that.