You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Kustomize for deployment of Kroki to Kubernetes. Use the zipped manifests from https://docs.kroki.io/kroki/setup/use-kubernetes/ and adding a kustomization.yaml file for some image name transforming, patching etc.
We would like to be able to mirror this repo with the base instead of wget the zip. Then we could use the base files from this repo using remote target in Kustomize in an overlay repo. The tag is then used for correct version with e.g.: ?ref=v0.21.3.
Like this:
If the yuzutech/kroki repo contained the base k8s manifest the mirrored repo could be used as a resource for internal overlays and deployed to K8s.
What to do:
add base manifeste to a folder in the repo (proposal /kustomize)
verify that the mirroring and overlay with remote target works as expected
We use Kustomize for deployment of Kroki to Kubernetes. Use the zipped manifests from https://docs.kroki.io/kroki/setup/use-kubernetes/ and adding a kustomization.yaml file for some image name transforming, patching etc.
We would like to be able to mirror this repo with the base instead of wget the zip. Then we could use the base files from this repo using remote target in Kustomize in an overlay repo. The tag is then used for correct version with e.g.:
?ref=v0.21.3
.Like this:
If the yuzutech/kroki repo contained the base k8s manifest the mirrored repo could be used as a resource for internal overlays and deployed to K8s.
What to do:
/kustomize
)If this sounds like an interesting idea, I could propose a PR.
The text was updated successfully, but these errors were encountered: