Catalog Details

• CATEGORY

  deployment

• CREATED BY

  sonal singh

• UPDATED AT

  November 23, 2024

• VERSION

  0.0.1

Pattern Snapshot

Related Patterns

deployment

Example Labels and Annotations

MESHERY4649

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

• Nov 22 | Meshery CI Maintainer: Sangram Rath Vivek Vishal
• Dec 04 | Link Meshery Integrations and Github workflow or local code Shlok Mishra
• Nov 20 | Meshery Development Meeting | Nov 20th 2024 Vivek Vishal
• Nov 10 | Error in "make server" and "make ui-server" Aadarsh Shekhar
• Nov 11 | Difference in dev Environments on port 9081 and 3000 Divyansh Khatri
• Nov 10 | npm run lint:fix error Sankarshan Mishra
• Oct 30 | Getting Meshery locally using Docker Desktop for Meshery UI contribution Davidudale
• Nov 07 | Meshery + GCP Connector Santosh Kumar Doodala
• Oct 24 | Getting error when using utils.SetupContextEnv() when writing tests for relationship command Sujai Gupta
• Nov 16 | Where's the Cortex Integration of Meshmap? Aditya Gupta