Closed dirien closed 2 years ago
@dirien I will gladly take a PR with a fully implemented Operator 😉 Jokes aside, the use case is valid though, even more once we are ready to ship Checkly to private / behind the firewall locations.
I am sure you are halfway done, with your already existing terraform provider which contains a big part of the logic already.
What left, would be a new wrapper aka the Operator Framwork and cutting out the core logic from the terraform provider.
but then again, its easy to talk from the Spielfeldrand 😉
Annotations on resources are cool but a CRD could be easier to build and maintain, both for Checkly & users of that CRD.
It would work very similar to how Terraform provider works.
In short, it would just provide a Kubernetes-native way to define checks. A Checkly user can template it with regular tools like Helm and kustomize, use existing CI flows to deploy the manifests etc.
I like the idea too, but i want it dynamically depending on the ingress i spawn.
Having to maintain an Ingress with the path an host variables and adding them to an seperate crd could break the DRY approach.
But then i am lazy 😄
let us close this one, and reopen or recreate if needed.
found this via google any reference where to follow up from here would be helpful.
@Vad1mo, we can reopen this if we get feedback from Checkly that they consider any work in this direction.
@Vad1mo @dirien we are not planning any work in this direction. With our public API I think an open source effort would receive a warm welcome though! Some links to maybe help:
@dirien @Vad1mo we have a repo for this open right now in collaboration with the folks at IMG Arena https://github.com/checkly/checkly-operator
We will support the team working on that there, so any input and PR's are more than welcome.
Closing this one for now!
It would be nice to have an Checkly Kubernetes Operator, where i could just annotate my ingress ressource with checkly specific informations.
Like
So any exposed endpoint gets automatically add to checkly and the perform the checks.
More fancy checks could be also part of a configmap for the operator...