Avoid undesired image expansion in the template about rules_k8s HOT 5 CLOSED

A workaround for this is to change the deployment.yaml and use `:latest'.:

apiVersion: extensions/v1beta1
kind: Deployment
spec:
  replicas: 1
  template:
    spec:
      containers:
      - name: web-frontend
        image: web-frontend:latest

from rules_k8s.

We've had to work around this via an image tag, too. What do you think about using the Python Kubernetes client library to parse the YAML (rather than just walking the untyped YAML? Then we could just replace the image references using the typed structure the K8s Python client would give us.

Picking the right client version seems like the tricky part, as the rules don't have a notion of version yet.

from rules_k8s.

That wouldn't work well with CRDs, or with image names in contexts other than a corev1.Container's image: field.

e.g. in WarmImage I am using this to pass the digest of a sidecar I'm injecting into DaemonSets: https://github.com/mattmoor/warm-image/blob/master/release.yaml#L39

from rules_k8s.

@mattmoor I've come around to your view here. In fact, I propose an even more flexible expansion policy in #134, motivated by a workaround we have where the full YAML of an init container needs to be encoded as JSON and stuck into spec->template->metadata->annotations.pod.beta.kubernetes.io/init-containers. Maybe we just need better documentation on how this works and recommendations for using flexible image replacement without getting burned?

from rules_k8s.

Looks like this has died

from rules_k8s.