Skip to content

Add an introductory paragraph #779

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

Closed

Conversation

IwonaLanger
Copy link
Contributor

Description

Changes proposed in this pull request:

Provide a general description of the modular approach to Kyma.

Related issue(s)
See #17210

@IwonaLanger IwonaLanger added the area/documentation Issues or PRs related to documentation label Apr 21, 2023
@IwonaLanger IwonaLanger requested review from NHingerl and jacekon April 21, 2023 07:46
@IwonaLanger IwonaLanger requested a review from pbochynski as a code owner April 21, 2023 07:46
@IwonaLanger IwonaLanger self-assigned this Apr 21, 2023
@kyma-bot kyma-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 21, 2023
@jacekon
Copy link

jacekon commented Apr 27, 2023

@varbanv hey buddy please review the whole doc :D

With Kyma’s modular approach, you can install exactly the Kyma components you want, making the installation very lightweight and adjusted to your business needs. Kyma uses three system components to support the modular approach: Module Manager, Lifecycle Manager, and Runtime Watcher.
## Overview

The out-of-the-box Kyma offered a fixed set of mandatory preconfigured components whose development rhythm was synchronized and determined by the release schedule. With the modular approach, Kyma components become modules, each providing one functionality developed independently of the other ones. This approach also boosts Kyma’s extensibility and scalability. You can install and configure exactly the modules you want, making the installation very lightweight and adjusted to your business needs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The out-of-the-box Kyma offered a fixed set of mandatory preconfigured components whose development rhythm was synchronized and determined by the release schedule. With the modular approach, Kyma components become modules, each providing one functionality developed independently of the other ones. This approach also boosts Kyma’s extensibility and scalability. You can install and configure exactly the modules you want, making the installation very lightweight and adjusted to your business needs.
Classic Kyma offered a fixed set of mandatory preconfigured components with a synchronized development and release schedule. With the modular approach, Kyma components become modules, each providing one functionality developed independently of the other ones. The modular approach also boosts Kyma’s extensibility and scalability. You can install and configure exactly the modules you want, making the installation very lightweight and adjusted to your business needs.

I think the first sentence could be simplified slightly.
"Classic" is a word I'd suggest, because "out-of-the-box" doesn't imply that that's the "older" approach which is going to be replaced by modular Kyma at some time.

@IwonaLanger
Copy link
Contributor Author

I'm closing this PR as the information will be added to the website with kyma-project/kyma#17454. I've used your suggestions @NHingerl. Thank you!

@IwonaLanger IwonaLanger closed this May 8, 2023
@IwonaLanger IwonaLanger deleted the Add_modularization_overview branch November 21, 2023 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Give overview on current Kyma structure and future modular approach
4 participants