Network Multihome support for csi Nodes
Please add support for multihome configurations in combination with MULTUS.
Why is this usefull ?
We can seperate frontend traffic from storage traffic and can assign dedicated network cards/bond´s.
How can it be implemented
In the TridentOrchestrator add some config parameters like this:
apiVersion: trident.netapp.io/v1
kind: TridentOrchestrator
spec:
hostNetworkNode: false
NodeStorageNetwork: <namespace>/<NetworkAttachementDefinition-Name>
In the source code e.g. of : trident/cli/k8s_client/yaml_factory.go
const daemonSet120YAMLTemplateLinux = `---
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: {DAEMONSET_NAME}
{LABELS}
{OWNER_REF}
spec:
selector:
matchLabels:
app: {LABEL_APP}
template:
metadata:
labels:
app: {LABEL_APP}
annotations:
openshift.io/required-scc: {SERVICE_ACCOUNT}
k8s.v1.cni.cncf.io/networks: {NodeStorageNetwork} # When {NodeStorageNetwork} is defined
spec:
serviceAccount: {SERVICE_ACCOUNT}
hostNetwork: false # When {NodeStorageNetwork} is defined
hostIPC: true
hostPID: true
Network Multihome support for csi Nodes
Please add support for multihome configurations in combination with MULTUS.
Why is this usefull ?
We can seperate frontend traffic from storage traffic and can assign dedicated network cards/bond´s.
How can it be implemented
In the TridentOrchestrator add some config parameters like this:
In the source code e.g. of : trident/cli/k8s_client/yaml_factory.go