Participating in the Meshery Catalog is an excellent opportunity to enhance and share your cloud native configurations with the community. By contributing your models and patterns, you not only showcase your work but also empower others to leverage your innovations. This guide provides a defined approach to using mesheryctl for uploading your models and patterns to the Catalog, ensuring a smooth and efficient contribution process.

As a self-service engineering platform, Meshery enables collaborative design and operation of cloud and cloud native infrastructure. Meshery is not service mesh-centric. Meshery is not service mesh-focused. Meshery is for modern and collaborative DevOps engineering teams, infrastructure teams, Site Reliability Engineer, Platform Engineers, Application Development and Service delivery teams to use an internal engineering platform for the Day 0 design, Day 1 deployment, and Day 2 opeeration of cloud and cloud native infrastructure and services.

On Friday, August 20, 2024, join us for a special enlightning session titled Infrastructure as Design by Meshery. This session will be a deep dive into how Meshery can transform your approach to designing, deploying, and managing cloud-native infrastructure. Join Whitney Lee from VMware as she hosts Lee Calcote, the Founder of Layer5, discussing the intricacies of Meshery and its significant impact on Cloud and Cloud Native space.

We are excited to announce a huge milestone for the Meshery community: over 200 new Meshery Designs have just been published on ArtifactHub! 🎉

As a proud contributor to the Meshery project, I’m thrilled to announce that Artifact Hub has officially recognized Meshery Designs as a native artifact kind. 🎉 Meshery Designs allow you to create, manage, and deploy complex architectures seamlessly, which make them a great addition to the growing collection of Artifact Hub artifacts such as Helm charts, Argo templates, and many more.

In Meshery, two key concepts play a pivotal role in managing infrastructure and deployments: Meshery Models and Meshery Designs. Understanding their difference and their similarities will greatly increase your benefit from these two powerful, systems management paradigms.

In the world of cloud computing and Kubernetes-based infrastructure, managing and optimizing resources can be complex and time-consuming. Meshery emerges as a powerful platform that simplifies cloud infrastructure and Kubernetes management, enabling organizations to streamline their operations. In this article, we will explore the features and benefits of Meshery and how it empowers organizations to efficiently manage their cloud infrastructure.

v0.7.0 is the latest and most significant release of Meshery, the CNCF’s cloud native manager. Included in this release is GitOps-enablement, a complete GraphQL API (in addition to the REST API), completely new CLI commands, a number of new resources with an internal capabilities registry, 200+ new integrations, and much more is now generally available.

As an extensible engineering platform, Meshery’s focus on flexibility and adaptability are key. Meshery has embraced this philosophy wholeheartedly as evident by the myriad ways in which it is extensible. By incorporating both REST and GraphQL APIs into its architecture, this dual approach allows Meshery to cater to a diverse range of use cases and developer preferences, ensuring that the platform remains a powerful and versatile tool for managing infrastructure and applications.

Ready to take your open source journey to the next level? We’re thrilled to announce an exciting update for all Layer5 users and contributors: the launch of our improved recognition program! 🎉🎈

Meshery offers Providers as a point of extensibility. With a built-in Local Provider (named “None”), Meshery Remote Providers are designed to be pluggable. Remote Providers offer points of extension to users / integrators to deliver enhanced functionality, using Meshery as a platform.

Announced at KubeCon NA 2022 is the v0.6.0 release of Meshery, the CNCF’s cloud native manager. In this latest release, three new feature areas entered beta, and GitOps enablement, with new CLI commands and more are now available to users as previewed at KubeCon NA 2022 this week.

With growing adoption of service meshes in cloud native environments, service mesh abstractions - service mesh-neutral specifications - have emerged. Service Mesh Performance and Service Mesh Interface are two open specifications that address the need for universal interfaces for interacting with and managing any type of service mesh. Let’s examine what each specification provides.

“Cloud native” doesn’t just mean “running in the cloud.” It’s a specific deployment paradigm and uses containers and an orchestration system (usually Kubernetes) to help provision, schedule, run and control a production workload in the cloud, or even across multiple clouds. Within cloud native deployments, an increasingly common approach to networking is the service mesh concept. With a service mesh, instead of each individual container requiring a full networking stack, a grouping of containers all benefit from a mesh that provides connectivity and networking with other containers as well as the outside world.

As more organizations implement service meshes, they are finding what works and what needs more work, and they are creating new management practices around this knowledge. A few tried-and-tested best practices were detailed last month during KubeCon+CloudNativeCon.

Anytime performance questions are to be answered, they are subjective to the specific workload and infrastructure used for measurement. Given the variety of this measurement challenge, the Envoy project, for example, refuses to publish performance data because such tests can be

An introduction to MeshMark might be best explained through a simple story that we can all relate to. As a consumer, when you make a purchase, there are generically two methods by which we determine our happiness about making any given purchase.