#Trident installation, need to add annotation to pods

1 messages · Page 1 of 1 (latest)

inland obsidian
#

I am needing to add an annotation to the pods created when installing Trident and any created when adding a storage backend. This is so the pods get assigned to a secondary storage network defined by a NetworkAttachmentDefinition. The annotation need to be assigned at the time the pods are created. Is there a way to configure this in Trident?
I am using OpenShift 4.13 and Trident v23.07.1.

still gate
#

i believe the only annotations you can add today are linked to the nodes where the Trident PODs will run

#

are you talking about the internal network on which Trident will be plugged?

inland obsidian
#

i have a second network for storage traffic. I created a NetworkAttachmentDefinition for it and need to apply an annotation to the created pods so they can see the network and use it.

inland obsidian
#

i have been able to apply the annotations by patching the daemonset. the pods have recieved IPs on the secondary network. but I am getting "problem initializing storage driver 'ontap-san': error initializing ontap-san driver: could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post "https://192.168.50.45/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)".
I have a troubleshooting pod I created that can ping and ssh into the SVM without issue, so I believe the routing is fine.

If I run curl to the SVMs URL, "curl -k -u vsadmin -X POST https://192.168.50.45/netapp.servlets.admin.XMLrequest_filer", I get "404 Not Found" returned.

Any ideas what might be causing this? Things I have found do not seem to fix it yet.

still gate
#

Trident has 3 types of pods:

  • operator
  • controller (of type deployment)
  • daemonset
#

I believe the daemonset is in charge of attaching the storage resources when a POD mounts a PVC

#

the controller owns a bunch of CSI sidecars (snapshotter, provisionner, ...) as well as a trident container

#

did you also apply the annotation to the controller?

#

can you also share a digested version of the backend manifest you are trying to create?

dusk raptor
#

Is 192.168.50.45 a management interface on the storage array?

modern tinsel
#

Hi @inland obsidian
By seeing your message regarding Openshift, I guess you are setting up Trident on Openshift cluster.
Even I did the same and used Azure NetApp Files storage
I followed all the steps and able to setup Azure NetApp Files storage using Trident Operator on my Azure RedHat Openshift cluster v4.12.25
Could you please let me know, how to verify the status of NetApp storage setup on Azure ARO cluster??
Thanks

inland obsidian