[Goal] Istio Feature Deprecation Process

[whitneygriffith]

RFC: Istio Feature Deprecation

Background:

• Istio doesn’t have a strong history of deprecating features but there are APIs, etc. that are just confusing to users, and we also want a standard to reference when we begin to maintain an up and out movement of features in Istio.

Objective:

• Define a baseline for how we want to deprecate features moving forward with the understanding that based on the feature/situation we will need specific guidance from the TOC and community.
• This will help guide us in future work as we will have clarity around Istio’s appetite for deprecation and an understanding of how to facilitate the deprecation of any of the features we review.
• Identify the features that are confusing or should just be deprecated because it is no longer relevant. Gain consensus that a deprecation plan is needed for these features. Prioritize the features to be deprecated and tackle in upcoming milestones.

Feature/Process Owner:

Subtasks:

• Confirm process owner / co-owners
• Defining the subgroup’s objective for this process improvement
• Deprecate In-Cluster IstioOperator #166
• APIs Release and Versioning Model #160

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2023-10-02. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.