This makes the user experience error-prone because if you set in the custom_images config with the key frontend_image rather than frontend, it will not work.
This is the case for channels latest/edge and 2.0/stable.
When setting the config as shown in the To Reproduce section below, the charm goes to error, that's not the expected behavior, it should rather log a warning and ignore the config. This happens due to issue #485 in kfp-profile-controller charm.
To Reproduce
juju deploy kfp-profile-controller --trust --channel=2.0/stable
juju config kfp-profile-controller custom_images
#output
custom_images:
default: |
visualization_server : ''
frontend_image : ''
# set the image as the default tells you
juju config kfp-profile-controller custom_images="visualization_server: 'gcr.io/ml-pipeline/visualization-server:2.0.3'
frontend_image: 'gcr.io/ml-pipeline/visualization-server:2.0.3'
"
# check juju status: charm goes to error
kfp-profile-controller/0* error
Bug Description
the default of the
custom_images
config forkfp-profile-controller
charm is:Meanwhile, the actual key used in the json defining the default images is:
This makes the user experience error-prone because if you set in the
custom_images
config with the keyfrontend_image
rather thanfrontend
, it will not work. This is the case for channelslatest/edge
and2.0/stable
.When setting the config as shown in the
To Reproduce
section below, the charm goes to error, that's not the expected behavior, it should rather log a warning and ignore the config. This happens due to issue #485 inkfp-profile-controller
charm.To Reproduce
Environment
1.25-strict/stable juju 3.1/stable
Relevant Log Output
Additional Context
No response