e2e: move to use the maintained orchestrator-k8s helm chart

[rgolangh]

Signed-off-by: Roy Golan rgolan@redhat.com

[rgolangh]

@gfarache @masayag hoping this change will help catching errors like the auth issues with notifs more quicker

This will work nicely with the change by @masayag to always send notifications.

Also, I assume the orchestrator-k8s chart would need some changes, like bumping the notification plugin versions, and few config changes.

[masayag]

@gfarache @masayag hoping this change will help catching errors like the auth issues with notifs more quicker

This will work nicely with the change by @masayag to always send notifications.

Also, I assume the orchestrator-k8s chart would need some changes, like bumping the notification plugin versions, and few config changes.

The required changes are replacing the existing notifications plugins with the new one and add also the signal plugin.
ATM we have those artifacts on in the staging registry - https://npm.stage.registry.redhat.com/

[rgolangh]

@gfarache @masayag hoping this change will help catching errors like the auth issues with notifs more quicker
This will work nicely with the change by @masayag to always send notifications.
Also, I assume the orchestrator-k8s chart would need some changes, like bumping the notification plugin versions, and few config changes.

The required changes are replacing the existing notifications plugins with the new one and add also the signal plugin. ATM we have those artifacts on in the staging registry - https://npm.stage.registry.redhat.com/

no upstream packages?

[masayag]

@gfarache @masayag hoping this change will help catching errors like the auth issues with notifs more quicker
This will work nicely with the change by @masayag to always send notifications.
Also, I assume the orchestrator-k8s chart would need some changes, like bumping the notification plugin versions, and few config changes.

The required changes are replacing the existing notifications plugins with the new one and add also the signal plugin. ATM we have those artifacts on in the staging registry - https://npm.stage.registry.redhat.com/

no upstream packages?

I am unaware of a version of those plugins being released as dynamic plugins to the upstream.
Let's confirm this with @batzionb @mareklibra

[batzionb]

There are upstream plugins for the orchestrator plugin
Different story with notifications plugins

[rgolangh]

closing in favour of #313