Open ca-scribner opened 6 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5167.
This message was autogenerated
Some different communication paths to keep track of:
Context
To support improved network isolation of Charmed Kubeflow components, we need to document all the communication paths that exist between Charmed Kubeflow's charms. This is important so we have a reference doc that we can design off of when hardening the networking security within Charmed Kubeflow.
In particular, this will be useful for defining tests cases and identifying special cases within the communication. The documentation should include the URLs that need to be exposed (eg:
/metrics
, etc) so we can know whatAuthorizationPolicy
objects need to be defined, and possibly so we can define broaderAuthorizationPolicy
objects that apply to multiple applications.What needs to get done
see DoD
Definition of Done