Feature Request: customize the trident orchestrator configuration options while using helm chart

[radhika-pr]

In helm include options for configuring hostNetwork and https_port for trident-controller.

Trident helm chart now allows only limited options for customizing the configuration options of trident orchestrator. It would be nice to have the options to run the trident-controller deployment on host network when required and options to change the http port too.

An alternate solution we have tried is using tridentctl generate the manifests and use it for additional configuration changes.

[clintonk]

Hi, @radhika-pr. tridentctl is the preferred way to customize Trident to the extent you describe.

[radhika-pr]

@clintonk We are currently using manifest created by tridentctl. The addon is installed using Argocd+kustomize and it will be much cleaner to have helm chart for our setup.

[morete]

We are also interested on having HELM able to customise "hostNetwork" for the trident controller deployment as nowadays we need to manually patch the configs after deployment/upgrade by running:

kubectl patch deployment trident-controller -n trident -p '{"spec":{"template":{"spec":{"hostNetwork":true}}}}'

As I agreed with NetApp support to create a new feature request on github, I +1 this existing request/ticket.

@clintonk we can already customise several options, why not exposing one additional? might be just done optional, doesn't seem to be a big deal. In case you feel this is not feasible, what would be the suggestion to automate this using some gitops tooling like ArgoCD.

Thanks @radhika-pr for the request/suggestion. Thanks @clintonk for your feedback.

[phhutter]

Hi,

Do we already have an update regarding this feature request? The use of tridentctl as mentioned by @clintonk might work, but it would be definitely a step backwards in terms of IaC. As mentioned by @morete a way to configure it directly in helm would be preferred.

use-cases where the missing feature leads to problems and a manual workaround is currently required:

• SDN to OVN-K migration when using a dedicated network for storage.

[clintonk]

This issue is addressed in Trident 25.10.