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

Evaluate what will need to be done to support incremental config #6551

Open
2 of 5 tasks
lahabana opened this issue Oct 18, 2024 · 0 comments
Open
2 of 5 tasks

Evaluate what will need to be done to support incremental config #6551

lahabana opened this issue Oct 18, 2024 · 0 comments
Assignees
Labels
area/spike release/required it is required that this be resolved before releasing
Milestone

Comments

@lahabana
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

There's a version of Gateway that has incremental config and an internal control plane which has an implementation of it.

Now is probably a good time to look at this new feature and get an idea of how it will work for KIC.

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

  • Familiarity with Incremental config
  • Understand if some code may be shared between us and the internal go-control-plane which uses it
  • High level design which explains how we could start using incremental config
@lahabana lahabana added this to the KIC v3.4.x milestone Oct 18, 2024
@randmonkey randmonkey self-assigned this Oct 21, 2024
@randmonkey randmonkey added the release/required it is required that this be resolved before releasing label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/spike release/required it is required that this be resolved before releasing
Projects
None yet
Development

No branches or pull requests

2 participants