Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add beta support for confidential_nodes #1040

Conversation

stenalpjolly
Copy link
Contributor

@stenalpjolly stenalpjolly commented Oct 30, 2021

Reference: #737

@stenalpjolly stenalpjolly marked this pull request as draft October 30, 2021 15:23
@comment-bot-dev

This comment has been minimized.

@stenalpjolly stenalpjolly marked this pull request as ready for review October 31, 2021 06:43
@stenalpjolly stenalpjolly marked this pull request as draft October 31, 2021 08:17
@stenalpjolly stenalpjolly marked this pull request as ready for review October 31, 2021 10:34
@stenalpjolly stenalpjolly self-assigned this Oct 31, 2021
dynamic "confidential_nodes" {
for_each = local.confidential_node_config
content {
enabled = confidential_nodes.value.enabled
Copy link
Contributor

Choose a reason for hiding this comment

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

For future reference, it's usually more intuitive to just hard-code this (enabled = true).

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 thought this would be more aligned with existing code like

enabled = network_policy.value.enabled

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that's an anti-pattern though.

@@ -614,6 +614,12 @@ variable "shadow_firewall_rules_priority" {
}

{% if beta_cluster %}
variable "enable_confidential_node" {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
variable "enable_confidential_node" {
variable "enable_confidential_nodes" {

@@ -0,0 +1,72 @@
/**
Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you for adding a test! However, we're trying to avoid too many examples. Could you instead consolidate this by adding confidential notes to one of the existing examples/tests?

@@ -64,6 +64,8 @@ module "gke" {
},
]

enable_confidential_node = true
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't correct.

@morgante morgante merged commit e105bb5 into terraform-google-modules:master Nov 2, 2021
@stenalpjolly stenalpjolly deleted the spj/support_confidential_nodes branch November 3, 2021 03:34
CPL-markus pushed a commit to WALTER-GROUP/terraform-google-kubernetes-engine that referenced this pull request Jul 15, 2024
…es#1040)

* Add beta support for confidential_nodes

* Cannot use a null value in for_each

* Add example and test

* Add example and test

* Update test name

* Review Comments

* Review Comments

* Review Comments

Co-authored-by: Stenal P Jolly <stenalpjolly@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants