Optional host macvlan for storage network #731
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds an optional environmental variable called
NETWORK_STORAGE_MACVLAN
that when set will create a macvlan on top of the storage VLAN network to hold the IPs instead of the VLAN itself.This allows host to/from pod network communication on the same host using the storage VLAN.
This is necessary for example when using Cinder's LVM driver with the iSCSI transport protocol and using the IP assigned to the pod's storage network attachment.
The iscsi initiator (client) is run on the host, but it won't have network access to the iSCSI target port that gets opened in the cinder volume network namespace.
We don't default to always create the macvlan because LVM is a Proof of Concept backend that should not be used in production for serious workloads.
An example of how to use this is to use the existing cinder-operator LVM iSCSI sample, but changing how we deploy the operators:
Related cinder-operator PR: openstack-k8s-operators/cinder-operator#338