New Catalog publish request
no-r...@layer5.io
New publish request received from Junaid Ali for catalog content of type design named wordpress-26.0.0.tgz. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- wordpress-operator
Description
A popular open-source content management system for building websites and blogs.
Caveats and Consideration
Persistent Storage: This design requires a Persistent Volume to store the database and user-uploaded content. Ensure a Storage Class is available in your cluster for dynamic provisioning. Admin Credentials: The admin username and password are automatically generated in a Kubernetes Secret upon first deployment. You will need to retrieve these from the secret to log in for the first time. Production Database: For production use, it is highly recommended to use an external, managed database instead of the default one deployed by the chart.
Need any help? Simply visit the forum, email, or slack us.
|
|
|
|
|
Copyright 2025, Layer5, Inc. All right reserved.
Lee Calcote
--
Visit and engage with the Meshery community in the forum at http://discuss.meshery.io or in Slack at https://slack.meshery.io.
---
You received this message because you are subscribed to the Google Groups "Meshery Maintainers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maintainers...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/maintainers/68d66bbd.050a0220.15c70a.5910%40mx.google.com.
no-r...@layer5.io
New publish request received from Nafisa Tahasin for catalog content of type design named fullstack-app-design. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- ace
Description
This design represents a minimal full-stack web application architecture. Client Browser → sends requests to the application. Nginx (port 80) → acts as a reverse proxy, serving the frontend and forwarding API requests. Node.js Backend (port 3000) → handles application logic and API endpoints. Redis (port 6379) → used as an in-memory database/cache for fast data access, session storage, or queue management.
Caveats and Consideration
No persistent database is included (Redis is in-memory, so data is lost if the service restarts). Security (HTTPS/TLS, authentication, and authorization) is not configured yet. Scaling is single-instance; no load balancing or replication is set up. Monitoring/Logging tools (like Prometheus, Grafana, ELK) are not included. Frontend is assumed to be static files served by Nginx — if a modern React/Angular app is needed, a separate build process may be required.
no-r...@layer5.io
New publish request received from Naveen Srinivas for catalog content of type design named Basic Web Deployment. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
workloads
Technology
- accurate
Description
This is a basic design depicting traffic entering through an ingress before going through the frontend service and pods before reaching the backend service and pods. The backend connects to a database through its pods, and the database also runs a StatefulSet to manage itself
Caveats and Consideration
Deployments work for frontend and backend, but the database needs a stateful set for preventing data loss. Ingress only handles traffic entering the cluster and doesn't interact with the pods
Mia Grenell
On Sep 28, 2025, at 11:31 AM, no-reply via Meshery Maintainers <maint...@meshery.io> wrote:
--
Visit and engage with the Meshery community in the forum at http://discuss.meshery.io or in Slack at https://slack.meshery.io.
---
You received this message because you are subscribed to the Google Groups "Meshery Maintainers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maintainers...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/maintainers/68d962f5.050a0220.4741f.da38%40mx.google.com.
no-r...@layer5.io
New publish request received from Ritesh Karankal for catalog content of type design named robot-shop. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- nginx-ingress
Description
robot-shop is a sample microservices application designed as a sandbox for learning containerized application orchestration and monitoring techniques. Main features & components: - Multiple microservices built using a variety of languages / frameworks: Node.js (Express), Java (Spring Boot), Python (Flask), Go, PHP (Apache) - Uses multiple data stores & middleware: MongoDB, Redis, MySQL, RabbitMQ - Frontend (web) service using AngularJS - Nginx for web serving / reverse proxy - Observability / monitoring / tracing support: services expose Prometheus metrics (e.g. cart/payment), Instana agent for tracing & metrics. - Includes load generation utility (load-gen) (using Locust) for simulating traffic / testing performance. - Supports being run via Docker Compose locally, or deployed to Kubernetes (using Helm Chart)
Caveats and Consideration
- Error handling is patchy and there is not any security built into the application. - Load generation is not automatic; it needs to be triggered manually or via provided load generator utilities. - This sample microservice application has been built using these technologies: NodeJS (Express), Java (Spring Boot), Python (Flask), Golang, PHP (Apache), MongoDB, Redis, MySQL (Maxmind data), RabbitMQ, Nginx, AngularJS (1.x) - AngularJS (1.x) is an older frontend framework; some libraries / dependencies may be deprecated.
no-r...@layer5.io
New publish request received from Kavya Katal for catalog content of type design named ELKK Stack with Kafka. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- kubernetes
Description
ELKK (ELK + Kafka) logging pipeline: My App emits logs → Kafka Producer publishes to Kafka topic logs → Kafka brokers the stream (9092) → Logstash consumes from Kafka and indexes into Elasticsearch (index pattern app-logs-*, port 9200) → Kibana queries Elasticsearch for visualisation (5601). This Meshery Design captures the topology and intent; some nodes use generic workload placeholders where native models were not available.
Caveats and Consideration
Design is topology-focused; some components (Kafka Producer, Logstash, Kibana) are represented as generic workloads/Namespaces. Provides a Logstash pipeline that consumes from Kafka and outputs to Elasticsearch. Update hostnames/ports for your environment (e.g., kafka:9092, elasticsearch:9200). Security/auth not configured (no TLS/SASL for Kafka, no X-Pack auth for ES/Kibana). Intended for a single-namespace demo; scaling and production hardening are out of scope.
no-r...@layer5.io
New publish request received from Kavya Katal for catalog content of type design named kibana-helm-design-fixed. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- kubernetes
Description
Kibana Helm chart imported as a Meshery Design using mesheryctl. Includes core Kibana Deployment and Service rendered from the charts default values and validated on Kanvas.
Caveats and Consideration
• Requires an accessible Elasticsearch endpoint at runtime (this design does not deploy Elasticsearch). • Images/versions are taken from chart defaults adjust for your environment. • Security/auth not configured (no TLS/SASL for Kafka; no X-Pack for Kibana/Elasticsearch). • Intended as a minimal, single-namespace demo; production hardening and scaling are left to the user. • Optional resources (Ingress, HPA, extra ConfigMaps) are disabled by default; enable via Helm values and re-import if needed. • Service/ports/hostnames should be updated per your cluster (e.g., service type ClusterIP/NodePort/LoadBalancer).
no-r...@layer5.io
New publish request received from Kavya Katal for catalog content of type design named ELKK Design Kafka. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- kubernetes
Description
ELKK (ELK + Kafka) logging pipeline: My App emits logs → Kafka Producer publishes to Kafka topic logs → Kafka brokers the stream (9092) → Logstash consumes from Kafka and indexes into Elasticsearch (index pattern app-logs-*, port 9200) → Kibana queries Elasticsearch for visualisation (5601). This Meshery Design captures the topology and intent; some nodes use generic workload placeholders where native models were not available.
Caveats and Consideration
Design is topology-focused; some components (Kafka Producer, Logstash, Kibana) are represented as generic workloads/Namespaces. Provides a Logstash pipeline that consumes from Kafka and outputs to Elasticsearch. Update hostnames/ports for your environment (e.g., kafka:9092, elasticsearch:9200). Security/auth not configured (no TLS/SASL for Kafka, no X-Pack auth for ES/Kibana).
no-r...@layer5.io
New publish request received from Sumit Kumar for catalog content of type design named Kafka Meshery design. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- accurate
Description
Name: Kafka Streaming Platform Version: 0.0.1 Type: Deployment Description: Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications. This design is based on the Bitnami Kafka Helm chart version 32.4.3 with Kafka 4.0.0. Tags: kafka,streaming,messaging,bitnami,infrastructure Category: Infrastructure Visibility: Public (so it can be published to catalog)
Caveats and Consideration
• Requires persistent storage for data durability • Uses KRaft mode (no Zookeeper dependency) • Default configuration suitable for development/testing • For production use, consider scaling replicas and configuring resource limits • Ensure proper network policies are in place for security
no-r...@layer5.io
New publish request received from Abhinav Rana for catalog content of type design named Terraform-Architecture. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- terraform
Description
Terraform Architecture
Caveats and Consideration
This architecture design is created for visual representation and understanding of the Terraform workflow.
no-r...@layer5.io
New publish request received from Kavya Katal for catalog content of type design named Vald(Helm)-v1.7.17.tgz. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- kubernetes
Description
This design was generated from the Vald Helm chart (v1.7.17) and includes core components like discoverer, manager, agent, and gateway.
Caveats and Consideration
- This design reflects Vald Helm chart v1.7.17.
no-r...@layer5.io
New publish request received from Sekar C for catalog content of type design named MERN . Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- appmesh-controller
Description
A foundational, three-tier MERN stack architecture designed for full-stack application deployment. It includes a React frontend, an Express/Node.js backend, and a MongoDB database, illustrating the data flow between them.
Caveats and Consideration
This is a conceptual architecture diagram created with Kanvas shapes and images. It does not contain deployable configuration logic (Kubernetes YAML, deployment ports, environment variables, etc.) and is intended for visualization purposes only.
no-r...@layer5.io
New publish request received from Kavya Katal for catalog content of type design named clickhouse-otel-hyperdx-arch. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- clickhouse
Description
Architecture design for ClickHouse with OpenTelemetry Collector, HyperDX, and MongoDB. - OTLP (HTTP/gRPC) data is ingested by OpenTelemetry Collector. - Collector exports telemetry to ClickHouse. - HyperDX queries ClickHouse for analytics. - MongoDB is used by HyperDX to maintain application state.
Caveats and Consideration
HyperDX is represented as a Kubernetes Deployment since a dedicated MeshModel is not available. MongoDB and OpenTelemetry Collector are also modeled as Deployments for the same reason.
no-r...@layer5.io
New publish request received from Jeeva Ramanathan for catalog content of type design named Prometheus and Grafana monitoring stack. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- kube-prometheus
- kubedb-grafana-dashboards
Description
Prometheus and Grafana monitoring stack design
Caveats and Consideration
Prometheus and Grafana
no-r...@layer5.io
New publish request received from Om Rai for catalog content of type design named first design. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- kubernetes
Description
A simple kubernetes flow using pods and deployment
Caveats and Consideration
Be aware of what kubernetes is , what pods and containers are
no-r...@layer5.io
New publish request received from Junaid Ali for catalog content of type design named chaos-mesh-architecture-copy. Head over to Layer5 Cloud to approve or deny user's request. User will be notified if their request is approved or denied.
Type
deployment
Technology
- chaos-mesh
Description
A visual design representing the core architecture of the Chaos Mesh platform and its components within a Kubernetes environment.
Caveats and Consideration
This is a non-deployable visual design intended for informational and illustrative purposes only.