+
+
+
+### How Load Balancing Works:
+
+Load balancing involves three main components:
+
+1. **Load Balancer:** Positioned between users and application servers, it monitors incoming traffic and redirects it to the most suitable server. It can be hardware-based or software-based, with the latter running on existing infrastructure.
+
+2. **Application Servers:** These servers host applications, receiving traffic from the load balancer and serving requested content to users.
+
+3. **Users:** End-users access applications through the internet or intranet.
+
+When a user initiates a request, the load balancer evaluates factors such as server capacity, usage rate, and response time to determine the optimal server. This process enhances efficiency and reduces user wait times.
+
+## Benefits of Load Balancers: Performance, Reliability, and Scalability
+
+ > **Improved Performance:** By distributing workloads evenly, response time and system latency are reduced.
+
+ > **Increased Reliability:** Fault tolerance is enhanced by detecting and removing failed or unhealthy servers,redirecting traffic to functional servers.
+
+ > **Enhanced Scalability:** The system's capacity can be horizontally scaled by adding more servers without impacting existing ones.
+
+ > **Reduced Costs:** Efficient resource utilization avoids underutilization or overprovisioning of servers.
+
+## Load Balancing with [Meshery](https://meshery.io/)
+
+Meshery serves as a platform for managing various Cloud Native applications . While it doesn't directly perform load balancing directly, Meshery allows users to configure and observe load balancing within their chosen Cloud Native Adaptors. Through a unified dashboard, users can customize load balancing settings, monitor relevant metrics, and leverage observability tools to gain insights into the performance and health of load balancing features. Meshery's focus is on providing a consistent and user-friendly interface for Cloud Native Lifecycle Management, including load balancing configuration.
+
+**Adapters**
+
+ - [Istio](https://docs.meshery.io/service-meshes/adapters/istio)
+ - [Linkerd](https://docs.meshery.io/service-meshes/adapters/linkerd)
+ - [Consul](https://docs.meshery.io/service-meshes/adapters/consul)
+ - [Network Service Mesh](https://docs.meshery.io/service-meshes/adapters/nsm)
+
+
+## Types of Load Balancers in Kubernetes: Service, Ingress, and External
+
+1. **Service Load Balancing:** This basic Kubernetes tactic routes all requests to a service and directs them to matching pods. It's suitable for cluster-internal traffic but lacks advanced features like SSL termination.
+
+2. **Ingress Load Balancing:** Handling external traffic, it routes requests based on rules defined in an ingress resource. It offers more flexibility and functionality, including SSL termination and authentication.
+
+3. **External Load Balancing:** Involving external load balancers from cloud providers (AWS ELB, Google Cloud Load Balancer), it provides layer-4 or layer-7 load balancing and high availability. However, it adds complexity and additional costs.
+
+## Challenges of Load Balancing
+
+Despite its advantages, load balancing comes with challenges such as the need for careful configuration to address specific application requirements and potential complexities in managing dynamic workloads.
+
+
+## Load Balance Algorithms: Static and Dynamic
+
+
+##### Static Load Balancing Algorithms:
+
+1. **Round Robin:** Distributes requests sequentially across servers.
+
+2. **Hash:** Distributes requests based on a key, such as client IP address or request URL.
+
+3. **Random:** Distributes requests randomly.
+
+##### Dynamic Load Balancing Algorithms:
+
+1. **Least Connections:** Directs requests to the server with the fewest active connections.
+
+2. **Least Response Time:** Considers active connections and average response time to determine the optimal server.
+
+3. **Least Bandwidth:** Routes requests to the server with the least traffic.
+
+## Choosing the Right Load Balancer: Tips and Considerations
+
+Consider factors like application needs, performance requirements, and scalability when selecting a load balancer—whether hardware, software, or a combination.
+
+
+## Conclusion: Empowering Applications with Optimal Load Balancing
+
+Load balancing is a powerful technique that significantly impacts the performance, reliability, and scalability of applications. Whether distributing workloads based on static or dynamic algorithms, choosing the right load balancing strategy is crucial for delivering an exceptional user experience and optimizing resources. As technologies evolve, staying informed about the latest load balancing practices ensures continuous improvement in application delivery.
+
+
diff --git a/src/collections/blog/2024/01-07-contributing-as-a-designer/header-image.svg b/src/collections/blog/2024/01-07-contributing-as-a-designer/header-image.svg
new file mode 100644
index 000000000000..874c306526d5
--- /dev/null
+++ b/src/collections/blog/2024/01-07-contributing-as-a-designer/header-image.svg
@@ -0,0 +1,36 @@
+
diff --git a/src/collections/blog/2024/01-07-contributing-as-a-designer/index.mdx b/src/collections/blog/2024/01-07-contributing-as-a-designer/index.mdx
new file mode 100644
index 000000000000..e8d96eddfc20
--- /dev/null
+++ b/src/collections/blog/2024/01-07-contributing-as-a-designer/index.mdx
@@ -0,0 +1,60 @@
+---
+title: "Contributing to Layer5: A Designer’s Journey"
+subtitle: "Insights from a visual design intern at Layer5"
+date: 2024-01-07 10:30:05 -0530
+author: Victoria Nduka
+thumbnail: ./header-image.svg
+darkthumbnail: ./header-image.svg
+category: "Community"
+description: "Insights from my experience contributing to Layer5 as a design intern"
+tags:
+ - Community
+ - Internship
+type: Blog
+resource: false
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+
+
+
+Early last month, I got the news that I had been accepted as a UI Visual Design Intern at Layer5. Five months ago, I was a new contributor with zero knowledge of cloud native technologies roaming through their Github looking to make my first contribution. In this article, I’ll share my journey contributing to Layer5 as a designer. I’ll also share insights I hope new contributors find useful as they navigate their open source journey.
+
+### Discovery
+I first learned about Layer5 through the LFX Mentorship. I stumbled upon a tweet by [Anita Ihuman](/community/members/anita-ihuman) announcing that [Meshery](https://layer5.io/cloud-native-management/meshery) was accepting mentees for a design-related project. I had always been looking to make design contributions to open source projects but it was hard finding one. So, this was a great opportunity for me.
+
+### My First Contribution
+Interestingly, my first contribution to Layer5 had nothing to do with design. It was a writing task. They needed a blog that highlighted [the importance of GitHub stars](https://layer5.io/blog/community/on-the-importance-of-github-stars) to a project. The purpose of the blog was to boost the project’s visibility by encouraging more people to [give Meshery a star](https://github.com/meshery/meshery) on GitHub. Since I had some experience writing, I volunteered to write the blog. It was a bit more tasking than I had anticipated but with the help of the community, I was able to work through it.
+
+### Making Design Contributions
+I noticed there were a bunch of open issues to design badges for users and contributors. I requested to work on one of the badges and got assigned. I didn’t initially have edit access to the community Figma file so I struggled to get assets like the logo and font to create the design. I eventually found them in the local branch of Layer5 that I had cloned earlier on my PC. Turned out that all the resources I needed to complete that task were available to me; I just needed to know where to look.
+
+That was my first design contribution. Since then I’ve designed more badges and contributed in many other ways besides design. For instance, I worked on documentation and helped with marketing and community management.
+
+### How I've Benefited
+Here’s a non-exhaustive summary of how contributing to Layer5 has benefited me:
+1. **Autonomy** - I’ve learned to own my process and see tasks from start to finish. When I volunteered to write that first blog, I thought I’d do just the writing part and someone else would get it up on the website. I didn’t realize that I would have to clone a repository, learn to use Git CMD, make commits, learn Markdown, and raise a pull request. These were all foreign to me and I was doing them for the first time. It was a great learning opportunity and I’m grateful for it.
+1. **Presentation** - We hold weekly meetings where contributors share what they’re working on and receive feedback. Presenting at these meetings has taught me to not just show my work, but to talk about it. I’m not a great orator so this was challenging for me at first but I’ve noticed that I’m getting more confident with each presentation I make. I’m gradually learning how to clearly articulate my thought process and have a valid justification for any route I choose to take to complete a task.
+1. **Design** - Making design contributions has helped improve the quality of my work. Sometimes, I’d nail a design on my first try. Other times, I may have to iterate several times before I get it right. The important thing is that I end up producing high-quality work. I’ve also learned to detach myself from my work, be objective, and gracefully accept constructive criticism.
+1. **Collaboration** - For the first time, I get to work together with developers and other designers. Thanks to Layer5. I’m also learning to use communication and collaboration tools like Slack, GitHub, and ClickUp.
+
+### How You Can Contribute to Layer5
+My experience clearly shows that you don’t necessarily need to know anything about coding or cloud native technologies to contribute to Layer5 projects. Are you a designer, technical writer, community manager, or digital marketer? There are several ways to contribute. You can
+- Work on improving the [documentation](https://docs.layer5.io),
+- Design new website pages or improve the UX of existing ones,
+- Warmly welcome newcomers to the community and offer support,
+- Give constructive feedback during the weekly meetings,
+- Talk about Layer5 and invite your friends to use and [star Meshery](https://github.com/meshery),
+- Write articles for our blog.
+
+The list is endless. My advice is that you do not box yourself. Don’t feel that because you’re a designer, your contributions will be strictly design-related. If you want to make impactful contributions, pay attention to the needs of the community/project and help where you can.
+
+For more guidance on contributing to Layer5, check out our [newcomer’s guide](https://layer5.io/community/newcomers).
+
+
+\-- Victoria Nduka
+
+_**P.S.: If these topics excite you and you want to explore the beautiful realm of service meshes, come and say "Hi" on our [Slack Channel](http://slack.layer5.io) and one of us will reach out to you!**_
+
+
diff --git a/src/collections/blog/2024/02-13-what-is-platform-engineering/index.mdx b/src/collections/blog/2024/02-13-what-is-platform-engineering/index.mdx
new file mode 100644
index 000000000000..19dc42b45414
--- /dev/null
+++ b/src/collections/blog/2024/02-13-what-is-platform-engineering/index.mdx
@@ -0,0 +1,155 @@
+---
+title: What is Platform Engineering?
+subtitle:
+date: 2024-02-23 08:00:00 -0530
+author: Layer5 Team
+thumbnail: ./platform-engineering-hero.png
+darkthumbnail: ./platform-engineering-hero.png
+description: "What is Platform Engineering? What is an internal developer platform? How Meshery is a self-service, extensible engineering platform."
+type: Blog
+category: Platform Engineering
+tags:
+ - Platform Engineering
+ - Kubernetes
+featured: true
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import Button from "../../../../reusecore/Button";
+import CTA_FullWidth from "../../../../components/Call-To-Actions/CTA_FullWidth";
+import CTAImg from "../../../../assets/images/meshery/icon-only/meshery-logo-shadow.webp"
+
+
+
In today's fast-paced and interconnected world, the success of many businesses depends heavily on technology platforms that enable them to deliver their products and services efficiently. Platform engineering plays a crucial role in the development, operation, and maintenance of these platforms, ensuring their stability, scalability, and security.
+
+
+In this article, we will explore the fundamentals of platform engineering, providing a comprehensive overview of the key concepts, benefits, and challenges associated with this field. We will delve into the process of designing and building a platform, discussing the identification of requirements, architectural considerations, and the tools and technologies that facilitate platform development. Additionally, we will explore the critical aspects of operating and maintaining a platform, including managing infrastructure, monitoring performance, and ensuring security and compliance.
+
+
+By understanding the intricacies of platform engineering, businesses and technology professionals can effectively leverage the power of platforms to drive innovation, enhance customer experiences, and achieve their organizational goals. Whether you are a software engineer, a platform architect, or a business leader, this article will provide valuable insights into the world of platform engineering and equip you with the knowledge required to navigate this ever-evolving landscape.
+
+## Fundamentals of Platform Engineering
+
+Platform engineering is a rapidly evolving discipline that plays a crucial role in the development and success of modern software systems. In this section, we will explore the fundamentals of platform engineering, including its definition, importance, key concepts, and the benefits and challenges associated with it.
+
+### Definition and Importance of Platform Engineering
+
+Platform engineering can be defined as the process of designing, building, and maintaining a stable and scalable foundation upon which software applications and services can be developed, deployed, and operated. It involves creating a set of reusable and customizable components, tools, and frameworks that enable developers to build and deploy applications with greater efficiency and speed.
+
+
The importance of platform engineering cannot be overstated. A well-designed platform provides a solid foundation for software development, allowing organizations to deliver high-quality applications that meet the needs of their users. By creating a standardized set of tools, processes, and best practices, platform engineering ensures consistency and reduces the time and effort required to develop, deploy, and maintain software systems.
+
+### Key Concepts in Platform Engineering
+
+To understand platform engineering better, it is essential to familiarize ourselves with some key concepts. These concepts include:
+
+1. Modularity: Platforms are designed to be modular, with components that can be easily added, removed, or replaced. This modularity enables flexibility and adaptability, allowing for the rapid development and integration of new features and functionalities.
+
+2. Scalability: A well-designed platform can handle increased workloads and user demands without sacrificing performance. Scalability involves the ability to add resources, such as servers or processing power, to meet growing demands and ensure optimal system performance.
+
+3. Extensibility: Platforms should be designed to accommodate future growth and evolution. They should provide the necessary flexibility to integrate new technologies, frameworks, and tools as they emerge, allowing developers to stay ahead of the curve and leverage the latest advancements. Learn about Meshery's extensibility.
+
+### Benefits and Challenges of Platform Engineering
+
+Platform engineering offers numerous benefits to organizations, including:
+
+1. Increased development speed: By providing reusable components and standardized processes, platforms enable developers to build applications more quickly, reducing time-to-market and increasing productivity.
+
+2. Improved collaboration: Platforms foster collaboration by providing a shared framework and tools that allow developers to work together seamlessly. This collaborative environment promotes knowledge sharing, reduces duplication of effort, and facilitates efficient problem-solving.
+
+3. Cost savings: Building on a solid platform foundation reduces development costs by eliminating the need to reinvent the wheel for each application. Additionally, platforms enable organizations to leverage economies of scale by sharing resources and infrastructure across multiple applications.
+
+However, platform engineering also presents its own set of challenges, including:
+
+1. Complexity: Building and maintaining a platform can be complex due to the interdependencies between various components and the need for integration with other systems. It requires a deep understanding of the underlying technologies and the ability to manage and mitigate potential risks and issues.
+
+2. Continuous evolution: Platforms need to evolve continuously to keep up with changing technologies and user needs. This requires a proactive approach to stay updated with emerging trends, evaluate new tools and frameworks, and invest in ongoing maintenance and upgrades.
+
+In the next section, we will delve into the process of designing and building a platform, exploring the key considerations, requirements, and tools involved in the platform engineering journey.
+
+<>
+
+
+
+## Designing and Building a Platform
+
+Designing and building a platform is a crucial step in platform engineering. It requires careful consideration of various factors to ensure a robust and scalable infrastructure that meets the needs of the organization and its users. In this section, we will explore the key aspects of designing and building a platform, including identifying platform requirements, architectural considerations, and the tools and technologies involved in platform development.
+
+### Identifying Platform Requirements
+
+Before starting the design and development process, it is essential to identify the specific requirements of the platform. This involves understanding the goals and objectives of the platform, as well as the target audience and their needs. By clearly defining the requirements, platform engineers can make informed decisions throughout the development process.
+
+Platform requirements can vary significantly depending on the industry and organization. For example, an e-commerce platform may need to handle high volumes of traffic and transactions, while a healthcare platform may require stringent security and privacy measures. It is important to consider factors such as scalability, performance, security, integration capabilities, and user experience when determining the platform requirements.
+
+### Architectural Considerations for Platform Design
+
+Once the requirements are in place, the next step is to determine the architectural design of the platform. The architecture serves as the blueprint for the platform and guides the development process. It defines the structure, components, and interactions within the platform.
+
+There are various architectural patterns to consider, such as monolithic, microservices, serverless, and container-based architectures. Each pattern has its own advantages and trade-offs, and the choice depends on factors like scalability, flexibility, maintainability, and cost.
+
+Additionally, platform engineers need to consider factors such as data storage and management, communication protocols, integration with external systems, and fault tolerance. These considerations ensure that the platform is designed to handle the expected workload and can adapt to future needs.
+
+### Tools and Technologies for Platform Development
+
+Designing and building a platform requires the use of various tools and technologies that facilitate the development process. These tools range from integrated development environments (IDEs) to version control systems, testing frameworks, and deployment automation tools.
+
+Depending on the chosen architecture and requirements, platform engineers may utilize technologies like cloud computing platforms, containerization technologies like Docker and Kubernetes, programming languages such as Java, Python, or JavaScript, and frameworks like Spring Boot or Node.js.
+
+It is crucial for platform engineers to stay updated with the latest tools and technologies in the industry. This enables them to leverage the most efficient and effective solutions for platform development, ensuring optimal performance, scalability, and maintainability.
+
+By carefully considering platform requirements, architectural design, and utilizing appropriate tools and technologies, platform engineers can build a robust and scalable platform that meets the organization's needs. In the next section, we will explore the operational aspects of platform engineering.
+
+## Operating and Maintaining a Platform
+
+Operating and maintaining a platform is crucial for ensuring its continued functionality, scalability, and security. This section will explore the key aspects of managing a platform's infrastructure, monitoring its performance, and ensuring security and compliance in its operations.
+
+### Managing Platform Infrastructure
+
+Managing the infrastructure of a platform involves various tasks, such as provisioning and configuring servers, managing databases, and deploying software updates. It is essential to have a robust infrastructure management strategy to ensure the platform's stability and availability.
+
+One of the key considerations in managing platform infrastructure is scalability. As the platform grows and user demands increase, the infrastructure must be able to handle the load efficiently. This may involve scaling up the existing infrastructure or adopting cloud-based solutions to ensure flexibility and elasticity.
+
+Moreover, effective resource allocation is critical for optimizing platform performance and cost-efficiency. By monitoring resource utilization and performance metrics, platform engineers can identify bottlenecks and allocate resources accordingly, ensuring optimal use of available infrastructure.
+
+### Platform Monitoring and Performance Optimization
+
+Monitoring the platform's performance is essential for identifying and resolving issues proactively. Platform engineers employ various monitoring tools and techniques to track key performance indicators, such as response time, resource utilization, and availability.
+
+Real-time monitoring enables the early detection of performance degradation or system failures, allowing platform engineers to take immediate action to mitigate the impact on users. Moreover, historical performance data can provide valuable insights for capacity planning and future optimizations.
+
+Performance optimization involves fine-tuning the platform to enhance its efficiency and responsiveness. This may include optimizing database queries, improving caching mechanisms, or implementing load balancing techniques. Regular performance testing and profiling can uncover potential bottlenecks and guide optimization efforts.
+
+### Ensuring Security and Compliance in Platform Operations
+
+Security and compliance are paramount in platform operations, especially when dealing with sensitive data or regulated industries. Platform engineers must implement robust security measures to protect the platform and its users from potential threats.
+
+This may involve implementing secure authentication and authorization mechanisms, encrypting data in transit and at rest, and regularly patching and updating software components to address security vulnerabilities. Additionally, platform engineers should establish strict access control policies and regularly audit system logs for any suspicious activities.
+
+Compliance with industry regulations and standards is also essential for platform operations. Platform engineers must stay updated with the latest compliance requirements and ensure that the platform meets the necessary standards. This may involve conducting regular audits, documenting compliance processes, and implementing necessary controls.
+
+## Conclusion
+
+Operating and maintaining a platform requires diligent attention to infrastructure management, performance monitoring, and security and compliance practices. By focusing on these key aspects, platform engineers can ensure the platform's stability, scalability, and data integrity, ultimately providing a reliable and secure experience for users.
+
+In conclusion, platform engineering plays a crucial role in the development and success of any digital product or service. By providing a robust and scalable foundation, platform engineering enables organizations to accelerate their innovation, streamline operations, and enhance customer experiences.
+
+Throughout this article, we have explored the fundamentals of platform engineering, including its definition, importance, and key concepts. We have also discussed the benefits and challenges associated with platform engineering, recognizing that while it offers numerous advantages, it requires careful planning, design, and maintenance.
+
+Designing and building a platform necessitates a thorough understanding of the requirements and architectural considerations. By leveraging the right tools and technologies, organizations can create a platform that aligns with their goals and objectives, while also ensuring flexibility and scalability to accommodate future growth.
+
+Operating and maintaining a platform demands ongoing management of the infrastructure, including continuous monitoring and performance optimization. Organizations must also prioritize security and compliance to safeguard sensitive data and ensure regulatory adherence.
+
+Platform engineering is a dynamic and ever-evolving field, driven by the rapid advancements in technology and the changing needs of businesses and consumers. As organizations embrace digital transformation and seek to stay competitive in the digital age, platform engineering will continue to play a pivotal role in delivering innovative solutions and driving business success.
+
+In summary, platform engineering is the backbone of modern-day digital products and services. It empowers organizations to build, operate, and maintain robust platforms that can support their business objectives, enhance customer experiences, and drive growth. By understanding the fundamentals, embracing best practices, and staying abreast of emerging trends, organizations can leverage platform engineering to unlock their full potential in an increasingly digital world.
+
+
\ No newline at end of file
diff --git a/src/collections/blog/2024/02-13-what-is-platform-engineering/platform-engineering-hero.png b/src/collections/blog/2024/02-13-what-is-platform-engineering/platform-engineering-hero.png
new file mode 100644
index 000000000000..65d89b8eeddd
Binary files /dev/null and b/src/collections/blog/2024/02-13-what-is-platform-engineering/platform-engineering-hero.png differ
diff --git a/src/collections/blog/2024/02-24-open-container-image-meshery/index.mdx b/src/collections/blog/2024/02-24-open-container-image-meshery/index.mdx
new file mode 100644
index 000000000000..f1ebe479f5ed
--- /dev/null
+++ b/src/collections/blog/2024/02-24-open-container-image-meshery/index.mdx
@@ -0,0 +1,92 @@
+---
+title: Making Container Registries a home for Meshery Designs
+subtitle: The ubiquity of the OCI format
+date: 2024-02-24 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./oci-images-meshery.png
+darkthumbnail: ./oci-images-meshery.png
+description: "The adoption of OCI format by container registries and its integration within Meshery's design pattern management brings numerous benefits to the world of collaborative application infrastructure management."
+type: Blog
+category: Meshery
+tags:
+ - Docker
+ - Kubernetes
+featured: true
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import Button from "../../../../reusecore/Button";
+import CTA_FullWidth from "../../../../components/Call-To-Actions/CTA_FullWidth";
+import CTAImg from "../../../../assets/images/meshery/icon-only/meshery-logo-shadow.webp"
+
+
+
Containers provide a lightweight and portable solution to package applications, making them easy to deploy across different environments. With Docker as the most popular container engine and image format, but not the only runtime or format, the need for a standardized format to store and distribute container images became apparent and is why the Open Container Initiative (OCI) image format comes into play.
+
+The OCI was established as a community-driven initiative to create open standards for container formats and runtimes. Its goal is to promote interoperability and ensure that containers can be used across different platforms and runtime environments. One of the key components of the OCI initiative is the OCI image format, which has been widely adopted by container registries.
+
+
+Why have container registries have embraced the OCI format? How does Meshery, a popular internal developer platform, leverage this format for pushing and pulling design patterns? By understanding the benefits of OCI format for container registries and Meshery's support for it, we can gain valuable insights into the advantages of using this standardized format.
+
+
+## Why Container Registries Use OCI Format
+
+Container registries play a crucial role in the container ecosystem, serving as repositories for storing and distributing container images. These images are the building blocks of containerized applications, containing everything needed to run an application, from the code to the dependencies and configurations. In recent years, container registries have widely adopted the Open Container Initiative (OCI) format as the standard for packaging and distributing container images.
+
+### Benefits of OCI Format
+
+The adoption of OCI format by container registries offers several compelling benefits. Firstly, the OCI format provides a standardized and vendor-neutral way to package and distribute container images. This standardization ensures that images created using one container runtime can be run using a different runtime without any compatibility issues. This portability not only enhances interoperability but also encourages collaboration and innovation within the container ecosystem.
+
+Secondly, the OCI format promotes transparency and openness. It allows developers and users to inspect and understand the contents of a container image easily. By providing a clear structure for storing metadata and file system layers, the OCI format enables greater visibility into the image's composition, making it easier to identify potential security vulnerabilities or licensing issues.
+
+### Interoperability with Different Container Runtimes
+
+Another key reason why container registries prefer the OCI format is its compatibility with various container runtimes. Since container runtimes are responsible for executing the container images, it is crucial to have a format that can work seamlessly across different runtime environments. The OCI format achieves this by defining a set of specifications that are implemented by various container runtimes like Docker, containerd, and CRI-O. This compatibility ensures that container images stored in OCI format can be executed on different runtimes, giving developers the flexibility to choose the runtime that best suits their needs.
+
+### Security and Trustworthiness
+
+Security is a top concern for container registries, and the OCI format offers robust security features. By adhering to the OCI format, container registries can leverage the security mechanisms provided by OCI specifications. These mechanisms include content-addressable storage, which ensures that the integrity of the image is maintained throughout its lifecycle, and digital signatures, which enable image verification and establish trust between the registry and the consumers. The use of the OCI format adds an additional layer of trustworthiness to container images, assuring users that the images have not been tampered with and come from a trusted source.
+
+## How Meshery Design Patterns Utilize OCI Format
+
+### Introduction to Meshery
+
+Meshery, an open-source service mesh management plane, has rapidly gained popularity among developers and operators for its ability to simplify and streamline the deployment, management, and observability of service meshes. One of the key features that sets Meshery apart is its utilization of the Open Container Initiative (OCI) format for pushing and pulling design patterns.
+
+### Advantages of Pushing and Pulling Design Patterns in OCI Format
+
+Using the OCI format for design patterns offers several advantages for Meshery users. Firstly, it ensures that design patterns can be easily shared and reused across different container runtimes, regardless of the specific implementation details. This interoperability simplifies the process of deploying applications on various platforms, eliminating the need for time-consuming modifications and customizations.
+
+Secondly, the OCI format enhances security and trustworthiness by providing a standardized and verifiable way to package and distribute design patterns. By utilizing cryptographic signing, developers can ensure the integrity and authenticity of the design patterns they push and pull from container registries. This prevents tampering and reduces the risk of running malicious or compromised design patterns, enhancing the overall security posture of applications deployed using Meshery.
+
+Another advantage of the OCI format is its ability to encapsulate not only the application code but also the underlying dependencies and runtime environment. This self-contained nature simplifies the process of distributing and maintaining design patterns, as all the necessary components are bundled together. It also allows for more consistent and reproducible deployments, ensuring that the design pattern behaves consistently regardless of the environment in which it is deployed.
+<>
+
+
+## Meshery's Support for OCI Format
+
+Meshery fully embraces the use of OCI format for pushing and pulling design patterns. It provides a seamless integration with container registries that support OCI, enabling users to easily discover, share, and deploy design patterns. Meshery's user-friendly interface allows developers and operators to browse the available design patterns, inspect their metadata, and quickly deploy them to their service mesh environments.
+
+Furthermore, Meshery's support for OCI format extends beyond just deploying design patterns. It also provides tools and capabilities to manage the lifecycle of these patterns, including versioning, updating, and deprecating. This ensures that users can easily keep track of the design patterns they utilize and stay up to date with the latest releases and improvements.
+
+## Conclusion
+
+In conclusion, the adoption of OCI format by container registries and its integration within Meshery's design pattern management brings numerous benefits to the world of collaborative application infrastructure management. The use of OCI format ensures compatibility across different container runtimes, enhances security and trustworthiness, and simplifies the distribution and management of design patterns. With Meshery's support for OCI format, developers and operators can leverage these advantages to streamline and optimize their service mesh environments, ultimately improving the efficiency and reliability of their applications.
+
+
+
+ahead of the curve and leverage the latest advancements. Learn about Meshery's extensibility.
+
+
+
+
+
\ No newline at end of file
diff --git a/src/collections/blog/2024/02-24-open-container-image-meshery/oci-images-meshery.png b/src/collections/blog/2024/02-24-open-container-image-meshery/oci-images-meshery.png
new file mode 100644
index 000000000000..0ab25d957d58
Binary files /dev/null and b/src/collections/blog/2024/02-24-open-container-image-meshery/oci-images-meshery.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/booth.png b/src/collections/blog/2024/03-20-kubeconeu2024/booth.png
new file mode 100644
index 000000000000..02d0451e30a1
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/booth.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/catalog.png b/src/collections/blog/2024/03-20-kubeconeu2024/catalog.png
new file mode 100644
index 000000000000..a532d04e98d6
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/catalog.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/index.mdx b/src/collections/blog/2024/03-20-kubeconeu2024/index.mdx
new file mode 100644
index 000000000000..00cfacce86c4
--- /dev/null
+++ b/src/collections/blog/2024/03-20-kubeconeu2024/index.mdx
@@ -0,0 +1,128 @@
+---
+title: Layer5 at KubeCon EU 2024
+subtitle: Deep Dive into Cloud Native Networking with CNCF TAG Network & Service Mesh WG
+date: 2024-03-20
+author: Ritik Saxena
+
+thumbnail: ./kubeconeu2024.png
+darkthumbnail: ./kubeconeu2024.png
+description: "Layer5 projects on stage at KubeCon + CloudNativeCon EU 2024"
+type: Blog
+category: Meshery
+tags:
+ - KubeCon
+ - Meshery
+ - Service Mesh Performance
+ - Nighthawk
+featured: true
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import Button from "../../../../reusecore/Button";
+import MeshMarkFormula from "./meshmark-formula.png";
+import MeshMark from "./meshmark.png";
+import Catalog from "./catalog.png";
+import NighthawkSlide from "./nighthawk-slide.png";
+import SMPSpec from "./smp-spec.png";
+import Booth from "./booth.png";
+
+
+Happy KubeCon week! We hope you are as excited as we are about all the fantastic things we will learn.
+
+Zack and Nic are here in Paris representing TAG Network; today at 2:30. They have a lightning talk, and every afternoon, the TAG Network booth will be open for business!
+
+
+We're excited to connect with you in person at KubeCon EU! You can find us at kiosk **PP19-A**, located in the **Solutions Showcase | Level 7.2 | Hall 7.2 | Project Pavilion**.
+
+At the booth, we'll be showcasing demos of our two newest projects:
+
+* **Applying for Sandbox Status:** Learn how to easily apply for Sandbox status for your innovative cloud-native networking project.
+* **ConnectRPC:** Discover a revolutionary new approach to service mesh interoperability with ConnectRPC.
+* **KubeSlice:** Dive into the world of network slicing with KubeSlice, designed for optimal network resource utilization.
+
+
+
Don't forget to catch our lightning talk today at 2:30!
+
+
+
+
+
+Whether you're interested in these projects, have questions about the TAG Network, or simply want to chat about cloud-native networking, we'd love to see you! Drop by our booth for a coffee and a conversation – we look forward to meeting you!
+
+
+## Building a Strong Foundation: The TAG Network Mission
+
+The TAG Network, led by Lee Calcote (Layer5), Nic Jackson (HashiCorp), Zack Butcher (Tetrate), and technical lead Zhonghu Xu (Huawei), is dedicated to empowering the cloud native community. Their mission is fourfold:
+
+* **Clarity and Education:** Providing developers and operators with the knowledge and guidance they need to navigate cloud native networking.
+* **Collaboration and Integration:** Fostering collaboration between network projects and other CNCF initiatives for a unified ecosystem.
+* **Project Growth and Adoption:** Supporting the development and widespread adoption of promising network projects within the CNCF landscape.
+* **Neutral Stewardship:** Ensuring a fair and open environment for innovation in cloud native networking.
+
+## A Look Back: Tracking Progress Through KubeCon Events
+
+The TAG Network and Service Mesh WG have a strong presence at KubeCon events, showcasing the evolution of cloud native networking:
+
+* **KubeCon NA 2019:** This marked the introduction of foundational projects like CNI (Container Network Interface), CoreDNS, Envoy, and Linkerd, laying the groundwork for future advancements.
+* **KubeCon Throughout 2020 & 2021:** The focus shifted towards service mesh adoption, with projects like BFE, Istio, SMI (Service Mesh Interface), and Meshery taking center stage, empowering developers to manage complex microservices architectures.
+* **Recent KubeCon Events:** The latest gatherings highlighted cutting-edge projects like GetNighthawk (performance analysis), KubeSlice (network slicing), and Connect (service mesh interoperability), demonstrating the continuous push for innovation.
+
+## Unveiling Service Mesh Patterns: Reusability Meets Best Practices
+
+The Service Mesh WG champions the concept of service mesh patterns, a collection of reusable architectural building blocks designed for:
+
+* **End-User Focus:** Explained in clear language, these patterns are independent of specific service meshes, making them easy to understand and implement.
+* **Flexibility:** While core functionality remains consistent, users can leverage features specific to their chosen service mesh for even greater control.
+* **Reusability:** Patterns are designed to be easily copied, modified, and combined to create complex solutions tailored to your specific needs.
+* **Best Practices Integration:** Each pattern incorporates recommended practices for optimal network design, ensuring a solid foundation for your cloud native applications.
+
+Explore the extensive service mesh pattern library at [https://meshery.io/catalog](https://meshery.io/catalog) to discover a treasure trove of reusable solutions for your cloud native network.
+
+
+
+
+## Nighthawk Takes Flight: Distributed Performance Analysis
+
+The Service Mesh Performance initiative tackles the challenge of accurately measuring service mesh performance under load. Enter Nighthawk, a distributed performance analysis tool that empowers you to:
+
+* Generate realistic load scenarios that mimic real-world traffic patterns for a more accurate picture of your network's behavior.
+* Gain valuable insights into system behavior under pressure, allowing you to make informed decisions about configuration and optimization.
+* Compare performance across different service mesh deployments and configurations to identify the best fit for your specific needs.
+
+
+
+
+## Standardization Efforts: MeshMark and the SMP Spec
+
+The CNCF TAG Network actively promotes standardization within the cloud native networking space. Two key initiatives are:
+
+ #### **MeshMark:**
+
MeshMark serves as a performance index gauging the significance and overhead within your cloud native ecosystem. By transforming performance metrics into actionable insights regarding the significance of individual networking functions within cloud native applications, MeshMark consolidates diverse overhead signals and crucial performance metrics into a straightforward index.
This initiative establishes a vendor-neutral standard for measuring and reporting service mesh performance. This standardization paves the way for consistent performance comparisons and facilitates informed service mesh selection.
+
+
+
+
+
+## Join the Movement: Get Involved!
+
+The CNCF TAG Network and Service Mesh WG are open communities that thrive on collaboration. Here's how you can contribute:
+
+* Attend their bi-weekly meetings on the 1st and 3rd Thursdays of each month at 11 AM Pacific Time.
+* Stay informed by reading meeting minutes on the CNCF website.
+* Connect with the community on the #tag-network Slack channel and share your experiences and ideas.
+* Subscribe to the cncf-sig-network-servicemesh-wg mailing list for updates and announcements.
+
+By actively participating in these initiatives, you can play a vital role in shaping the future of resilient and intelligent cloud native networks
+
+
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/kubeconeu2024.png b/src/collections/blog/2024/03-20-kubeconeu2024/kubeconeu2024.png
new file mode 100644
index 000000000000..1f3e51110b5c
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/kubeconeu2024.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/meshmark-formula.png b/src/collections/blog/2024/03-20-kubeconeu2024/meshmark-formula.png
new file mode 100644
index 000000000000..a0748d96d1fd
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/meshmark-formula.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/meshmark.png b/src/collections/blog/2024/03-20-kubeconeu2024/meshmark.png
new file mode 100644
index 000000000000..649f71d17533
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/meshmark.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/nighthawk-slide.png b/src/collections/blog/2024/03-20-kubeconeu2024/nighthawk-slide.png
new file mode 100644
index 000000000000..da9be9b0a2e2
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/nighthawk-slide.png differ
diff --git a/src/collections/blog/2024/03-20-kubeconeu2024/smp-spec.png b/src/collections/blog/2024/03-20-kubeconeu2024/smp-spec.png
new file mode 100644
index 000000000000..53f78d9355f6
Binary files /dev/null and b/src/collections/blog/2024/03-20-kubeconeu2024/smp-spec.png differ
diff --git a/src/collections/blog/2024/03-27-models-designs-legos/five-instructions.png b/src/collections/blog/2024/03-27-models-designs-legos/five-instructions.png
new file mode 100644
index 000000000000..b61b1238564f
Binary files /dev/null and b/src/collections/blog/2024/03-27-models-designs-legos/five-instructions.png differ
diff --git a/src/collections/blog/2024/03-27-models-designs-legos/five-legos.png b/src/collections/blog/2024/03-27-models-designs-legos/five-legos.png
new file mode 100644
index 000000000000..9f7e85b6400c
Binary files /dev/null and b/src/collections/blog/2024/03-27-models-designs-legos/five-legos.png differ
diff --git a/src/collections/blog/2024/03-27-models-designs-legos/index.mdx b/src/collections/blog/2024/03-27-models-designs-legos/index.mdx
new file mode 100644
index 000000000000..8e64ca00333b
--- /dev/null
+++ b/src/collections/blog/2024/03-27-models-designs-legos/index.mdx
@@ -0,0 +1,68 @@
+---
+title: Lego Bricks and Lego Instructions
+subtitle: Comparing Meshery Models and Meshery Designs
+date: 2024-03-27
+author: Lee Calcote
+thumbnail: ./five-legos.png
+darkthumbnail: ./five-legos.png
+description: "Understanding the difference between Meshery Models and Meshery Designs"
+type: Blog
+category: Meshery
+tags:
+ - Meshery
+featured: true
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import Button from "../../../../reusecore/Button";
+import FiveInstructions from "./five-instructions.png";
+import FiveLegos from "./five-legos.png";
+
+
+
+
+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.
+
+
+### Meshery Models
+
+Meshery Models represent the fundamental building blocks of your infrastructure. Think of them as blueprints or templates that define the structure, components, and configurations of your deployments. These models encapsulate everything from network configurations to service definitions, making them essential for consistent and scalable deployments across environments.
+
+### Meshery Designs
+
+On the other hand, Meshery Designs are the practical implementations based on Meshery Models. They represent declarations of your infrastructure deployments, customized according to specific use cases, environments, and requirements. Meshery Designs allow you to create, manage, and deploy complex architectures seamlessly, leveraging the power and flexibility of Meshery Models as their foundation.
+
+
+
Meshery Models (similar to Lego bricks)
+
+
Meshery Models are packages that contain infrastructure components with specific properties and functionalities. (e.g., standard bricks, window pieces, wheels). Models and their Components cannot be directly used to build something complete on their own, but are standardized and reused across different Lego sets (instructions).
+
+
+
Definition: Building blocks for infrastructure definition.
+
Focus: Describe how to manage specific infrastructure types and their interactions.
+
Content: Define properties, capabilities, and relationships for infrastructure components.
+
Usability: Not directly deployable, but used as building blocks within Designs.
+
Sharing: Can be packaged and shared for others to use in their Designs.
+
+{/* */}
+
Meshery Models are like the individual Lego bricks - they define the building blocks for infrastructure with specific characteristics.
+
+
Meshery Designs (similar to Lego instructions)
+
+
Meshery Designs provide a collaborative blueprint for building a specific model using Lego bricks (Meshery Models). Designs define the structure and placement of the bricks to achieve the desired outcome. Desan be shared, versioned, and used as reference for building the same model.
+In essence:
+
+
Definition: Collaborative documents for infrastructure and application deployment.
+
Focus: Describe the desired state of infrastructure for a specific deployment.
+
Content: Use components (based on Models) and relationships to define your infrastructure.
+
Usability: Designs are the deployable unit in Meshery.
+
Sharing: Can be exported, versioned, shared, and published for reuse by others.
+
+{/* */}
+
Meshery Designs are like the Lego instructions - they use Models (like bricks) to lay out the specific infrastructure deployment plan.
+
+
Analogy: Think of Models as Lego bricks (defining types of pieces) and Designs as Lego instructions (defining how to build something specific).
In summary, Meshery Models serve as the theoretical frameworks, while Meshery Designs translate these frameworks into tangible deployments, enabling you to design, deploy, and manage your infrastructure efficiently within the cloud and cloud native ecosystem.
+
+
diff --git a/src/collections/blog/blog-template/index.mdx b/src/collections/blog/blog-template/index.mdx
index 6b24ccb39268..08b93523f229 100644
--- a/src/collections/blog/blog-template/index.mdx
+++ b/src/collections/blog/blog-template/index.mdx
@@ -2,42 +2,46 @@
title: "Lorem Ipsum"
subtitle: "Lorem Ipsum"
date: 2020-06-23 10:30:05 -0530
-author: John Doe
-thumbnail: ./gsoc-wide.webp
-darkthumbnail: ./gsoc-wide.webp
+author: Layer5 Team
+thumbnail: ../../../assets/images/layer5/layer5-only/svg/layer5-black.svg
+darkthumbnail: ../../../assets/images/layer5/layer5-only/svg/layer5-light-bg.svg
category: "Lorem Ipsum"
description: "This is a short summary of my blog post. This text will show in the blog's list view and in community newsletters."
tags:
- Community
- Meshery
type: Blog
-resource: false
+resource: true
published: false
---
import { BlogWrapper } from "../Blog.style.js";
import Blockquote from "../../../reusecore/Blockquote";
-
-import gsoc from "./gsoc.webp";
+import image from "../../../assets/images/layer5/layer5-only/svg/layer5-light-no-trim.svg";
-### Lorem Ipsum
+## Lorem Ipsum
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean vehicula consequat ipsum, at egestas leo. Donec molestie ipsum ut neque lobortis convallis.
-
+
This is text for the image
+Curabitur iaculis ante sit amet condimentum interdum. Cras tellus nunc, gravida sit amet pellentesque eu, placerat ac diam. Mauris fermentum condimentum odio, ac fringilla ante condimentum vel. Vivamus volutpat sit amet libero eleifend ultricies. Praesent tempor libero tincidunt aliquam convallis. Aliquam in magna ante. Morbi egestas efficitur massa sed pretium.
+
+### Lorem Ipsum
Curabitur iaculis ante sit amet condimentum interdum. Cras tellus nunc, gravida sit amet pellentesque eu, placerat ac diam. Mauris fermentum condimentum odio, ac fringilla ante condimentum vel. Vivamus volutpat sit amet libero eleifend ultricies. Praesent tempor libero tincidunt aliquam convallis. Aliquam in magna ante. Morbi egestas efficitur massa sed pretium.
-
+
+
+Curabitur iaculis ante sit amet condimentum interdum. Cras tellus nunc, gravida sit amet pellentesque eu, placerat ac diam. Mauris fermentum condimentum odio, ac fringilla ante condimentum vel. Vivamus volutpat sit amet libero eleifend ultricies. Praesent tempor libero tincidunt aliquam convallis. Aliquam in magna ante. Morbi egestas efficitur massa sed pretium.
\-- John Jane Doe
diff --git a/src/collections/events/kubecon-EU-2024/index.mdx b/src/collections/events/kubecon-EU-2024/index.mdx
new file mode 100644
index 000000000000..ecf35f9685c9
--- /dev/null
+++ b/src/collections/events/kubecon-EU-2024/index.mdx
@@ -0,0 +1,24 @@
+---
+title: "KubeCon + CloudNativeCon EU Paris, France 2024"
+description: "CNCF Tag Network and Service mesh Working Group Deep Dive"
+date: 2024-03-19
+thumbnail: ./kubeconEU2024.png
+darkthumbnail: ./kubeconEU2024.png
+eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
+type: Event
+published: true
+upcoming: true
+feature: true
+speakers: ["Lee Calcote", "Nic Jackson", "Zack Butcher", "Zhonghu Xu"]
+
+---
+import Button from "../../../reusecore/Button";
+
+Join Layer5 at KubeCon + CloudNativeCon EU Paris, France 2024!
+
+
+
+Join the Meshery project at KubeCon Europe 2024 from 19th March to 22nd March, 2024 and get introduced to the cloud native management plane and its open source maintainers.
+
+
+
diff --git a/src/collections/events/kubecon-EU-2024/kubeconEU2024.png b/src/collections/events/kubecon-EU-2024/kubeconEU2024.png
new file mode 100644
index 000000000000..2ace7373c6f6
Binary files /dev/null and b/src/collections/events/kubecon-EU-2024/kubeconEU2024.png differ
diff --git a/src/collections/events/making-the-cncf-landscape-interactive-with-meshery/index.mdx b/src/collections/events/making-the-cncf-landscape-interactive-with-meshery/index.mdx
new file mode 100644
index 000000000000..0824d3463938
--- /dev/null
+++ b/src/collections/events/making-the-cncf-landscape-interactive-with-meshery/index.mdx
@@ -0,0 +1,26 @@
+---
+title: "Making the CNCF Landscape Interactive with Meshery"
+description: "Join the Kubesimplify livestream for an engaging livestream where we dive into the dynamic world of the Cloud Native Computing Foundation (CNCF) Landscape and explore how Meshery, the collaborative cloud native manager, is revolutionizing it. In this session, we’ll demonstrate how Meshery not only simplifies the management of all Kubernetes-based infrastructure, but also makes the CNCF Landscape interactive, allowing for a more intuitive and hands-on experience."
+date: 2024-05-01
+thumbnail: ./thumbnail.png
+darkthumbnail: ./thumbnail.png
+type: Event
+eurl: "https://www.youtube.com/@Layer5io"
+published: false
+upcoming: true
+resource: false
+speakers: ["Lee Calcote", "Saiyam Pathak"]
+---
+
+Join the Kubesimplify livestream for an engaging livestream where we dive into the dynamic world of the Cloud Native Computing Foundation (CNCF) Landscape and explore how Meshery, the collaborative cloud native manager, is revolutionizing it. In this session, we’ll demonstrate how Meshery not only simplifies the management of all Kubernetes-based infrastructure, but also makes the CNCF Landscape interactive, allowing for a more intuitive and hands-on experience.
+
+Whether you’re a developer, an operator, or simply a cloud-native enthusiast, you’ll discover how Meshery’s powerful visualization and collaboration features can help you navigate the CNCF Landscape with ease. Get ready to learn about:
+- Meshery’s role in the CNCF ecosystem
+- Interactive features that enhance your understanding of EVERY CNCF project
+- Real-time demonstrations of Meshery in action
+- Tips and tricks for leveraging Meshery to its full potential
+
+
+Don’t miss out on this opportunity to enhance your cloud-native journey with Meshery. Subscribe and set a reminder for our livestream to stay at the forefront of cloud-native technologies!
+
+
diff --git a/src/collections/events/making-the-cncf-landscape-interactive-with-meshery/thumbnail.png b/src/collections/events/making-the-cncf-landscape-interactive-with-meshery/thumbnail.png
new file mode 100644
index 000000000000..8e31c5b7b200
Binary files /dev/null and b/src/collections/events/making-the-cncf-landscape-interactive-with-meshery/thumbnail.png differ
diff --git a/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Design-dark.png b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Design-dark.png
new file mode 100644
index 000000000000..77789bbc5cc3
Binary files /dev/null and b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Design-dark.png differ
diff --git a/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Design-light.png b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Design-light.png
new file mode 100644
index 000000000000..01c32d9aa75e
Binary files /dev/null and b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Design-light.png differ
diff --git a/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Visualize-dark.png b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Visualize-dark.png
new file mode 100644
index 000000000000..ae7a9aa2aefc
Binary files /dev/null and b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Visualize-dark.png differ
diff --git a/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Visualize-light.png b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Visualize-light.png
new file mode 100644
index 000000000000..bfdbce56d487
Binary files /dev/null and b/src/collections/integrations/_images/aperture-agent/Aperture-Agent-Visualize-light.png differ
diff --git a/src/collections/integrations/_images/confidential-containers/confidential-containers-design-dark.png b/src/collections/integrations/_images/confidential-containers/confidential-containers-design-dark.png
new file mode 100644
index 000000000000..38bb33fc8be4
Binary files /dev/null and b/src/collections/integrations/_images/confidential-containers/confidential-containers-design-dark.png differ
diff --git a/src/collections/integrations/_images/confidential-containers/confidential-containers-design-light.png b/src/collections/integrations/_images/confidential-containers/confidential-containers-design-light.png
new file mode 100644
index 000000000000..0e5d867e2877
Binary files /dev/null and b/src/collections/integrations/_images/confidential-containers/confidential-containers-design-light.png differ
diff --git a/src/collections/integrations/_images/confidential-containers/confidential-containers-visualization-dark.png b/src/collections/integrations/_images/confidential-containers/confidential-containers-visualization-dark.png
new file mode 100644
index 000000000000..05d7691dac51
Binary files /dev/null and b/src/collections/integrations/_images/confidential-containers/confidential-containers-visualization-dark.png differ
diff --git a/src/collections/integrations/_images/confidential-containers/confidential-containers-visualization-design.png b/src/collections/integrations/_images/confidential-containers/confidential-containers-visualization-design.png
new file mode 100644
index 000000000000..c889df76ec3b
Binary files /dev/null and b/src/collections/integrations/_images/confidential-containers/confidential-containers-visualization-design.png differ
diff --git a/src/collections/integrations/_images/containerd/meshmap-containerd-dark.png b/src/collections/integrations/_images/containerd/meshmap-containerd-dark.png
new file mode 100644
index 000000000000..fe7c4116846f
Binary files /dev/null and b/src/collections/integrations/_images/containerd/meshmap-containerd-dark.png differ
diff --git a/src/collections/integrations/_images/containerd/meshmap-containerd-light.png b/src/collections/integrations/_images/containerd/meshmap-containerd-light.png
new file mode 100644
index 000000000000..035dcb61e83d
Binary files /dev/null and b/src/collections/integrations/_images/containerd/meshmap-containerd-light.png differ
diff --git a/src/collections/integrations/_images/containerd/meshmap-containerd-views-dark.png b/src/collections/integrations/_images/containerd/meshmap-containerd-views-dark.png
new file mode 100644
index 000000000000..2e07194141b0
Binary files /dev/null and b/src/collections/integrations/_images/containerd/meshmap-containerd-views-dark.png differ
diff --git a/src/collections/integrations/_images/containerd/meshmap-containerd-views-light.png b/src/collections/integrations/_images/containerd/meshmap-containerd-views-light.png
new file mode 100644
index 000000000000..6fc163171627
Binary files /dev/null and b/src/collections/integrations/_images/containerd/meshmap-containerd-views-light.png differ
diff --git a/src/collections/integrations/_images/contour/Contour-Design-dark.png b/src/collections/integrations/_images/contour/Contour-Design-dark.png
new file mode 100644
index 000000000000..55f435e218f1
Binary files /dev/null and b/src/collections/integrations/_images/contour/Contour-Design-dark.png differ
diff --git a/src/collections/integrations/_images/contour/Contour-Design-light.png b/src/collections/integrations/_images/contour/Contour-Design-light.png
new file mode 100644
index 000000000000..15007bb91160
Binary files /dev/null and b/src/collections/integrations/_images/contour/Contour-Design-light.png differ
diff --git a/src/collections/integrations/_images/contour/Contour-Visualize-dark.png b/src/collections/integrations/_images/contour/Contour-Visualize-dark.png
new file mode 100644
index 000000000000..f7e1ba0b5b05
Binary files /dev/null and b/src/collections/integrations/_images/contour/Contour-Visualize-dark.png differ
diff --git a/src/collections/integrations/_images/contour/Contour-Visualize-light.png b/src/collections/integrations/_images/contour/Contour-Visualize-light.png
new file mode 100644
index 000000000000..68a5e38c8351
Binary files /dev/null and b/src/collections/integrations/_images/contour/Contour-Visualize-light.png differ
diff --git a/src/collections/integrations/_images/coredns/Coredns-Design-dark.png b/src/collections/integrations/_images/coredns/Coredns-Design-dark.png
new file mode 100644
index 000000000000..db3f11729937
Binary files /dev/null and b/src/collections/integrations/_images/coredns/Coredns-Design-dark.png differ
diff --git a/src/collections/integrations/_images/coredns/Coredns-Design-light.png b/src/collections/integrations/_images/coredns/Coredns-Design-light.png
new file mode 100644
index 000000000000..fc9507ff56d9
Binary files /dev/null and b/src/collections/integrations/_images/coredns/Coredns-Design-light.png differ
diff --git a/src/collections/integrations/_images/coredns/Coredns-Visualize-dark.png b/src/collections/integrations/_images/coredns/Coredns-Visualize-dark.png
new file mode 100644
index 000000000000..266528268526
Binary files /dev/null and b/src/collections/integrations/_images/coredns/Coredns-Visualize-dark.png differ
diff --git a/src/collections/integrations/_images/coredns/Coredns-Visualize-light.png b/src/collections/integrations/_images/coredns/Coredns-Visualize-light.png
new file mode 100644
index 000000000000..51cd4c1f6d7f
Binary files /dev/null and b/src/collections/integrations/_images/coredns/Coredns-Visualize-light.png differ
diff --git a/src/collections/integrations/_images/dex/designDark.png b/src/collections/integrations/_images/dex/designDark.png
new file mode 100644
index 000000000000..be11a2379ecd
Binary files /dev/null and b/src/collections/integrations/_images/dex/designDark.png differ
diff --git a/src/collections/integrations/_images/dex/designLight.png b/src/collections/integrations/_images/dex/designLight.png
new file mode 100644
index 000000000000..05e430013f05
Binary files /dev/null and b/src/collections/integrations/_images/dex/designLight.png differ
diff --git a/src/collections/integrations/_images/dex/visualizeDark.png b/src/collections/integrations/_images/dex/visualizeDark.png
new file mode 100644
index 000000000000..567129f324c2
Binary files /dev/null and b/src/collections/integrations/_images/dex/visualizeDark.png differ
diff --git a/src/collections/integrations/_images/dex/visualizeLight.png b/src/collections/integrations/_images/dex/visualizeLight.png
new file mode 100644
index 000000000000..fc91da5023c2
Binary files /dev/null and b/src/collections/integrations/_images/dex/visualizeLight.png differ
diff --git a/src/collections/integrations/_images/docker/docker_integration_dark.png b/src/collections/integrations/_images/docker/docker_integration_dark.png
new file mode 100644
index 000000000000..6e103e04b4c0
Binary files /dev/null and b/src/collections/integrations/_images/docker/docker_integration_dark.png differ
diff --git a/src/collections/integrations/_images/docker/docker_integration_light.png b/src/collections/integrations/_images/docker/docker_integration_light.png
new file mode 100644
index 000000000000..d8df8c78b53d
Binary files /dev/null and b/src/collections/integrations/_images/docker/docker_integration_light.png differ
diff --git a/src/collections/integrations/_images/docker/docker_integration_visualize_dark.png b/src/collections/integrations/_images/docker/docker_integration_visualize_dark.png
new file mode 100644
index 000000000000..9002fdc5f332
Binary files /dev/null and b/src/collections/integrations/_images/docker/docker_integration_visualize_dark.png differ
diff --git a/src/collections/integrations/_images/docker/docker_integration_visualize_light.png b/src/collections/integrations/_images/docker/docker_integration_visualize_light.png
new file mode 100644
index 000000000000..eafa21edacb4
Binary files /dev/null and b/src/collections/integrations/_images/docker/docker_integration_visualize_light.png differ
diff --git a/src/collections/integrations/_images/elastic-search/MeshDark.png b/src/collections/integrations/_images/elastic-search/MeshDark.png
new file mode 100644
index 000000000000..5cd4b981732c
Binary files /dev/null and b/src/collections/integrations/_images/elastic-search/MeshDark.png differ
diff --git a/src/collections/integrations/_images/elastic-search/MeshLight.png b/src/collections/integrations/_images/elastic-search/MeshLight.png
new file mode 100644
index 000000000000..2abe107bf02c
Binary files /dev/null and b/src/collections/integrations/_images/elastic-search/MeshLight.png differ
diff --git a/src/collections/integrations/_images/elastic-search/VisDark.png b/src/collections/integrations/_images/elastic-search/VisDark.png
new file mode 100644
index 000000000000..f77fe35c2da8
Binary files /dev/null and b/src/collections/integrations/_images/elastic-search/VisDark.png differ
diff --git a/src/collections/integrations/_images/elastic-search/VisLight.png b/src/collections/integrations/_images/elastic-search/VisLight.png
new file mode 100644
index 000000000000..4b07bf5e2768
Binary files /dev/null and b/src/collections/integrations/_images/elastic-search/VisLight.png differ
diff --git a/src/collections/integrations/_images/emissary/Emissary-Design-dark.png b/src/collections/integrations/_images/emissary/Emissary-Design-dark.png
new file mode 100644
index 000000000000..f75c8a3eae4c
Binary files /dev/null and b/src/collections/integrations/_images/emissary/Emissary-Design-dark.png differ
diff --git a/src/collections/integrations/_images/emissary/Emissary-Design-light.png b/src/collections/integrations/_images/emissary/Emissary-Design-light.png
new file mode 100644
index 000000000000..db44ba947133
Binary files /dev/null and b/src/collections/integrations/_images/emissary/Emissary-Design-light.png differ
diff --git a/src/collections/integrations/_images/emissary/Emissary-Visualize-dark.png b/src/collections/integrations/_images/emissary/Emissary-Visualize-dark.png
new file mode 100644
index 000000000000..d0999f833565
Binary files /dev/null and b/src/collections/integrations/_images/emissary/Emissary-Visualize-dark.png differ
diff --git a/src/collections/integrations/_images/emissary/Emissary-Visualize-light.png b/src/collections/integrations/_images/emissary/Emissary-Visualize-light.png
new file mode 100644
index 000000000000..eadde2f18193
Binary files /dev/null and b/src/collections/integrations/_images/emissary/Emissary-Visualize-light.png differ
diff --git a/src/collections/integrations/_images/external-secrets-operator/designDark.png b/src/collections/integrations/_images/external-secrets-operator/designDark.png
new file mode 100644
index 000000000000..c878c2e78431
Binary files /dev/null and b/src/collections/integrations/_images/external-secrets-operator/designDark.png differ
diff --git a/src/collections/integrations/_images/external-secrets-operator/designLight.png b/src/collections/integrations/_images/external-secrets-operator/designLight.png
new file mode 100644
index 000000000000..091b50693b49
Binary files /dev/null and b/src/collections/integrations/_images/external-secrets-operator/designLight.png differ
diff --git a/src/collections/integrations/_images/external-secrets-operator/visualizeDark.png b/src/collections/integrations/_images/external-secrets-operator/visualizeDark.png
new file mode 100644
index 000000000000..e2ff901e0641
Binary files /dev/null and b/src/collections/integrations/_images/external-secrets-operator/visualizeDark.png differ
diff --git a/src/collections/integrations/_images/external-secrets-operator/visualizeLight.png b/src/collections/integrations/_images/external-secrets-operator/visualizeLight.png
new file mode 100644
index 000000000000..82ebb068d74c
Binary files /dev/null and b/src/collections/integrations/_images/external-secrets-operator/visualizeLight.png differ
diff --git a/src/collections/integrations/_images/falco/Falco-Design-dark.png b/src/collections/integrations/_images/falco/Falco-Design-dark.png
new file mode 100644
index 000000000000..4ad53328c735
Binary files /dev/null and b/src/collections/integrations/_images/falco/Falco-Design-dark.png differ
diff --git a/src/collections/integrations/_images/falco/Falco-Design-light.png b/src/collections/integrations/_images/falco/Falco-Design-light.png
new file mode 100644
index 000000000000..462689c13259
Binary files /dev/null and b/src/collections/integrations/_images/falco/Falco-Design-light.png differ
diff --git a/src/collections/integrations/_images/falco/Falco-Visualize-dark.png b/src/collections/integrations/_images/falco/Falco-Visualize-dark.png
new file mode 100644
index 000000000000..8a80af45aa5a
Binary files /dev/null and b/src/collections/integrations/_images/falco/Falco-Visualize-dark.png differ
diff --git a/src/collections/integrations/_images/falco/Falco-Visualize-light.png b/src/collections/integrations/_images/falco/Falco-Visualize-light.png
new file mode 100644
index 000000000000..d98bca3a4426
Binary files /dev/null and b/src/collections/integrations/_images/falco/Falco-Visualize-light.png differ
diff --git a/src/collections/integrations/_images/fluent-operator/fluent-operator-Design-dark.png b/src/collections/integrations/_images/fluent-operator/fluent-operator-Design-dark.png
new file mode 100644
index 000000000000..5323e8caaf57
Binary files /dev/null and b/src/collections/integrations/_images/fluent-operator/fluent-operator-Design-dark.png differ
diff --git a/src/collections/integrations/_images/fluent-operator/fluent-operator-Design-light.png b/src/collections/integrations/_images/fluent-operator/fluent-operator-Design-light.png
new file mode 100644
index 000000000000..772af4094c02
Binary files /dev/null and b/src/collections/integrations/_images/fluent-operator/fluent-operator-Design-light.png differ
diff --git a/src/collections/integrations/_images/fluent-operator/fluent-operator-Visualize-dark.png b/src/collections/integrations/_images/fluent-operator/fluent-operator-Visualize-dark.png
new file mode 100644
index 000000000000..c421d63ecfa6
Binary files /dev/null and b/src/collections/integrations/_images/fluent-operator/fluent-operator-Visualize-dark.png differ
diff --git a/src/collections/integrations/_images/fluent-operator/fluent-operator-Visualize-light.png b/src/collections/integrations/_images/fluent-operator/fluent-operator-Visualize-light.png
new file mode 100644
index 000000000000..2bab6fdc2034
Binary files /dev/null and b/src/collections/integrations/_images/fluent-operator/fluent-operator-Visualize-light.png differ
diff --git a/src/collections/integrations/_images/flux/MeshFluxDark.png b/src/collections/integrations/_images/flux/MeshFluxDark.png
new file mode 100644
index 000000000000..defca0a23fa8
Binary files /dev/null and b/src/collections/integrations/_images/flux/MeshFluxDark.png differ
diff --git a/src/collections/integrations/_images/flux/MeshFluxLight.png b/src/collections/integrations/_images/flux/MeshFluxLight.png
new file mode 100644
index 000000000000..f0b532a257b4
Binary files /dev/null and b/src/collections/integrations/_images/flux/MeshFluxLight.png differ
diff --git a/src/collections/integrations/_images/flux/visFluxDark.png b/src/collections/integrations/_images/flux/visFluxDark.png
new file mode 100644
index 000000000000..260d58034354
Binary files /dev/null and b/src/collections/integrations/_images/flux/visFluxDark.png differ
diff --git a/src/collections/integrations/_images/flux/visFluxLight.png b/src/collections/integrations/_images/flux/visFluxLight.png
new file mode 100644
index 000000000000..ab1f738b7058
Binary files /dev/null and b/src/collections/integrations/_images/flux/visFluxLight.png differ
diff --git a/src/collections/integrations/_images/fonio/Fonio-Design-dark.png b/src/collections/integrations/_images/fonio/Fonio-Design-dark.png
new file mode 100644
index 000000000000..11d95fc34f9c
Binary files /dev/null and b/src/collections/integrations/_images/fonio/Fonio-Design-dark.png differ
diff --git a/src/collections/integrations/_images/fonio/Fonio-Design-light.png b/src/collections/integrations/_images/fonio/Fonio-Design-light.png
new file mode 100644
index 000000000000..efdd82e952f7
Binary files /dev/null and b/src/collections/integrations/_images/fonio/Fonio-Design-light.png differ
diff --git a/src/collections/integrations/_images/fonio/Fonio-visualize-dark.png b/src/collections/integrations/_images/fonio/Fonio-visualize-dark.png
new file mode 100644
index 000000000000..2d1e299236c4
Binary files /dev/null and b/src/collections/integrations/_images/fonio/Fonio-visualize-dark.png differ
diff --git a/src/collections/integrations/_images/fonio/Fonio-visualize-light.png b/src/collections/integrations/_images/fonio/Fonio-visualize-light.png
new file mode 100644
index 000000000000..f6caa7af2e20
Binary files /dev/null and b/src/collections/integrations/_images/fonio/Fonio-visualize-light.png differ
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-assigned-identity/icons/color/azure-assigned-identity-color.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-assigned-identity/icons/color/azure-assigned-identity-color.svg
new file mode 100644
index 000000000000..d450b6224913
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-assigned-identity/icons/color/azure-assigned-identity-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-assigned-identity/icons/white/azure-assigned-identity-white.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-assigned-identity/icons/white/azure-assigned-identity-white.svg
new file mode 100644
index 000000000000..adf3476d6664
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-assigned-identity/icons/white/azure-assigned-identity-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-identity-binding/icons/color/azure-identity-binding-color.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity-binding/icons/color/azure-identity-binding-color.svg
new file mode 100644
index 000000000000..d450b6224913
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity-binding/icons/color/azure-identity-binding-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-identity-binding/icons/white/azure-identity-binding-white.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity-binding/icons/white/azure-identity-binding-white.svg
new file mode 100644
index 000000000000..adf3476d6664
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity-binding/icons/white/azure-identity-binding-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-identity/icons/color/azure-identity-color.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity/icons/color/azure-identity-color.svg
new file mode 100644
index 000000000000..d450b6224913
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity/icons/color/azure-identity-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-identity/icons/white/azure-identity-white.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity/icons/white/azure-identity-white.svg
new file mode 100644
index 000000000000..adf3476d6664
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-identity/icons/white/azure-identity-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-pod-identity-exception/icons/color/azure-pod-identity-exception-color.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-pod-identity-exception/icons/color/azure-pod-identity-exception-color.svg
new file mode 100644
index 000000000000..d450b6224913
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-pod-identity-exception/icons/color/azure-pod-identity-exception-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/icons/components/azure-pod-identity-exception/icons/white/azure-pod-identity-exception-white.svg b/src/collections/integrations/aad-pod-identity/icons/components/azure-pod-identity-exception/icons/white/azure-pod-identity-exception-white.svg
new file mode 100644
index 000000000000..adf3476d6664
--- /dev/null
+++ b/src/collections/integrations/aad-pod-identity/icons/components/azure-pod-identity-exception/icons/white/azure-pod-identity-exception-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/aad-pod-identity/index.mdx b/src/collections/integrations/aad-pod-identity/index.mdx
index 10c730203c77..01006404d71c 100644
--- a/src/collections/integrations/aad-pod-identity/index.mdx
+++ b/src/collections/integrations/aad-pod-identity/index.mdx
@@ -7,8 +7,32 @@ docURL: https://docs.meshery.io/extensibility/integrations/aad-pod-identity
description:
category: Provisioning
subcategory: Security & Compliance
-registrant: artifacthub
-components: []
+registrant: Artifact Hub
+components: [
+{
+"name": "azure-assigned-identity",
+"colorIcon": "icons/components/azure-assigned-identity/icons/color/azure-assigned-identity-color.svg",
+"whiteIcon": "icons/components/azure-assigned-identity/icons/white/azure-assigned-identity-white.svg",
+"description": "",
+},
+{
+"name": "azure-identity",
+"colorIcon": "icons/components/azure-identity/icons/color/azure-identity-color.svg",
+"whiteIcon": "icons/components/azure-identity/icons/white/azure-identity-white.svg",
+"description": "",
+},
+{
+"name": "azure-identity-binding",
+"colorIcon": "icons/components/azure-identity-binding/icons/color/azure-identity-binding-color.svg",
+"whiteIcon": "icons/components/azure-identity-binding/icons/white/azure-identity-binding-white.svg",
+"description": "",
+},
+{
+"name": "azure-pod-identity-exception",
+"colorIcon": "icons/components/azure-pod-identity-exception/icons/color/azure-pod-identity-exception-color.svg",
+"whiteIcon": "icons/components/azure-pod-identity-exception/icons/white/azure-pod-identity-exception-white.svg",
+"description": "",
+}]
featureList: [
"Use Azure Active Directory pod-managed identities in Azure Kubernetes Service.",
"A maximum of 200 pod-managed identities are allowed for a cluster.",
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/horizontal-runner-autoscaler/icons/color/horizontal-runner-autoscaler-color.svg b/src/collections/integrations/actions-runner-controller/icons/components/horizontal-runner-autoscaler/icons/color/horizontal-runner-autoscaler-color.svg
new file mode 100644
index 000000000000..8435de5170ce
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/horizontal-runner-autoscaler/icons/color/horizontal-runner-autoscaler-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/horizontal-runner-autoscaler/icons/white/horizontal-runner-autoscaler-white.svg b/src/collections/integrations/actions-runner-controller/icons/components/horizontal-runner-autoscaler/icons/white/horizontal-runner-autoscaler-white.svg
new file mode 100644
index 000000000000..bd221db3b75a
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/horizontal-runner-autoscaler/icons/white/horizontal-runner-autoscaler-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner-deployment/icons/color/runner-deployment-color.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner-deployment/icons/color/runner-deployment-color.svg
new file mode 100644
index 000000000000..8435de5170ce
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner-deployment/icons/color/runner-deployment-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner-deployment/icons/white/runner-deployment-white.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner-deployment/icons/white/runner-deployment-white.svg
new file mode 100644
index 000000000000..bd221db3b75a
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner-deployment/icons/white/runner-deployment-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner-replica-set/icons/color/runner-replica-set-color.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner-replica-set/icons/color/runner-replica-set-color.svg
new file mode 100644
index 000000000000..8435de5170ce
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner-replica-set/icons/color/runner-replica-set-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner-replica-set/icons/white/runner-replica-set-white.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner-replica-set/icons/white/runner-replica-set-white.svg
new file mode 100644
index 000000000000..bd221db3b75a
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner-replica-set/icons/white/runner-replica-set-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner-set/icons/color/runner-set-color.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner-set/icons/color/runner-set-color.svg
new file mode 100644
index 000000000000..8435de5170ce
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner-set/icons/color/runner-set-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner-set/icons/white/runner-set-white.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner-set/icons/white/runner-set-white.svg
new file mode 100644
index 000000000000..bd221db3b75a
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner-set/icons/white/runner-set-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner/icons/color/runner-color.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner/icons/color/runner-color.svg
new file mode 100644
index 000000000000..8435de5170ce
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner/icons/color/runner-color.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/icons/components/runner/icons/white/runner-white.svg b/src/collections/integrations/actions-runner-controller/icons/components/runner/icons/white/runner-white.svg
new file mode 100644
index 000000000000..bd221db3b75a
--- /dev/null
+++ b/src/collections/integrations/actions-runner-controller/icons/components/runner/icons/white/runner-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/collections/integrations/actions-runner-controller/index.mdx b/src/collections/integrations/actions-runner-controller/index.mdx
index 23bef41ca32f..0c991cbd16bc 100644
--- a/src/collections/integrations/actions-runner-controller/index.mdx
+++ b/src/collections/integrations/actions-runner-controller/index.mdx
@@ -7,8 +7,38 @@ docURL: https://docs.meshery.io/extensibility/integrations/actions-runner-contro
description:
category: App Definition and Development
subcategory: Continuous Integration & Delivery
-registrant: artifacthub
-components: []
+registrant: Artifact Hub
+components: [
+{
+"name": "horizontal-runner-autoscaler",
+"colorIcon": "icons/components/horizontal-runner-autoscaler/icons/color/horizontal-runner-autoscaler-color.svg",
+"whiteIcon": "icons/components/horizontal-runner-autoscaler/icons/white/horizontal-runner-autoscaler-white.svg",
+"description": "",
+},
+{
+"name": "runner-deployment",
+"colorIcon": "icons/components/runner-deployment/icons/color/runner-deployment-color.svg",
+"whiteIcon": "icons/components/runner-deployment/icons/white/runner-deployment-white.svg",
+"description": "",
+},
+{
+"name": "runner-replica-set",
+"colorIcon": "icons/components/runner-replica-set/icons/color/runner-replica-set-color.svg",
+"whiteIcon": "icons/components/runner-replica-set/icons/white/runner-replica-set-white.svg",
+"description": "",
+},
+{
+"name": "runner",
+"colorIcon": "icons/components/runner/icons/color/runner-color.svg",
+"whiteIcon": "icons/components/runner/icons/white/runner-white.svg",
+"description": "",
+},
+{
+"name": "runner-set",
+"colorIcon": "icons/components/runner-set/icons/color/runner-set-color.svg",
+"whiteIcon": "icons/components/runner-set/icons/white/runner-set-white.svg",
+"description": "",
+}]
featureList: [
"Deploy self hosted runners on Kubernetes cluster with a simple set of commands.",
"Auto scale runners based on demand.",
diff --git a/src/collections/integrations/admin-console-operator/icons/components/admin-console/icons/white/admin-console-white.svg b/src/collections/integrations/admin-console-operator/icons/components/admin-console/icons/white/admin-console-white.svg
index 3784e2dc898f..5bf531a9674f 100644
--- a/src/collections/integrations/admin-console-operator/icons/components/admin-console/icons/white/admin-console-white.svg
+++ b/src/collections/integrations/admin-console-operator/icons/components/admin-console/icons/white/admin-console-white.svg
@@ -1,5 +1,5 @@
+