Skip to content
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 registry Path #1367

Open
denis-tingaikin opened this issue Oct 12, 2022 · 1 comment
Open

Add support for registry Path #1367

denis-tingaikin opened this issue Oct 12, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@denis-tingaikin
Copy link
Member

denis-tingaikin commented Oct 12, 2022

Overview

Previously we added a support OPA for registry service. (See at #269)

The second step is to add for registries the possibility to use a zero trust.

For this reason, we planned to add a Path structure for registries.

Link to the Google Docs document

networkservicemesh/api#147 (comment)

References

#269

Solutions

  1. Spec: Store spiffeID of NSE in NetworkSerivceEndpoint message api#148
  2. Your options
@denis-tingaikin
Copy link
Member Author

denis-tingaikin commented Oct 12, 2022

@NikitaSkrynnik

For a first step, we could try to implement metadata sending/receiving for the registry service.

Basically, we need to support these cases:

  1. client adds its token to the path from metadata
  2. server adds its token to the path in metadata
  3. server sends a path to the second registry server via metadata

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants