Open nishant-dash opened 7 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5269.
This message was autogenerated
this charm erroring out effectively breaks segregation between charmed kubeflow services and other workloads (when the pods get restarted that is)
also chatted with @kimwnasptd and we agree that it makes sense for this functionality to exist in juju itself
Bug Description
the charm gets into this state wheres logging tls errors and it stays active idle. Its not working as expected and is not injecting configs specified in its
settings_yaml
config to the other pods (in the corresponding namespaces.)There is no proper visibility into the state of this charm outside of logs. It would be nice if the charm workload status reflected its state and it could forward its logs to COS(loki).
To Reproduce
N/A
Environment
Relevant Log Output
Additional Context
settings_yaml
config