[Bug]: when running on vanilla k8s, operator constantly spamming with the message #2903
Description
What happened?
with the message "Not running on OpenShift, so won't configure OAuthProxy imagestream."
As DevOps engineer I want to have only meaningful messages in the logs. It looks like that nobody can switch from Vanilla k8s to openshift distribution. Even more - I did not find option to install openshift specific APIs onto vanilla k8s, so constant checking of if we are running on openshift distribution does not makes sense at all.
The full log looks like:
2025-06-23T11:21:01Z INFO cleaning orphaned deployments.
2025-06-23T11:21:06Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:06Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:06Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:06Z INFO cleaning orphaned deployments.
2025-06-23T11:21:11Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:11Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:11Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:11Z INFO cleaning orphaned deployments.
2025-06-23T11:21:16Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:16Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:16Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:16Z INFO cleaning orphaned deployments.
2025-06-23T11:21:21Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:21Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:21Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:21Z INFO cleaning orphaned deployments.
2025-06-23T11:21:26Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:26Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:26Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:26Z INFO cleaning orphaned deployments.
2025-06-23T11:21:31Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:31Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:31Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:31Z INFO cleaning orphaned deployments.
2025-06-23T11:21:36Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:36Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:36Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:36Z INFO cleaning orphaned deployments.
2025-06-23T11:21:41Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:41Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:41Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:41Z INFO cleaning orphaned deployments.
2025-06-23T11:21:46Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:46Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:46Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:46Z INFO cleaning orphaned deployments.
2025-06-23T11:21:51Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream.
2025-06-23T11:21:51Z INFO Determining whether we should enable the Elasticsearch Operator integration
2025-06-23T11:21:51Z INFO Determining whether we should enable the Kafka Operator integration
2025-06-23T11:21:51Z INFO cleaning orphaned deployments.
It is completely opposite to the checks for Elasticsearch and Kafka operators - as they may be installed after jaeger operator or even REMOVED during run of jaeger operator, which is unlikely, but very possible scenario and I totally bet, that it is not covered by operator logic. So finally I am kindly asking developers to consider next things:
- removal of check for OpenShift distribution - it should be done only during operator start-up
- possibility of adding option of k8s distribution type on arguments level of operator so eliminating checks that are not necessary (also it could be useful for debug purposes - let's say try to run operator in k8s mode in OC cluster)
- check that proper logic is implemented for different corner cases with EO and Kafka operators (like removal of them AFTER jaeger operator is already working)
- possibility of disabling EO and KO integration with arguments of command line.
Steps to reproduce
- install jaeger operator of the latest version
- observe the logs
Expected behavior
- no spamming of messages in the logs.
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response