Introduce internal network policy support - Githubissues

epam / cloud-pipeline

Cloud agnostic genomics analysis, scientific computation and storage platform

https://cloud-pipeline.com

Apache License 2.0

144 stars 58 forks source link

Introduce internal network policy support #3420

Open tcibinan opened 6 months ago

tcibinan commented 6 months ago

Background

Currently, there are two network policy types in Cloud Pipeline:

common
- ingress restricted to
- common runs of the same user
- egress unrestricted
sensitive
- ingress restricted to
- sensitive runs of the same user
- egress restricted to
- sensitive runs of the same user
- file share endpoints
- aws, gcp, azure endpoints via sensitive proxy

Approach

Additional network policy type shall be introduced

internal
- ingress restricted to
- internal runs of the same user
- egress restricted to
- internal runs of the same user
- file share endpoints
- aws, gcp, azure endpoints via sensitive proxy