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
where as when we create new network interface, we did not explicity set AssociatePublicIpAddress. This field, when omited, AWS will use the default value which is true as documented here
Together with the if aws.BoolValue(machineProviderConfig.PublicIP) { only check, render us unable to set this value to false even if we set machineProviderConfig.PublicIP to false.
The fix for this could be
Default value for network interface changes to AssociatePublicIpAddress to false.
Or Add a else clause to handle false path.
What do you think?
The text was updated successfully, but these errors were encountered:
In corporate context, we often have a SCP (service control policy) to block
AssociatePublicIpAddress
when set totrue
by default.However, in machine-api-provider-aws, we have this code path
machine-api-provider-aws/pkg/actuators/machine/instances.go
Lines 364 to 389 in 318ae2f
where as when we create new network interface, we did not explicity set
AssociatePublicIpAddress
. This field, when omited, AWS will use the default value which istrue
as documented hereTogether with the
if aws.BoolValue(machineProviderConfig.PublicIP) {
only check, render us unable to set this value tofalse
even if we setmachineProviderConfig.PublicIP
to false.The fix for this could be
AssociatePublicIpAddress
tofalse
.else
clause to handlefalse
path.What do you think?
The text was updated successfully, but these errors were encountered: