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

feat: add host-set attribute 'only_default' #22

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

justenwalker
Copy link

Add a new attribute to the plugin host-set named 'only_default' which is a boolean that, if set to true, will only include default ip and dns names from the ec2 instances it finds.

A default IP is defined as the primary value on the instance for each attribute. These would be the values that you see in the AWS Console as a column in list view or on the Details tab when selecting a specific instnace.

A feature like this is necessary to support dynamic node pools (ASGs) on EKS Clusters where there may be multiple nics attached, and multiple ips per nic; but the host is only listening for SSH connections on the primary NIC/Address. There isn't a good way to specify dynamically which ip to connect to for SSH connections; and it may pick the wrong one (like a pod IP).

It will fall back to the primary addresses on the first network device (device index = 0) if those are not set for some reason.

Add a new attribute to the plugin host-set named 'only_default'
which is a boolean that, if set to true, will only include default
ip and dns names from the ec2 instances it finds.

A default IP is defined as the primary value on the instance for each
attribute. These would be the values that you see in the AWS Console as a column in list view
or on the Details tab when selecting a specific instnace.

A feature like this is necessary to support dynamic node pools (ASGs) on EKS Clusters where
there may be multiple nics attached, and multiple ips per nic; but the host is only listening for
SSH connections on the primary NIC/Address. There isn't a good way to specify dynamically which
ip to connect to for SSH connections; and it may pick the wrong one (like a pod IP).

It will fall back to the primary addresses on the first network device (device index = 0)
if those are not set for some reason.

Signed-off-by: Justen Walker <justen.walker+github@gmail.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

1 participant