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
feat(robot): forward InternalIPs by default on Robot nodes (#865)
Whenever a user configures the `--node-ip` flag, we forward the
configured IPs. We validate if the IP already exists as an ExternalIP
and does not collide with the configured address family. This improves
the Robot support for HCCM, as users can configure private IPs for Robot
nodes.
Forwarding only happens during the initialization phase of HCCM and
should therefore not break existing clusters.
This feature can be disabled by setting the environment variable
`ROBOT_FORWARD_INTERNAL_IPS` to `false`.
---------
Co-authored-by: Alexander Block <ablock84@gmail.com>
Co-authored-by: Julian Tölle <julian.toelle@hetzner-cloud.de>
Copy file name to clipboardexpand all lines: docs/robot.md
+1
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,7 @@ The Node controller adds information about the server to the Node object. The va
56
56
- Addresses
57
57
- We add the Hostname and (depending on the configuration and availability) the IPv4 and IPv6 addresses of the server in `Node.status.addresses`.
58
58
- For the IPv6 address we use the first address in the Network -> For the network `2a01:f48:111:4221::` we add the address `2a01:f48:111:4221::1`.
59
+
- By default, we pass along InternalIPs configured via the kubelet flag `--node-ip`. This can be disabled by setting the environment variable `ROBOT_FORWARD_INTERNAL_IPS` to `false`. It is not allowed to configure the same IP for InternalIP and ExternalIP.
0 commit comments