Improve StreamFlow on Kubernetes #659
Open
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 commit heavily refactors the StreamFlow Helm chart to simplify its deployment on top of Kubernetes clusters.
In addition, this commit adds a
networkPolicyflag to control the behaviour of CWLDockerRequirementobjects into KubernetesPoditems. Normally, the CWLNetworkAccessrequirement is enforced through KubernetesNetworkPolicyobjects. However,NetworkPolicyobjects regulate the network security inside a cluster, and giving the StreamFlowPodpermissions to create/delete them may result in unwanted security flaws. ThenetworkPolicyoption can be set toFalseto ignore the CWLNetworkAccessenforcement in such cases.