k8s-provisioner seems to be ignoring config options defined on bundle

[Pedro Guimarães]

When configuring charm mariadb [1] on my bundle for k8s-provisioner, like this: https://pastebin.canonical.com/p/6nGh7W8WkQ/

I can see database is correctly configured following "database" option, however root-password is ignored. I can verify this via juju config katib-db, which returns empty "root-password".

The full bundle I am using is: https://github.com/juju-solutions/bundle-kubeflow/blob/master/bundle.yaml

[1] https://jaas.ai/u/kubeflow-charmers/mariadb/15

[Ian Booth (wallyworld)]

I can't reproduce this using Juju 2.6. What version of Juju are you using?

$ cat test-bundle.yaml
bundle: kubernetes
applications:
  katib-db:
    charm: cs:~kubeflow-charmers/mariadb
    source: ./test/mariadb
    scale: 1
    annotations:
      gui-x: '0'
      gui-y: '1036'
    options:
      database: katib
      root-password: "passw0rd"

$ juju deploy ./test-bundle.yaml
$ juju config katib-db
...
  root-password:
    default: ""
    description: |
      Password to use for the database root user. If not specified,
      one will be generated automatically.
    source: user
    type: string
    value: passw0rd
$ kubectl edit pod/katib-db-0
...
spec:
  containers:
  - env:
    - name: MYSQL_ROOT_PASSWORD
      value: passw0rd
    image: registry.jujucharms.com/kubeflow-charmers/mariadb/oci-image@sha256:3b00a364fb7
    imagePullPolicy: IfNotPresent
    name: mariadb
...

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.