Expand more data in the template about rules_k8s HOT 9 CLOSED

This would be useful for other projects too, see:
https://github.com/istio/istio/blob/HEAD/install/updateVersion.sh and https://github.com/istio/istio/tree/HEAD/install/kubernetes/templates

from rules_k8s.

I had this in my initial prototype and specifically avoided it because templating is a hot topic of debate in the K8s space right now.

I would much rather see this solved by templating rules that compose with (or even wrap) these rules. rules_jsonnet is an option, but without this may be of limited use.

from rules_k8s.

I'm going to close this for now, but happy to continue the discussion. If specific items fall out of further discussion, let's open more bugs. WDYT?

from rules_k8s.

It is mostly a question of what the purpose of the k8s rules is. if it is to configure the k8s templates for the given build, then we should look for a templating solution as part of it. I have an idea that I will try today and keep you posted.

from rules_k8s.

At this point I would say: mostly development.

I want folks to be able to build/push/deploy in a tight cycle, and for that Bazel needs to be able to model the dependencies of the K8s resources.

There is possibility for involving this in a release process to "freeze" templates via something like:

bazel run :everything > release.yaml

(I use that here)

I agree that templating is often the next thing folks will want, but the DSL wars for K8s are just getting started, so my goal is for rules_k8s to compose with things like rules_jsonnet vs. embed very limited templating (as my original prototype did).

You can see some of the original discussion on this here.

from rules_k8s.

@ensonic ... and yes, keep me posted (but I'm OOTO starting tonight).

from rules_k8s.

The problem with bazel run :everything > release.yaml is that this assumes all those things are safe to run. We have a build with all kind of things, tools, services, .... For some targets 'run' would actually run a binary. So conceptually we want to build everything and for the k8s rules that would mean to resolve the yaml files.

from rules_k8s.

For some targets 'run' would actually run a binary

bazel run on k8s_object[s] just publishes the images and prints the resolved template to stdout. It should not run any binaries. We do this on bazel run because publishing is non-hermetic, and neither is accessing your credential keyring.

from rules_k8s.

is there a way to use a list or object in the template?

from rules_k8s.