A jk Kubernetes operator

[dlespiau]

It would be useful to be able to have a jk program in a git repository and create k8s resources from it. It could look like

• store the jk module(s) in a ConfigMap
• create a Custom Resource pointing at the config map, maybe with input parameters and the docker image to use to run the script with (so node_modules can be prepopulated in that image).
• flux can sync ConfigMap and custom resource to the cluster
• an operator would create a pod with the image defined in 2) to run jk in. We need to get the results (files) back, with a small protocol between the two
• cluster objects need to be modified to have an ownerReference pointing a the customResource
• create the jk-produced resources

[brandonkal]

Have you seen this? I'd love to see jk as a templating option in that generic controller. Because jk is only a config generator (as it should be), jk should integrate there rather than building duplicate logic to handle creation and lifecycle of resources and requiring the user to interact with yet another Custom Resource and CRD.