the charm exposes config for port and management-port but these are only used to configure the KubernetesServicePatch. I think these are meant to represent the ports that the kubeflow-profiles and kfam containers expose - when would a user need to adjust these with juju config? For example, how can I make juju deploy kubeflow-profiles --config port=8888 work with this charm?
What I think is missing here is telling the underlying workload containers to actually use these ports. As is, it looks like these port configs change how the data is routed, but do not make sure something is listening at the new place.
the charm exposes config for
portandmanagement-portbut these are only used to configure theKubernetesServicePatch. I think these are meant to represent the ports that the kubeflow-profiles and kfam containers expose - when would a user need to adjust these withjuju config? For example, how can I makejuju deploy kubeflow-profiles --config port=8888work with this charm?What I think is missing here is telling the underlying workload containers to actually use these ports. As is, it looks like these port configs change how the data is routed, but do not make sure something is listening at the new place.