• Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • Testable
    • No
    • No
    • Pending
    • None
    • RHODS 1.22, RHODS 1.23, RHODS 1.24, RHODS 1.26, RHODS 1.27, RHODS 1.28, RHODS 1.29, RHODS 1.30, RHODS 1.32

      Currently, when a new namespace is created, it must be manually added to the service mesh configuration. 

      To improve this process, we need to develop a solution that allows for the automatic addition of namespaces to the service mesh. For example, Kubeflow profile controller creates a namespace for every user that logs in. The creation of a Data Science project will also result in a new namespace created.

      This solution should only apply to namespaces labeled in a specific way (e.g. "service-mesh=enabled") to avoid adding non-RHODS namespaces to Service Mesh, as this could be not desired by users.

      Ideally, it would not require the modification of existing controllers, but rather be implemented as a separate component that integrates with the service mesh.

      Acceptance Criteria

      • A new component is created that monitors the creation of namespaces with a specific label. 
      • When a matching namespace is created, the component automatically adds it to the service mesh configuration.
      • The component integrates seamlessly with the existing architecture, without the need to extend existing controllers.
      • Automated tests are provided to ensure correctness.
      • The component is deployed to production and is monitored for any issues.

              Unassigned Unassigned
              bartosz-1 Bartosz Majsak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: