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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Models]: Add support for DataDog Operator #10721

Open
jameshorton2337 opened this issue Apr 11, 2024 · 2 comments
Open

[Models]: Add support for DataDog Operator #10721

jameshorton2337 opened this issue Apr 11, 2024 · 2 comments
Labels
area/models Models, Components, Relationships related changes issue/stale Issue has not had any activity for an extended period of time

Comments

@jameshorton2337
Copy link
Contributor

Proposed Change

Support the custom resources and deployment of this operator - https://github.com/DataDog/datadog-operator


Contributor Guides and Handbook

Contributing to Meshery Models

!! See https://docs.meshery.io/project/contributing/contributing-models

Instructions for Models

Forthcoming

Instructions for Components

While the default shape for new components is a circle, each component should be considered for its best-fit shape.

  1. Review and familiarize with the available set of predefined relationship types. Refer the Cytoscape node types for a list of possible shapes.
  2. Propose a specific shape, best-suited to visually represent the Component. Example - Deployment as a pentagon.
  3. Proposee a specific icon, best-suited to visually represent the Component. Example - DaemonSet as a skull icon.

Instructions for Relationships

  1. Identify the relationship and any specific constraints to be enforced between the two specific components, their models or potentially other components, models, or environmental considerations.
  2. Propose a specific visual representation for the relationship. See example on Modeling Relationships.
  3. Prospose the appropriate relationship type, using one of the predefined set of relationship types or suggest a new relationship where an existing type does not fit.
  4. Create a Relationship Definition (yaml).
  5. Create a policy for evaluation of the relationship (rego).
  6. Review a prior pull request as an example of how to define a Relationships: https://github.com/meshery/meshery/pull/9880/files

Instructions for Policies

  1. Forthcoming
@jameshorton2337 jameshorton2337 added the area/models Models, Components, Relationships related changes label Apr 11, 2024
Copy link

welcome bot commented Apr 11, 2024

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.

Copy link

stale bot commented May 22, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/models Models, Components, Relationships related changes issue/stale Issue has not had any activity for an extended period of time
Projects
None yet
Development

No branches or pull requests

1 participant