Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
August 08, 2024VERSION
0.0.1
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
- Aug 07 | Trying to build server on meshery is failing
- Aug 07 | Meshery Development Meeting | Aug 7th 2024
- Aug 04 | Unable to run Meshery locally
- Aug 04 | How to setup e2e testing environment with playwright and docker for Meshery
- Jul 31 | Unable to access meshery server after meshery server status is running
- Jan 13 | Successfully setup cloud based developer environment to contribute to Meshery using GitHub Codespaces
- Jul 20 | Looking for a Meshmate for LFX
- Jul 17 | Meshery Development Meeting | July 17th 2024
- Nov 11 | Unable setup local Meshery development server
- Jul 13 | Looking for a Meshmate as I want to apply for this project in LFX mentorship program