Repository navigation
How do I enable the Kubernetes inspections? #308
Answered
by
brichbash
Mridang Agarwalla (mridang)
asked this question in
Q&A
|
I'm using GoLand 2025.2.3 and when I run the inspections locally, I can see the inspection warnins for Kuberneted but I don't see them in Qodana. Here is my Qodana config. The plugin name has been fetched from https://plugins.jetbrains.com/plugin/10485-kubernetes and I've also enabled the inspections. No matter what I do, the inspections do not show. Would someone be able to tell me what I'm doing wrong? |
Answered by
brichbash
Oct 30, 2025
Replies: 2 comments 5 replies
|
Do you see the Kubernetes inspections in the Configuration tab in the Qodana reports from non-local runs? If not, it's possible the plugin wasn't actually installed to Qodana due to some error. To investigate further, please share Qodana output. You can also your Qodana logs to us at qodana-support@jetbrains.com |
0 replies
|
I don't see it there. 
Here are the logs from the action run. The PR is at zitadel/zitadel-charts#466 As you can see, the plugin in installed. I'm also using the latest version of the action. |
5 replies
|
That didn't help. zitadel/zitadel-charts#466 I still get the same issue. 0 errors or warnings reported. I can now see the "Kuberntes" plugin in the admin but no checks are reported. The same inspections when run in my IDE, light up like a christmas tree. 
|
|
In this case, could you retrive Qodana logs by following this article and then share the |
|
Done. I've mailed them with the |
|
The problem was caused by the discrepancy in Qodana configurations between the main branch and feature branches from the pull requests. If you want to test out a new Qodana configuration on a separate branch, we recommend first running Qodana analysis on it using the workflow_dispatch trigger on the branch. This way Qodana run full scan on the specified branch and will apply Qodana configuration from that branch. |
Answer selected by
brichbash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem was caused by the discrepancy in Qodana configurations between the main branch and feature branches from the pull requests.
When analyzing pull requests, Qodana by default runs the analysis on the changed files first from the target branch, and then on the same files from the source branch, so it can use an unexpected configuration.
If you want to test out a new Qodana configuration on a separate branch, we recommend first running Qodana analysis on it using the workflow_dispatch trigger on the branch. This way Qodana run full scan on the specified branch and will apply Qodana configuration from that branch.