Which isn't ordered. But since we're generating a dictionary that gets turned into YAML, which then in turn gets deserialized by Juju, we're reliant on Go's deserialization behavior. Go doesn't guarantee any ordering according to https://github.com/golang/go/issues/27179, so any ordering we specify in the pod spec yaml won't necessarily be reflected in what Juju/Go parse from that YAML.
Additionally, I don't think I can solve this properly from within the charm. Here's where we generate the relevant pod spec:
https:/ /github. com/juju- solutions/ bundle- kubeflow/ blob/f233435c/ charms/ pipelines- api/reactive/ pipelines_ api.py# L176-L183
Which isn't ordered. But since we're generating a dictionary that gets turned into YAML, which then in turn gets deserialized by Juju, we're reliant on Go's deserialization behavior. Go doesn't guarantee any ordering according to https:/ /github. com/golang/ go/issues/ 27179, so any ordering we specify in the pod spec yaml won't necessarily be reflected in what Juju/Go parse from that YAML.