Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
November 23, 2024VERSION
0.0.4
What this pattern does:
This represents a parent-child relationship between components, where one component is a dependency of another. Parent-child relationships show clear lineage, similar to a family tree. In this design, the namespace serves as a parent to the config map and role.
Caveats and Consideration:
Dependency Awareness: Users should understand that the child components (e.g., config maps, roles) depend on the parent (e.g., namespace). If the parent component is deleted or modified, it will affect the child components.
Compatibility:
Recent Discussions with "meshery" Tag
- Nov 22 | Meshery CI Maintainer: Sangram Rath
- Dec 04 | Link Meshery Integrations and Github workflow or local code
- Nov 20 | Meshery Development Meeting | Nov 20th 2024
- Nov 10 | Error in "make server" and "make ui-server"
- Nov 11 | Difference in dev Environments on port 9081 and 3000
- Nov 10 | npm run lint:fix error
- Oct 30 | Getting Meshery locally using Docker Desktop for Meshery UI contribution
- Nov 07 | Meshery + GCP Connector
- Oct 24 | Getting error when using utils.SetupContextEnv() when writing tests for relationship command
- Nov 16 | Where's the Cortex Integration of Meshmap?