Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
May 01, 2024VERSION
1.0
What this pattern does:
This infrastructure design defines two services within a system: 1. **Customer Service**: - Type: Customer - Version: 0.0.50 - Model: Jira Service Desk Operator - Attributes: This service is configured with specific settings, including an email address, legacy customer mode, and a name. It is categorized as a tool within the system.2. **Notebook Service**: - Type: Notebook - Version: 1.6.1 - Model: Kubeflow - Attributes: This service is categorized as a machine learning tool. It has metadata related to its source URI and appearance. These services are components within a larger system or design, each serving a distinct purpose. The Customer Service is associated with customer-related operations, while the Notebook Service is related to machine learning tasks.
Caveats and Consideration:
Make sure to use correct credentials for Jira service operator
Compatibility:
Recent Discussions with "meshery" Tag
- Apr 24 | Meshery Development Meeting | April 24th 2024
- Mar 11 | [Help Wanted] A list of open DevOps-centric needs on Meshery projects
- Apr 14 | Unable to deploy meshery to minikube
- Apr 16 | Help needed for setup of meshery cli
- Apr 17 | Meshery Development Meeting | April 17th 2024
- Apr 12 | What exactly is this sistent design system project
- Nov 11 | Unable setup local Meshery development server
- Apr 10 | How a beginner can start exploring project of meshery?
- Apr 10 | Meshery Development Meeting | April 10th 2024
- Apr 07 | Regarding [Bug]: Connection page shows error in "Local Provider" #10595