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.

Sign up for GitHub

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

Jump to bottom

Move feature AutoreachableServices out of experimental and use by default #11700

Open
lukidzi opened this issue Oct 7, 2024 · 0 comments
Open

Move feature AutoreachableServices out of experimental and use by default #11700

lukidzi opened this issue Oct 7, 2024 · 0 comments
Labels
kind/design Design doc or related kind/feature New feature triage/pending This issue will be looked at on the next triage meeting
Milestone
2.10.x

Comments

@lukidzi
Copy link
Contributor

lukidzi commented Oct 7, 2024 •
edited
Loading

Description

We have introduced Autoreachable services #6551 in a Kuma 2.5 and added support for ExternalServices in a version 2.6 but since then we haven't moved the feature out of experimental phase. We should move it out of the experimental phase to give users confidence in the feature. The idea is to enable it by default and allow you to opt-out.

Keep in mind:

  • tags limitation
  • MeshExternalService not using MeshTrafficPermissions
@lukidzi lukidzi added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature kind/design Design doc or related labels Oct 7, 2024
@lukidzi lukidzi added this to the 2.10.x milestone Oct 7, 2024
@lukidzi lukidzi changed the title Use AutoreachableServices by default Move feature AutoreachableServices out of experimental and use by default Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/design Design doc or related kind/feature New feature triage/pending This issue will be looked at on the next triage meeting
Projects
None yet
Milestone
2.10.x
Development

No branches or pull requests
1 participant
@lukidzi