You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reverse firewall precedence to prioritize direct IDs over references (#717)
Direct firewall IDs now take precedence over references for both
LinodeMachine and LinodeCluster resources, bringing firewall configuration
logic in line with how we handle VPC resources. This change provides more
intuitive behavior and prevents reference-resolved IDs from being stored
back in the spec. Documentation updated with migration notes for existing
clusters.
For `LinodeCluster` resources, when both `NodeBalancerFirewallID` and `NodeBalancerFirewallRef` are specified:
204
204
205
-
- `NodeBalancerFirewallRef`takes precedence over `NodeBalancerFirewallID`
206
-
- The ID from the referenced `LinodeFirewall` will be used instead of the directly specified `NodeBalancerFirewallID`
205
+
- `NodeBalancerFirewallID`takes precedence over `NodeBalancerFirewallRef`
206
+
- The directly specified `NodeBalancerFirewallID` will be used instead of the referenced `LinodeFirewall`
207
207
208
208
```admonish warning
209
-
While you can specify both direct IDs and references, it's recommended to use only one approach for clarity and to avoid confusion.
209
+
While describing the precedence rules above, please note that specifying both direct IDs and references in the same resource is not recommended and will be rejected by the webhook validator. You should use either a direct ID or a reference, but not both.
210
+
```
211
+
212
+
```admonish note title="Migration Note for Existing Clusters"
213
+
In previous versions, the behavior was reversed - references took precedence over direct IDs, and the resolved ID from a reference was stored back in the direct ID field.
214
+
215
+
If you have existing clusters that were created with references, you may need to:
216
+
1. Clear the direct ID field (`firewallID` or `NodeBalancerFirewallID`)
217
+
2. Keep only the reference field (`firewallRef` or `NodeBalancerFirewallRef`)
218
+
3. Allow the cluster to reconcile with the new behavior
219
+
220
+
This ensures that changes to your references will be properly respected.
0 commit comments