**What happened**: I am trying to install submariner add-ons from the UI on two ppc64le clusters in IBM Cloud. IBM Cloud is not a supported provider so some manual steps are required, but we used to be able to install the submariner add-ons using the UI anyway. **What you expected to happen**: Submariner add-ons should install even if the cloud provider is not supported. **How to reproduce it (as minimally and precisely as possible)**: Try to install submariner add-ons from UI with clusters managed by unsupported cloud provider. **Anything else we need to know?**: **Environment**: - Submariner version (use `subctl version`): - Kubernetes version (use `kubectl version`): - Diagnose information (use `subctl diagnose all`): - Gather information (use `subctl gather`) - Cloud provider or hardware configuration: - OS (e.g `cat /etc/os-release`): - Kernel (e.g `uname -a`): - Install tools: - Others:
Created attachment 1880723 [details] YAML is empty
Created attachment 1880724 [details] YAML is empty
The YAML generated bythe UI should contain at least the Broker and the two ManagedClusterAddOn. This is what we do to deploy submariner from the CLI: $ oc apply -f - << EOF apiVersion: addon.open-cluster-management.io/v1alpha1 kind: ManagedClusterAddOn metadata: name: submariner namespace: local-cluster spec: installNamespace: submariner-operator EOF $ oc apply -f - << EOF apiVersion: addon.open-cluster-management.io/v1alpha1 kind: ManagedClusterAddOn metadata: name: submariner namespace: roks-cluster spec: installNamespace: submariner-operator EOF $ oc apply -f - << EOF apiVersion: submariner.io/v1alpha1 kind: Broker metadata: name: submariner-broker namespace: submariner-broker spec: globalnetEnabled: false EOF
The initial YAML generated by UI contains: apiVersion: addon.open-cluster-management.io/v1alpha1 kind: ManagedClusterAddOn metadata: name: submariner namespace: "" spec: installNamespace: submariner-operator --- apiVersion: submarineraddon.open-cluster-management.io/v1alpha1 kind: SubmarinerConfig metadata: name: submariner namespace: "" spec: gatewayConfig: gateways: 0 IPSecNATTPort: 0 NATTEnable: false cableDriver: "" credentialsSecret: name: "" --- apiVersion: submariner.io/v1alpha1 kind: Broker metadata: name: submariner-broker namespace: submariner-broker spec: globalnetEnabled: false but as soon as I select a target cluster that is not from a supported provider, the YAML becomes empty. While it should remove the SubmarinerConfig entry, the other entries should be preserved.
*** Bug 2098087 has been marked as a duplicate of this bug. ***
@noam manos Please verify fixed in 2.5.1. Thanks.
Unfortunately, since the mentioned platform is not officially supported by the submariner yet and we don't have a resources mentioned in the BZ, we unable to verify the bug.
Since we had customers complaining about this, I'd like to get it fixed in 2.5.1 if possible. Let me see if I can find some clusters and verify myself.
Created attachment 1893479 [details] ACM 2.5.1: Custom Yaml for Submariner of the unsupported platform
Created attachment 1893480 [details] ACM 2.5.1: Unsupported platform for Submariner addon warning
Verified on ACM 2.5.1 - See screenshot attached.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Advanced Cluster Management 2.5.1 security updates and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5531