Charmed Kubeflow 1.7 Airgapped deployment - user namespace repository about bundle-kubeflow HOT 3 OPEN

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5476.

This message was autogenerated

from bundle-kubeflow.

Since the admin namespace is a user's namespace, I'm pretty sure this is coming from the kfp-profile-controller. What I think we've missed is that we need to set the environment variables FRONTEND_IMAGE and VISUALIZATION_SERVER_IMAGE here when creating the deployment for the kfp-profile-controller's sync.py (or, in @Barteus case, since I think ckf 1.7 uses a podspec version of the charm, wherever the equivalent place was back then).

from bundle-kubeflow.

@ca-scribner is right, I did some digging ... both the podspec and the sidecar rewrite are setting those images in sync.py here and here. The value is propagated from the env variables VISUALIZATION_SERVER_IMAGE and FRONTEND_IMAGE ... its also important to note that the tags are received from variables VISUALIZATION_SERVER_TAG and FRONTEND_TAG which are by default set to value of KFP_VERSION example here. We were never setting those variables and because of that the images were using default values.

In charm code we need to create default-custom-images.json with both images set and then correctly set the envronment variables.

from bundle-kubeflow.