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

[stable] multi-cluster support #38

Open
14 of 31 tasks
stevenctl opened this issue Apr 19, 2021 · 4 comments
Open
14 of 31 tasks

[stable] multi-cluster support #38

stevenctl opened this issue Apr 19, 2021 · 4 comments
Labels
lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/staleproof Indicates a PR or issue has been deemed to be immune from becoming stale and/or automatically closed

Comments

@stevenctl
Copy link
Contributor

stevenctl commented Apr 19, 2021

beta issue: #13

This document covers the stability of multi-primary and primary-remote configurations.

This does not include:

  • external control plane
  • multi-network

Stable Feature Requirements

This page lists the requirements for promoting multicluster to stable. Please check off and document the steps as they are completed.

Requirements

Features/Fixes:

Tests:

Docs:

Each task here also includes providing an automated test for the document on istio.io.

Other:

Approvals:

  • The appropriate work group(s) have reviewed and approved promotion of the feature.
  • The supportability review panel has reviewed promotion of the feature.
  • The TOC has reviewed and approved promotion of the feature as part of the
    road map for a release.
@hzxuzhonghu
Copy link
Member

We also need cluster-aware load balancing when clusters are in different networks

@stevenctl
Copy link
Contributor Author

Multi-network is a separate concern from multi-cluster

@brian-avery
Copy link
Member

@stevenctl can you please create a PR for this following https://github.com/istio/enhancements/blob/master/FEATURES.md? Thanks

@stevenctl
Copy link
Contributor Author

@brian-avery I started moving it over... but I'll do that as the last step. That format is pretty hard to use as a living checklist while the work is in progress.

@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label Apr 15, 2024
@stevenctl stevenctl reopened this Apr 16, 2024
@stevenctl stevenctl added the lifecycle/staleproof Indicates a PR or issue has been deemed to be immune from becoming stale and/or automatically closed label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/staleproof Indicates a PR or issue has been deemed to be immune from becoming stale and/or automatically closed
Projects
None yet
Development

No branches or pull requests

4 participants