Skip to content
This repository has been archived by the owner on Mar 10, 2023. It is now read-only.

Add NetworkPolicy to separate user functions #108

Closed
alexellis opened this issue Aug 23, 2018 · 2 comments
Closed

Add NetworkPolicy to separate user functions #108

alexellis opened this issue Aug 23, 2018 · 2 comments

Comments

@alexellis
Copy link
Member

alexellis commented Aug 23, 2018

We need a NetworkPolicy which does the following:

  • Prevent functions calling system services - block (openfaas-fn) -> (openfaas)
  • Prevent functions calling other functions - block (openfaas-fn) -> (openfaas-fn)
  • Allow OpenFaaS Cloud "system" functions to do the above. Use a label to decide which functions belong to this group.

In addition we will have to prevent users from adding this "system" or "openfaas" label to their functions in the buildshiprun function.

Testing:

Show above conditions are satisfied in a deployment on Kubernetes.

Changes should be made to / added to the Kubernetes YAML files in ./yaml/ and documented in the docs/README.md file.

@alexellis
Copy link
Member Author

I closed the original issue from April since this has more detail.

Example policy definition:
https://github.com/stefanprodan/openfaas-flux/tree/bb69dffda2ae8cead8035eaf35c9a92cb29a2924/network-policies

@bartsmykla
Copy link
Contributor

Derek assign: me

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants