Replies: 1 comment 1 reply
-
Hi @lgerard-pass ! The issue is related to incorrect resolution of submodules. This issue is known and it will be fixed in the next release. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
Hello,
We are currently evaluating Trivy and we have rune into an issue. We are using this terraform module https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/latest/submodules/beta-private-cluster inside one of our root modules.
So we have a block like this :
In particular we have this line
enable_private_nodes = true
which forces nodes in the cluster to have only internal IP addresses.When we run trivy against this configuration we get this output :
Note that we have the same behaviour when setting
enable_private_nodes = false
so it seems trivy is using the default module variable (which isfalse
) to perform its analysis.Here are some logs from running trivy with
-d
option :This is inconsistent with what
tfsec
produces, as we do not get this output unless we specifyenable_private_nodes = false
, which seems like the desired behavior.Desired Behavior
When setting
enable_private_nodes
totrue
. I should not get a warning that my nodes are not private.When setting
enable_private_nodes
tofalse
. I should get that warning.Actual Behavior
When setting
enable_private_nodes
totrue
. I get a warning that my nodes are not private.When setting
enable_private_nodes
tofalse
. I also get that warningReproduction Steps
trivy config . --skip-dirs .terraform
tfsec .
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions