Customized resource type extension support

Open
#147 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
grpc, java
Domain
api, backend-api-design

Research direction

Start by clarifying how customized resource types should extend the xDSv2/xDSv3 control-plane API and how the UDPA-TP and UDPA-DM separation applies. Define completion as a documented extension mechanism that supports private resource types and their specific configurations.

Written by the indexing model from the issue text.

Description

enhancement

Currently there is limited count of resource types in xDSv2/xDSv3, and should be enough for common scenarios.

But if we have some customized resource types, e.g. private module in envoy which relies on specific configs, then resource type extension support is needed.

Like that the pattern UDPA suggests: separate transport(UDPA-TP) and data-models(UDPA-DM), and it should be easy to extend data models.

Dominant language
Java
Stars
312
Forks
150
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/java-control-plane

All issues in envoyproxy/java-control-plane

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.