[Feature] multiple namespace support

[alexellis]

Feature: multiple namespace support

The feature is outlined at #433, which can be used for comments, questions, and suggestions.

The use-case is: multiple namespaces, single installation, i.e. dev/staging, team-a/team-b, client-a/client-b.

Checklist:

• Allow . in paths for faas-provider Allow "." in function name faas-provider#26
• Allow . in paths for faas/gateway Allow dot in function name faas#1315
• Update "direction functions" behaviour in gateway to allow namespace in path
• Check/Update behaviour for auto-scaling via alerts Scale functions with namespace option faas#1316
• Check the way Prometheus metrics are recorded
• Define optional RBAC role for ClusterRole e2c013b
• Update faas-netes CRUD to use namespace detected or passed in Enable namespace selection for scaling #513 Add support for namespace to commands #519
• Update faas-netes to populate namespace in "get" endpoint - Populate namespace when querying functions #512
• Update faas-netes, faas and faas-provider with list namespaces endpoint Add namespaces endpoint faas#1318 Add namespaces lister endpoint #518 Add /system/namespaces endpoint faas-provider#27
• Add a list functions flag / endpoint which enumerates all valid namespaces
• Add namespace filtering to only OpenFaaS namespaces
• Update CLI to become namespace-aware for Function CRUD Add support for namespaces faas-cli#694
• Check/Update nats-queue-worker so that it is namespace-aware
• Check/Update connector-sdk so that it is namespace-aware Add multiple namespaces support connector-sdk#36
• Document approach for testing e2e
• Update docs repo where required to document multiple-namespaces

CLI

• Deploy via --namespace for single function

• Deploy via stack.yml with multiple functions - Add namespace field to the stack.yml schema faas-cli#737
  UI [Feature] Namespace selector in UI faas#1379

• UI - add namespace selector

• UI - add "all namespaces" option

Secrets

• Update faas-netes for CRUD for secrets to use namespace detected or passed

Logs

• Update faas-netes to use namespace detected or passed for logs

Docs

• Add overview and testing instructions page https://docs.openfaas.com/reference/namespaces/
• Add to CLI --help pages
• Add to YAML reference page

Triggers

• Support in event-connector SDK Add support for namespaces connector-sdk#50
• Support in faas-idler https://github.com/openfaas-incubator/faas-idler/issues/37
• Support in cron-connector Cron-Connector only looks for functions in openfaas-fn namespace cron-connector#6

OpenFaaS operator

• Copy approach/changes from faas-netes https://github.com/openfaas-incubator/openfaas-operator/issues/92

• Basic logs

• Endpoint load-balancing

• Multiple-namespace support

Diagram

Test out the patches so far

Test e2e with this Gist and the following patches: https://gist.github.com/alexellis/3b285ca0952d4cef48ca5dbff7e4e288

[viveksyngh]

I will work on updating faas-netes to make secrets API namespace aware and add namespace flag to the secrets command to CLI.

[jonatasbaldin]

hey @viveksyngh, I'm working on the faas-netes, faas-provider and faas for that already 🙈

would u like to focus on the CLI?

for the GET /system/secrets I'm gonna pass a namespace query parameter and for the other ones (POST, PUT, DELETE) I'll pass a new namespace field in the body.

what do u think?

[jonatasbaldin]

I have a POC working locally already, will cleanup and push today :)

[viveksyngh]

or the GET /system/secrets I'm gonna pass a namespace query parameter and for the other ones (POST, PUT, DELETE) I'll pass a new namespace field in the body.

I think that should be fine. Please let me know if you need any help.

I can work on the CLI.

[jonatasbaldin]

Here's the PRs from the Secrets:

• faas-provider #28
• faas #1334
• faas-netes #530

❤️