Open
Conversation
…anary, Component, Connection, IncidentRule, Notification, Permission, Playbook, ScrapeConfig, and Topology. Co-authored-by: Genie <genie@cosine.sh>
✅ Deploy Preview for canarychecker canceled.
|
✅ Deploy Preview for flanksource-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds comprehensive documentation for various Custom Resource Definitions (CRDs) used in Mission Control. The following CRDs have been documented:
Each CRD includes a definition, schema, examples, and links to related documentation. This update ensures that users have access to detailed information about the CRDs available in Mission Control, enhancing usability and understanding.
Original Task: docs/fyg03ygyxvnh
Author: Moshe Immerman