#Change IP trident-node-linux-5czkw

1 messages · Page 1 of 1 (latest)

lapis wolf
#

We have a kubernetes node wit a client ip (eth0) and a storage ip (eth1).
The trident-node-linux pod has a ip in the client range. We are not able to connect to the ontap cluster via the client lan. How to change the trident-node-linux ip (or configuration) to the storage lan?

ebon flame
#

It sounds like the route is not setup correctly on the nodes to make sure the storage ip is routed to the correct subnet. Does the network work outside of kubernetes?

lapis wolf
#

Hello Scott, the network works outside of kubernetes. I'm able to ping the management LIF

keen charm
#

Trident pods use the ip's from the node hosts for external networking, no way to change that I am aware. Follows K8S Networking: (https://kubernetes.io/docs/concepts/cluster-administration/networking/). Networking must work from node to storage. Then test same from a test pod. If pod to storage networking doesnt work, confirm the required ports are open (firewall?) and check K8S cluster CNI. https://docs.netapp.com/us-en/trident/trident-reference/ports.html, plus NFS (2049), iscsi (860,3260) etc.., What is Trident NOT able to do? ie. what is NOT working? Can it create a volume (uses mgmtLIF). Can it mount the volume from a pod (uses dataLIF)? What is the error you see?

Kubernetes
Cluster Networking

Networking is a central part of Kubernetes, but it can be challenging to understand exactly how it is expected to work. There are 4 distinct networking problems to address:
Highly-coupled container-to-container communications: this is solved by Pods and localhost communications. Pod-to-Pod communications: this is the primary focus of this docume...

Trident ports

Learn more about the ports that Trident communicates over.

lapis wolf
#

@keen charm The error:
kubectl get tbc,tbe -n trident
NAME BACKEND NAME BACKEND UUID PHASE STATUS
tridentbackendconfig.trident.netapp.io/backend-ontap-nas Failed

In the events:
Failed to create backend: unsupported config error; input is missing the credentials field
It appears I made an indentation error in the Trident Backend Configuration yaml
After correction this I got the expected result:
kubectl get tbc,tbe -n trident
NAME BACKEND NAME BACKEND UUID PHASE STATUS
tridentbackendconfig.trident.netapp.io/backend-ontap-nas ontap-nas d937a270-a489-400f-9cfe-0e20fb7088cd Bound Success

Thanks for pointing me in the correct direction.