Skip to content

[FEATURE] Make Kyma production ready #164

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
Open
sdischer-sap opened this issue May 7, 2025 · 0 comments
Open

[FEATURE] Make Kyma production ready #164

sdischer-sap opened this issue May 7, 2025 · 0 comments

Comments

@sdischer-sap
Copy link
Member

sdischer-sap commented May 7, 2025 •
edited by GenosseOtt
Loading

Context

Since the CIS API changed it behaviour we see more and more issues with using KymaEnvironment. We discussed a couple of measures to make using KymaEnvironment more fail proof and to add more capabilities to its feature set. Those will be collected as part of this Epic.

Scope

Allow managing Kyma in a convinent way across all of its lifecycle. This includes fixing the current behaviour issues, as well as comfort features like fixing external-naming handling as well as eventually maturing it to be a v1beta1 resource.

See subissues for concrete tasks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sdischer-sap