Insights recommendation reappeared

[Diegunio]

During the migration from the main distribution FCOS to SCOS (around version 4.16), the default Insights recommendation:

Insights recommendation "GSS does not provide enterprise-level support for an OKD cluster" with total risk "Moderate" was detected on the cluster.

was disabled.

However, as of March 26, 2025, I noticed that this message has reappeared across all environments.
Is there a way to disable it again?

[Prashanth684]

Hey @Diegunio . thanks for raising this. Which release version are you seeing this issue in? Could you link the payload which is causing the issue or which you noticed it first on?

[Diegunio]

Hey @Diegunio . thanks for raising this. Which release version are you seeing this issue in? Could you link the payload which is causing the issue or which you noticed it first on?

Thanks for the response.
I'm using a wide range of OKD versions, starting from 4.17.0-okd-scos.3 up to 4.18.0-okd-scos.4.
This message appears on every cluster, and it showed up at the same time across all environments

It appears on the /dashboards, under the cluster status section.

[titou10titou10]

Sorry to interfere with this issue but IMHO to get insight recommendations, you must have your OKD cluster connected to RH via an RH account and the "insight" capability enabled, which is by default.
Right?
But I have read in many places in the "discussions" and "issues" on the https://github.com/okd-project/okd project that is was "not legal" to install and use OKS-SCOS with an account connected to RH...("pullSecret"in install-config.yaml)
In my case I install OKS-SCOS cluster without an RH account and do not activate the"insight" capability so I do not receive the alert saying that insight is not configured
So is it "legal" or not to connect an OKD-SCOS cluster to RH?
Maybe it is "tolarated" to keep it for migrated clusters as IMHO it is not possible to disconnect it afterward?

[Prashanth684]

You can remove the redhat specific pull secrets and update the cluster pull secret following this article here: https://access.redhat.com/solutions/4902871. But as @titou10titou10 mentions, this is due to the face that the cluster is installed with RH pull secrets and that is not recommended. I am not sure about it not being legal as it does not do anything, but the recommendation is to not install with RH pull secrets.