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

Node IP and the IP address the skuba deployer uses to access a node can't be specified separately #1133

Open
rktidwell opened this issue Jun 1, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@rktidwell
Copy link
Contributor

skuba node bootstrap/join takes only a single IP address. This address is used as both the node IP and the address that skuba uses to SSH into the node. There are cases where a node has 2 interfaces: one that is public and one that is private. You may want your cluster to to use the address on the private network as the cluster IP, but allow skuba to configure the cluster using the public address (or vice versa). To support this, skuba needs to support a mechanism by which the node IP and the node "management" IP can be specified separately.

@rktidwell rktidwell added the enhancement New feature or request label Jun 1, 2020
@rktidwell
Copy link
Contributor Author

rktidwell commented Jun 1, 2020

Here's what I'm envisioning:

Use existing behavior as the default: assume a single interface and use the IP/FQDN passed on skube node bootstrap/join as both the "management" IP and the node IP.

Add an optional flag for specifying the node IP:

skuba node bootstrap --user opensuse --sudo --target <IP/fqdn for SSH access> --node-ip < IP > my-master
skuba node join --role worker --user opensuse --sudo --target <IP/fqdn for SSH access> --node-ip < IP > my-worker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant