Skip to content

Conversation

@omidtavakoli
Copy link
Contributor

No description provided.

@omidtavakoli omidtavakoli self-assigned this Nov 24, 2025
@omidtavakoli omidtavakoli marked this pull request as ready for review November 24, 2025 15:14
Copy link

@loiro loiro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

{
String labelSelector = String.format("%s=%s", serviceLabel, service);
log.debug("Filtering deployment {} using selector {}", resource, labelSelector);
log.debug("Filtering resource {} using selector {}", resource, labelSelector);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we could keep it as Filtering deployment for consistency with other logs and because we actually filtering data from deployments....

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see but it's logging like this Filtering deployment DEPLOYMENT using selector. Actually argument KubernetesResources resource is representing the resource type which in this function is Deployment.
There are another resource type defined : https://github.com/freenowtech/sauron/blob/main/plugins/kubernetesapi-report/src/main/java/com/freenow/sauron/plugins/utils/KubernetesResources.java#L5

log.error("getDeploymentSpec failed '{}'", ex.getMessage(), ex);
}

log.warn("No deployment returned for service '{}'", service);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consider this log as DEBUG instead? Also, maybe add the labelSelector?

public static final String K8S_DEFAULT_NAMESPACE = "default";

public static final int K8S_API_TIMEOUT_SECONDS = 5;
public static final int K8S_API_TIMEOUT_SECONDS = 30;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m not sure if you noticed, but the timeout is only happening in the mgmt. Are we sure that the K8s API is accessible there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants