feat(query): implemented query that ensures that integrity monitoring for Shielded GKE Nodes is enabled #7886
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.








Closes #
Reason for Proposed Changes
Proposed Changes
node_config.shielded_instance_config.enable_integrity_monitoringdefines if the instance has integrity monitoring enabled for both resources, since in the documentation of thegoogle_container_node_poolthere is no documentation for the node_config block, and demands to see the information about this field on thegoogle_container_clusterdocumentation so, I assumed that thenode_confighave the same configuration for both resources.enable_integrity_monitoringistrue.I submit this contribution under the Apache-2.0 license.