Jaeger Operator OpenShift logs

[jele84]

Hello everyone,
I installed Jaeger Operator version 1.62.0 in OpenShift and was faced with the fact that the jaeger-operator pod endlessly write logs like:
...

2024-11-22T17:38:09Z INFO verify deployment {"namespace": "openshift-machine-config-operator"}
2024-11-22T17:38:10Z INFO OAuthProxy ImageStream namespace and/or name not defined {"namespace": "", "name": ""}
2024-11-22T17:38:10Z INFO Determining whether we should enable the Elasticsearch Operator integration
2024-11-22T17:38:10Z INFO Determining whether we should enable the Kafka Operator integration
2024-11-22T17:38:10Z INFO cleaning orphaned deployments.
...

What's going on here and how to fix it? Thank you.

[dosubot[bot]]

Hey @jele84! I'm here to help you with the Jaeger Operator issue you're facing. I'm a bot designed to assist with bug fixes, questions, and contributions. Let's tackle this together!

The log messages you're seeing from the Jaeger Operator in OpenShift are related to various checks and operations it performs:

1. "verify deployment": This message indicates that the operator is checking the status of deployments in the specified namespace. Unfortunately, the specific conditions that trigger this message are not detailed in the available documentation.

2. "OAuthProxy ImageStream namespace and/or name not defined": This message suggests that the operator is expecting an ImageStream for OAuthProxy, but the namespace or name is not defined. This might require configuration adjustments to specify the correct ImageStream details.

3. "Determining whether we should enable the Elasticsearch Operator integration": This indicates that the operator is checking if the conditions are met to enable Elasticsearch integration. For this integration to be enabled, the Jaeger instance must be of the production strategy, the storage type must be elasticsearch, and no es.server-urls should be specified ^[1][2][3].

4. "Determining whether we should enable the Kafka Operator integration": This is a similar check for Kafka integration, but specific criteria for enabling this integration are not detailed in the available information.

5. "cleaning orphaned deployments": This message indicates that the operator is attempting to clean up deployments that are no longer needed. The specific process for cleaning orphaned deployments is not detailed in the available documentation.

To address these log messages, you may need to review your Jaeger Operator and OpenShift configurations, particularly around ImageStreams and operator integrations. Adjusting these configurations based on your deployment needs might help reduce or eliminate these log messages.

To continue talking to Dosu, mention @dosu.

[jele84]

How to define ImageStream for OAuthProxy?

[dosubot[bot]]

To define an ImageStream for OAuthProxy in OpenShift, you need to create an ImageStream resource in your OpenShift project. Here is a basic example of how you can define an ImageStream for OAuthProxy:

apiVersion: image.openshift.io/v1
kind: ImageStream
metadata:
  name: oauth-proxy
  namespace: your-namespace
spec:
  tags:
  - name: latest
    from:
      kind: DockerImage
      name: quay.io/openshift/origin-oauth-proxy:latest
    importPolicy:
      scheduled: true

Replace your-namespace with the appropriate namespace where you want the ImageStream to be created. The name under from should point to the Docker image you want to use for OAuthProxy. In this example, it uses the quay.io/openshift/origin-oauth-proxy:latest image, but you can specify a different image or version as needed.

Once the ImageStream is defined, ensure that your Jaeger Operator configuration references this ImageStream correctly, so it can use it for deploying the OAuthProxy component.

To continue talking to Dosu, mention @dosu.

[jele84]

Where can I check the Jaeger operator configuration to see if it is referencing this ImageStream correctly?

[jele84]

Once the ImageStream is defined, ensure that your Jaeger Operator configuration references this ImageStream correctly, so it can use it for deploying the OAuthProxy component.

in which configuration file is ImageStream specified for OAuth?

[dosubot[bot]]

The Jaeger Operator configuration for referencing an ImageStream is typically specified in the custom resource (CR) file that defines your Jaeger instance. This file is usually a YAML file where you configure various aspects of the Jaeger deployment, including the use of ImageStreams.

However, specific details on how to configure the ImageStream for OAuthProxy in the Jaeger Operator are not readily available in the documentation I have access to. You might need to look into the Jaeger custom resource definitions (CRDs) or the operator's configuration files to find where the ImageStream is referenced.

If the configuration is not explicitly documented, you may need to check the operator's deployment or configuration files in your OpenShift environment to see if there are any references to ImageStreams. This could involve looking at the operator's deployment YAML or any related configuration maps or secrets that might specify image details.

To continue talking to Dosu, mention @dosu.