remove scary deprecation warning

xrstf commented 3 months ago

What this PR does / why we need it: While technically correct, the warning about the API stability is causing uncertainty with integrators. In practice the KKP REST API is not going away anytime soon, especially not in KKP 2.x, given KKP's architecture and inherent limitations.

CRDs are still the way to go for "simple" setups or setups where a singular entity is managing KKP (like when you have a GitOps pipeline and only scripts modify KKP directly, instead of all members in a team individually connecting to KKP). But I can see how my strong stance on deprecating and de-emphasizing the REST API might have caused more friction than I intended.

/cc @moadqassem

What type of PR is this? /kind cleanup

Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

kubermatic-bot commented 3 months ago

LGTM label has been added.

Git tree hash: 290a4fa1fc8647f6955f8278bb8abe95db3c6e25

Waseem826 commented 3 months ago

/approve

kubermatic-bot commented 3 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: moadqassem, Waseem826

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[modules/api/OWNERS](https://github.com/kubermatic/dashboard/blob/main/modules/api/OWNERS)~~ [Waseem826] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

kubermatic / dashboard

remove scary deprecation warning #6728