-
Notifications
You must be signed in to change notification settings - Fork 405
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
Remove Loki #17751
Remove Loki #17751
Conversation
✅ Deploy Preview for kyma-project-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -112,7 +112,7 @@ To deploy Kyma with only specific components, run: | |||
kyma deploy --components-file {COMPONENTS_FILE_PATH} | |||
``` | |||
|
|||
`{COMPONENTS_FILE_PATH}` is the path to a YAML file containing the desired component list to be installed. In the following example, only eight components are deployed on the cluster: | |||
`{COMPONENTS_FILE_PATH}` is the path to a YAML file containing the desired component list to be installed. In the following example, only seven components are deployed on the cluster: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good job for noticing this!!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! 😄
/test pre-main-kyma-integration-k3d-runtime-agent |
5 similar comments
/test pre-main-kyma-integration-k3d-runtime-agent |
/test pre-main-kyma-integration-k3d-runtime-agent |
/test pre-main-kyma-integration-k3d-runtime-agent |
/test pre-main-kyma-integration-k3d-runtime-agent |
/test pre-main-kyma-integration-k3d-runtime-agent |
* remove Loki resources * remove logging from components list * adjust docs for loki removal * remove Loki from dashboard * add migration script * adjust migration guide for Kyma 2.17
Description
Changes proposed in this pull request:
Related issue(s)
#17637