-
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
Add information on modular Kyma #17454
Add information on modular Kyma #17454
Conversation
✅ Deploy Preview for kyma-project-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/retest |
…ger/kyma into Add_modularization_info
/retest |
@@ -341,7 +341,7 @@ spec: | |||
type: array | |||
unsupportedMode: | |||
description: Is active when the LogPipeline uses a `custom` output | |||
or filter; see [unsupported mode](./../../01-overview/main-areas/telemetry/telemetry-02-logs.md#unsupported-mode#unsupported-mode). | |||
or filter; see [unsupported mode](./../../01-overview/telemetry/telemetry-02-logs.md#unsupported-mode#unsupported-mode). |
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.
We should not use relative links in the CRD description since this is also used outside of the docs and will not work there. Can you fix this within this PR or should we create a follow-up PR?
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.
We should not use relative links in the CRD description since this is also used outside of the docs and will not work there. Can you fix this within this PR or should we create a follow-up PR?
TBH, I'd prefer to do it in another PR.
/retest |
1 similar comment
/retest |
/test pre-main-kyma-integration-k3d-runtime-agent |
Description
Changes proposed in this pull request:
Related issue(s)
#17210