generated from networkservicemesh/cmd-template
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for namespaces #126
Comments
@edwarnicke I think this could be an inresting one for v1.5.0 |
@denis-tingaikin Could you say more? :) |
@edwarnicke Sure. Use-case
kind: Namespace
apiVersion: v1
metadata:
name: test
labels:
"networkservicemesh.io": "kernel://my-vl3-network"
Makes sense? |
@denis-tingaikin Would this be labels or annotations? |
It will be an annotation. |
This was referenced Aug 12, 2022
nsmbot
pushed a commit
that referenced
this issue
Jan 18, 2024
This PR syncs files with https://github.com/networkservicemesh/cmd-template Revision: https://github.com/networkservicemesh/cmd-template/commits/8b3ce39b8f3cbfec1f1e1ce445893118f514d0ee commit 8b3ce39b8f3cbfec1f1e1ce445893118f514d0ee Author: Nikita Skrynnik <[email protected]> Date: Thu Jan 18 19:54:16 2024 +1100 Update Spire and Delve in Dockerfile (#126) Signed-off-by: Nikita Skrynnik <[email protected]> Signed-off-by: NSMBot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Since NSM is able to provide vl3 networks, it could be useful to add support for labled namespaces. All pods within the labled namespace could be handled by the webhook that injects nsm client based on the NSM label in each POD.
The text was updated successfully, but these errors were encountered: