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
This commit was implemented based in spec to define optoinal vpc endpoints for AWS, take into consideration this is a breaking change as when endpoints were introduced they were created by default, now behavior is the other way around unless they are explicit in params they will no be created
Co-authored-by: Claude <noreply@anthropic.com>
Signed-off-by: Adrian Riobo <ariobolo@redhat.com>
Copy file name to clipboardExpand all lines: cmd/mapt/cmd/params/params.go
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -130,6 +130,9 @@ const (
130
130
KindExtraPortMappings="extra-port-mappings"
131
131
KindExtraPortMappingsDesc="Additional port mappings for the Kind cluster. Value should be a JSON array of objects with containerPort, hostPort, and protocol properties. Example: '[{\"containerPort\": 8080, \"hostPort\": 8080, \"protocol\": \"TCP\"}]'"
132
132
133
+
// Network
134
+
ServiceEndpoints="service-endpoints"
135
+
133
136
// Spot
134
137
spot="spot"
135
138
spotDesc="if spot is set the spot prices across all regions will be checked and machine will be started on best spot option (price / eviction)"
@@ -143,6 +146,14 @@ const (
143
146
spotExcludedHostedZonesDesc="Comma-separated list of zone IDs to exclude from spot selection"
0 commit comments