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
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: