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
What steps did you take and what happened:
I deployed a cluster and used additionalNetworks to attach all cluster nodes to a private network.
This works fine, see
The problem is Node.status.addresses shows
addresses:
- type: InternalIP
address: 194.164.205.212
- type: Hostname
address: ...
What did you expect to happen:
I'd expect
addresses:
- type: ExternalIP
address: 194.164.205.212
- type: InternalIP
address: 10.7.222.16
Anything else you would like to add:
We need a correctly set internal IP to utilize ciliums auto-direct-node-routes feature.
This would enable us to keep the internal traffic inside our datacenter.
The text was updated successfully, but these errors were encountered:
CCM currently only considers the primary NIC when looking up the values for ExternalIP and InternalIP. CCM actually also no longer reports ExternalIP since 1.29.
What steps did you take and what happened:
I deployed a cluster and used additionalNetworks to attach all cluster nodes to a private network.
This works fine, see
The problem is Node.status.addresses shows
addresses:
- type: InternalIP
address: 194.164.205.212
- type: Hostname
address: ...
What did you expect to happen:
I'd expect
addresses:
- type: ExternalIP
address: 194.164.205.212
- type: InternalIP
address: 10.7.222.16
Anything else you would like to add:
We need a correctly set internal IP to utilize ciliums auto-direct-node-routes feature.
This would enable us to keep the internal traffic inside our datacenter.
The text was updated successfully, but these errors were encountered: