Skip to content
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

Review and update community/docs/guidelines/technical-guidelines #836

Open
mmitoraj opened this issue Sep 12, 2023 · 2 comments
Open

Review and update community/docs/guidelines/technical-guidelines #836

mmitoraj opened this issue Sep 12, 2023 · 2 comments
Labels
area/documentation Issues or PRs related to documentation

Comments

@mmitoraj
Copy link
Collaborator

Description

While checking links in the community repo, it occurred that the Custom Resource Definition is outdated. We have been decomposing cluster essentials and with modularization, CRDs are created in the module manifests.

If you want to/ need to add your CRD, you need to add a Kyma module and define the CRD in it (info from KK).

While updating the document, please have a look at the whole technical-guidelines directory and check if it is up-to-date.

Area

Reasons

Assignees

@kyma-project/technical-writers

Attachments

@mmitoraj mmitoraj added the area/documentation Issues or PRs related to documentation label Sep 12, 2023
@mmitoraj mmitoraj changed the title Review and update community/docs/guidelines/releases-guidelines Review and update community/docs/guidelines/technical-guidelines Sep 12, 2023
@kyma-bot
Copy link
Contributor

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 11, 2023
@mmitoraj mmitoraj removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 16, 2023
@kyma-bot
Copy link
Contributor

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 15, 2024
@grego952 grego952 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 15, 2024
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
Projects
None yet
Development

No branches or pull requests

3 participants