+
+The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the [`master` branch](https://github.com/layer5io/layer5/tree/master).
+
+- 📚 See [contributing instructions](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md).
+- 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
+- 🙋🏾🙋🏼 Questions: [Discussion Forum](https://discuss.layer5.io) and [Community Slack](https://slack.layer5.io).
+
+Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer).
diff --git a/.github/ISSUE_TEMPLATE/chore_task.md b/.github/ISSUE_TEMPLATE/chore_task.md
index aca67feb99b4..b12594d45209 100644
--- a/.github/ISSUE_TEMPLATE/chore_task.md
+++ b/.github/ISSUE_TEMPLATE/chore_task.md
@@ -1,22 +1,22 @@
----
-name: 🧹Chore or task
-about: Identify a necessary task to be addressed.
-title: ''
-labels: 'kind/chore'
-assignees: ''
----
-### Current Behavior
-
-
-### Desired Situation
-
-
----
-
-
-The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the [`master` branch](https://github.com/layer5io/layer5/tree/master).
-- 📚 See [contributing instructions](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md).
-- 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
-- 🙋🏾🙋🏼 Questions: [Discussion Forum](https://discuss.layer5.io) and [Community Slack](https://slack.layer5.io).
-
-Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer).
+---
+name: 🧹Chore or task
+about: Identify a necessary task to be addressed.
+title: ''
+labels: 'kind/chore'
+assignees: ''
+---
+### Current Behavior
+
+
+### Desired Situation
+
+
+---
+
+
+The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the [`master` branch](https://github.com/layer5io/layer5/tree/master).
+- 📚 See [contributing instructions](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md).
+- 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
+- 🙋🏾🙋🏼 Questions: [Discussion Forum](https://discuss.layer5.io) and [Community Slack](https://slack.layer5.io).
+
+Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer).
diff --git a/.github/ISSUE_TEMPLATE/sistent_feature.md b/.github/ISSUE_TEMPLATE/sistent_feature.md
index 52444c480226..f90306130535 100644
--- a/.github/ISSUE_TEMPLATE/sistent_feature.md
+++ b/.github/ISSUE_TEMPLATE/sistent_feature.md
@@ -1,29 +1,29 @@
----
-name: 🚀 Enhancement in Sistent Project
-about: Propose a new feature, suggest a component, or report an issue for Sistent.
-title: '[Sistent]'
-labels: 'project/sistent, kind/enhancement'
-assignees: ''
----
-### Current Behavior
-
-
-### Desired Behavior
-
-
-### Screenshots / Mockups
-
-
-### Implementation
-
-
----
-
-
-The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the [`master` branch](https://github.com/layer5io/layer5/tree/master).
-- 🎨 See [Sistent Repository](https://github.com/layer5io/sistent).
-- 📚 See [contributing instructions](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md).
-- 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
-- 🙋🏾🙋🏼 Questions: [Discussion Forum](https://discuss.layer5.io) and [Community Slack](https://slack.layer5.io).
-
-Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer).
+---
+name: 🚀 Enhancement in Sistent Project
+about: Propose a new feature, suggest a component, or report an issue for Sistent.
+title: '[Sistent]'
+labels: 'project/sistent, kind/enhancement'
+assignees: ''
+---
+### Current Behavior
+
+
+### Desired Behavior
+
+
+### Screenshots / Mockups
+
+
+### Implementation
+
+
+---
+
+
+The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the [`master` branch](https://github.com/layer5io/layer5/tree/master).
+- 🎨 See [Sistent Repository](https://github.com/layer5io/sistent).
+- 📚 See [contributing instructions](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md).
+- 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
+- 🙋🏾🙋🏼 Questions: [Discussion Forum](https://discuss.layer5.io) and [Community Slack](https://slack.layer5.io).
+
+Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer).
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ffce62888d59..49946dc705c3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,695 +1,695 @@
-# Contributing at Layer5
-
-We are beyond excited to see that you want to contribute! We would love to accept your contributions. Layer5 is built by the community and warmly welcomes collaboration. There are many ways in which one could contribute to Layer5 and every contribution is equally appreciated here. Navigate through the following to understand more about contributing here.
-
-- [Before You Get Started](#before-you-get-started)
-- [Contributing to Layer5 Projects](#contributing-to-layer5-projects)
-- [Contributing to Layer5's Blogs](#contributing-to-layer5s-blogs)
-- [Contributing to Layer5's Sistent](#contributing-to-layer5s-sistent)
-- [How to Contribute](#how-to-contribute)
- - [Prerequisites](#prerequisites)
- - [Set up your Local Development Environment](#set-up-your-local-development-environment)
- - [Signing-off on Commits](#signing-off-on-commits)
-
-⚠️ Cloning this repository ⚠️
-
-Cloning the repo with all its history results in a ~6 GB download. To contribute to this site, you don't need its entire history. Use the `--depth=1` flag to significantly reduce the footprint this repo creates in your environment.
-
-```bash
-git clone --depth=1 https://github.com/layer5io/layer5.git
-```
-
-# Before You Get Started
-
-## Code of Conduct
-
-Layer5 follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting community@layer5.io.
-Violation of the code of conduct is taken seriously, kindly report any violations of the Code of Conduct by filling in the Incident report.
-The comfort and safety of Layer5 community members are our priority. Please do well to adhere to the Code of Conduct to participate in the Layer5 community.
-
-## For Newcomers
-
-To help you get started on contributing to Layer5 projects, refer to the [Layer5 Newcomers Guide](https://layer5.io/community/newcomers), which aims to make contributions easier for new folks like you! See the resources and tutorials to help you get started. Along with this we have an extensive handbook on how this community works , how folks inside the community wear different hats to run it and few of its guidelines, have a look inside the [Community Handbook](https://layer5.io/community/handbook).
-
-## Issues & Pull Requests
-
-### Creating an Issue
-
-Before **creating** an Issue i.e for `features`/`bugs`/`improvements` please follow these steps:
-
-
-1. Search existing Issues before creating a new Issue (look to see if the Issue has already been created).
-1. If it doesn't exist create a new Issue giving as much context as possible (please take note and select the correct Issue type, for example `bug`, `documentation` or `feature`.
-1. If you wish to work on the Issue once it has been triaged, please include this in your Issue description.
-
-### Working on an Issue
-
-Before working on an existing Issue please follow these steps:
-
-1. Comment asking for the Issue to be assigned to you.
-1. To best position yourself for Issues assignment, we recommend that you:
- 1. Confirm that you have read the CONTRIBUTING.md.
- 1. Have a functional development environment (have built and are able to run the project).
- 1. Convey your intended approach to solving the issue.
- 1. Put each of these items in writing in one or more comments.
-1. After the Issue is assigned to you, you can start working on it.
-1. In general, **only** start working on this Issue (and open a Pull Request) when it has been assigned to you. Doing so will prevent confusion, duplicate work (some of which may go unaccepted given its duplicity), incidental stepping on toes, and the headache involved for maintainers and contributors alike as Issue assignments collide and heads bump together.
-1. Reference the Issue in your Pull Request (for example `This PR fixes #123`). so that the corresponding Issue is automatically closed upon merge of your Pull Request.
-
-> Notes:
->
-> - Check the `Assignees` box at the top of the page to see if the Issue has been assigned to someone else before requesting this be assigned to you. If the issue has a current Assignee, but appears to be inactive, politely inquire with the current Assignee as to whether they are still working on a solution and/or if you might collaborate with them.
-> - Only request to be assigned an Issue if you know how to work on it.
-> - If an Issue is unclear, ask questions to get more clarity before asking to have the Issue assigned to you; avoid asking "what do I do next? how do I fix this?" (see the item above this line)
-> - An Issue can be assigned to multiple people, if you all agree to collaborate on the Issue (the Pull Request can contain commits from different collaborators)
-> - Any Issues that has no activity after 2 weeks will be unassigned and re-assigned to someone else.
-
-## Reviewing Pull Requests
-
-We welcome everyone to review Pull Requests. It is a great way to learn, network, and support each other.
-
-### DOs
-
-- Use inline comments to explain your suggestions
-- Use inline suggestions to propose changes
-- Exercise patience and empathy while offering critiques of the works of others.
-
-### DON'Ts
-
-- Do not repeat feedback, this creates more noise than value (check the existing conversation), use GitHub reactions if you agree/disagree with a comment
-- Do not blindly approve Pull Requests to improve your GitHub contributors graph
-
-
-## Style Guide
-
-The Layer5 website is hosted in this repository and is built using Gatsbyjs. Before opening a Pull Request, please review the [design doc](https://docs.google.com/document/d/1rvUZy2_S1a2_14BAQIg6b9cMhUuu04kYzkOPDPaPptI/edit#) to learn more about the structure of the website. Once a Pull Request has been submitted, a preview deployment will be built and made available to you and other contributors on your PR to review.
-
-## Discussion Forum
-
-Join the [discussion forum](https://discuss.layer5.io/c/landscape/7) (the Landscape topic is appropriate for all layer5.io questions) to discuss suggested new features, possible bugs, enhancement in user experience, and any other aspects of the site. The discussion forum is our preferred method of communication, you can, however, also inquire in the [#websites](https://layer5io.slack.com/archives/C015QJKUMPU) channel in the Layer5 Slack workspace.
-
-# Contributing to Layer5 Projects
-
-Please follow these steps and note these guidelines to begin contributing:
-
-1. First step is to set up the local development environment.
-1. Bug fixes are always welcome. Start by reviewing the [list of bugs](https://github.com/layer5io/layer5/labels/kind%2Fbug).
-1. A good way to easily start contributing is to pick and work on a [good first issue](https://github.com/layer5io/layer5/labels/good%20first%20issue). We try to make these Issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the Issue.
-1. We regularly discuss new Issues to work on in our [discussion forum](https://discuss.layer5.io/c/landscape/7) and the [#websites](https://layer5io.slack.com/archives/C015QJKUMPU) channel. Feel free to join and discuss any Issue or any idea that you may have.
-
-# Contributing to Layer5's Blogs Section
-
-If you'd like to contribute a post to layer5.io/blog, please open an Issue and suggest a topic. If you don't have a topic, then hop into the [#blog-kitchen](https://layer5io.slack.com/archives/C0210TZRF88) channel, and we'll help you find one.
-
-## Things to keep in mind
-
-1. We use inbuilt components called Call to Action(CTAs), prominently in our MarkDown(.mdx) files. Check out our [guide to CTAs](https://github.com/layer5io/layer5/blob/master/src/components/Call-To-Actions/README.md).
-
-## Adding a Blog Post
-
-1. In order to contribute a blog post, fork this repository, clone it, create a new branch and navigate to the `src/collections/blog` directory.
-2. Create a copy of the [blog template](https://github.com/layer5io/layer5/tree/master/src/collections/blog/blog-template).
-3. Follow the instructions included in the blog template and name the new file after the title of the blog article.
-4. Entries will be listed in chronological order automatically.
-
-## Adding a Resource
-
-1. In order to contribute a resource, fork this repository, clone it, create a new branch and navigate to the `src/collections/resources` directory.
-2. Create a copy of the [resource template](https://github.com/layer5io/layer5/tree/master/src/collections/resources/resources-template).
-3. Follow the instructions included in the resource template and name the new file after the title of the resource.
-4. Please note that different types of resources like `article`,`tutorial`, `webinars` are organized into separate folders inside the `/resource` collection. Add your entries in the respective folders.
-5. To qualify any post as a resource, the field `resource: true` must be added. This applies for `/news`, `/blog`, `/events` as well.
-6. Each resource can be associated with 4 additional fields: `type`, `mesh`, `technology` and `product`. The current list of values can be found from these [options](https://github.com/layer5io/layer5/blob/master/src/sections/Resources/Resources-grid/options.js).
-
-## Adding News
-
-1. In order to add/update news items, fork this repository, clone it, create a new branch, and navigate to the `src/collections/news` directory.
-2. Create a copy of the [news template](https://github.com/layer5io/layer5/tree/master/src/collections/news/news-template/0000-00-00-news-title).
-3. Follow the instructions included in the news template and name the new file after the title of the news article.
-4. Entries will be listed in chronological order automatically.
-
-# Contributing to Layer5's Sistent
-
-If you'd like to contribute to Sistent, start by selecting the project/sistent label in the [#GitHub issue tracker](https://github.com/layer5io/layer5/labels/project%2Fsistent).
-
-### General Contribution Guidelines
-
-1. Select the [project/sistent](https://github.com/layer5io/layer5/labels/project%2Fsistent) label in the GitHub issue tracker.
-1. Navigate to the relevant directory, such as:
- ```
- src/sections/Projects/Sistent
- ```
- > Note: For other parts of the project, the file path may vary. Ensure you're working in the correct file associated with the area you're contributing to.
-1. Add or update content. The system dynamically generates pages and routes to maintain consistency.
-
-### Adding Sistent Component
-
-We've streamlined the process by introducing a dynamic page creation workflow, simplifying the addition of new pages and ensuring a consistent structure for all contributions.
-
-1. Navigate to the relevant directory, such as:
- ```
- src/sections/Projects/Sistent
- ```
-1. To add a new page, simply update this `content.js` file with the necessary details. All content is managed in a centralized file:
- ```
- src/sections/Projects/Sistent/components/content.js
- ```
-1. The system will dynamically generate pages based on this content and handle routing automatically.
-
-### Example
-Refer to the [**Button component**](https://layer5.io/projects/sistent/components/button) in the Sistent Library for an example of how to structure the content.
-
-# Common Types of Site Contributions
-
-The following list of instructions pertains to commonplace site updates by contributors.
-
-## Things to keep in mind
-
-1. Prioritize using only the theme colors and hexcodes that are already being used in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js) instead of introducing new color codes to the file.
-2. Avoid adding `rel="noreferrer"` attribute to internal links on the site. Use gatsby [`` component](https://www.gatsbyjs.com/docs/linking-between-pages/) for internal links on the site.
-
-## Adding dark mode for components
-
-The site currently has dark and light mode, the colors used in these two modes can be found in the dark and light theme objects in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js).
-
-These theme objects use a property whose value automatically changes based on the active theme without using a conditional.
-
-An example of a conditional:
-
-```
-theme === "dark" ? "white" : "black"
-```
-
-The preference is to **not use conditionals** for elements because they will flicker when reloading a page in dark mode.
-
-As currently constructed, the dark and light theme objects share similar property names that have different values.
-
-The property name will tell you how the value (color or hexcode) will change from dark mode to light mode. The first part is for dark mode, then "To", and the next part is for light mode.
-
-example #1: `whiteToBlack`
-
-"white" is the first part for dark mode
-"To"
-"Black" is the second part for light mode
-
-In dark mode the value of `whiteToBlack` will be `white`
-In light mode the value of `whiteToBlack` will be `black`
-
-example #2: `grey141414ToGreyF5F5F5`
-
-In dark mode this value will be `#141414` (a dark shade of grey)
-In light mode this value will be `#F5F5F5` (a light shade of grey).
-
-The hexcode in the property name is the indication of the color shade being used in the active theme. Always check the hexcode to confirm it is the desired shade/color.
-
-In a styled component, you can use the property name in the following way:
-
-#### Examples
-
-example #1:
-`color: ${props => props.theme.whiteToBlack};`
-
-example #2:
-`color: ${props => props.theme.greyDEE3DEToGreen3C494F}`
-
-### Adding a new color pair transition property
-
-It is recommended to use pre-existing styles, colors, hexcodes from the theme. Avoid adding your own CSS variables and incorporating new colors.
-
-If you must add a new property that changes with the theme:
-
-1. Add a new property with the same name to the dark and light theme objects in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js) and the corresponding values you want them to have in each mode.
-
-#### Example:
-
-```
-const lighttheme = {
- blue0000FFToRedFF0000: "#FF0000",
-```
-
-```
-const darktheme = {
- blue0000FFToRedFF0000: "#0000FF",
-
-```
-
-2. Use that property name in your styled component
-
-```
-color: ${props => props.theme.blue0000FFToRedFF0000};
-```
-
-### Adding the transition property to the element in the styled component
-
-Transition property is not inherited. It must be added for each element that is changing colors and be consistent with the transition timing and style of the background color in [`GlobalStyle`](https://github.com/layer5io/layer5/blob/master/src/sections/app.style.js) to ensure uniform color change.
-
-Currently this property:value is
-
-```
-transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
-```
-
-## Preferable SVG and Images
-
-- SVG or image does not need to change colors depending on the theme
-
-OR
-
-- SVG or image uses transparent sections that change with the background color to work with either theme.
-
-[Example of SVG file with transparent sections](https://github.com/layer5io/layer5/blob/master/src/assets/images/kanvas/icon-only/kanvas-icon-color.svg)
-
-[Example of image file with transparent sections](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/projects/meshery-logo-light.webp)
-
-You can see these two examples in action [here](https://layer5.io/projects) by toggling the theme (located on the right side of the navigation bar).
-
-The above are the preferred kinds of SVG and images. If your SVG or image fits one of the descriptions above, then you do not need to read further.
-
-### Changing SVG according to theme
-
-SVG image formats are the preferred format because of the ability to control colors used to fill path or stroke with styled-components and have them change dependent on the theme without using a conditional.
-
-#### Importing SVG as a React Component
-
-To use the SVG as an `svg` element and not a source for an `img` element, we will import the SVG as a ReactComponent. You can see an example of importing the SVG as a ReactComponent in the code [here](https://github.com/layer5io/layer5/blob/master/src/sections/General/Navigation/index.js)
-
-```
-import { ReactComponent as Logo } from "../../../assets/images/app/layer5-colorMode.svg";
-```
-
-Then we include the component where you want to display it
-
-```
-
-
-
-```
-
-#### Adding the color change property to the SVG
-
-To change a fill for a SVG depending on the theme, you will need to create a class in the SVG to fill inner paths or rect or polygon with default colors, then assign that SVG class in a styled-component to a property value as done in components.
-
-#### Example: Layer5 Logo
-
-To see the code for this SVG click [here](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/layer5-colorMode.svg?short_path=e76da80). (note: if link is not working , click [here](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/layer5-colorMode.svg) and then click the "<>" button to display the source blob.)
-
-In the SVG code, we see classes declared here:
-
-```
-
-
-
-```
-
-We use `colorMode[#]` in the class name to designate classes that we want to change depending on the theme.
-
-Then in the related styled component, we use a specific class generated by styled-components to add the theme property.
-
-In our example with the logo in the navigation, this is the relevant [styled component](https://github.com/layer5io/layer5/blob/master/src/sections/General/Navigation/navigation.style.js).
-
-Here, if we want to update the CSS of the SVG then we target the appropriate parent class. For this example, looking at the where the SVG React component (``) was placed, we see `className="logo"` as the relevant parent class.
-
-```
-
-
-
-```
-
-In the styled component, we find ".logo", add the `svg` element, and within that add the class that is generated by the styled-component plugin, in our example it is `.layer5-colorMode_svg__colorMode1`.
-
-> Note: the styled-component generated class name is based off the file name and the colorMode class name, using the following structure:
->
-> svg file name (`layer5-colorMode`)
-
-- a separator (`_svg___`)
-- the class name being targeted inside the SVG (`colorMode1`)
- > this results in the class `.layer5-colorMode_svg__colorMode1`
-
-```
- .logo {
- margin-top: 8px;
-
- svg {
- width: 155px;
- .layer5-colorMode_svg__colorMode1 {
- fill: ${props => props.theme.whiteToGreen3C494F};
- transition: fill 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
- }
- }
- }
-```
-
-> Notes:
->
-> - You can add presentation css attributes to `svg` similar to how you would add to an `img`.
-> - You can find the generated class name when you inspect the element in the browser console and look at the styles section of the svg code.
-> - Even though we have a default fill property in the SVG itself (just in case), the fill property in the styled component will override it.
-> - Whenever we are changing colors in a SVG, be sure to add the transition timing and style that is used for the background color in [GlobalStyle](https://github.com/layer5io/layer5/blob/master/src/sections/app.style.js) to have everything smoothly transition. Currently this property: value is
->
-> ```
-> transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
-> ```
-
-## Changing images depending on the theme.
-
-If possible we wish to avoid using images dependent on the theme because we are required to use a conditional (which will cause a flicker of the image when the page is reloaded). If necessary, please use the following instructions.
-
-1. To change images or SVG as the image source, according to the theme, you have to import the hook `useStyledDarkMode` from the following [folder](https://github.com/layer5io/layer5/blob/master/src/theme/app/useStyledDarkMode.js), and then use the `isDark` value from `useStyledDarkMode` hook for the conditional.
-
-For example, you can view the code for [this file](https://github.com/layer5io/layer5/blob/master/src/sections/Kanvas/Kanvas-collaborate/kanvas-collaborate-banner.js).
-
-Here are the relevant parts of the code:
-
-```
-import { useStyledDarkMode } from "../../../theme/app/useStyledDarkMode";
-
-const { isDark } = useStyledDarkMode();
-
-
-```
-
-## Changing images in gatsby-image-plugin according to the theme.
-
-Procedure of changing the image for the gatsby-image is the same as we change for images, however, it is recommended to fetch two images, one for a dark theme and one for a light theme change it according to the `isDark` value as done with images.
-
-Example (For Thumbnail):
-Fetching images through Graphql. Add this in graphql query in frontmatter
-
- darkthumbnail {
- childImageSharp {
- gatsbyImageData(layout: FULL_WIDTH)
- }
- extension
- publicURL
- }
-
-Change image according to isDark value:
-
-```
-
-```
-
-> Note:
->
-> - A condition `frontmatter.darkthumbnail.publicURL !== frontmatter.thumbnail.publicURL` is added so that the image only changes if there is a difference between the thumbnail publicURLs.
-
-## Adding Images and Icons
-
-1. It is recommended to use `@react-icons/all-files` instead of `react-icons` for importing icons. The Issue with react-icons is that even though we are importing a single icon from the package/folder it still imports the complete icon folder which is creating unwanted junks of JS in the build.
-2. It is recommended to use Gatsby's `` instead of `` tag to display static images on the site **except for SVG images**. This performs automatic image optimization, thereby improving site performance.
-3. Avoid creating duplicate copies of the same image under different folders. All images must be imported from `/assets/images` folder.
-
-## Site Performance Considerations
-
-1. Analyze page load metrics of mobile version in lighthouse report (see status of GitHub workflow on your open PR).
-2. While creating a new page make sure to use Gatsby Head API for SEO.
-3. Prefer using `loading="eager"` for Hero images to improve LCP(Largest Contentful Paint) and FCP(First Contentful Paint).
-4. Optimise page by deferring loading of third party scripts. You can use [off-main-thread](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-script/#off-main-thread-strategy-experimental) in Script API.
-5. Prefer Code Splitting using [loadable](https://github.com/gregberge/loadable-components) to lazy load heavy components which are not in the viewport.
-
-Note:- You can also refer to [Improving Site Performance](https://www.gatsbyjs.com/docs/how-to/performance/improving-site-performance/), [web.dev](https://web.dev/vitals/).
-
-## Updating/Creating a Community Member Profile
-
-Layer5 community members are an integral part of what makes Layer5 and its projects successful. Prominently highlighting our members and their works is something that we think is important. To initiate adding a new or updating an existing community member profile, be sure to use the community member [issue template](https://github.com/layer5io/layer5/issues/new?assignees=&labels=area%2Fcommunity%2C+help+wanted%2C+framework%2Fgatsby%2C+language%2Fmarkdown%2C+good+first+issue&template=community_member_profile.md&title=%5BCommunity%5D+Member+Profile%3A). When creating or updating a community member profile, use the [profile template](https://github.com/layer5io/layer5/tree/master/src/collections/members/_member-profile-template). You can easily understand how the template is used by reviewing other profiles.
-
-### Badges for Community Members
-
-Badges are a great way of highlighting the area of contribution by any given community member. A variety of badges exist so that community members and their efforts may be affiliated with a particular project or with a community initiative. An example of how a badge is assigned using markdown can be found [here](https://github.com/layer5io/layer5/blob/master/src/collections/members/lee-calcote/index.mdx), and it will appear [this way](https://layer5.io/community/members/lee-calcote) on a member profile.
-
-#### Possible Badges:
-
-- Community
-- Docker Extension
-- Docs
-- Meshery Catalog
-- Kanvas
-- Landscape
-- ImageHub
-- Meshery
-- Meshery Operator
-- SMP
-- Nighthawk
-- Patterns
-- UI/UX Design
-- Writer Program
-
-## Updating the Service Mesh Landscape
-
-Another common site update includes the updation of the Service Mesh Landscape. The service mesh landscape is powered by Gatsby.js. To update the landscape, fork this repository, clone it, create a branch and navigate to the **src/collections/landscape** folder.
-
-Make sure to open a [new issue](https://github.com/layer5io/layer5/issues/new?assignees=&labels=area%2Flandscape&template=landscape.md&title=%5BLandscape%5D) first. Following is a list of files that you may edit and make the necessary updates (if appropriate):
-
-- [non-functional.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/non-functional.js) - overview of various service meshes
-- [meshes.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/meshes.js) - list of individual service mesh details
-- [proxies.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/proxies.js) - list of individual modern proxies
-- [gateway.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/gateways.js) - list of API gateways
-- [load-balancer.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/load-balancer.js) - list of load balancers
-
-Entries should be listed in alphabetical order. Data provided to the `smi.js` is dynamic and based upon results from conformance tests run using Meshery.
-
-To update the Service Mesh Timeline, add the new service mesh in the [non-functional.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/non-functional.js) file. Add an `announce-date` key for the service mesh, then add a `timeline-order` key having a value 1+`maximum value of timeline-order` till now, to list the service mesh in the timeline correctly.
-
-# How to Contribute
-
-## Prerequisites
-
-Make sure you have the following prerequisites installed on your operating system before you start contributing:
-
-- [Nodejs and npm](https://nodejs.org/en/)
-
- To verify run:
-
- ```
- node -v
- ```
-
- ```
- npm -v
- ```
-
-- [Gatsby.js](https://www.gatsbyjs.com/)
-
- To verify run:
-
- ```
- gatsby --version
- ```
-
-**Note:** If you're on a _Windows environment_ then it is highly recommended that you install [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/install) both for performance and ease of use. Refer to the [documentation](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/gatsby-on-wsl) for the installation of _Gatsby.js on WSL_.
-
-## Set up your Local Development Environment
-
-Follow the following instructions to start contributing.
-
-**1.** Fork [this](https://github.com/layer5io/layer5) repository.
-
-**2.** Clone your forked copy of the project.
-
-```
-git clone --depth=1 https://github.com//layer5.git
-```
-
-**3.** Navigate to the project directory.
-
-```
-cd layer5
-```
-
-**4.** Add a reference(remote) to the original repository.
-
-```
-git remote add upstream https://github.com/layer5io/layer5.git
-```
-
-**5.** Check the remotes for this repository.
-
-```
-git remote -v
-```
-
-**6.** Always take a pull from the upstream repository to your master branch to keep it at par with the main project (updated repository).
-
-```
-git pull upstream master
-```
-
-**7.** Create a new branch.
-
-```
-git checkout -b
-```
-
-**8.** Install the dependencies for running the site.
-
-```
-make setup
-```
-
-**9.** Make the desired changes.
-
-**10.** Run the site locally to preview changes.
-
-```
-make site
-```
-
-This will run a local webserver with "live reload" conveniently enabled. ( **NOTE**: while using the make command on Windows, there sometimes arises an error in identifying the command even after it is installed (unrecognized command), this is because the PATH for the binary might not be set correctly ).
-
-**11.** Track your changes.
-
-```
-git add .
-```
-
-**12.** Commit your changes. To contribute to this project, you must agree to the [Developer Certificate of Origin (DCO)](#signing-off-on-commits) for each commit you make.
-
-```
-git commit --signoff -m ""
-```
-
-or you could go with the shorter format for the same, as shown below.
-
-```
-git commit -s -m ""
-```
-
-**13.** While you are working on your branch, other developers may update the `master` branch with their branch. This action means your branch is now out of date with the `master` branch and missing content. So to fetch the new changes, follow along:
-
-```
-git checkout master
-git fetch origin master
-git merge upstream/master
-git push origin
-```
-
-Now you need to merge the `master` branch into your branch. This can be done in the following way:
-
-```
-git checkout
-git merge master
-```
-
-**14.** Push the committed changes in your feature branch to your remote repo.
-
-```
-git push -u origin
-```
-
-**15.** Once you’ve committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. Please ensure that you compare your feature branch to the desired branch of the repo you are supposed to make a PR to. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes in your development branch and update it.
-
-### Lint Rules
-
-Layer5 uses ESLint to maintain code quality and consistency in our UI code. Use this command to trigger a lint check:
-
-```sh
-make lint
-```
-
-> Note:
-> - Eslint in Gatsby requires generating config files from CLI. Run `gatsby build` or `gatsby develop` if you face this error during linting.
-
-
-## Signing-off on Commits
-
-To contribute to this project, you must agree to the **Developer Certificate of
-Origin (DCO)** for each commit you make. The DCO is a simple statement that you,
-as a contributor, have the legal right to make the contribution.
-
-See the [DCO](https://developercertificate.org) file for the full text of what you must agree to
-and how it works [here](https://github.com/probot/dco#how-it-works).
-To signify that you agree to the DCO for contributions, you simply add a line to each of your
-git commit messages:
-
-```
-Signed-off-by: Jane Smith
-```
-
-**Note:** you don't have to manually include this line on your commits, git does that for you as shown below:
-
-```
-$ git commit -s -m “my commit message w/signoff”
-```
-
-In most cases, git automatically adds the signoff to your commit with the use of
-`-s` or `--signoff` flag to `git commit`. You must use your real name and a reachable email
-address (sorry, no pseudonyms or anonymous contributions).
-
-To ensure all your commits are signed, you may choose to add this alias to your global `.gitconfig`:
-
-_~/.gitconfig_
-
-```
-[alias]
- amend = commit -s --amend
- cm = commit -s -m
- commit = commit -s
-```
-
-Or you may configure your IDE, for example, Visual Studio Code to automatically sign-off commits for you:
-
-
-
-## FYI regarding the dev environment
-
-### Dev and Browser Warnings You May Encounter
-
-Note:
-
-- These are **non-blocking warnings** you can expect to see in your terminal or browser while working in local development environment.
-- They do not impact the performance of the code and are unrelated to your contributions.
-- These will not show in `build` or `production` mode.
-- These are being documented to minimize confusion for the user while doing development.
-
----
-
-> warn ./node_modules/react-accessible-accordion/dist/es/index.js
-> Attempted import error: 'useId' is not exported from 'react' (imported as 'useId').
-
-and
-
-> client.js:196 export 'useId' (imported as 'useId') was not found in 'react' (possible exports: Children, Component, Fragment, Profiler, PureComponent, StrictMode, Suspense, \_\_SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED, cloneElement, createContext, createElement, createFactory, createRef, forwardRef, isValidElement, lazy, memo, useCallback, useContext, useDebugValue, useEffect, useImperativeHandle, useLayoutEffect, useMemo, useReducer, useRef, useState, version)
-
-Where/When:
-
-- In terminal: after `npm start`
-- In browser: loading https://layer5.io
-
-Reason: [https://github.com/springload/react-accessible-accordion/issues/351](https://github.com/springload/react-accessible-accordion/issues/351)
-
-> V5 is a release we cut explicitly for React 18 support (Hence the major upgrade, this was a breaking change, the webpack fix would not work as we are using React 18 new APIs), we are sticking with V4 for React 17 and under compatibility, using V4 has no functional difference outside of React version compatibility.
-
-Layer5 currently using:
-"react-accessible-accordion": "^5.0.0"
-react": "^17.0.2"
-
-To clear the warning:
-Upgrade the `react`package to ^18. However upgrading may introduce too many breaking changes and complexity.
-
----
-
-> Warning: Each child in a list should have a unique "key" prop.
-> Check the top-level render call using . See https://reactjs.org/link/warning-keys for more information.
-> at title
-
-Where/When:
-
-- In terminal: after `npm start` and loading page
-
-Reason: In this version of Gatsby (4.20), the file:
-`node_modules/gatsby/cache-dir/head/head-export-handler-for-ssr.js` is missing code to assign `key` prop to each head tag included in the `SEO` component.
-
-To clear the warning:
-This could be resolved by adding code to the package, but requires too much complexity to include for each user. This warning is cleared in later versions of Gatsby.
+# Contributing at Layer5
+
+We are beyond excited to see that you want to contribute! We would love to accept your contributions. Layer5 is built by the community and warmly welcomes collaboration. There are many ways in which one could contribute to Layer5 and every contribution is equally appreciated here. Navigate through the following to understand more about contributing here.
+
+- [Before You Get Started](#before-you-get-started)
+- [Contributing to Layer5 Projects](#contributing-to-layer5-projects)
+- [Contributing to Layer5's Blogs](#contributing-to-layer5s-blogs)
+- [Contributing to Layer5's Sistent](#contributing-to-layer5s-sistent)
+- [How to Contribute](#how-to-contribute)
+ - [Prerequisites](#prerequisites)
+ - [Set up your Local Development Environment](#set-up-your-local-development-environment)
+ - [Signing-off on Commits](#signing-off-on-commits)
+
+⚠️ Cloning this repository ⚠️
+
+Cloning the repo with all its history results in a ~6 GB download. To contribute to this site, you don't need its entire history. Use the `--depth=1` flag to significantly reduce the footprint this repo creates in your environment.
+
+```bash
+git clone --depth=1 https://github.com/layer5io/layer5.git
+```
+
+# Before You Get Started
+
+## Code of Conduct
+
+Layer5 follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting community@layer5.io.
+Violation of the code of conduct is taken seriously, kindly report any violations of the Code of Conduct by filling in the Incident report.
+The comfort and safety of Layer5 community members are our priority. Please do well to adhere to the Code of Conduct to participate in the Layer5 community.
+
+## For Newcomers
+
+To help you get started on contributing to Layer5 projects, refer to the [Layer5 Newcomers Guide](https://layer5.io/community/newcomers), which aims to make contributions easier for new folks like you! See the resources and tutorials to help you get started. Along with this we have an extensive handbook on how this community works , how folks inside the community wear different hats to run it and few of its guidelines, have a look inside the [Community Handbook](https://layer5.io/community/handbook).
+
+## Issues & Pull Requests
+
+### Creating an Issue
+
+Before **creating** an Issue i.e for `features`/`bugs`/`improvements` please follow these steps:
+
+
+1. Search existing Issues before creating a new Issue (look to see if the Issue has already been created).
+1. If it doesn't exist create a new Issue giving as much context as possible (please take note and select the correct Issue type, for example `bug`, `documentation` or `feature`.
+1. If you wish to work on the Issue once it has been triaged, please include this in your Issue description.
+
+### Working on an Issue
+
+Before working on an existing Issue please follow these steps:
+
+1. Comment asking for the Issue to be assigned to you.
+1. To best position yourself for Issues assignment, we recommend that you:
+ 1. Confirm that you have read the CONTRIBUTING.md.
+ 1. Have a functional development environment (have built and are able to run the project).
+ 1. Convey your intended approach to solving the issue.
+ 1. Put each of these items in writing in one or more comments.
+1. After the Issue is assigned to you, you can start working on it.
+1. In general, **only** start working on this Issue (and open a Pull Request) when it has been assigned to you. Doing so will prevent confusion, duplicate work (some of which may go unaccepted given its duplicity), incidental stepping on toes, and the headache involved for maintainers and contributors alike as Issue assignments collide and heads bump together.
+1. Reference the Issue in your Pull Request (for example `This PR fixes #123`). so that the corresponding Issue is automatically closed upon merge of your Pull Request.
+
+> Notes:
+>
+> - Check the `Assignees` box at the top of the page to see if the Issue has been assigned to someone else before requesting this be assigned to you. If the issue has a current Assignee, but appears to be inactive, politely inquire with the current Assignee as to whether they are still working on a solution and/or if you might collaborate with them.
+> - Only request to be assigned an Issue if you know how to work on it.
+> - If an Issue is unclear, ask questions to get more clarity before asking to have the Issue assigned to you; avoid asking "what do I do next? how do I fix this?" (see the item above this line)
+> - An Issue can be assigned to multiple people, if you all agree to collaborate on the Issue (the Pull Request can contain commits from different collaborators)
+> - Any Issues that has no activity after 2 weeks will be unassigned and re-assigned to someone else.
+
+## Reviewing Pull Requests
+
+We welcome everyone to review Pull Requests. It is a great way to learn, network, and support each other.
+
+### DOs
+
+- Use inline comments to explain your suggestions
+- Use inline suggestions to propose changes
+- Exercise patience and empathy while offering critiques of the works of others.
+
+### DON'Ts
+
+- Do not repeat feedback, this creates more noise than value (check the existing conversation), use GitHub reactions if you agree/disagree with a comment
+- Do not blindly approve Pull Requests to improve your GitHub contributors graph
+
+
+## Style Guide
+
+The Layer5 website is hosted in this repository and is built using Gatsbyjs. Before opening a Pull Request, please review the [design doc](https://docs.google.com/document/d/1rvUZy2_S1a2_14BAQIg6b9cMhUuu04kYzkOPDPaPptI/edit#) to learn more about the structure of the website. Once a Pull Request has been submitted, a preview deployment will be built and made available to you and other contributors on your PR to review.
+
+## Discussion Forum
+
+Join the [discussion forum](https://discuss.layer5.io/c/landscape/7) (the Landscape topic is appropriate for all layer5.io questions) to discuss suggested new features, possible bugs, enhancement in user experience, and any other aspects of the site. The discussion forum is our preferred method of communication, you can, however, also inquire in the [#websites](https://layer5io.slack.com/archives/C015QJKUMPU) channel in the Layer5 Slack workspace.
+
+# Contributing to Layer5 Projects
+
+Please follow these steps and note these guidelines to begin contributing:
+
+1. First step is to set up the local development environment.
+1. Bug fixes are always welcome. Start by reviewing the [list of bugs](https://github.com/layer5io/layer5/labels/kind%2Fbug).
+1. A good way to easily start contributing is to pick and work on a [good first issue](https://github.com/layer5io/layer5/labels/good%20first%20issue). We try to make these Issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the Issue.
+1. We regularly discuss new Issues to work on in our [discussion forum](https://discuss.layer5.io/c/landscape/7) and the [#websites](https://layer5io.slack.com/archives/C015QJKUMPU) channel. Feel free to join and discuss any Issue or any idea that you may have.
+
+# Contributing to Layer5's Blogs Section
+
+If you'd like to contribute a post to layer5.io/blog, please open an Issue and suggest a topic. If you don't have a topic, then hop into the [#blog-kitchen](https://layer5io.slack.com/archives/C0210TZRF88) channel, and we'll help you find one.
+
+## Things to keep in mind
+
+1. We use inbuilt components called Call to Action(CTAs), prominently in our MarkDown(.mdx) files. Check out our [guide to CTAs](https://github.com/layer5io/layer5/blob/master/src/components/Call-To-Actions/README.md).
+
+## Adding a Blog Post
+
+1. In order to contribute a blog post, fork this repository, clone it, create a new branch and navigate to the `src/collections/blog` directory.
+2. Create a copy of the [blog template](https://github.com/layer5io/layer5/tree/master/src/collections/blog/blog-template).
+3. Follow the instructions included in the blog template and name the new file after the title of the blog article.
+4. Entries will be listed in chronological order automatically.
+
+## Adding a Resource
+
+1. In order to contribute a resource, fork this repository, clone it, create a new branch and navigate to the `src/collections/resources` directory.
+2. Create a copy of the [resource template](https://github.com/layer5io/layer5/tree/master/src/collections/resources/resources-template).
+3. Follow the instructions included in the resource template and name the new file after the title of the resource.
+4. Please note that different types of resources like `article`,`tutorial`, `webinars` are organized into separate folders inside the `/resource` collection. Add your entries in the respective folders.
+5. To qualify any post as a resource, the field `resource: true` must be added. This applies for `/news`, `/blog`, `/events` as well.
+6. Each resource can be associated with 4 additional fields: `type`, `mesh`, `technology` and `product`. The current list of values can be found from these [options](https://github.com/layer5io/layer5/blob/master/src/sections/Resources/Resources-grid/options.js).
+
+## Adding News
+
+1. In order to add/update news items, fork this repository, clone it, create a new branch, and navigate to the `src/collections/news` directory.
+2. Create a copy of the [news template](https://github.com/layer5io/layer5/tree/master/src/collections/news/news-template/0000-00-00-news-title).
+3. Follow the instructions included in the news template and name the new file after the title of the news article.
+4. Entries will be listed in chronological order automatically.
+
+# Contributing to Layer5's Sistent
+
+If you'd like to contribute to Sistent, start by selecting the project/sistent label in the [#GitHub issue tracker](https://github.com/layer5io/layer5/labels/project%2Fsistent).
+
+### General Contribution Guidelines
+
+1. Select the [project/sistent](https://github.com/layer5io/layer5/labels/project%2Fsistent) label in the GitHub issue tracker.
+1. Navigate to the relevant directory, such as:
+ ```
+ src/sections/Projects/Sistent
+ ```
+ > Note: For other parts of the project, the file path may vary. Ensure you're working in the correct file associated with the area you're contributing to.
+1. Add or update content. The system dynamically generates pages and routes to maintain consistency.
+
+### Adding Sistent Component
+
+We've streamlined the process by introducing a dynamic page creation workflow, simplifying the addition of new pages and ensuring a consistent structure for all contributions.
+
+1. Navigate to the relevant directory, such as:
+ ```
+ src/sections/Projects/Sistent
+ ```
+1. To add a new page, simply update this `content.js` file with the necessary details. All content is managed in a centralized file:
+ ```
+ src/sections/Projects/Sistent/components/content.js
+ ```
+1. The system will dynamically generate pages based on this content and handle routing automatically.
+
+### Example
+Refer to the [**Button component**](https://layer5.io/projects/sistent/components/button) in the Sistent Library for an example of how to structure the content.
+
+# Common Types of Site Contributions
+
+The following list of instructions pertains to commonplace site updates by contributors.
+
+## Things to keep in mind
+
+1. Prioritize using only the theme colors and hexcodes that are already being used in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js) instead of introducing new color codes to the file.
+2. Avoid adding `rel="noreferrer"` attribute to internal links on the site. Use gatsby [`` component](https://www.gatsbyjs.com/docs/linking-between-pages/) for internal links on the site.
+
+## Adding dark mode for components
+
+The site currently has dark and light mode, the colors used in these two modes can be found in the dark and light theme objects in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js).
+
+These theme objects use a property whose value automatically changes based on the active theme without using a conditional.
+
+An example of a conditional:
+
+```
+theme === "dark" ? "white" : "black"
+```
+
+The preference is to **not use conditionals** for elements because they will flicker when reloading a page in dark mode.
+
+As currently constructed, the dark and light theme objects share similar property names that have different values.
+
+The property name will tell you how the value (color or hexcode) will change from dark mode to light mode. The first part is for dark mode, then "To", and the next part is for light mode.
+
+example #1: `whiteToBlack`
+
+"white" is the first part for dark mode
+"To"
+"Black" is the second part for light mode
+
+In dark mode the value of `whiteToBlack` will be `white`
+In light mode the value of `whiteToBlack` will be `black`
+
+example #2: `grey141414ToGreyF5F5F5`
+
+In dark mode this value will be `#141414` (a dark shade of grey)
+In light mode this value will be `#F5F5F5` (a light shade of grey).
+
+The hexcode in the property name is the indication of the color shade being used in the active theme. Always check the hexcode to confirm it is the desired shade/color.
+
+In a styled component, you can use the property name in the following way:
+
+#### Examples
+
+example #1:
+`color: ${props => props.theme.whiteToBlack};`
+
+example #2:
+`color: ${props => props.theme.greyDEE3DEToGreen3C494F}`
+
+### Adding a new color pair transition property
+
+It is recommended to use pre-existing styles, colors, hexcodes from the theme. Avoid adding your own CSS variables and incorporating new colors.
+
+If you must add a new property that changes with the theme:
+
+1. Add a new property with the same name to the dark and light theme objects in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js) and the corresponding values you want them to have in each mode.
+
+#### Example:
+
+```
+const lighttheme = {
+ blue0000FFToRedFF0000: "#FF0000",
+```
+
+```
+const darktheme = {
+ blue0000FFToRedFF0000: "#0000FF",
+
+```
+
+2. Use that property name in your styled component
+
+```
+color: ${props => props.theme.blue0000FFToRedFF0000};
+```
+
+### Adding the transition property to the element in the styled component
+
+Transition property is not inherited. It must be added for each element that is changing colors and be consistent with the transition timing and style of the background color in [`GlobalStyle`](https://github.com/layer5io/layer5/blob/master/src/sections/app.style.js) to ensure uniform color change.
+
+Currently this property:value is
+
+```
+transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
+```
+
+## Preferable SVG and Images
+
+- SVG or image does not need to change colors depending on the theme
+
+OR
+
+- SVG or image uses transparent sections that change with the background color to work with either theme.
+
+[Example of SVG file with transparent sections](https://github.com/layer5io/layer5/blob/master/src/assets/images/kanvas/icon-only/kanvas-icon-color.svg)
+
+[Example of image file with transparent sections](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/projects/meshery-logo-light.webp)
+
+You can see these two examples in action [here](https://layer5.io/projects) by toggling the theme (located on the right side of the navigation bar).
+
+The above are the preferred kinds of SVG and images. If your SVG or image fits one of the descriptions above, then you do not need to read further.
+
+### Changing SVG according to theme
+
+SVG image formats are the preferred format because of the ability to control colors used to fill path or stroke with styled-components and have them change dependent on the theme without using a conditional.
+
+#### Importing SVG as a React Component
+
+To use the SVG as an `svg` element and not a source for an `img` element, we will import the SVG as a ReactComponent. You can see an example of importing the SVG as a ReactComponent in the code [here](https://github.com/layer5io/layer5/blob/master/src/sections/General/Navigation/index.js)
+
+```
+import { ReactComponent as Logo } from "../../../assets/images/app/layer5-colorMode.svg";
+```
+
+Then we include the component where you want to display it
+
+```
+
+
+
+```
+
+#### Adding the color change property to the SVG
+
+To change a fill for a SVG depending on the theme, you will need to create a class in the SVG to fill inner paths or rect or polygon with default colors, then assign that SVG class in a styled-component to a property value as done in components.
+
+#### Example: Layer5 Logo
+
+To see the code for this SVG click [here](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/layer5-colorMode.svg?short_path=e76da80). (note: if link is not working , click [here](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/layer5-colorMode.svg) and then click the "<>" button to display the source blob.)
+
+In the SVG code, we see classes declared here:
+
+```
+
+
+
+```
+
+We use `colorMode[#]` in the class name to designate classes that we want to change depending on the theme.
+
+Then in the related styled component, we use a specific class generated by styled-components to add the theme property.
+
+In our example with the logo in the navigation, this is the relevant [styled component](https://github.com/layer5io/layer5/blob/master/src/sections/General/Navigation/navigation.style.js).
+
+Here, if we want to update the CSS of the SVG then we target the appropriate parent class. For this example, looking at the where the SVG React component (``) was placed, we see `className="logo"` as the relevant parent class.
+
+```
+
+
+
+```
+
+In the styled component, we find ".logo", add the `svg` element, and within that add the class that is generated by the styled-component plugin, in our example it is `.layer5-colorMode_svg__colorMode1`.
+
+> Note: the styled-component generated class name is based off the file name and the colorMode class name, using the following structure:
+>
+> svg file name (`layer5-colorMode`)
+
+- a separator (`_svg___`)
+- the class name being targeted inside the SVG (`colorMode1`)
+ > this results in the class `.layer5-colorMode_svg__colorMode1`
+
+```
+ .logo {
+ margin-top: 8px;
+
+ svg {
+ width: 155px;
+ .layer5-colorMode_svg__colorMode1 {
+ fill: ${props => props.theme.whiteToGreen3C494F};
+ transition: fill 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
+ }
+ }
+ }
+```
+
+> Notes:
+>
+> - You can add presentation css attributes to `svg` similar to how you would add to an `img`.
+> - You can find the generated class name when you inspect the element in the browser console and look at the styles section of the svg code.
+> - Even though we have a default fill property in the SVG itself (just in case), the fill property in the styled component will override it.
+> - Whenever we are changing colors in a SVG, be sure to add the transition timing and style that is used for the background color in [GlobalStyle](https://github.com/layer5io/layer5/blob/master/src/sections/app.style.js) to have everything smoothly transition. Currently this property: value is
+>
+> ```
+> transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
+> ```
+
+## Changing images depending on the theme.
+
+If possible we wish to avoid using images dependent on the theme because we are required to use a conditional (which will cause a flicker of the image when the page is reloaded). If necessary, please use the following instructions.
+
+1. To change images or SVG as the image source, according to the theme, you have to import the hook `useStyledDarkMode` from the following [folder](https://github.com/layer5io/layer5/blob/master/src/theme/app/useStyledDarkMode.js), and then use the `isDark` value from `useStyledDarkMode` hook for the conditional.
+
+For example, you can view the code for [this file](https://github.com/layer5io/layer5/blob/master/src/sections/Kanvas/Kanvas-collaborate/kanvas-collaborate-banner.js).
+
+Here are the relevant parts of the code:
+
+```
+import { useStyledDarkMode } from "../../../theme/app/useStyledDarkMode";
+
+const { isDark } = useStyledDarkMode();
+
+
+```
+
+## Changing images in gatsby-image-plugin according to the theme.
+
+Procedure of changing the image for the gatsby-image is the same as we change for images, however, it is recommended to fetch two images, one for a dark theme and one for a light theme change it according to the `isDark` value as done with images.
+
+Example (For Thumbnail):
+Fetching images through Graphql. Add this in graphql query in frontmatter
+
+ darkthumbnail {
+ childImageSharp {
+ gatsbyImageData(layout: FULL_WIDTH)
+ }
+ extension
+ publicURL
+ }
+
+Change image according to isDark value:
+
+```
+
+```
+
+> Note:
+>
+> - A condition `frontmatter.darkthumbnail.publicURL !== frontmatter.thumbnail.publicURL` is added so that the image only changes if there is a difference between the thumbnail publicURLs.
+
+## Adding Images and Icons
+
+1. It is recommended to use `@react-icons/all-files` instead of `react-icons` for importing icons. The Issue with react-icons is that even though we are importing a single icon from the package/folder it still imports the complete icon folder which is creating unwanted junks of JS in the build.
+2. It is recommended to use Gatsby's `` instead of `` tag to display static images on the site **except for SVG images**. This performs automatic image optimization, thereby improving site performance.
+3. Avoid creating duplicate copies of the same image under different folders. All images must be imported from `/assets/images` folder.
+
+## Site Performance Considerations
+
+1. Analyze page load metrics of mobile version in lighthouse report (see status of GitHub workflow on your open PR).
+2. While creating a new page make sure to use Gatsby Head API for SEO.
+3. Prefer using `loading="eager"` for Hero images to improve LCP(Largest Contentful Paint) and FCP(First Contentful Paint).
+4. Optimise page by deferring loading of third party scripts. You can use [off-main-thread](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-script/#off-main-thread-strategy-experimental) in Script API.
+5. Prefer Code Splitting using [loadable](https://github.com/gregberge/loadable-components) to lazy load heavy components which are not in the viewport.
+
+Note:- You can also refer to [Improving Site Performance](https://www.gatsbyjs.com/docs/how-to/performance/improving-site-performance/), [web.dev](https://web.dev/vitals/).
+
+## Updating/Creating a Community Member Profile
+
+Layer5 community members are an integral part of what makes Layer5 and its projects successful. Prominently highlighting our members and their works is something that we think is important. To initiate adding a new or updating an existing community member profile, be sure to use the community member [issue template](https://github.com/layer5io/layer5/issues/new?assignees=&labels=area%2Fcommunity%2C+help+wanted%2C+framework%2Fgatsby%2C+language%2Fmarkdown%2C+good+first+issue&template=community_member_profile.md&title=%5BCommunity%5D+Member+Profile%3A). When creating or updating a community member profile, use the [profile template](https://github.com/layer5io/layer5/tree/master/src/collections/members/_member-profile-template). You can easily understand how the template is used by reviewing other profiles.
+
+### Badges for Community Members
+
+Badges are a great way of highlighting the area of contribution by any given community member. A variety of badges exist so that community members and their efforts may be affiliated with a particular project or with a community initiative. An example of how a badge is assigned using markdown can be found [here](https://github.com/layer5io/layer5/blob/master/src/collections/members/lee-calcote/index.mdx), and it will appear [this way](https://layer5.io/community/members/lee-calcote) on a member profile.
+
+#### Possible Badges:
+
+- Community
+- Docker Extension
+- Docs
+- Meshery Catalog
+- Kanvas
+- Landscape
+- ImageHub
+- Meshery
+- Meshery Operator
+- SMP
+- Nighthawk
+- Patterns
+- UI/UX Design
+- Writer Program
+
+## Updating the Service Mesh Landscape
+
+Another common site update includes the updation of the Service Mesh Landscape. The service mesh landscape is powered by Gatsby.js. To update the landscape, fork this repository, clone it, create a branch and navigate to the **src/collections/landscape** folder.
+
+Make sure to open a [new issue](https://github.com/layer5io/layer5/issues/new?assignees=&labels=area%2Flandscape&template=landscape.md&title=%5BLandscape%5D) first. Following is a list of files that you may edit and make the necessary updates (if appropriate):
+
+- [non-functional.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/non-functional.js) - overview of various service meshes
+- [meshes.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/meshes.js) - list of individual service mesh details
+- [proxies.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/proxies.js) - list of individual modern proxies
+- [gateway.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/gateways.js) - list of API gateways
+- [load-balancer.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/load-balancer.js) - list of load balancers
+
+Entries should be listed in alphabetical order. Data provided to the `smi.js` is dynamic and based upon results from conformance tests run using Meshery.
+
+To update the Service Mesh Timeline, add the new service mesh in the [non-functional.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/non-functional.js) file. Add an `announce-date` key for the service mesh, then add a `timeline-order` key having a value 1+`maximum value of timeline-order` till now, to list the service mesh in the timeline correctly.
+
+# How to Contribute
+
+## Prerequisites
+
+Make sure you have the following prerequisites installed on your operating system before you start contributing:
+
+- [Nodejs and npm](https://nodejs.org/en/)
+
+ To verify run:
+
+ ```
+ node -v
+ ```
+
+ ```
+ npm -v
+ ```
+
+- [Gatsby.js](https://www.gatsbyjs.com/)
+
+ To verify run:
+
+ ```
+ gatsby --version
+ ```
+
+**Note:** If you're on a _Windows environment_ then it is highly recommended that you install [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/install) both for performance and ease of use. Refer to the [documentation](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/gatsby-on-wsl) for the installation of _Gatsby.js on WSL_.
+
+## Set up your Local Development Environment
+
+Follow the following instructions to start contributing.
+
+**1.** Fork [this](https://github.com/layer5io/layer5) repository.
+
+**2.** Clone your forked copy of the project.
+
+```
+git clone --depth=1 https://github.com//layer5.git
+```
+
+**3.** Navigate to the project directory.
+
+```
+cd layer5
+```
+
+**4.** Add a reference(remote) to the original repository.
+
+```
+git remote add upstream https://github.com/layer5io/layer5.git
+```
+
+**5.** Check the remotes for this repository.
+
+```
+git remote -v
+```
+
+**6.** Always take a pull from the upstream repository to your master branch to keep it at par with the main project (updated repository).
+
+```
+git pull upstream master
+```
+
+**7.** Create a new branch.
+
+```
+git checkout -b
+```
+
+**8.** Install the dependencies for running the site.
+
+```
+make setup
+```
+
+**9.** Make the desired changes.
+
+**10.** Run the site locally to preview changes.
+
+```
+make site
+```
+
+This will run a local webserver with "live reload" conveniently enabled. ( **NOTE**: while using the make command on Windows, there sometimes arises an error in identifying the command even after it is installed (unrecognized command), this is because the PATH for the binary might not be set correctly ).
+
+**11.** Track your changes.
+
+```
+git add .
+```
+
+**12.** Commit your changes. To contribute to this project, you must agree to the [Developer Certificate of Origin (DCO)](#signing-off-on-commits) for each commit you make.
+
+```
+git commit --signoff -m ""
+```
+
+or you could go with the shorter format for the same, as shown below.
+
+```
+git commit -s -m ""
+```
+
+**13.** While you are working on your branch, other developers may update the `master` branch with their branch. This action means your branch is now out of date with the `master` branch and missing content. So to fetch the new changes, follow along:
+
+```
+git checkout master
+git fetch origin master
+git merge upstream/master
+git push origin
+```
+
+Now you need to merge the `master` branch into your branch. This can be done in the following way:
+
+```
+git checkout
+git merge master
+```
+
+**14.** Push the committed changes in your feature branch to your remote repo.
+
+```
+git push -u origin
+```
+
+**15.** Once you’ve committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. Please ensure that you compare your feature branch to the desired branch of the repo you are supposed to make a PR to. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes in your development branch and update it.
+
+### Lint Rules
+
+Layer5 uses ESLint to maintain code quality and consistency in our UI code. Use this command to trigger a lint check:
+
+```sh
+make lint
+```
+
+> Note:
+> - Eslint in Gatsby requires generating config files from CLI. Run `gatsby build` or `gatsby develop` if you face this error during linting.
+
+
+## Signing-off on Commits
+
+To contribute to this project, you must agree to the **Developer Certificate of
+Origin (DCO)** for each commit you make. The DCO is a simple statement that you,
+as a contributor, have the legal right to make the contribution.
+
+See the [DCO](https://developercertificate.org) file for the full text of what you must agree to
+and how it works [here](https://github.com/probot/dco#how-it-works).
+To signify that you agree to the DCO for contributions, you simply add a line to each of your
+git commit messages:
+
+```
+Signed-off-by: Jane Smith
+```
+
+**Note:** you don't have to manually include this line on your commits, git does that for you as shown below:
+
+```
+$ git commit -s -m “my commit message w/signoff”
+```
+
+In most cases, git automatically adds the signoff to your commit with the use of
+`-s` or `--signoff` flag to `git commit`. You must use your real name and a reachable email
+address (sorry, no pseudonyms or anonymous contributions).
+
+To ensure all your commits are signed, you may choose to add this alias to your global `.gitconfig`:
+
+_~/.gitconfig_
+
+```
+[alias]
+ amend = commit -s --amend
+ cm = commit -s -m
+ commit = commit -s
+```
+
+Or you may configure your IDE, for example, Visual Studio Code to automatically sign-off commits for you:
+
+
+
+## FYI regarding the dev environment
+
+### Dev and Browser Warnings You May Encounter
+
+Note:
+
+- These are **non-blocking warnings** you can expect to see in your terminal or browser while working in local development environment.
+- They do not impact the performance of the code and are unrelated to your contributions.
+- These will not show in `build` or `production` mode.
+- These are being documented to minimize confusion for the user while doing development.
+
+---
+
+> warn ./node_modules/react-accessible-accordion/dist/es/index.js
+> Attempted import error: 'useId' is not exported from 'react' (imported as 'useId').
+
+and
+
+> client.js:196 export 'useId' (imported as 'useId') was not found in 'react' (possible exports: Children, Component, Fragment, Profiler, PureComponent, StrictMode, Suspense, \_\_SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED, cloneElement, createContext, createElement, createFactory, createRef, forwardRef, isValidElement, lazy, memo, useCallback, useContext, useDebugValue, useEffect, useImperativeHandle, useLayoutEffect, useMemo, useReducer, useRef, useState, version)
+
+Where/When:
+
+- In terminal: after `npm start`
+- In browser: loading https://layer5.io
+
+Reason: [https://github.com/springload/react-accessible-accordion/issues/351](https://github.com/springload/react-accessible-accordion/issues/351)
+
+> V5 is a release we cut explicitly for React 18 support (Hence the major upgrade, this was a breaking change, the webpack fix would not work as we are using React 18 new APIs), we are sticking with V4 for React 17 and under compatibility, using V4 has no functional difference outside of React version compatibility.
+
+Layer5 currently using:
+"react-accessible-accordion": "^5.0.0"
+react": "^17.0.2"
+
+To clear the warning:
+Upgrade the `react`package to ^18. However upgrading may introduce too many breaking changes and complexity.
+
+---
+
+> Warning: Each child in a list should have a unique "key" prop.
+> Check the top-level render call using . See https://reactjs.org/link/warning-keys for more information.
+> at title
+
+Where/When:
+
+- In terminal: after `npm start` and loading page
+
+Reason: In this version of Gatsby (4.20), the file:
+`node_modules/gatsby/cache-dir/head/head-export-handler-for-ssr.js` is missing code to assign `key` prop to each head tag included in the `SEO` component.
+
+To clear the warning:
+This could be resolved by adding code to the package, but requires too much complexity to include for each user. This warning is cleared in later versions of Gatsby.
diff --git a/content-learn/mastering-kubernetes-for-engineers/index.mdx b/content-learn/mastering-kubernetes-for-engineers/index.mdx
index 8d4d3cc692fa..6ef8a21dfad6 100644
--- a/content-learn/mastering-kubernetes-for-engineers/index.mdx
+++ b/content-learn/mastering-kubernetes-for-engineers/index.mdx
@@ -1,14 +1,14 @@
----
-title: 'Mastering Kubernetes for Engineers'
-description: 'Learn how to configure your Kubernetes clusters and manage the lifecycle of your workloads'
-order: 4
-themeColor: '#3C494F'
-cardImage: '../../src/assets/images/meshery/icon-only/meshery-logo-light.webp'
-courses: 0
-disabled: yes
----
-
-
\ No newline at end of file
+---
+title: 'Mastering Kubernetes for Engineers'
+description: 'Learn how to configure your Kubernetes clusters and manage the lifecycle of your workloads'
+order: 4
+themeColor: '#3C494F'
+cardImage: '../../src/assets/images/meshery/icon-only/meshery-logo-light.webp'
+courses: 0
+disabled: yes
+---
+
+{/*
+ This file is only used to render the courses list within a learning path.
+ Check the Learn-Layer5 folder under src/sections/, src/templates for more understanding of how the data is used
+*/}
\ No newline at end of file
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/index.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/index.mdx
index 6b6c163414a9..6824ba130603 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/index.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/index.mdx
@@ -1,35 +1,29 @@
----
-docType: "Course"
-title: "Course"
-description: "A course which teaches advanced concepts of service meshes and how to use them in an application effectively."
-courseTitle: "Advance Concepts of Service Meshes - Hands On"
-themeColor: "#466BB0"
-order: 2
-videos: 3
-lectures: 8
-cardImage: "../../../src/assets/images/service-mesh-icons/istio-white.svg"
-meshesYouLearn:
- [
- {
- imagepath: "../../../src/assets/images/service-mesh-icons/istio.svg",
- name: "Istio",
- },
- {
- imagepath: "../../../src/assets/images/service-mesh-icons/linkerd.webp",
- name: "Linkerd",
- }
- ]
-toc:
- [
- 'getting-started',
- 'deploy-an-application',
- 'expose-services',
- 'observability',
- 'traffic-management',
- 'service-security-capabilities',
- 'webassembly-and-intelligent-data-planes',
- 'conclusion',
- ]
----
-
-Chapters available
+---
+docType: "Course"
+title: "Course"
+description: "A course which teaches advanced concepts of service meshes and how to use them in an application effectively."
+courseTitle: "Advance Concepts of Service Meshes - Hands On"
+themeColor: "#466BB0"
+order: 2
+videos: 3
+lectures: 8
+cardImage: "../../../src/assets/images/service-mesh-icons/istio-white.svg"
+meshesYouLearn:
+ - imagepath: "../../../src/assets/images/service-mesh-icons/istio.svg"
+ name: "Istio"
+ - imagepath: "../../../src/assets/images/service-mesh-icons/linkerd.webp"
+ name: "Linkerd"
+toc:
+ [
+ 'getting-started',
+ 'deploy-an-application',
+ 'expose-services',
+ 'observability',
+ 'traffic-management',
+ 'service-security-capabilities',
+ 'webassembly-and-intelligent-data-planes',
+ 'conclusion',
+ ]
+---
+
+Chapters available
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/conclusion.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/conclusion.mdx
index 30a396acc55f..6dc00f5195df 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/conclusion.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/conclusion.mdx
@@ -1,27 +1,27 @@
----
-docType: "Chapter"
-chapterTitle: "Conclusion"
-description: "As a self-service engineering platform, Meshery enables collaborative design and operation of cloud native infrastructure."
-videos: 4
-lectures: 12
-order: 8
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-
-
-
- Deploying Sample App with Automatic sidecar injection
-
-
-
-Istio, deployed as part of this workshop, will also deploy the sidecar injector.
-Let us now verify sidecar injector deployment.
-
-```sh
-kubectl -n istio-system get configmaps istio-sidecar-injector
-```
-
-Output:
-
-```sh
-NAME DATA AGE
-istio-sidecar-injector 2 9h
-```
-
-NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the [selector](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors).
-
-```sh
-kubectl get namespace -L istio-injection
-```
-
-Output:
-
-```sh
-NAME STATUS AGE ISTIO-INJECTION
-default Active 1h enabled
-istio-system Active 1h disabled
-kube-public Active 1h
-kube-system Active 1h
-```
-
-Using Meshery, navigate to the Istio management page.
-
-1. Enter `default` in the `Namespace` field.
-1. Click the (+) icon on the `Sample Application` card and select `BookInfo Application` from the list.
-
-This will do 3 things:
-
-1. Label `default` namespace for sidecar injection.
-1. Deploys all the BookInfo services in the `default` namespace.
-1. Deploys the virtual service and gateway needed to expose the BookInfo's productpage application in the `default` namespace.
-
-
- Verify Bookinfo deployment{" "}
-
-
-1. Verify that the deployments are all in a state of AVAILABLE before continuing.
-
-```sh
-watch kubectl get deployment
-```
-
-2. Choose a service, for instance `productpage`, and view it's container configuration:
-
-```sh
-kubectl get po
-
-kubectl describe pod productpage-v1-.....
-```
-
-3. Examine details of the services:
-
-```sh
-kubectl describe svc productpage
-```
-
-Next, you will expose the BookInfo application to be accessed external from the cluster.
-
-
-
Alternative: Manual installation
-Follow this if the above steps did not work for you
-
-
-
-
Label namespace for injection
-
-Label the default namespace with istio-injection=enabled
-
-```sh
-kubectl label namespace default istio-injection=enabled
-```
-
-```sh
-kubectl get namespace -L istio-injection
-```
-
-Output:
-
-```sh
-NAME STATUS AGE ISTIO-INJECTION
-default Active 1h enabled
-istio-system Active 1h disabled
-kube-public Active 1h
-kube-system Active 1h
-```
-
-
Deploy BookInfo
-
-
-Applying this yaml file included in the Istio package you collected in [Getting Started](./getting-started) will deploy the BookInfo app in you cluster.
-
-```sh
-kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml
-```
-
-
- Deploy Gateway and Virtual Service for BookInfo app
-
Use this only when Automatic Sidecar injection doesn't work
-
-To do a manual sidecar injection we will be using `istioctl` command:
-
-```sh
-curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f - > newBookInfo.yaml
-```
-
-Observing the new yaml file reveals that additional container Istio Proxy has been added to the Pods with necessary configurations:
-
-```
- image: docker.io/istio/proxyv2:1.3.0
- imagePullPolicy: IfNotPresent
- name: istio-proxy
-```
-
-We need to now deploy the new yaml using `kubectl`
-
-```sh
-kubectl apply -f newBookInfo.yaml
-```
-
-To do both in a single command:
-
-```sh
-kubectl apply -f <(curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f -)
-```
-
-Now continue to [Verify Bookinfo deployment](#verify).
-
-
+---
+docType: "Chapter"
+chapterTitle: "Deploy a sample application"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 2
+---
+
+
+import BookInfoOffMesh from "../../../../src/assets/images/learn-layer5/istio/bookinfo-off-mesh.webp";
+import BookInfoOnMesh from "../../../../src/assets/images/learn-layer5/istio/bookinfo-on-mesh.webp";
+
+
+
+To play with Istio and demonstrate some of it's capabilities, you will deploy the example BookInfo application, which is included the Istio package.
+
+
What is the Bookinfo Application
+
+This application is a polyglot composition of microservices are written in
+different languages and sample BookInfo application displays information about a
+book, similar to a single catalog entry of an online book store. Displayed on
+the page is a description of the book, book details (ISBN, number of pages, and
+so on), and a few book reviews.
+
+The end-to-end architecture of the application is shown in the figure.
+
+
+
+
+
+
+_Figure: BookInfo deployed off the mesh_
+
+
+It’s worth noting that these services have no dependencies on Istio, but make an
+interesting service mesh example, particularly because of the multitude of services,
+languages and versions for the reviews service.
+
+As shown in the figure below, proxies are sidecarred to each of the application containers.
+
+
+
+
+
+
+_Figure: BookInfo deployed on the mesh_
+
+
+Sidecars proxy can be either manually or automatically injected into the pods. Automatic
+sidecar injection requires that your Kubernetes api-server supports `admissionregistration.k8s.io/v1`
+or `admissionregistration.k8s.io/v1beta1` or `admissionregistration.k8s.io/v1beta2`
+APIs. Verify whether your Kubernetes deployment supports these APIs by executing:
+
+```sh
+kubectl api-versions | grep admissionregistration
+```
+
+If your environment **does NOT** supports either of these two APIs, then you may use [manual sidecar injection](#manual-sidecar-inj) to deploy the sample app.
+
+As part of Istio deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
+
+
+
+ Deploying Sample App with Automatic sidecar injection
+
+
+
+Istio, deployed as part of this workshop, will also deploy the sidecar injector.
+Let us now verify sidecar injector deployment.
+
+```sh
+kubectl -n istio-system get configmaps istio-sidecar-injector
+```
+
+Output:
+
+```sh
+NAME DATA AGE
+istio-sidecar-injector 2 9h
+```
+
+NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the [selector](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors).
+
+```sh
+kubectl get namespace -L istio-injection
+```
+
+Output:
+
+```sh
+NAME STATUS AGE ISTIO-INJECTION
+default Active 1h enabled
+istio-system Active 1h disabled
+kube-public Active 1h
+kube-system Active 1h
+```
+
+Using Meshery, navigate to the Istio management page.
+
+1. Enter `default` in the `Namespace` field.
+1. Click the (+) icon on the `Sample Application` card and select `BookInfo Application` from the list.
+
+This will do 3 things:
+
+1. Label `default` namespace for sidecar injection.
+1. Deploys all the BookInfo services in the `default` namespace.
+1. Deploys the virtual service and gateway needed to expose the BookInfo's productpage application in the `default` namespace.
+
+
+ Verify Bookinfo deployment{" "}
+
+
+1. Verify that the deployments are all in a state of AVAILABLE before continuing.
+
+```sh
+watch kubectl get deployment
+```
+
+2. Choose a service, for instance `productpage`, and view it's container configuration:
+
+```sh
+kubectl get po
+
+kubectl describe pod productpage-v1-.....
+```
+
+3. Examine details of the services:
+
+```sh
+kubectl describe svc productpage
+```
+
+Next, you will expose the BookInfo application to be accessed external from the cluster.
+
+
+
Alternative: Manual installation
+Follow this if the above steps did not work for you
+
+
+
+
Label namespace for injection
+
+Label the default namespace with istio-injection=enabled
+
+```sh
+kubectl label namespace default istio-injection=enabled
+```
+
+```sh
+kubectl get namespace -L istio-injection
+```
+
+Output:
+
+```sh
+NAME STATUS AGE ISTIO-INJECTION
+default Active 1h enabled
+istio-system Active 1h disabled
+kube-public Active 1h
+kube-system Active 1h
+```
+
+
Deploy BookInfo
+
+
+Applying this yaml file included in the Istio package you collected in [Getting Started](./getting-started) will deploy the BookInfo app in you cluster.
+
+```sh
+kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml
+```
+
+
+ Deploy Gateway and Virtual Service for BookInfo app
+
Use this only when Automatic Sidecar injection doesn't work
+
+To do a manual sidecar injection we will be using `istioctl` command:
+
+```sh
+curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f - > newBookInfo.yaml
+```
+
+Observing the new yaml file reveals that additional container Istio Proxy has been added to the Pods with necessary configurations:
+
+```
+ image: docker.io/istio/proxyv2:1.3.0
+ imagePullPolicy: IfNotPresent
+ name: istio-proxy
+```
+
+We need to now deploy the new yaml using `kubectl`
+
+```sh
+kubectl apply -f newBookInfo.yaml
+```
+
+To do both in a single command:
+
+```sh
+kubectl apply -f <(curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f -)
+```
+
+Now continue to [Verify Bookinfo deployment](#verify).
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/expose-services.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/expose-services.mdx
index a19a0e925e59..b1a4a316dc70 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/expose-services.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/expose-services.mdx
@@ -1,253 +1,253 @@
----
-docType: "Chapter"
-chapterTitle: "Exposing services through Istio Ingress Gateway"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 3
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-The components deployed on the service mesh by default are not exposed outside the cluster. An Ingress Gateway is deployed as a Kubernetes service of type LoadBalancer (or NodePort). To make Bookinfo accessible external to the cluster, you have to create an `Istio Gateway` for the Bookinfo application and also define an `Istio VirtualService` with the routes we need.
-
-
-
-
-
Inspecting the Istio Ingress Gateway
-
-
-The ingress gateway gets exposed as a normal Kubernetes service of type LoadBalancer
-(or NodePort):
-
-```sh
-kubectl get svc istio-ingressgateway -n istio-system -o yaml
-```
-
-Because the Istio Ingress Gateway is an Envoy Proxy you can inspect it using the admin routes. First find the name of the istio-ingressgateway:
-
-```sh
-kubectl get pods -n istio-system
-```
-
-Copy and paste your ingress gateway's pod name. Execute:
-
-```sh
-kubectl -n istio-system exec -it bash
-```
-
-You can view the statistics, listeners, routes, clusters and server info for the Envoy proxy by forwarding the local port:
-
-```sh
-curl localhost:15000/help
-curl localhost:15000/stats
-curl localhost:15000/listeners
-curl localhost:15000/clusters
-curl localhost:15000/server_info
-```
-
-See the [admin docs](https://www.envoyproxy.io/docs/envoy/latest/operations/admin) for more details.
-
-Also it can be helpful to look at the log files of the Istio ingress controller to see what request is being routed.
-
-Before we check the logs, let us get out of the container back on the host:
-
-```sh
-exit
-```
-
-Now let us find the ingress pod and output the log:
-
-```sh
-kubectl logs istio-ingressgateway-... -n istio-system
-```
-
-
View Istio Ingress Gateway for Bookinfo
-
-
-
View the Gateway and VirtualServices
-
-Check the created `Istio Gateway` and `Istio VirtualService` to see the changes deployed:
-
-```sh
-kubectl get gateway
-kubectl get gateway -o yaml
-
-kubectl get virtualservices
-kubectl get virtualservices -o yaml
-```
-
-
- Find the external port of the Istio Ingress Gateway by running:
-
-
-```sh
-kubectl get service istio-ingressgateway -n istio-system -o wide
-```
-
-To just get the first port of istio-ingressgateway service, we can run this:
-
-```sh
-kubectl get service istio-ingressgateway -n istio-system --template='{{(index .spec.ports 1).nodePort}}'
-```
-
-
Create a DNS entry:
-
-Modify your local `/etc/hosts` file to add an entry for your sample application.
-
-`127.0.0.1. bookinfo.meshery.io`
-
-The HTTP port is usually 31380.
-
-Or run these commands to retrieve the full URL:
-
-```sh
-echo "http://$(kubectl get nodes --selector=kubernetes.io/role!=master -o jsonpath={.items[0].status.addresses[?\(@.type==\"InternalIP\"\)].address}):$(kubectl get svc istio-ingressgateway -n istio-system -o jsonpath='{.spec.ports[1].nodePort}')/productpage"
-```
-
-Docker Desktop users please use `http://localhost/productpage` to access product page in your browser.
-
-
Apply default destination rules
-
-Before we start playing with Istio's traffic management capabilities we need to define the available versions of the deployed services. They are called subsets, in destination rules.
-
-Using Meshery, navigate to the Custom yaml page, and apply the below to create the subsets for BookInfo:
-
-```sh
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: productpage
-spec:
- host: productpage
- subsets:
- - name: v1
- labels:
- version: v1
----
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: reviews
-spec:
- host: reviews
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
- - name: v3
- labels:
- version: v3
----
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: ratings
-spec:
- host: ratings
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
- - name: v2-mysql
- labels:
- version: v2-mysql
- - name: v2-mysql-vm
- labels:
- version: v2-mysql-vm
----
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: details
-spec:
- host: details
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
-```
-
-This creates destination rules for each of the BookInfo services and defines version subsets
-
-In a few seconds we should be able to verify the destination rules created by using the command below:
-
-```sh
-kubectl get destinationrules
-
-
-kubectl get destinationrules -o yaml
-```
-
-
Browse to BookInfo
-
-Browse to the website of the Bookinfo. To view the product page, you will have to append
-`/productpage` to the url.
-
-
Reload Page
-
-Now, reload the page multiple times and notice how it round robins between v1, v2 and v3 of the reviews service.
-
-
- Inspect the Istio proxy of the productpage pod
-
-
-To better understand the istio proxy, let's inspect the details. Let us `exec` into the productpage pod to find the proxy details. To do so we need to first find the full pod name and then `exec` into the istio-proxy container:
-
-```sh
-kubectl get pods
-kubectl exec -it productpage-v1-... -c istio-proxy sh
-```
-
-Once in the container look at some of the envoy proxy details by inspecting it's config file:
-
-```sh
-ps aux
-ls -l /etc/istio/proxy
-cat /etc/istio/proxy/envoy-rev0.json
-```
-
-For more details on envoy proxy please check out their [admin docs](https://www.envoyproxy.io/docs/envoy/v1.5.0/operations/admin).
-
-As a last step, lets exit the container:
-
-```sh
-exit
-```
-
-
-
Alternative: Manual installation
-Follow this if the above steps did not work for you
-
-
-
-
-
Default destination rules
-
-Run the following command to create default destination rules for the Bookinfo services:
-
-```sh
-kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml
-```
-
-
- Configure the Bookinfo route with the Istio Ingress gateway
-
-
-We can create a virtualservice & gateway for bookinfo app in the ingress gateway by running the following:
-
-```sh
-kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Exposing services through Istio Ingress Gateway"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 3
+---
+
+
+
+
+The components deployed on the service mesh by default are not exposed outside the cluster. An Ingress Gateway is deployed as a Kubernetes service of type LoadBalancer (or NodePort). To make Bookinfo accessible external to the cluster, you have to create an `Istio Gateway` for the Bookinfo application and also define an `Istio VirtualService` with the routes we need.
+
+
+
+
+
Inspecting the Istio Ingress Gateway
+
+
+The ingress gateway gets exposed as a normal Kubernetes service of type LoadBalancer
+(or NodePort):
+
+```sh
+kubectl get svc istio-ingressgateway -n istio-system -o yaml
+```
+
+Because the Istio Ingress Gateway is an Envoy Proxy you can inspect it using the admin routes. First find the name of the istio-ingressgateway:
+
+```sh
+kubectl get pods -n istio-system
+```
+
+Copy and paste your ingress gateway's pod name. Execute:
+
+```sh
+kubectl -n istio-system exec -it bash
+```
+
+You can view the statistics, listeners, routes, clusters and server info for the Envoy proxy by forwarding the local port:
+
+```sh
+curl localhost:15000/help
+curl localhost:15000/stats
+curl localhost:15000/listeners
+curl localhost:15000/clusters
+curl localhost:15000/server_info
+```
+
+See the [admin docs](https://www.envoyproxy.io/docs/envoy/latest/operations/admin) for more details.
+
+Also it can be helpful to look at the log files of the Istio ingress controller to see what request is being routed.
+
+Before we check the logs, let us get out of the container back on the host:
+
+```sh
+exit
+```
+
+Now let us find the ingress pod and output the log:
+
+```sh
+kubectl logs istio-ingressgateway-... -n istio-system
+```
+
+
View Istio Ingress Gateway for Bookinfo
+
+
+
View the Gateway and VirtualServices
+
+Check the created `Istio Gateway` and `Istio VirtualService` to see the changes deployed:
+
+```sh
+kubectl get gateway
+kubectl get gateway -o yaml
+
+kubectl get virtualservices
+kubectl get virtualservices -o yaml
+```
+
+
+ Find the external port of the Istio Ingress Gateway by running:
+
+
+```sh
+kubectl get service istio-ingressgateway -n istio-system -o wide
+```
+
+To just get the first port of istio-ingressgateway service, we can run this:
+
+```sh
+kubectl get service istio-ingressgateway -n istio-system --template='{{(index .spec.ports 1).nodePort}}'
+```
+
+
Create a DNS entry:
+
+Modify your local `/etc/hosts` file to add an entry for your sample application.
+
+`127.0.0.1. bookinfo.meshery.io`
+
+The HTTP port is usually 31380.
+
+Or run these commands to retrieve the full URL:
+
+```sh
+echo "http://$(kubectl get nodes --selector=kubernetes.io/role!=master -o jsonpath={.items[0].status.addresses[?\(@.type==\"InternalIP\"\)].address}):$(kubectl get svc istio-ingressgateway -n istio-system -o jsonpath='{.spec.ports[1].nodePort}')/productpage"
+```
+
+Docker Desktop users please use `http://localhost/productpage` to access product page in your browser.
+
+
Apply default destination rules
+
+Before we start playing with Istio's traffic management capabilities we need to define the available versions of the deployed services. They are called subsets, in destination rules.
+
+Using Meshery, navigate to the Custom yaml page, and apply the below to create the subsets for BookInfo:
+
+```sh
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: productpage
+spec:
+ host: productpage
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+---
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: reviews
+spec:
+ host: reviews
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+ - name: v2
+ labels:
+ version: v2
+ - name: v3
+ labels:
+ version: v3
+---
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: ratings
+spec:
+ host: ratings
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+ - name: v2
+ labels:
+ version: v2
+ - name: v2-mysql
+ labels:
+ version: v2-mysql
+ - name: v2-mysql-vm
+ labels:
+ version: v2-mysql-vm
+---
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: details
+spec:
+ host: details
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+ - name: v2
+ labels:
+ version: v2
+```
+
+This creates destination rules for each of the BookInfo services and defines version subsets
+
+In a few seconds we should be able to verify the destination rules created by using the command below:
+
+```sh
+kubectl get destinationrules
+
+
+kubectl get destinationrules -o yaml
+```
+
+
Browse to BookInfo
+
+Browse to the website of the Bookinfo. To view the product page, you will have to append
+`/productpage` to the url.
+
+
Reload Page
+
+Now, reload the page multiple times and notice how it round robins between v1, v2 and v3 of the reviews service.
+
+
+ Inspect the Istio proxy of the productpage pod
+
+
+To better understand the istio proxy, let's inspect the details. Let us `exec` into the productpage pod to find the proxy details. To do so we need to first find the full pod name and then `exec` into the istio-proxy container:
+
+```sh
+kubectl get pods
+kubectl exec -it productpage-v1-... -c istio-proxy sh
+```
+
+Once in the container look at some of the envoy proxy details by inspecting it's config file:
+
+```sh
+ps aux
+ls -l /etc/istio/proxy
+cat /etc/istio/proxy/envoy-rev0.json
+```
+
+For more details on envoy proxy please check out their [admin docs](https://www.envoyproxy.io/docs/envoy/v1.5.0/operations/admin).
+
+As a last step, lets exit the container:
+
+```sh
+exit
+```
+
+
+
Alternative: Manual installation
+Follow this if the above steps did not work for you
+
+
+
+
+
Default destination rules
+
+Run the following command to create default destination rules for the Bookinfo services:
+
+```sh
+kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml
+```
+
+
+ Configure the Bookinfo route with the Istio Ingress gateway
+
+
+We can create a virtualservice & gateway for bookinfo app in the ingress gateway by running the following:
+
+```sh
+kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/getting-started.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/getting-started.mdx
index 316433b787d8..f7c9c748a841 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/getting-started.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/getting-started.mdx
@@ -1,132 +1,132 @@
----
-docType: "Chapter"
-chapterTitle: "Getting Started"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 1
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import InstallIstio from "../../../../src/assets/images/learn-layer5/istio/install-istio.webp";
-import IstioAdapter from "../../../../src/assets/images/learn-layer5/istio/istio-adapter.webp";
-
-
-
-
Setup Istio
-
-Now that we have a Kubernetes cluster and Meshery, we are ready to download and deploy Istio resources.
-
-
-
-Using Meshery, select `Istio` from the `Management` menu.
-
-
-
-
-
-In the Istio management page:
-
-1. Type `istio-system` into the namespace field.
-1. Click the (+) icon on the `Install` card and select `Latest Istio` to install the latest version of Istio.
-
-
-
-
-
-
Alternative:Manual installation
-Perform the below steps if the above steps doesn't work for you.
-
-
-
-
-
-
-You will download and deploy the latest Istio resources on your Kubernetes cluster.
-
-**_Note to Docker Desktop users:_** Please ensure your Docker VM has at least 4GiB of Memory, which is required for all services to run.
-
-On your local machine, execute:
-
-```sh
-curl -L https://git.io/getLatestIstio | ISTIO_VERSION=1.7.3 sh -
-```
-
-
-
-On a \*nix system, you can setup `istioctl` by doing the following:
-
-```sh
-brew install istioctl
-```
-
-Alternatively, change into the Istio package directory and add the `istioctl` client to your PATH environment variable.
-
-```sh
-cd istio-*
-export PATH=$PWD/bin:$PATH
-```
-
-Verify `istioctl` is available:
-
-```sh
-istioctl version
-```
-
-Check if the cluster is ready for installation:
-
-```sh
-istioctl verify-install
-```
-
-
-
-In the Istio management page:
-
-1. Click the (+) icon on the `Validate Service Mesh Configuration` card.
-1. Select `Verify Installation` to verify the installation of Istio.
-
-
Alternatively:
-
-Istio is deployed in a separate Kubernetes namespace `istio-system`. To check if Istio is deployed, and also, to see all the pieces that are deployed, execute the following:
-
-```sh
-kubectl get all -n istio-system
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Getting Started"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 1
+---
+
+
+import InstallIstio from "../../../../src/assets/images/learn-layer5/istio/install-istio.webp";
+import IstioAdapter from "../../../../src/assets/images/learn-layer5/istio/istio-adapter.webp";
+
+
+
+
Setup Istio
+
+Now that we have a Kubernetes cluster and Meshery, we are ready to download and deploy Istio resources.
+
+
+
+Using Meshery, select `Istio` from the `Management` menu.
+
+
+
+
+
+In the Istio management page:
+
+1. Type `istio-system` into the namespace field.
+1. Click the (+) icon on the `Install` card and select `Latest Istio` to install the latest version of Istio.
+
+
+
+
+
+
Alternative:Manual installation
+Perform the below steps if the above steps doesn't work for you.
+
+
+
+
+
+
+You will download and deploy the latest Istio resources on your Kubernetes cluster.
+
+**_Note to Docker Desktop users:_** Please ensure your Docker VM has at least 4GiB of Memory, which is required for all services to run.
+
+On your local machine, execute:
+
+```sh
+curl -L https://git.io/getLatestIstio | ISTIO_VERSION=1.7.3 sh -
+```
+
+
+
+On a \*nix system, you can setup `istioctl` by doing the following:
+
+```sh
+brew install istioctl
+```
+
+Alternatively, change into the Istio package directory and add the `istioctl` client to your PATH environment variable.
+
+```sh
+cd istio-*
+export PATH=$PWD/bin:$PATH
+```
+
+Verify `istioctl` is available:
+
+```sh
+istioctl version
+```
+
+Check if the cluster is ready for installation:
+
+```sh
+istioctl verify-install
+```
+
+
+
+In the Istio management page:
+
+1. Click the (+) icon on the `Validate Service Mesh Configuration` card.
+1. Select `Verify Installation` to verify the installation of Istio.
+
+
Alternatively:
+
+Istio is deployed in a separate Kubernetes namespace `istio-system`. To check if Istio is deployed, and also, to see all the pieces that are deployed, execute the following:
+
+```sh
+kubectl get all -n istio-system
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/observability.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/observability.mdx
index 8127fdbdb7ad..5d5c4f32588c 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/observability.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/observability.mdx
@@ -1,246 +1,246 @@
----
-docType: "Chapter"
-chapterTitle: "Observability"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 4
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import ImageAppIcon from "../../../../src/assets/images/learn-layer5/istio/istio-addons.webp";
-import GraffanaDash from "../../../../src/assets/images/learn-layer5/istio/Grafana_Istio_Dashboard.webp";
-import Prometheus from "../../../../src/assets/images/learn-layer5/istio/Prometheus.webp";
-import Jaeger from "../../../../src/assets/images/learn-layer5/istio/jaeger copy.webp";
-
-
-
-
Install Telemetry Add-ons
-
-Using Meshery, install Istio telemetry add-ons. In the Istio management page:
-
-1. Click the (+) icon on the `Apply Service Mesh Configuration` card.
-1. Select each of the following add-ons:
- 1. [Prometheus](https://prometheus.io/)
- 1. [Grafana](https://grafana.com/)
- 1. [Jaeger](https://www.jaegertracing.io/)
-
-
-
-
-
-You will use Prometheus and Grafana for collecting and viewing metrics and [Jaeger](https://www.jaegertracing.io/) collecting and viewing distributed traces. Expose each add-on external to the cluster. Each the service network typs are set to "LoadBalancer".
-
-
Service Mesh Performance and Telemetry
-
-Many of the labs require load to be placed on the sample apps. Let's generate HTTP traffic against the BookInfo application, so we can see interesting telemetry.
-
-Verify access through the Ingress Gateway:
-
-```sh
-kubectl get service istio-ingressgateway -n istio-system
-```
-
-Once we have the port, we can append the IP of one of the nodes to get the host.
-
-The URL to run a load test against will be `http://:/productpage`
-
-**Please note:** If you are using Docker Desktop, please use the IP address of your host. You can leave the port blank. For example: `http://1.2.3.4/productpage`
-
-Use the computed URL above in Meshery, in the browser, to run a load test and see the results.
-
-
- Connect Grafana (optionally, Prometheus) to Meshery.
-
-
-On the Settings page:
-
-1. Navigate to the `Metrics` tab.
-1. Enter Grafana's URL:port number and submit.
-
-
- Use Meshery to generate load and analyze performance.
-
-
-On the Performance page:
-
-1. give this load test a memorable name
-1. enter the URL to the BookInfo productpage
-1. select `Istio` in the `Service Mesh` dropdown
-1. enter a valid number for `Concurrent requests`
-1. enter a valid number for `Queries per second`
-1. enter a valid `Duration` (a number followed by `s` for seconds (OR) `m` for minutes (OR) `h` for hour)
-1. use the host IP address in the request Tab and in the advanced options, type in the header as `Host:`
-
-Click on `Run Test`. A performance test will run and statistical analysis performed. Examine the results of the test and behavior of the service mesh.
-
-Next, you will begin controlling requests to BookInfo using traffic management features.
-
-
-
Alternative: Manual installation
-Follow these steps if the above steps did not work
-
-
-
-
-
-Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress.
-
-**Option 1: Expose services with NodePort**
-To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
-
-**Option 2: Expose services with port-forwarding**
-Port-forwarding runs in the foreground. We have appended `&` to the end of the above 2 commands to run them in the background. If you donot want this behavior, please remove the `&` from the end.
-
-
Prometheus
-
-You will need to expose the Prometheus service on a port either of the two following methods:
-
-**Option 1: Expose services with NodePort**
-
-```sh
-kubectl -n istio-system edit svc prometheus
-```
-
-To find the assigned ports for Prometheus:
-
-```sh
-kubectl -n istio-system get svc prometheus
-```
-
-**Option 2: Expose Prometheus service with port-forwarding:**
-\*\*
-Expose Prometheus service with port-forwarding:
-
-```sh
-kubectl -n istio-system port-forward \
- $(kubectl -n istio-system get pod -l app=prometheus -o jsonpath='{.items[0].metadata.name}') \
- 9090:9090 &
-```
-
-Browse to `http://:` and in the `Expression` input box enter: `istio_request_bytes_count`. Click the Execute button.
-
-
-
-
-
-
-
Grafana
-
-You will need to expose the Grafana service on a port either of the two following methods:
-
-```sh
-kubectl -n istio-system edit svc grafana
-```
-
-Once this is done the services will be assigned dedicated ports on the hosts.
-
-To find the assigned ports for Grafana:
-
-```sh
-kubectl -n istio-system get svc grafana
-```
-
-**Expose Grafana service with port-forwarding:**
-
-```sh
-kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=grafana \
- -o jsonpath='{.items[0].metadata.name}') 3000:3000 &
-```
-
-
-
-
-
-
Distributed Tracing
-
-The sample Bookinfo application is configured to collect trace spans using Zipkin or Jaeger. Although Istio proxies are able to automatically send spans, it needs help from the application to tie together the entire trace. To do this applications need to propagate the appropriate HTTP headers so that when the proxies send span information to Zipkin or Jaeger, the spans can be correlated correctly into a single trace.
-
-To do this the application collects and propagates the following headers from the incoming request to any outgoing requests:
-
-- `x-request-id`
-- `x-b3-traceid`
-- `x-b3-spanid`
-- `x-b3-parentspanid`
-- `x-b3-sampled`
-- `x-b3-flags`
-- `x-ot-span-context`
-
-
-
-
-
-
-
-
-
-
-
Exposing services
-
-Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress. In this lab, we will briefly demonstrate the `NodePort` and port-forwarding ways of exposing services.
-
-
Option 1: Expose services with NodePort
-
-To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
-
-For Jaeger, either of `tracing` or `jaeger-query` can be exposed.
-
-```sh
-kubectl -n istio-system edit svc tracing
-```
-
-Once this is done the services will be assigned dedicated ports on the hosts.
-
-To find the assigned ports for Jaeger:
-
-```sh
-kubectl -n istio-system get svc tracing
-```
-
-
- Option 2: Expose services with port-forwarding
-
-
-Let us find the port Jaeger is exposed on by running the following command:
-
-```sh
-kubectl -n istio-system get svc tracing
-```
-
-You can click on the link at the top of the page which maps to the right port and it will open Jaeger UI in a new tab.
-
-
+---
+docType: "Chapter"
+chapterTitle: "Observability"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 4
+---
+
+
+import ImageAppIcon from "../../../../src/assets/images/learn-layer5/istio/istio-addons.webp";
+import GraffanaDash from "../../../../src/assets/images/learn-layer5/istio/Grafana_Istio_Dashboard.webp";
+import Prometheus from "../../../../src/assets/images/learn-layer5/istio/Prometheus.webp";
+import Jaeger from "../../../../src/assets/images/learn-layer5/istio/jaeger copy.webp";
+
+
+
+
Install Telemetry Add-ons
+
+Using Meshery, install Istio telemetry add-ons. In the Istio management page:
+
+1. Click the (+) icon on the `Apply Service Mesh Configuration` card.
+1. Select each of the following add-ons:
+ 1. [Prometheus](https://prometheus.io/)
+ 1. [Grafana](https://grafana.com/)
+ 1. [Jaeger](https://www.jaegertracing.io/)
+
+
+
+
+
+You will use Prometheus and Grafana for collecting and viewing metrics and [Jaeger](https://www.jaegertracing.io/) collecting and viewing distributed traces. Expose each add-on external to the cluster. Each the service network typs are set to "LoadBalancer".
+
+
Service Mesh Performance and Telemetry
+
+Many of the labs require load to be placed on the sample apps. Let's generate HTTP traffic against the BookInfo application, so we can see interesting telemetry.
+
+Verify access through the Ingress Gateway:
+
+```sh
+kubectl get service istio-ingressgateway -n istio-system
+```
+
+Once we have the port, we can append the IP of one of the nodes to get the host.
+
+The URL to run a load test against will be `http://:/productpage`
+
+**Please note:** If you are using Docker Desktop, please use the IP address of your host. You can leave the port blank. For example: `http://1.2.3.4/productpage`
+
+Use the computed URL above in Meshery, in the browser, to run a load test and see the results.
+
+
+ Connect Grafana (optionally, Prometheus) to Meshery.
+
+
+On the Settings page:
+
+1. Navigate to the `Metrics` tab.
+1. Enter Grafana's URL:port number and submit.
+
+
+ Use Meshery to generate load and analyze performance.
+
+
+On the Performance page:
+
+1. give this load test a memorable name
+1. enter the URL to the BookInfo productpage
+1. select `Istio` in the `Service Mesh` dropdown
+1. enter a valid number for `Concurrent requests`
+1. enter a valid number for `Queries per second`
+1. enter a valid `Duration` (a number followed by `s` for seconds (OR) `m` for minutes (OR) `h` for hour)
+1. use the host IP address in the request Tab and in the advanced options, type in the header as `Host:`
+
+Click on `Run Test`. A performance test will run and statistical analysis performed. Examine the results of the test and behavior of the service mesh.
+
+Next, you will begin controlling requests to BookInfo using traffic management features.
+
+
+
Alternative: Manual installation
+Follow these steps if the above steps did not work
+
+
+
+
+
+Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress.
+
+**Option 1: Expose services with NodePort**
+To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
+
+**Option 2: Expose services with port-forwarding**
+Port-forwarding runs in the foreground. We have appended `&` to the end of the above 2 commands to run them in the background. If you donot want this behavior, please remove the `&` from the end.
+
+
Prometheus
+
+You will need to expose the Prometheus service on a port either of the two following methods:
+
+**Option 1: Expose services with NodePort**
+
+```sh
+kubectl -n istio-system edit svc prometheus
+```
+
+To find the assigned ports for Prometheus:
+
+```sh
+kubectl -n istio-system get svc prometheus
+```
+
+**Option 2: Expose Prometheus service with port-forwarding:**
+\*\*
+Expose Prometheus service with port-forwarding:
+
+```sh
+kubectl -n istio-system port-forward \
+ $(kubectl -n istio-system get pod -l app=prometheus -o jsonpath='{.items[0].metadata.name}') \
+ 9090:9090 &
+```
+
+Browse to `http://:` and in the `Expression` input box enter: `istio_request_bytes_count`. Click the Execute button.
+
+
+
+
+
+
+
Grafana
+
+You will need to expose the Grafana service on a port either of the two following methods:
+
+```sh
+kubectl -n istio-system edit svc grafana
+```
+
+Once this is done the services will be assigned dedicated ports on the hosts.
+
+To find the assigned ports for Grafana:
+
+```sh
+kubectl -n istio-system get svc grafana
+```
+
+**Expose Grafana service with port-forwarding:**
+
+```sh
+kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=grafana \
+ -o jsonpath='{.items[0].metadata.name}') 3000:3000 &
+```
+
+
+
+
+
+
Distributed Tracing
+
+The sample Bookinfo application is configured to collect trace spans using Zipkin or Jaeger. Although Istio proxies are able to automatically send spans, it needs help from the application to tie together the entire trace. To do this applications need to propagate the appropriate HTTP headers so that when the proxies send span information to Zipkin or Jaeger, the spans can be correlated correctly into a single trace.
+
+To do this the application collects and propagates the following headers from the incoming request to any outgoing requests:
+
+- `x-request-id`
+- `x-b3-traceid`
+- `x-b3-spanid`
+- `x-b3-parentspanid`
+- `x-b3-sampled`
+- `x-b3-flags`
+- `x-ot-span-context`
+
+
+
+
+
+
+
+
+
+
+
Exposing services
+
+Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress. In this lab, we will briefly demonstrate the `NodePort` and port-forwarding ways of exposing services.
+
+
Option 1: Expose services with NodePort
+
+To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
+
+For Jaeger, either of `tracing` or `jaeger-query` can be exposed.
+
+```sh
+kubectl -n istio-system edit svc tracing
+```
+
+Once this is done the services will be assigned dedicated ports on the hosts.
+
+To find the assigned ports for Jaeger:
+
+```sh
+kubectl -n istio-system get svc tracing
+```
+
+
+ Option 2: Expose services with port-forwarding
+
+
+Let us find the port Jaeger is exposed on by running the following command:
+
+```sh
+kubectl -n istio-system get svc tracing
+```
+
+You can click on the link at the top of the page which maps to the right port and it will open Jaeger UI in a new tab.
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/service-security-capabilities.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/service-security-capabilities.mdx
index a96ed8405fc5..25460d889330 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/service-security-capabilities.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/service-security-capabilities.mdx
@@ -1,284 +1,284 @@
----
-docType: "Chapter"
-chapterTitle: "Service security capabilities"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 6
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-
Access Control
-
-You will start by denying all traffic.
-
-```yaml
-apiVersion: security.istio.io/v1beta1
-kind: AuthorizationPolicy
-metadata:
- name: deny-all
- namespace: default
-spec: {}
-```
-
-
- And then begin poking holes in your service mesh "firewall".
-
-Follow these steps if the above steps did not work
-
-
-
-
Traffic management with Istio
-
-If you haven't forked or cloned this repository, please do so now:
-
-```sh
-git clone https://github.com/layer5io/advanced-istio-service-mesh-workshop
-
-```
-
+Follow these steps if the above steps did not work
+
+
+
+
Traffic management with Istio
+
+If you haven't forked or cloned this repository, please do so now:
+
+```sh
+git clone https://github.com/layer5io/advanced-istio-service-mesh-workshop
+
+```
+
+
+```sh
+kubectl apply -f route-header/user.yaml
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/webassembly-and-intelligent-data-planes.mdx b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/webassembly-and-intelligent-data-planes.mdx
index 2624f589540f..7ceb51e538dc 100644
--- a/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/webassembly-and-intelligent-data-planes.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/istio/webassembly-and-intelligent-data-planes.mdx
@@ -1,148 +1,148 @@
----
-docType: "Chapter"
-chapterTitle: "WebAssembly and intelligent data planes"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 7
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-import installimagehub from "../../../../src/assets/images/learn-layer5/istio/install-imagehub.webp";
-import deployenvoyfilter from "../../../../src/assets/images/learn-layer5/istio/deploy-envoyfilter.webp";
-
-
-
-In this lab, you will use the sample application [Image Hub](https://github.com/layer5io/image-hub). This version of the Image Hub filter has been simplified for your lab. To self-study deeper functionality, try the other version of the Image Hub filter that is available in the Image Hub repo.
-
-
Deploy Sample Application
-
-Using Meshery, select Istio from the Management menu.
-
-In the Istio management page:
-
-1. Type default into the namespace field.
-2. Click the (+) icon on the Manage Sample Application Lifecycle card and select Image Hub Application to install the latest version of Image Hub
-
-
-
-
-
-
-
-
Load the filter
-
-Next, load the custom Envoy filter. This filter is written in Rust and is compiled against WebAssembly as it's target runtime.
-
-Using Meshery, select Istio from the Management menu.
-
-In the Istio management page:
-
-1. Type default into the namespace field.
-2. Click the (+) icon on the Apply Service Mesh Configuration card and select Envoy Filter for Image Hub to deploy the custom filter.
-
-
-
-
-
-
Send traffic
-
-
Analyze behavior
-
-Alternative, manual installation steps are provided for reference below. No need to execute these if you have performed the steps above.
-
-Manually deploy the Image Hub filter.
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: EnvoyFilter
-metadata:
- name: custom-filter
-spec:
- configPatches:
- - applyTo: HTTP_FILTER
- match:
- context: SIDECAR_OUTBOUND # will match outbound listeners in all sidecars
- listener:
- portNumber: 9080
- filterChain:
- name: envoy.http_connection_manager
- filter:
- name: "envoy.tcp_proxy"
- patch:
- operation: INSERT_BEFORE
- value:
- # This is the full filter config including the name and config or typed_config section.
- name: "envoy.filters.http.wasm"
- config:
- config:
- name: custom-filter
- rootId: my_root_id
- vmConfig:
- code:
- local:
- filename: /var/lib/imagehub/filter.wasm
- runtime: envoy.wasm.runtime.v8
- vmId: custom-filter
- allow_precompiled: true
- workloadSelector:
- labels:
- app: api-v1
- version: v1
-
-```
-Manually patch the Image Hub Deployment.
-
-```yaml
----(
- // kubectl patch deployment/api-v1 -p '
- {
- "spec": {
- "template": {
- "metadata": {
- "annotations": {
- "sidecar.istio.io/userVolumeMount": "[{\"mountPath\":\"/var/lib/imagehub\",\"name\":\"wasm-filter\"}]"
- }
- },
- "spec": {
- "initContainers": [
- {
- "command": [
- "curl",
- "-L",
- "-o",
- "/var/lib/imagehub/filter.wasm",
- "https://github.com/layer5io/advanced-istio-service-mesh-workshop/raw/master/lab-7/ratelimiter/ratelimit-filter.wasm"
- ],
- "image": "curlimages/curl",
- "imagePullPolicy": "Always",
- "name": "add-wasm",
- "resources": {},
- "terminationMessagePath": "/dev/termination-log",
- "terminationMessagePolicy": "File",
- "volumeMounts": [
- {
- "mountPath": "/var/lib/imagehub",
- "name": "wasm-filter"
- }
- ]
- }
- ],
- "volumes": [
- {
- "emptyDir": {},
- "name": "wasm-filter"
- }
- ]
- }
- }
- }
- }
-)
-// '
-
-```
-A future version of Meshery will allow you to deploy any filter from the [wasm-filters](https://github.com/layer5io/wasm-filters) repo. PR the repo to upload your custom filter and have Meshery deploy it.
-
-
+---
+docType: "Chapter"
+chapterTitle: "WebAssembly and intelligent data planes"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 7
+---
+
+
+
+import installimagehub from "../../../../src/assets/images/learn-layer5/istio/install-imagehub.webp";
+import deployenvoyfilter from "../../../../src/assets/images/learn-layer5/istio/deploy-envoyfilter.webp";
+
+
+
+In this lab, you will use the sample application [Image Hub](https://github.com/layer5io/image-hub). This version of the Image Hub filter has been simplified for your lab. To self-study deeper functionality, try the other version of the Image Hub filter that is available in the Image Hub repo.
+
+
Deploy Sample Application
+
+Using Meshery, select Istio from the Management menu.
+
+In the Istio management page:
+
+1. Type default into the namespace field.
+2. Click the (+) icon on the Manage Sample Application Lifecycle card and select Image Hub Application to install the latest version of Image Hub
+
+
+
+
+
+
+
+
Load the filter
+
+Next, load the custom Envoy filter. This filter is written in Rust and is compiled against WebAssembly as it's target runtime.
+
+Using Meshery, select Istio from the Management menu.
+
+In the Istio management page:
+
+1. Type default into the namespace field.
+2. Click the (+) icon on the Apply Service Mesh Configuration card and select Envoy Filter for Image Hub to deploy the custom filter.
+
+
+
+
+
+
Send traffic
+
+
Analyze behavior
+
+Alternative, manual installation steps are provided for reference below. No need to execute these if you have performed the steps above.
+
+Manually deploy the Image Hub filter.
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: EnvoyFilter
+metadata:
+ name: custom-filter
+spec:
+ configPatches:
+ - applyTo: HTTP_FILTER
+ match:
+ context: SIDECAR_OUTBOUND # will match outbound listeners in all sidecars
+ listener:
+ portNumber: 9080
+ filterChain:
+ name: envoy.http_connection_manager
+ filter:
+ name: "envoy.tcp_proxy"
+ patch:
+ operation: INSERT_BEFORE
+ value:
+ # This is the full filter config including the name and config or typed_config section.
+ name: "envoy.filters.http.wasm"
+ config:
+ config:
+ name: custom-filter
+ rootId: my_root_id
+ vmConfig:
+ code:
+ local:
+ filename: /var/lib/imagehub/filter.wasm
+ runtime: envoy.wasm.runtime.v8
+ vmId: custom-filter
+ allow_precompiled: true
+ workloadSelector:
+ labels:
+ app: api-v1
+ version: v1
+
+```
+Manually patch the Image Hub Deployment.
+
+```yaml
+---(
+ // kubectl patch deployment/api-v1 -p '
+ {
+ "spec": {
+ "template": {
+ "metadata": {
+ "annotations": {
+ "sidecar.istio.io/userVolumeMount": "[{\"mountPath\":\"/var/lib/imagehub\",\"name\":\"wasm-filter\"}]"
+ }
+ },
+ "spec": {
+ "initContainers": [
+ {
+ "command": [
+ "curl",
+ "-L",
+ "-o",
+ "/var/lib/imagehub/filter.wasm",
+ "https://github.com/layer5io/advanced-istio-service-mesh-workshop/raw/master/lab-7/ratelimiter/ratelimit-filter.wasm"
+ ],
+ "image": "curlimages/curl",
+ "imagePullPolicy": "Always",
+ "name": "add-wasm",
+ "resources": {},
+ "terminationMessagePath": "/dev/termination-log",
+ "terminationMessagePolicy": "File",
+ "volumeMounts": [
+ {
+ "mountPath": "/var/lib/imagehub",
+ "name": "wasm-filter"
+ }
+ ]
+ }
+ ],
+ "volumes": [
+ {
+ "emptyDir": {},
+ "name": "wasm-filter"
+ }
+ ]
+ }
+ }
+ }
+ }
+)
+// '
+
+```
+A future version of Meshery will allow you to deploy any filter from the [wasm-filters](https://github.com/layer5io/wasm-filters) repo. PR the repo to upload your custom filter and have Meshery deploy it.
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/index.mdx b/content-learn/mastering-service-meshes-for-developers/index.mdx
index d512ee4381bc..398cc72f2096 100644
--- a/content-learn/mastering-service-meshes-for-developers/index.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/index.mdx
@@ -1,13 +1,13 @@
----
-title: 'Mastering Service Meshes for Developers'
-description: 'Learn how to setup a service mesh and build an application'
-order: 4
-themeColor: '#3C494F'
-cardImage: '../../src/assets/images/service-mesh-icons/service-mesh.svg'
-courses: 4
----
-
-
\ No newline at end of file
+---
+title: 'Mastering Service Meshes for Developers'
+description: 'Learn how to setup a service mesh and build an application'
+order: 4
+themeColor: '#3C494F'
+cardImage: '../../src/assets/images/service-mesh-icons/service-mesh.svg'
+courses: 4
+---
+
+{/*
+ This file is only used to render the courses list within a learning path.
+ Check the Learn-Layer5 folder under src/sections/, src/templates for more understanding of how the data is used
+*/}
\ No newline at end of file
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/index.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/index.mdx
index e3fdab8cdf30..903a5d2a488a 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/index.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/index.mdx
@@ -1,37 +1,31 @@
----
-docType: "Course"
-title: "Course"
-description: "Learn how to setup a service mesh and deploy an application using it."
-videos: 4
-lectures: 12
-courseTitle: "Introduction to Service Meshes - Hands On"
-themeColor: "#00B39F"
-order: 1
-cardImage: "../../../src/assets/images/service-mesh-icons/linkerd-white.svg"
-meshesYouLearn:
- [
- {
- imagepath: "../../../src/assets/images/service-mesh-icons/istio.svg",
- name: "Istio",
- },
- {
- imagepath: "../../../src/assets/images/service-mesh-icons/linkerd.svg",
- name: "Linkerd",
- },
- ]
-toc:
- [
- "getting-started",
- "deploy-an-application",
- "expose-services",
- "observability",
- "routing-and-canary",
- "fault-injection",
- "mutual-tls",
- "circuit-breaking",
- "conclusion",
- ]
----
-
-A course to help you setup a service-mesh and start using it to build real-life applications using Meshery
-as the cloud native management plane.
+---
+docType: "Course"
+title: "Course"
+description: "Learn how to setup a service mesh and deploy an application using it."
+videos: 4
+lectures: 12
+courseTitle: "Introduction to Service Meshes - Hands On"
+themeColor: "#00B39F"
+order: 1
+cardImage: "../../../src/assets/images/service-mesh-icons/linkerd-white.svg"
+meshesYouLearn:
+ - imagepath: "../../../src/assets/images/service-mesh-icons/istio.svg"
+ name: "Istio"
+ - imagepath: "../../../src/assets/images/service-mesh-icons/linkerd.svg"
+ name: "Linkerd"
+toc:
+ [
+ "getting-started",
+ "deploy-an-application",
+ "expose-services",
+ "observability",
+ "routing-and-canary",
+ "fault-injection",
+ "mutual-tls",
+ "circuit-breaking",
+ "conclusion",
+ ]
+---
+
+A course to help you setup a service-mesh and start using it to build real-life applications using Meshery
+as the cloud native management plane.
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/circuit-breaking.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/circuit-breaking.mdx
index f5171ea16a7d..0994f80fb24c 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/circuit-breaking.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/circuit-breaking.mdx
@@ -1,128 +1,128 @@
----
-docType: "Chapter"
-chapterTitle: "Circuit Breaking"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 8
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import MesheryInitialLoadTest from "../../../../src/assets/images/learn-layer5/istio/meshery_initial_load_test.webp";
-import MesheryCbLoadTest from "../../../../src/assets/images/learn-layer5/istio/meshery_cb_load_test.webp";
-
-
-
-In this chapter we will configure circuit breaking using Istio. Circuit breaking allows developers to write applications that limit the impact of failures, latency spikes, and other undesirable effects of network peculiarities. This task will show how to configure circuit breaking for connections, requests, and outlier detection.
-
-
Preparing for circuit breaking
-
-
-Before we can configure circuit breaking, please try to access the `product page` app from within `Meshery` to ensure all the calls are making it through **without** errors as we did in [Observability chapter](observability) (see screenshot).
-
-
Configure circuit breaking
-
-
-Now that we have the needed services in place, it is time to configure circuit breaking
-using a destination rule.
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-
-
-This will update the existing destination rule definition for product page service to break the circuit if there are more than one connection and more than one pending request.
-
-In a few, we should be able to verify the destination rule by using the command below:
-
-```sh
-kubectl get destinationrule productpage -o yaml
-```
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: productpage
-spec:
- host: productpage
- subsets:
- - /obserlabels:
- version: v1
- name: v1
- trafficPolicy:
- connectionPool:
- http:
- http1MaxPendingRequests: 1
- maxRequestsPerConnection: 1
- tcp:
- maxConnections: 1
- outlierDetection:
- baseEjectionTime: 3m
- consecutiveErrors: 1
- interval: 1s
- maxEjectionPercent: 100
- tls:
- mode: ISTIO_MUTUAL
-```
-
-
Time to trip the circuit
-
-
-In the circuit-breaker settings, we specified maxRequestsPerConnection: 1 and http1MaxPendingRequests:
-1. This should mean that if we exceed more than one request per connection and more
-than one pending request, we should see the istio-proxy sidecar open the circuit
-for further requests/connections.
-
-Let us now use Meshery to make several calls to `product page` app by changing the number of concurrent connections to 5 from within Meshery's Performance page.
-
-Once you have updated the fields, you now click on `Run Test`.
-
-This will run the load test and show the results in a chart. ( see screenshot ).
-
-You should only see a percentage of the requests succeed and the rest trapped by the configured circuit breaker.
-
-
-
- {" "}
- Manual Steps
-
-
-
Configure circuit breaking
-
-```sh
-kubectl apply -f - <
+---
+docType: "Chapter"
+chapterTitle: "Circuit Breaking"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 8
+---
+
+
+import MesheryInitialLoadTest from "../../../../src/assets/images/learn-layer5/istio/meshery_initial_load_test.webp";
+import MesheryCbLoadTest from "../../../../src/assets/images/learn-layer5/istio/meshery_cb_load_test.webp";
+
+
+
+In this chapter we will configure circuit breaking using Istio. Circuit breaking allows developers to write applications that limit the impact of failures, latency spikes, and other undesirable effects of network peculiarities. This task will show how to configure circuit breaking for connections, requests, and outlier detection.
+
+
Preparing for circuit breaking
+
+
+Before we can configure circuit breaking, please try to access the `product page` app from within `Meshery` to ensure all the calls are making it through **without** errors as we did in [Observability chapter](observability) (see screenshot).
+
+
Configure circuit breaking
+
+
+Now that we have the needed services in place, it is time to configure circuit breaking
+using a destination rule.
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+
+
+This will update the existing destination rule definition for product page service to break the circuit if there are more than one connection and more than one pending request.
+
+In a few, we should be able to verify the destination rule by using the command below:
+
+```sh
+kubectl get destinationrule productpage -o yaml
+```
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: productpage
+spec:
+ host: productpage
+ subsets:
+ - /obserlabels:
+ version: v1
+ name: v1
+ trafficPolicy:
+ connectionPool:
+ http:
+ http1MaxPendingRequests: 1
+ maxRequestsPerConnection: 1
+ tcp:
+ maxConnections: 1
+ outlierDetection:
+ baseEjectionTime: 3m
+ consecutiveErrors: 1
+ interval: 1s
+ maxEjectionPercent: 100
+ tls:
+ mode: ISTIO_MUTUAL
+```
+
+
Time to trip the circuit
+
+
+In the circuit-breaker settings, we specified maxRequestsPerConnection: 1 and http1MaxPendingRequests:
+1. This should mean that if we exceed more than one request per connection and more
+than one pending request, we should see the istio-proxy sidecar open the circuit
+for further requests/connections.
+
+Let us now use Meshery to make several calls to `product page` app by changing the number of concurrent connections to 5 from within Meshery's Performance page.
+
+Once you have updated the fields, you now click on `Run Test`.
+
+This will run the load test and show the results in a chart. ( see screenshot ).
+
+You should only see a percentage of the requests succeed and the rest trapped by the configured circuit breaker.
+
+
+
+ You have successfully completed the course on{" "}
+ "Introduction to service meshes - Hands on" using{" "}
+
+ Istio
+
+ .
+
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/deploy-an-application.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/deploy-an-application.mdx
index 037630e3a328..5ba0d3246999 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/deploy-an-application.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/deploy-an-application.mdx
@@ -1,219 +1,219 @@
----
-docType: "Chapter"
-chapterTitle: "Deploy a sample application"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 2
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import BookInfoOffMesh from "../../../../src/assets/images/learn-layer5/istio/bookinfo-off-mesh.webp";
-import BookInfoOnMesh from "../../../../src/assets/images/learn-layer5/istio/bookinfo-on-mesh.webp";
-
-
-
-To play with Istio and demonstrate some of it's capabilities, you will deploy the example BookInfo application, which is included the Istio package.
-
-
What is the Bookinfo Application
-
-This application is a polyglot composition of microservices are written in
-different languages and sample BookInfo application displays information about a
-book, similar to a single catalog entry of an online book store. Displayed on
-the page is a description of the book, book details (ISBN, number of pages, and
-so on), and a few book reviews.
-
-The end-to-end architecture of the application is shown in the figure.
-
-
-
-
-
-
-_Figure: BookInfo deployed off the mesh_
-
-
-It’s worth noting that these services have no dependencies on Istio, but make an
-interesting service mesh example, particularly because of the multitude of services,
-languages and versions for the reviews service.
-
-As shown in the figure below, proxies are sidecarred to each of the application containers.
-
-
-
-
-
-
-_Figure: BookInfo deployed on the mesh_
-
-
-Sidecars proxy can be either manually or automatically injected into the pods. Automatic
-sidecar injection requires that your Kubernetes api-server supports `admissionregistration.k8s.io/v1`
-or `admissionregistration.k8s.io/v1beta1` or `admissionregistration.k8s.io/v1beta2`
-APIs. Verify whether your Kubernetes deployment supports these APIs by executing:
-
-```sh
-kubectl api-versions | grep admissionregistration
-```
-
-If your environment **does NOT** supports either of these two APIs, then you may use [manual sidecar injection](#manual-sidecar-inj) to deploy the sample app.
-
-As part of Istio deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
-
-
-
- Deploying Sample App with Automatic sidecar injection
-
-
-
-Istio, deployed as part of this workshop, will also deploy the sidecar injector.
-Let us now verify sidecar injector deployment.
-
-```sh
-kubectl -n istio-system get configmaps istio-sidecar-injector
-```
-
-Output:
-
-```sh
-NAME DATA AGE
-istio-sidecar-injector 2 9h
-```
-
-NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the [selector](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors).
-
-```sh
-kubectl get namespace -L istio-injection
-```
-
-Output:
-
-```sh
-NAME STATUS AGE ISTIO-INJECTION
-default Active 1h enabled
-istio-system Active 1h disabled
-kube-public Active 1h
-kube-system Active 1h
-```
-
-Using Meshery, navigate to the Istio management page.
-
-1. Enter `default` in the `Namespace` field.
-1. Click the (+) icon on the `Sample Application` card and select `BookInfo Application` from the list.
-
-This will do 3 things:
-
-1. Label `default` namespace for sidecar injection.
-1. Deploys all the BookInfo services in the `default` namespace.
-1. Deploys the virtual service and gateway needed to expose the BookInfo's productpage application in the `default` namespace.
-
-
- Verify Bookinfo deployment{" "}
-
-
-1. Verify that the deployments are all in a state of AVAILABLE before continuing.
-
-```sh
-watch kubectl get deployment
-```
-
-2. Choose a service, for instance `productpage`, and view it's container configuration:
-
-```sh
-kubectl get po
-
-kubectl describe pod productpage-v1-.....
-```
-
-3. Examine details of the services:
-
-```sh
-kubectl describe svc productpage
- ```
-
-Next, you will expose the BookInfo application to be accessed external from the cluster.
-
-
-
Alternative: Manual installation
-Follow this if the above steps did not work for you
-
-
-
-
Label namespace for injection
-
-Label the default namespace with istio-injection=enabled
-
-```sh
-kubectl label namespace default istio-injection=enabled
-```
-
-```sh
-kubectl get namespace -L istio-injection
-```
-
-Output:
-
-```sh
-NAME STATUS AGE ISTIO-INJECTION
-default Active 1h enabled
-istio-system Active 1h disabled
-kube-public Active 1h
-kube-system Active 1h
-```
-
-
Deploy BookInfo
-
-
-Applying this yaml file included in the Istio package you collected in [Getting Started](./getting-started) will deploy the BookInfo app in you cluster.
-
-```sh
-kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml
-```
-
-
- Deploy Gateway and Virtual Service for BookInfo app
-
Use this only when Automatic Sidecar injection doesn't work
-
-To do a manual sidecar injection we will be using `istioctl` command:
-
-```sh
-curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f - > newBookInfo.yaml
-```
-
-Observing the new yaml file reveals that additional container Istio Proxy has been added to the Pods with necessary configurations:
-
-```
- image: docker.io/istio/proxyv2:1.3.0
- imagePullPolicy: IfNotPresent
- name: istio-proxy
-```
-
-We need to now deploy the new yaml using `kubectl`
-
-```sh
-kubectl apply -f newBookInfo.yaml
-```
-
-To do both in a single command:
-
-```sh
-kubectl apply -f <(curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f -)
-```
-
-Now continue to [Verify Bookinfo deployment](#verify).
-
-
+---
+docType: "Chapter"
+chapterTitle: "Deploy a sample application"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 2
+---
+
+
+import BookInfoOffMesh from "../../../../src/assets/images/learn-layer5/istio/bookinfo-off-mesh.webp";
+import BookInfoOnMesh from "../../../../src/assets/images/learn-layer5/istio/bookinfo-on-mesh.webp";
+
+
+
+To play with Istio and demonstrate some of it's capabilities, you will deploy the example BookInfo application, which is included the Istio package.
+
+
What is the Bookinfo Application
+
+This application is a polyglot composition of microservices are written in
+different languages and sample BookInfo application displays information about a
+book, similar to a single catalog entry of an online book store. Displayed on
+the page is a description of the book, book details (ISBN, number of pages, and
+so on), and a few book reviews.
+
+The end-to-end architecture of the application is shown in the figure.
+
+
+
+
+
+
+_Figure: BookInfo deployed off the mesh_
+
+
+It’s worth noting that these services have no dependencies on Istio, but make an
+interesting service mesh example, particularly because of the multitude of services,
+languages and versions for the reviews service.
+
+As shown in the figure below, proxies are sidecarred to each of the application containers.
+
+
+
+
+
+
+_Figure: BookInfo deployed on the mesh_
+
+
+Sidecars proxy can be either manually or automatically injected into the pods. Automatic
+sidecar injection requires that your Kubernetes api-server supports `admissionregistration.k8s.io/v1`
+or `admissionregistration.k8s.io/v1beta1` or `admissionregistration.k8s.io/v1beta2`
+APIs. Verify whether your Kubernetes deployment supports these APIs by executing:
+
+```sh
+kubectl api-versions | grep admissionregistration
+```
+
+If your environment **does NOT** supports either of these two APIs, then you may use [manual sidecar injection](#manual-sidecar-inj) to deploy the sample app.
+
+As part of Istio deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
+
+
+
+ Deploying Sample App with Automatic sidecar injection
+
+
+
+Istio, deployed as part of this workshop, will also deploy the sidecar injector.
+Let us now verify sidecar injector deployment.
+
+```sh
+kubectl -n istio-system get configmaps istio-sidecar-injector
+```
+
+Output:
+
+```sh
+NAME DATA AGE
+istio-sidecar-injector 2 9h
+```
+
+NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the [selector](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors).
+
+```sh
+kubectl get namespace -L istio-injection
+```
+
+Output:
+
+```sh
+NAME STATUS AGE ISTIO-INJECTION
+default Active 1h enabled
+istio-system Active 1h disabled
+kube-public Active 1h
+kube-system Active 1h
+```
+
+Using Meshery, navigate to the Istio management page.
+
+1. Enter `default` in the `Namespace` field.
+1. Click the (+) icon on the `Sample Application` card and select `BookInfo Application` from the list.
+
+This will do 3 things:
+
+1. Label `default` namespace for sidecar injection.
+1. Deploys all the BookInfo services in the `default` namespace.
+1. Deploys the virtual service and gateway needed to expose the BookInfo's productpage application in the `default` namespace.
+
+
+ Verify Bookinfo deployment{" "}
+
+
+1. Verify that the deployments are all in a state of AVAILABLE before continuing.
+
+```sh
+watch kubectl get deployment
+```
+
+2. Choose a service, for instance `productpage`, and view it's container configuration:
+
+```sh
+kubectl get po
+
+kubectl describe pod productpage-v1-.....
+```
+
+3. Examine details of the services:
+
+```sh
+kubectl describe svc productpage
+ ```
+
+Next, you will expose the BookInfo application to be accessed external from the cluster.
+
+
+
Alternative: Manual installation
+Follow this if the above steps did not work for you
+
+
+
+
Label namespace for injection
+
+Label the default namespace with istio-injection=enabled
+
+```sh
+kubectl label namespace default istio-injection=enabled
+```
+
+```sh
+kubectl get namespace -L istio-injection
+```
+
+Output:
+
+```sh
+NAME STATUS AGE ISTIO-INJECTION
+default Active 1h enabled
+istio-system Active 1h disabled
+kube-public Active 1h
+kube-system Active 1h
+```
+
+
Deploy BookInfo
+
+
+Applying this yaml file included in the Istio package you collected in [Getting Started](./getting-started) will deploy the BookInfo app in you cluster.
+
+```sh
+kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml
+```
+
+
+ Deploy Gateway and Virtual Service for BookInfo app
+
Use this only when Automatic Sidecar injection doesn't work
+
+To do a manual sidecar injection we will be using `istioctl` command:
+
+```sh
+curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f - > newBookInfo.yaml
+```
+
+Observing the new yaml file reveals that additional container Istio Proxy has been added to the Pods with necessary configurations:
+
+```
+ image: docker.io/istio/proxyv2:1.3.0
+ imagePullPolicy: IfNotPresent
+ name: istio-proxy
+```
+
+We need to now deploy the new yaml using `kubectl`
+
+```sh
+kubectl apply -f newBookInfo.yaml
+```
+
+To do both in a single command:
+
+```sh
+kubectl apply -f <(curl https://raw.githubusercontent.com/istio/istio/master/samples/bookinfo/platform/kube/bookinfo.yaml | istioctl kube-inject -f -)
+```
+
+Now continue to [Verify Bookinfo deployment](#verify).
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/expose-services.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/expose-services.mdx
index a6212a8efa02..2da9d997454c 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/expose-services.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/expose-services.mdx
@@ -1,292 +1,292 @@
----
-docType: "Chapter"
-chapterTitle: "Exposing services through Istio Ingress Gateway"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 3
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-The components deployed on the service mesh by default are not exposed outside the cluster. An Ingress Gateway is deployed as a Kubernetes service of type LoadBalancer (or NodePort). To make Bookinfo accessible external to the cluster, you have to create an `Istio Gateway` for the Bookinfo application and also define an `Istio VirtualService` with the routes we need.
-
-
-
-
-
Inspecting the Istio Ingress Gateway
-
-
-The ingress gateway gets exposed as a normal Kubernetes service of type LoadBalancer
-(or NodePort):
-
-```sh
-kubectl get svc istio-ingressgateway -n istio-system -o yaml
-```
-
-Because the Istio Ingress Gateway is an Envoy Proxy you can inspect it using the admin routes. First find the name of the istio-ingressgateway:
-
-```sh
-kubectl get pods -n istio-system
-```
-
-Copy and paste your ingress gateway's pod name. Execute:
-
-```sh
-kubectl -n istio-system exec -it bash
-```
-
-You can view the statistics, listeners, routes, clusters and server info for the Envoy proxy by forwarding the local port:
-
-```sh
-curl localhost:15000/help
-curl localhost:15000/stats
-curl localhost:15000/listeners
-curl localhost:15000/clusters
-curl localhost:15000/server_info
-```
-
-See the [admin docs](https://www.envoyproxy.io/docs/envoy/latest/operations/admin) for more details.
-
-Also it can be helpful to look at the log files of the Istio ingress controller to see what request is being routed.
-
-Before we check the logs, let us get out of the container back on the host:
-
-```sh
-exit
-```
-
-Now let us find the ingress pod and output the log:
-
-```sh
-kubectl logs istio-ingressgateway-... -n istio-system
-```
-
-
View Istio Ingress Gateway for Bookinfo
-
-
-
View the Gateway and VirtualServices
-
-Check the created `Istio Gateway` and `Istio VirtualService` to see the changes deployed:
-
-```sh
-kubectl get gateway
-kubectl get gateway -o yaml
-
-kubectl get virtualservices
-kubectl get virtualservices -o yaml
-```
-
-
- Find the external port of the Istio Ingress Gateway by running:
-
-
-```sh
-kubectl get service istio-ingressgateway -n istio-system -o wide
-```
-
-To just get the first port of istio-ingressgateway service, we can run this:
-
-```sh
-kubectl get service istio-ingressgateway -n istio-system --template='{{(index .spec.ports 1).nodePort}}'
-```
-
-
Create a DNS entry:
-
-Modify you local `/etc/hosts` file to add an entry for your sample application.
-
-`127.0.0.1. bookinfo.meshery.io`
-
-The HTTP port is usually 31380.
-
-Or run these commands to retrieve the full URL:
-
-```sh
-echo "http://$(kubectl get nodes --selector=kubernetes.io/role!=master -o jsonpath={.items[0].status.addresses[?\(@.type==\"InternalIP\"\)].address}):$(kubectl get svc istio-ingressgateway -n istio-system -o jsonpath='{.spec.ports[1].nodePort}')/productpage"
-```
-
-Docker Desktop users please use `http://localhost/productpage` to access product page in your browser.
-
-In case you are using a managed kubernetes cluster like AKS, EKS, or GCE please follow the procedure described below:
-
-- Get the external IP of the service istio-ingressgateway using the following command:
-
- ```sh
- kubectl get service istio-ingressgateway -n istio-system
- ```
-
-- Using Meshery, navigate to the Custom yaml page, and apply the manifest given below to allow all hosts instead of allowing bookinfo.meshery.io only and you are good to access the page using the following url `http:///productpage`.
-
-```yaml
-apiVersion: networking.istio.io/v1beta1
-kind: VirtualService
-metadata:
- name: bookinfo
-spec:
- gateways:
- - sample-app-gateway
- hosts:
- - "*"
- http:
- - match:
- - uri:
- exact: /productpage
- - uri:
- prefix: /static
- - uri:
- exact: /login
- - uri:
- exact: /logout
- - uri:
- prefix: /api/v1/products
- route:
- - destination:
- host: productpage
- port:
- number: 9080
-```
-
-
Apply default destination rules
-
-Before we start playing with Istio's traffic management capabilities we need to define the available versions of the deployed services. They are called subsets, in destination rules.
-
-Using Meshery, navigate to the Custom yaml page, and apply the below to create the subsets for BookInfo:
-
-```sh
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: productpage
-spec:
- host: productpage
- subsets:
- - name: v1
- labels:
- version: v1
----
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: reviews
-spec:
- host: reviews
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
- - name: v3
- labels:
- version: v3
----
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: ratings
-spec:
- host: ratings
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
- - name: v2-mysql
- labels:
- version: v2-mysql
- - name: v2-mysql-vm
- labels:
- version: v2-mysql-vm
----
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: details
-spec:
- host: details
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
-```
-
-This creates destination rules for each of the BookInfo services and defines version subsets
-
-In a few seconds we should be able to verify the destination rules created by using the command below:
-
-```sh
-kubectl get destinationrules
-
-
-kubectl get destinationrules -o yaml
-```
-
-
Browse to BookInfo
-
-Browse to the website of the Bookinfo. To view the product page, you will have to append
-`/productpage` to the url.
-
-
Reload Page
-
-Now, reload the page multiple times and notice how it round robins between v1, v2 and v3 of the reviews service.
-
-
- Inspect the Istio proxy of the productpage pod
-
-
-To better understand the istio proxy, let's inspect the details. Let us `exec` into the productpage pod to find the proxy details. To do so we need to first find the full pod name and then `exec` into the istio-proxy container:
-
-```sh
-kubectl get pods
-kubectl exec -it productpage-v1-... -c istio-proxy sh
-```
-
-Once in the container look at some of the envoy proxy details by inspecting it's config file:
-
-```sh
-ps aux
-ls -l /etc/istio/proxy
-cat /etc/istio/proxy/envoy-rev0.json
-```
-
-For more details on envoy proxy please check out their [admin docs](https://www.envoyproxy.io/docs/envoy/v1.5.0/operations/admin).
-
-As a last step, lets exit the container:
-
-```sh
-exit
-```
-
-
-
Alternative: Manual installation
-Follow this if the above steps did not work for you
-
-
-
-
-
Default destination rules
-
-Run the following command to create default destination rules for the Bookinfo services:
-
-```sh
-kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml
-```
-
-
- Configure the Bookinfo route with the Istio Ingress gateway
-
-
-We can create a virtualservice & gateway for bookinfo app in the ingress gateway by running the following:
-
-```sh
-kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Exposing services through Istio Ingress Gateway"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 3
+---
+
+
+
+
+The components deployed on the service mesh by default are not exposed outside the cluster. An Ingress Gateway is deployed as a Kubernetes service of type LoadBalancer (or NodePort). To make Bookinfo accessible external to the cluster, you have to create an `Istio Gateway` for the Bookinfo application and also define an `Istio VirtualService` with the routes we need.
+
+
+
+
+
Inspecting the Istio Ingress Gateway
+
+
+The ingress gateway gets exposed as a normal Kubernetes service of type LoadBalancer
+(or NodePort):
+
+```sh
+kubectl get svc istio-ingressgateway -n istio-system -o yaml
+```
+
+Because the Istio Ingress Gateway is an Envoy Proxy you can inspect it using the admin routes. First find the name of the istio-ingressgateway:
+
+```sh
+kubectl get pods -n istio-system
+```
+
+Copy and paste your ingress gateway's pod name. Execute:
+
+```sh
+kubectl -n istio-system exec -it bash
+```
+
+You can view the statistics, listeners, routes, clusters and server info for the Envoy proxy by forwarding the local port:
+
+```sh
+curl localhost:15000/help
+curl localhost:15000/stats
+curl localhost:15000/listeners
+curl localhost:15000/clusters
+curl localhost:15000/server_info
+```
+
+See the [admin docs](https://www.envoyproxy.io/docs/envoy/latest/operations/admin) for more details.
+
+Also it can be helpful to look at the log files of the Istio ingress controller to see what request is being routed.
+
+Before we check the logs, let us get out of the container back on the host:
+
+```sh
+exit
+```
+
+Now let us find the ingress pod and output the log:
+
+```sh
+kubectl logs istio-ingressgateway-... -n istio-system
+```
+
+
View Istio Ingress Gateway for Bookinfo
+
+
+
View the Gateway and VirtualServices
+
+Check the created `Istio Gateway` and `Istio VirtualService` to see the changes deployed:
+
+```sh
+kubectl get gateway
+kubectl get gateway -o yaml
+
+kubectl get virtualservices
+kubectl get virtualservices -o yaml
+```
+
+
+ Find the external port of the Istio Ingress Gateway by running:
+
+
+```sh
+kubectl get service istio-ingressgateway -n istio-system -o wide
+```
+
+To just get the first port of istio-ingressgateway service, we can run this:
+
+```sh
+kubectl get service istio-ingressgateway -n istio-system --template='{{(index .spec.ports 1).nodePort}}'
+```
+
+
Create a DNS entry:
+
+Modify you local `/etc/hosts` file to add an entry for your sample application.
+
+`127.0.0.1. bookinfo.meshery.io`
+
+The HTTP port is usually 31380.
+
+Or run these commands to retrieve the full URL:
+
+```sh
+echo "http://$(kubectl get nodes --selector=kubernetes.io/role!=master -o jsonpath={.items[0].status.addresses[?\(@.type==\"InternalIP\"\)].address}):$(kubectl get svc istio-ingressgateway -n istio-system -o jsonpath='{.spec.ports[1].nodePort}')/productpage"
+```
+
+Docker Desktop users please use `http://localhost/productpage` to access product page in your browser.
+
+In case you are using a managed kubernetes cluster like AKS, EKS, or GCE please follow the procedure described below:
+
+- Get the external IP of the service istio-ingressgateway using the following command:
+
+ ```sh
+ kubectl get service istio-ingressgateway -n istio-system
+ ```
+
+- Using Meshery, navigate to the Custom yaml page, and apply the manifest given below to allow all hosts instead of allowing bookinfo.meshery.io only and you are good to access the page using the following url `http:///productpage`.
+
+```yaml
+apiVersion: networking.istio.io/v1beta1
+kind: VirtualService
+metadata:
+ name: bookinfo
+spec:
+ gateways:
+ - sample-app-gateway
+ hosts:
+ - "*"
+ http:
+ - match:
+ - uri:
+ exact: /productpage
+ - uri:
+ prefix: /static
+ - uri:
+ exact: /login
+ - uri:
+ exact: /logout
+ - uri:
+ prefix: /api/v1/products
+ route:
+ - destination:
+ host: productpage
+ port:
+ number: 9080
+```
+
+
Apply default destination rules
+
+Before we start playing with Istio's traffic management capabilities we need to define the available versions of the deployed services. They are called subsets, in destination rules.
+
+Using Meshery, navigate to the Custom yaml page, and apply the below to create the subsets for BookInfo:
+
+```sh
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: productpage
+spec:
+ host: productpage
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+---
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: reviews
+spec:
+ host: reviews
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+ - name: v2
+ labels:
+ version: v2
+ - name: v3
+ labels:
+ version: v3
+---
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: ratings
+spec:
+ host: ratings
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+ - name: v2
+ labels:
+ version: v2
+ - name: v2-mysql
+ labels:
+ version: v2-mysql
+ - name: v2-mysql-vm
+ labels:
+ version: v2-mysql-vm
+---
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: details
+spec:
+ host: details
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+ - name: v2
+ labels:
+ version: v2
+```
+
+This creates destination rules for each of the BookInfo services and defines version subsets
+
+In a few seconds we should be able to verify the destination rules created by using the command below:
+
+```sh
+kubectl get destinationrules
+
+
+kubectl get destinationrules -o yaml
+```
+
+
Browse to BookInfo
+
+Browse to the website of the Bookinfo. To view the product page, you will have to append
+`/productpage` to the url.
+
+
Reload Page
+
+Now, reload the page multiple times and notice how it round robins between v1, v2 and v3 of the reviews service.
+
+
+ Inspect the Istio proxy of the productpage pod
+
+
+To better understand the istio proxy, let's inspect the details. Let us `exec` into the productpage pod to find the proxy details. To do so we need to first find the full pod name and then `exec` into the istio-proxy container:
+
+```sh
+kubectl get pods
+kubectl exec -it productpage-v1-... -c istio-proxy sh
+```
+
+Once in the container look at some of the envoy proxy details by inspecting it's config file:
+
+```sh
+ps aux
+ls -l /etc/istio/proxy
+cat /etc/istio/proxy/envoy-rev0.json
+```
+
+For more details on envoy proxy please check out their [admin docs](https://www.envoyproxy.io/docs/envoy/v1.5.0/operations/admin).
+
+As a last step, lets exit the container:
+
+```sh
+exit
+```
+
+
+
Alternative: Manual installation
+Follow this if the above steps did not work for you
+
+
+
+
+
Default destination rules
+
+Run the following command to create default destination rules for the Bookinfo services:
+
+```sh
+kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml
+```
+
+
+ Configure the Bookinfo route with the Istio Ingress gateway
+
+
+We can create a virtualservice & gateway for bookinfo app in the ingress gateway by running the following:
+
+```sh
+kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/fault-injection.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/fault-injection.mdx
index 49fa69a3e96d..75b6176d640e 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/fault-injection.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/fault-injection.mdx
@@ -1,186 +1,186 @@
----
-docType: "Chapter"
-chapterTitle: "Fault Injection"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 6
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-In this chapter we will learn how to test the resiliency of an application by injecting systematic faults.
-Before we start, we will need to reset the virtual services.
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: reviews
-spec:
- hosts:
- - reviews
- http:
- - route:
- - destination:
- host: reviews
- subset: v2
-```
-
-
- Inject a route rule to create a fault using HTTP delay
-
-
-To start, we will inject a 7s delay for accessing the ratings service for a user `jason`. reviews v2 service has a 10s hard-coded connection timeout for its calls to the ratings service configured globally.
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-This will update the existing virtual service definition for ratings to inject a delay for user `jason` to access the ratings V1.
-
-In a few, we should be able to verify the virtual service by using the command below:
-
-```sh
-kubectl get virtualservice ratings -o yaml
-```
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: ratings
-spec:
- hosts:
- - ratings
- http:
- - fault:
- delay:
- fixedDelay: 7s
- percentage:
- value: 100
- match:
- - headers:
- end-user:
- exact: jason
- route:
- - destination:
- host: ratings
- subset: v1
- - route:
- - destination:
- host: ratings
- subset: v1
-```
-
-Now we login to `/productpage` as user `jason` and observe that the page loads but because of the induced delay between services the reviews section will show :
-
-Error fetching product reviews!
-Sorry, product reviews are currently unavailable for this book.
-
-If you logout or login as a different user, the page should load normally without any errors.
-
-
- Inject a route rule to create a fault using HTTP abort
-
-
-In this section, , we will introduce an HTTP abort to the ratings microservices for user `jason`.
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-This will update the existing virtual service definition for ratings to inject a HTTP abort for user `jason` to access the ratings V1.
-
-In a few, we should be able to verify the virtual service by using the command below:
-
-```sh
-kubectl get virtualservice ratings -o yaml
-```
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: ratings
-spec:
- hosts:
- - ratings
- http:
- - fault:
- abort:
- httpStatus: 500
- percentage:
- value: 100
- match:
- - headers:
- end-user:
- exact: jason
- route:
- - destination:
- host: ratings
- subset: v1
- - route:
- - destination:
- host: ratings
- subset: v1
-```
-
-Now we login to `/productpage` as user `jason` and observe that the page loads without any new delays but because of the induced fault between services the reviews section will show:
-
-`Ratings service is currently unavailable`.
-
-
Verify fault injection
-
-Verify the fault injection by logging out (or logging in as a different user), the page should load normally without any errors.
-
-
-
Alternative: Manual installation
-Follow these steps if the above steps did not work
-
-
-
-
- Route all traffic to version V1 of all services
-
-
-```sh
-kubectl apply -f samples/bookinfo/networking/virtual-service-ratings-test-abort.yaml
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Fault Injection"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 6
+---
+
+
+
+
+
+In this chapter we will learn how to test the resiliency of an application by injecting systematic faults.
+Before we start, we will need to reset the virtual services.
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: reviews
+spec:
+ hosts:
+ - reviews
+ http:
+ - route:
+ - destination:
+ host: reviews
+ subset: v2
+```
+
+
+ Inject a route rule to create a fault using HTTP delay
+
+
+To start, we will inject a 7s delay for accessing the ratings service for a user `jason`. reviews v2 service has a 10s hard-coded connection timeout for its calls to the ratings service configured globally.
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+This will update the existing virtual service definition for ratings to inject a delay for user `jason` to access the ratings V1.
+
+In a few, we should be able to verify the virtual service by using the command below:
+
+```sh
+kubectl get virtualservice ratings -o yaml
+```
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: ratings
+spec:
+ hosts:
+ - ratings
+ http:
+ - fault:
+ delay:
+ fixedDelay: 7s
+ percentage:
+ value: 100
+ match:
+ - headers:
+ end-user:
+ exact: jason
+ route:
+ - destination:
+ host: ratings
+ subset: v1
+ - route:
+ - destination:
+ host: ratings
+ subset: v1
+```
+
+Now we login to `/productpage` as user `jason` and observe that the page loads but because of the induced delay between services the reviews section will show :
+
+Error fetching product reviews!
+Sorry, product reviews are currently unavailable for this book.
+
+If you logout or login as a different user, the page should load normally without any errors.
+
+
+ Inject a route rule to create a fault using HTTP abort
+
+
+In this section, , we will introduce an HTTP abort to the ratings microservices for user `jason`.
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+This will update the existing virtual service definition for ratings to inject a HTTP abort for user `jason` to access the ratings V1.
+
+In a few, we should be able to verify the virtual service by using the command below:
+
+```sh
+kubectl get virtualservice ratings -o yaml
+```
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: ratings
+spec:
+ hosts:
+ - ratings
+ http:
+ - fault:
+ abort:
+ httpStatus: 500
+ percentage:
+ value: 100
+ match:
+ - headers:
+ end-user:
+ exact: jason
+ route:
+ - destination:
+ host: ratings
+ subset: v1
+ - route:
+ - destination:
+ host: ratings
+ subset: v1
+```
+
+Now we login to `/productpage` as user `jason` and observe that the page loads without any new delays but because of the induced fault between services the reviews section will show:
+
+`Ratings service is currently unavailable`.
+
+
Verify fault injection
+
+Verify the fault injection by logging out (or logging in as a different user), the page should load normally without any errors.
+
+
+
Alternative: Manual installation
+Follow these steps if the above steps did not work
+
+
+
+
+ Route all traffic to version V1 of all services
+
-
-Using Meshery, select `Istio` from the `Lifecycle` menu.
-
-In the Istio management page:
-
-1. Type `istio-system` into the namespace field.
-2. Click the (+) icon on the `Install` card and click on `Istio Service Mesh` to install latest version of Istio.
-
-
-
-
-
-3. Click the `Deploy` button on the confirmation modal.
-
-
-
-
-
-
Alternative:Manual installation
-Perform the below steps if the above steps doesn't work for you.
-
-
-
-
-
-
-You will download and deploy the latest Istio resources on your Kubernetes cluster.
-
-**_Note to Docker Desktop users:_** Please ensure your Docker VM has atleast 4GiB of Memory, which is required for all services to run.
-
-On your local machine, execute:
-
-```sh
-curl -L https://git.io/getLatestIstio | ISTIO_VERSION=1.7.3 sh -
-```
-
-
-
-On a \*nix system, you can setup `istioctl` by doing the following:
-
-```sh
-brew install istioctl
-```
-
-Alternatively, change into the Istio package directory and add the `istioctl` client to your PATH environment variable.
-
-```sh
-cd istio-*
-export PATH=$PWD/bin:$PATH
-```
-
-Verify `istioctl` is available:
-
-```sh
-istioctl version
-```
-
-Check if the cluster is ready for installation:
-
-```sh
-istioctl verify-install
-```
-
-
-
-In the Istio management page:
-
-1. Click the (+) icon on the `Validate Service Mesh Configuration` card.
-1. Select `Verify Installation` to verify the installation of Istio.
-
-
Alternatively:
-
-Istio is deployed in a separate Kubernetes namespace `istio-system`. To check if Istio is deployed, and also, to see all the pieces that are deployed, execute the following:
-
-```sh
-kubectl get all -n istio-system
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Getting Started"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 1
+---
+
+
+import InstallIstio from "../../../../src/assets/images/learn-layer5/istio/install-istio1.webp";
+import IstioDeploy from "../../../../src/assets/images/learn-layer5/istio/install-istio2.webp";
+
+
+
+
Setup Istio
+
+Now that we have a Kubernetes cluster and Meshery, we are ready to download and deploy Istio resources.
+
+
+
+Using Meshery, select `Istio` from the `Lifecycle` menu.
+
+In the Istio management page:
+
+1. Type `istio-system` into the namespace field.
+2. Click the (+) icon on the `Install` card and click on `Istio Service Mesh` to install latest version of Istio.
+
+
+
+
+
+3. Click the `Deploy` button on the confirmation modal.
+
+
+
+
+
+
Alternative:Manual installation
+Perform the below steps if the above steps doesn't work for you.
+
+
+
+
+
+
+You will download and deploy the latest Istio resources on your Kubernetes cluster.
+
+**_Note to Docker Desktop users:_** Please ensure your Docker VM has atleast 4GiB of Memory, which is required for all services to run.
+
+On your local machine, execute:
+
+```sh
+curl -L https://git.io/getLatestIstio | ISTIO_VERSION=1.7.3 sh -
+```
+
+
+
+On a \*nix system, you can setup `istioctl` by doing the following:
+
+```sh
+brew install istioctl
+```
+
+Alternatively, change into the Istio package directory and add the `istioctl` client to your PATH environment variable.
+
+```sh
+cd istio-*
+export PATH=$PWD/bin:$PATH
+```
+
+Verify `istioctl` is available:
+
+```sh
+istioctl version
+```
+
+Check if the cluster is ready for installation:
+
+```sh
+istioctl verify-install
+```
+
+
+
+In the Istio management page:
+
+1. Click the (+) icon on the `Validate Service Mesh Configuration` card.
+1. Select `Verify Installation` to verify the installation of Istio.
+
+
Alternatively:
+
+Istio is deployed in a separate Kubernetes namespace `istio-system`. To check if Istio is deployed, and also, to see all the pieces that are deployed, execute the following:
+
+```sh
+kubectl get all -n istio-system
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/mutual-tls.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/mutual-tls.mdx
index fd3e3c0c91e1..2e80ae71adce 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/mutual-tls.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/mutual-tls.mdx
@@ -1,203 +1,203 @@
----
-docType: "Chapter"
-chapterTitle: "Mutual TLS & Identity Verification"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 7
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-Istio provides transparent mutual TLS to services inside the service mesh where both the client and the server authenticate each others' certificates as part of the TLS handshake. As part of this course, we have deployed Istio with mTLS.
-
-By default istio sets mTLS in `PERMISSIVE` mode which allows plain text traffic to be sent and accepted by a mesh. We first disallow plain text traffic using `PeerAuthentication` and setting mTLS mode to STRICT.
-
-
Confirm mTLS is being enforced
-
-This can be easily done by executing a simple command:-
-
-```sh
-kubectl get peerauthentication --all-namespaces
-```
-
-
Verify mTLS
-
-Citadel is Istio’s key management service. As a first step, confirm that Citadel is up and running:
-
-```sh
-kubectl get deploy -l istio=citadel -n istio-system
-```
-
-Output will be similar to:
-
-```
-NAME READY UP-TO-DATE AVAILABLE AGE
-istio-citadel 1/1 1 1 3m23s
-```
-
-To experiment with mTLS, let's do so by logging into the sidecar proxy of the `productpage` pod by executing this command:
-
-```sh
-kubectl exec -it $(kubectl get pod | grep productpage | awk '{ print $1 }') -c istio-proxy -- /bin/bash
-```
-
-We are now in the proxy of the `productpage` pod. Check that all the ceritificates are loaded in this proxy:
-
-```sh
-ls /etc/certs/
-```
-
-You should see 3 entries:
-
-```sh
-cert-chain.pem key.pem root-cert.pem
-```
-
-Now, try to make a curl call to the `details` service over HTTP:
-
-```sh
-curl http://details:9080/details/0
-```
-
-Since, we have TLS between the sidecar's, an HTTP call will not work. The request will timeout. You will see an error like the one below:
-
-```sh
-curl: (7) Failed to connect to details port 9080: Connection timed out
-```
-
-Let us try to make a curl call to the details service over HTTPS but **WITHOUT** certs:
-
-```sh
-curl https://details:9080/details/0 -k
-```
-
-The request will be denied and you will see an error like the one below:
-
-```sh
-curl: (16) SSL_write() returned SYSCALL, errno = 104
-```
-
-Now, let us use curl over HTTPS with certificates to the details service:
-
-```sh
-curl https://details:9080/details/0 -v --key /etc/certs/key.pem --cert /etc/certs/cert-chain.pem --cacert /etc/certs/root-cert.pem -k
-```
-
-Output will be similar to this:
-
-```sh
-* Trying 10.107.35.26...
-* Connected to details (10.107.35.26) port 9080 (#0)
-* found 1 certificates in /etc/certs/root-cert.pem
-* found 0 certificates in /etc/ssl/certs
-* ALPN, offering http/1.1
-* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
-* server certificate verification SKIPPED
-* server certificate status verification SKIPPED
-* error fetching CN from cert:The requested data were not available.
-* common name: (does not match 'details')
-* server certificate expiration date OK
-* server certificate activation date OK
-* certificate public key: RSA
-* certificate version: #3
-* subject: O=#1300
-* start date: Thu, 26 Oct 2018 14:36:56 GMT
-* expire date: Wed, 05 Jan 2019 14:36:56 GMT
-* issuer: O=k8s.cluster.local
-* compression: NULL
-* ALPN, server accepted to use http/1.1
-> GET /details/0 HTTP/1.1
-> Host: details:9080
-> User-Agent: curl/7.47.0
-> Accept: */*
->
-< HTTP/1.1 200 OK
-< content-type: application/json
-< server: envoy
-< date: Thu, 07 Jun 2018 15:19:46 GMT
-< content-length: 178
-< x-envoy-upstream-service-time: 1
-< x-envoy-decorator-operation: default-route
-<
-* Connection #0 to host details left intact
-{"id":0,"author":"William Shakespeare","year":1595,"type":"paperback","pages":200,"publisher":"PublisherA","language":"English","ISBN-10":"1234567890","ISBN-13":"123-1234567890"}
-```
-
-This proves the existence of mTLS between the services on the Istio mesh.
-
-Now lets come out of the container before we go to the next section:
-
-```sh
-exit
-```
-
-
- Secure Production Identity Framework for Everyone (SPIFFE)
-
-
-Istio uses [SPIFFE](https://spiffe.io/) to assert the identify of workloads on
-the cluster. SPIFFE consists of a notion of identity and a method of proving it.
-A SPIFFE identity consists of an authority part and a path. The meaning of the
-path in spiffe land is implementation defined. In k8s it takes the form
-`/ns/$namespace/sa/$service-account` with the expected meaning. A SPIFFE
-identify is embedded in a document. This document in principle can take many
-forms but currently the only defined format is x509.
-
-To start our investigation, let us check if the certs are in place in the productpage sidecar:
-
-```sh
-kubectl exec $(kubectl get pod -l app=productpage -o jsonpath={.items..metadata.name}) -c istio-proxy -- ls /etc/certs
-```
-
-Output will be similar to:
-
-```sh
-cert-chain.pem
-key.pem
-root-cert.pem
-```
-
-Mac users, MacOS should have openssl available. If your machine does not have openssl install, install it using your preferred method.
-
-Here is one way to install it on RHEL or CentOS or its derivatives:
-
-```sh
-sudo yum install -y openssl-devel
-```
-
-Here is one way to install it on Ubuntu or Debian or its derivatives:
-
-```sh
-sudo apt install -y libssl-dev
-```
-
-Now that we have found the certs, let us verify the certificate of productpage sidecar by running this command:
-
-```sh
-kubectl exec $(kubectl get pod -l app=productpage -o jsonpath={.items..metadata.name}) -c istio-proxy -- cat /etc/certs/cert-chain.pem | openssl x509 -text -noout | grep Validity -A 2
-```
-
-Output will be similar to:
-
-```sh
- Not Before: Sep 23 17:32:28 2019 GMT
- Not After : Dec 22 17:32:28 2019 GMT
-```
-
-Lets also verify the URI SAN:
-
-```sh
-kubectl exec $(kubectl get pod -l app=productpage -o jsonpath={.items..metadata.name}) -c istio-proxy -- cat /etc/certs/cert-chain.pem | openssl x509 -text -noout | grep 'Subject Alternative Name' -A 1
-```
-
-Output will be similar to:
-
-```sh
-X509v3 Subject Alternative Name: critical
- URI:spiffe://cluster.local/ns/default/sa/bookinfo-productpage
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Mutual TLS & Identity Verification"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 7
+---
+
+
+
+
+
+Istio provides transparent mutual TLS to services inside the service mesh where both the client and the server authenticate each others' certificates as part of the TLS handshake. As part of this course, we have deployed Istio with mTLS.
+
+By default istio sets mTLS in `PERMISSIVE` mode which allows plain text traffic to be sent and accepted by a mesh. We first disallow plain text traffic using `PeerAuthentication` and setting mTLS mode to STRICT.
+
+
Confirm mTLS is being enforced
+
+This can be easily done by executing a simple command:-
+
+```sh
+kubectl get peerauthentication --all-namespaces
+```
+
+
Verify mTLS
+
+Citadel is Istio’s key management service. As a first step, confirm that Citadel is up and running:
+
+```sh
+kubectl get deploy -l istio=citadel -n istio-system
+```
+
+Output will be similar to:
+
+```
+NAME READY UP-TO-DATE AVAILABLE AGE
+istio-citadel 1/1 1 1 3m23s
+```
+
+To experiment with mTLS, let's do so by logging into the sidecar proxy of the `productpage` pod by executing this command:
+
+```sh
+kubectl exec -it $(kubectl get pod | grep productpage | awk '{ print $1 }') -c istio-proxy -- /bin/bash
+```
+
+We are now in the proxy of the `productpage` pod. Check that all the ceritificates are loaded in this proxy:
+
+```sh
+ls /etc/certs/
+```
+
+You should see 3 entries:
+
+```sh
+cert-chain.pem key.pem root-cert.pem
+```
+
+Now, try to make a curl call to the `details` service over HTTP:
+
+```sh
+curl http://details:9080/details/0
+```
+
+Since, we have TLS between the sidecar's, an HTTP call will not work. The request will timeout. You will see an error like the one below:
+
+```sh
+curl: (7) Failed to connect to details port 9080: Connection timed out
+```
+
+Let us try to make a curl call to the details service over HTTPS but **WITHOUT** certs:
+
+```sh
+curl https://details:9080/details/0 -k
+```
+
+The request will be denied and you will see an error like the one below:
+
+```sh
+curl: (16) SSL_write() returned SYSCALL, errno = 104
+```
+
+Now, let us use curl over HTTPS with certificates to the details service:
+
+```sh
+curl https://details:9080/details/0 -v --key /etc/certs/key.pem --cert /etc/certs/cert-chain.pem --cacert /etc/certs/root-cert.pem -k
+```
+
+Output will be similar to this:
+
+```sh
+* Trying 10.107.35.26...
+* Connected to details (10.107.35.26) port 9080 (#0)
+* found 1 certificates in /etc/certs/root-cert.pem
+* found 0 certificates in /etc/ssl/certs
+* ALPN, offering http/1.1
+* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
+* server certificate verification SKIPPED
+* server certificate status verification SKIPPED
+* error fetching CN from cert:The requested data were not available.
+* common name: (does not match 'details')
+* server certificate expiration date OK
+* server certificate activation date OK
+* certificate public key: RSA
+* certificate version: #3
+* subject: O=#1300
+* start date: Thu, 26 Oct 2018 14:36:56 GMT
+* expire date: Wed, 05 Jan 2019 14:36:56 GMT
+* issuer: O=k8s.cluster.local
+* compression: NULL
+* ALPN, server accepted to use http/1.1
+> GET /details/0 HTTP/1.1
+> Host: details:9080
+> User-Agent: curl/7.47.0
+> Accept: */*
+>
+< HTTP/1.1 200 OK
+< content-type: application/json
+< server: envoy
+< date: Thu, 07 Jun 2018 15:19:46 GMT
+< content-length: 178
+< x-envoy-upstream-service-time: 1
+< x-envoy-decorator-operation: default-route
+<
+* Connection #0 to host details left intact
+{"id":0,"author":"William Shakespeare","year":1595,"type":"paperback","pages":200,"publisher":"PublisherA","language":"English","ISBN-10":"1234567890","ISBN-13":"123-1234567890"}
+```
+
+This proves the existence of mTLS between the services on the Istio mesh.
+
+Now lets come out of the container before we go to the next section:
+
+```sh
+exit
+```
+
+
+ Secure Production Identity Framework for Everyone (SPIFFE)
+
+
+Istio uses [SPIFFE](https://spiffe.io/) to assert the identify of workloads on
+the cluster. SPIFFE consists of a notion of identity and a method of proving it.
+A SPIFFE identity consists of an authority part and a path. The meaning of the
+path in spiffe land is implementation defined. In k8s it takes the form
+`/ns/$namespace/sa/$service-account` with the expected meaning. A SPIFFE
+identify is embedded in a document. This document in principle can take many
+forms but currently the only defined format is x509.
+
+To start our investigation, let us check if the certs are in place in the productpage sidecar:
+
+```sh
+kubectl exec $(kubectl get pod -l app=productpage -o jsonpath={.items..metadata.name}) -c istio-proxy -- ls /etc/certs
+```
+
+Output will be similar to:
+
+```sh
+cert-chain.pem
+key.pem
+root-cert.pem
+```
+
+Mac users, MacOS should have openssl available. If your machine does not have openssl install, install it using your preferred method.
+
+Here is one way to install it on RHEL or CentOS or its derivatives:
+
+```sh
+sudo yum install -y openssl-devel
+```
+
+Here is one way to install it on Ubuntu or Debian or its derivatives:
+
+```sh
+sudo apt install -y libssl-dev
+```
+
+Now that we have found the certs, let us verify the certificate of productpage sidecar by running this command:
+
+```sh
+kubectl exec $(kubectl get pod -l app=productpage -o jsonpath={.items..metadata.name}) -c istio-proxy -- cat /etc/certs/cert-chain.pem | openssl x509 -text -noout | grep Validity -A 2
+```
+
+Output will be similar to:
+
+```sh
+ Not Before: Sep 23 17:32:28 2019 GMT
+ Not After : Dec 22 17:32:28 2019 GMT
+```
+
+Lets also verify the URI SAN:
+
+```sh
+kubectl exec $(kubectl get pod -l app=productpage -o jsonpath={.items..metadata.name}) -c istio-proxy -- cat /etc/certs/cert-chain.pem | openssl x509 -text -noout | grep 'Subject Alternative Name' -A 1
+```
+
+Output will be similar to:
+
+```sh
+X509v3 Subject Alternative Name: critical
+ URI:spiffe://cluster.local/ns/default/sa/bookinfo-productpage
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/observability.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/observability.mdx
index ef5a5ceecc73..c263773c8cf5 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/observability.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/observability.mdx
@@ -1,246 +1,246 @@
----
-docType: "Chapter"
-chapterTitle: "Observability"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 4
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import ImageAppIcon from "../../../../src/assets/images/learn-layer5/istio/istio-addons.webp";
-import GraffanaDash from "../../../../src/assets/images/learn-layer5/istio/Grafana_Istio_Dashboard.webp";
-import Prometheus from "../../../../src/assets/images/learn-layer5/istio/Prometheus.webp";
-import Jaeger from "../../../../src/assets/images/learn-layer5/istio/jaeger.webp";
-
-
-
-
Install Telemetry Add-ons
-
-Using Meshery, install Istio telemetry add-ons. In the Istio management page:
-
-1. Click the (+) icon on the `Apply Service Mesh Configuration` card.
-1. Select each of the following add-ons:
- 1. [Prometheus](https://prometheus.io/)
- 1. [Grafana](https://grafana.com/)
- 1. [Jaeger](https://www.jaegertracing.io/)
-
-
-
-
-
-You will use Prometheus and Grafana for collecting and viewing metrics and [Jaeger](https://www.jaegertracing.io/) collecting and viewing distributed traces. Expose each add-on external to the cluster. Each the service network typs are set to "LoadBalancer".
-
-
Service Mesh Performance and Telemetry
-
-Many of the labs require load to be placed on the sample apps. Let's generate HTTP traffic against the BookInfo application, so we can see interesting telemetry.
-
-Verify access through the Ingress Gateway:
-
-```sh
-kubectl get service istio-ingressgateway -n istio-system
-```
-
-Once we have the port, we can append the IP of one of the nodes to get the host.
-
-The URL to run a load test against will be `http://:/productpage`
-
-**Please note:** If you are using Docker Desktop, please use the IP address of your host. You can leave the port blank. For example: `http://1.2.3.4/productpage`. Managed kubernetes service users will need to use `http:///productpage` as done in expose services section.
-
-Use the computed URL above in Meshery, in the browser, to run a load test and see the results.
-
-
- Connect Grafana (optionally, Prometheus) to Meshery.
-
-
-On the Settings page:
-
-1. Navigate to the `Metrics` tab.
-1. Enter Grafana's URL:port number and submit.
-
-
- Use Meshery to generate load and analyze performance.
-
-
-On the Performance page:
-
-1. give this load test a memorable name
-1. enter the URL to the BookInfo productpage
-1. select `Istio` in the `Service Mesh` dropdown
-1. enter a valid number for `Concurrent requests`
-1. enter a valid number for `Queries per second`
-1. enter a valid `Duration` (a number followed by `s` for seconds (OR) `m` for minutes (OR) `h` for hour)
-1. use the host IP address in the request Tab and in the advanced options, type in the header as `Host:`
-
-Click on `Run Test`. A performance test will run and statistical analysis performed. Examine the results of the test and behavior of the service mesh.
-
-Next, you will begin controlling requests to BookInfo using traffic management features.
-
-
-
Alternative: Manual installation
-Follow these steps if the above steps did not work
-
-
-
-
-
-Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress.
-
-**Option 1: Expose services with NodePort**
-To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
-
-**Option 2: Expose services with port-forwarding**
-Port-forwarding runs in the foreground. We have appeneded `&` to the end of the above 2 commands to run them in the background. If you donot want this behavior, please remove the `&` from the end.
-
-
Prometheus
-
-You will need to expose the Prometheus service on a port either of the two following methods:
-
-**Option 1: Expose services with NodePort**
-
-```sh
-kubectl -n istio-system edit svc prometheus
-```
-
-To find the assigned ports for Prometheus:
-
-```sh
-kubectl -n istio-system get svc prometheus
-```
-
-**Option 2: Expose Prometheus service with port-forwarding:**
-\*\*
-Expose Prometheus service with port-forwarding:
-
-```sh
-kubectl -n istio-system port-forward \
- $(kubectl -n istio-system get pod -l app=prometheus -o jsonpath='{.items[0].metadata.name}') \
- 9090:9090 &
-```
-
-Browse to `http://:` and in the `Expression` input box enter: `istio_request_bytes_count`. Click the Execute button.
-
-
-
-
-
-
-
Grafana
-
-You will need to expose the Grafana service on a port either of the two following methods:
-
-```sh
-kubectl -n istio-system edit svc grafana
-```
-
-Once this is done the services will be assigned dedicated ports on the hosts.
-
-To find the assigned ports for Grafana:
-
-```sh
-kubectl -n istio-system get svc grafana
-```
-
-**Expose Grafana service with port-forwarding:**
-
-```sh
-kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=grafana \
- -o jsonpath='{.items[0].metadata.name}') 3000:3000 &
-```
-
-
-
-
-
-
Distributed Tracing
-
-The sample Bookinfo application is configured to collect trace spans using Zipkin or Jaeger. Although Istio proxies are able to automatically send spans, it needs help from the application to tie together the entire trace. To do this applications need to propagate the appropriate HTTP headers so that when the proxies send span information to Zipkin or Jaeger, the spans can be correlated correctly into a single trace.
-
-To do this the application collects and propagates the following headers from the incoming request to any outgoing requests:
-
-- `x-request-id`
-- `x-b3-traceid`
-- `x-b3-spanid`
-- `x-b3-parentspanid`
-- `x-b3-sampled`
-- `x-b3-flags`
-- `x-ot-span-context`
-
-
-
-
-
-
-
-
-
-
-
Exposing services
-
-Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress. In this lab, we will briefly demonstrate the `NodePort` and port-forwarding ways of exposing services.
-
-
Option 1: Expose services with NodePort
-
-To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
-
-For Jaeger, either of `tracing` or `jaeger-query` can be exposed.
-
-```sh
-kubectl -n istio-system edit svc tracing
-```
-
-Once this is done the services will be assigned dedicated ports on the hosts.
-
-To find the assigned ports for Jaeger:
-
-```sh
-kubectl -n istio-system get svc tracing
-```
-
-
- Option 2: Expose services with port-forwarding
-
-
-Let us find the port Jaeger is exposed on by running the following command:
-
-```sh
-kubectl -n istio-system get svc tracing
-```
-
-You can click on the link at the top of the page which maps to the right port and it will open Jaeger UI in a new tab.
-
-
+---
+docType: "Chapter"
+chapterTitle: "Observability"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 4
+---
+
+
+import ImageAppIcon from "../../../../src/assets/images/learn-layer5/istio/istio-addons.webp";
+import GraffanaDash from "../../../../src/assets/images/learn-layer5/istio/Grafana_Istio_Dashboard.webp";
+import Prometheus from "../../../../src/assets/images/learn-layer5/istio/Prometheus.webp";
+import Jaeger from "../../../../src/assets/images/learn-layer5/istio/jaeger.webp";
+
+
+
+
Install Telemetry Add-ons
+
+Using Meshery, install Istio telemetry add-ons. In the Istio management page:
+
+1. Click the (+) icon on the `Apply Service Mesh Configuration` card.
+1. Select each of the following add-ons:
+ 1. [Prometheus](https://prometheus.io/)
+ 1. [Grafana](https://grafana.com/)
+ 1. [Jaeger](https://www.jaegertracing.io/)
+
+
+
+
+
+You will use Prometheus and Grafana for collecting and viewing metrics and [Jaeger](https://www.jaegertracing.io/) collecting and viewing distributed traces. Expose each add-on external to the cluster. Each the service network typs are set to "LoadBalancer".
+
+
Service Mesh Performance and Telemetry
+
+Many of the labs require load to be placed on the sample apps. Let's generate HTTP traffic against the BookInfo application, so we can see interesting telemetry.
+
+Verify access through the Ingress Gateway:
+
+```sh
+kubectl get service istio-ingressgateway -n istio-system
+```
+
+Once we have the port, we can append the IP of one of the nodes to get the host.
+
+The URL to run a load test against will be `http://:/productpage`
+
+**Please note:** If you are using Docker Desktop, please use the IP address of your host. You can leave the port blank. For example: `http://1.2.3.4/productpage`. Managed kubernetes service users will need to use `http:///productpage` as done in expose services section.
+
+Use the computed URL above in Meshery, in the browser, to run a load test and see the results.
+
+
+ Connect Grafana (optionally, Prometheus) to Meshery.
+
+
+On the Settings page:
+
+1. Navigate to the `Metrics` tab.
+1. Enter Grafana's URL:port number and submit.
+
+
+ Use Meshery to generate load and analyze performance.
+
+
+On the Performance page:
+
+1. give this load test a memorable name
+1. enter the URL to the BookInfo productpage
+1. select `Istio` in the `Service Mesh` dropdown
+1. enter a valid number for `Concurrent requests`
+1. enter a valid number for `Queries per second`
+1. enter a valid `Duration` (a number followed by `s` for seconds (OR) `m` for minutes (OR) `h` for hour)
+1. use the host IP address in the request Tab and in the advanced options, type in the header as `Host:`
+
+Click on `Run Test`. A performance test will run and statistical analysis performed. Examine the results of the test and behavior of the service mesh.
+
+Next, you will begin controlling requests to BookInfo using traffic management features.
+
+
+
Alternative: Manual installation
+Follow these steps if the above steps did not work
+
+
+
+
+
+Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress.
+
+**Option 1: Expose services with NodePort**
+To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
+
+**Option 2: Expose services with port-forwarding**
+Port-forwarding runs in the foreground. We have appeneded `&` to the end of the above 2 commands to run them in the background. If you donot want this behavior, please remove the `&` from the end.
+
+
Prometheus
+
+You will need to expose the Prometheus service on a port either of the two following methods:
+
+**Option 1: Expose services with NodePort**
+
+```sh
+kubectl -n istio-system edit svc prometheus
+```
+
+To find the assigned ports for Prometheus:
+
+```sh
+kubectl -n istio-system get svc prometheus
+```
+
+**Option 2: Expose Prometheus service with port-forwarding:**
+\*\*
+Expose Prometheus service with port-forwarding:
+
+```sh
+kubectl -n istio-system port-forward \
+ $(kubectl -n istio-system get pod -l app=prometheus -o jsonpath='{.items[0].metadata.name}') \
+ 9090:9090 &
+```
+
+Browse to `http://:` and in the `Expression` input box enter: `istio_request_bytes_count`. Click the Execute button.
+
+
+
+
+
+
+
Grafana
+
+You will need to expose the Grafana service on a port either of the two following methods:
+
+```sh
+kubectl -n istio-system edit svc grafana
+```
+
+Once this is done the services will be assigned dedicated ports on the hosts.
+
+To find the assigned ports for Grafana:
+
+```sh
+kubectl -n istio-system get svc grafana
+```
+
+**Expose Grafana service with port-forwarding:**
+
+```sh
+kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=grafana \
+ -o jsonpath='{.items[0].metadata.name}') 3000:3000 &
+```
+
+
+
+
+
+
Distributed Tracing
+
+The sample Bookinfo application is configured to collect trace spans using Zipkin or Jaeger. Although Istio proxies are able to automatically send spans, it needs help from the application to tie together the entire trace. To do this applications need to propagate the appropriate HTTP headers so that when the proxies send span information to Zipkin or Jaeger, the spans can be correlated correctly into a single trace.
+
+To do this the application collects and propagates the following headers from the incoming request to any outgoing requests:
+
+- `x-request-id`
+- `x-b3-traceid`
+- `x-b3-spanid`
+- `x-b3-parentspanid`
+- `x-b3-sampled`
+- `x-b3-flags`
+- `x-ot-span-context`
+
+
+
+
+
+
+
+
+
+
+
Exposing services
+
+Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress. In this lab, we will briefly demonstrate the `NodePort` and port-forwarding ways of exposing services.
+
+
Option 1: Expose services with NodePort
+
+To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
+
+For Jaeger, either of `tracing` or `jaeger-query` can be exposed.
+
+```sh
+kubectl -n istio-system edit svc tracing
+```
+
+Once this is done the services will be assigned dedicated ports on the hosts.
+
+To find the assigned ports for Jaeger:
+
+```sh
+kubectl -n istio-system get svc tracing
+```
+
+
+ Option 2: Expose services with port-forwarding
+
+
+Let us find the port Jaeger is exposed on by running the following command:
+
+```sh
+kubectl -n istio-system get svc tracing
+```
+
+You can click on the link at the top of the page which maps to the right port and it will open Jaeger UI in a new tab.
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/routing-and-canary.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/routing-and-canary.mdx
index 6330ca93a5fc..4a44d45742d9 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/routing-and-canary.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/istio/routing-and-canary.mdx
@@ -1,330 +1,330 @@
----
-docType: "Chapter"
-chapterTitle: "Request Routing and Canary Testing"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 5
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-In this chapter, we are going to get our hands on some of the traffic management capabilities of Istio.
-
-
-
-
Apply default destination rules
-
-
-Before we start playing with Istio's traffic management capabilities, we need to define the available versions of the deployed services. In Istio parlance, versions are called subsets. Subsets are defined in destination rules.
-
-Run the following in the custom yaml section to create default destination rules for the Bookinfo services:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
- name: productpage
-spec:
- host: productpage
- subsets:
- - name: v1
- labels:
- version: v1
----
-
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
-name: reviews
-spec:
-host: reviews
-subsets: - name: v1
-labels:
-version: v1 - name: v2
-labels:
-version: v2 - name: v3
-labels:
-version: v3
-
----
-
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
-name: ratings
-spec:
-host: ratings
-subsets: - name: v1
-labels:
-version: v1 - name: v2
-labels:
-version: v2 - name: v2-mysql
-labels:
-version: v2-mysql - name: v2-mysql-vm
-labels:
-version: v2-mysql-vm
-
----
-
-apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
-name: details
-spec:
-host: details
-subsets: - name: v1
-labels:
-version: v1 - name: v2
-labels:
-version: v2
-
----
-
-```
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-1. Click the (+) icon on the `Apply Service Mesh Configuration` card and select `Bookinfo subsets` from the list.
-
-This will deploy the destination rules for all the Book info services defining their subsets. Verify the destination rules created by using the command below:
-
-```sh
-kubectl get destinationrules
-
-
-kubectl get destinationrules -o yaml
-```
-
-
- Configure the default route for all services to V1
-
-
-
-As part of the bookinfo sample app, there are multiple versions of reviews service. When we load the `/productpage` in the browser multiple times we have seen the reviews service round robin between v1, v2 or v3. As the first exercise, let us first restrict traffic to just V1 of all the services.
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-To view the applied rule:
-
-```sh
-kubectl get virtualservice
-```
-
-To take a look at a specific one:
-
-```sh
-kubectl get virtualservice reviews -o yaml
-```
-
-_Please note:_ In the place of the above command, we can either use kubectl or istioctl.
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: reviews
-spec:
- hosts:
- - reviews
- http:
- - route:
- - destination:
- host: reviews
- subset: v1
----
-
-```
-
-Now when we reload the `/productpage` several times, we will ONLY be viewing the data from v1 of all the services, which means we will not see any ratings (any stars).
-
-
Content-based routing
-
-
-Let's replace our first rules with a new set. Enable the `ratings` service for a
-user `jason` by routing `productpage` traffic to `reviews` v2:
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-This will update the existing virtual service definition for reviews to route all traffic for user `jason` to review V2.
-
-In a few, we should be able to verify the virtual service by using the command below:
-
-```sh
-kubectl get virtualservice reviews -o yaml
-```
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: reviews
-spec:
- hosts:
- - reviews
- http:
- - match:
- - headers:
- end-user:
- exact: jason
- route:
- - destination:
- host: reviews
- subset: v2
- - route:
- - destination:
- host: reviews
- subset: v1
----
-
-```
-
-Now if we login as your `jason`, you will be able to see data from `reviews` v2. While if you NOT logged in or logged in as a different user, you will see data from `reviews` v1.
-
-
Canary Testing - Traffic Shifting
-
-
-
Canary testing w/50% load
-
-To start canary testing, let's begin by transferring 50% of the traffic from reviews:v1 to reviews:v3 with the following command:
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-This will update the existing virtual service definition for reviews to route 50% of all traffic to review V3.
-
-In a few, we should be able to verify the virtual service by using the command below:
-
-```sh
-kubectl get virtualservice reviews -o yaml
-```
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: reviews
-spec:
- hosts:
- - reviews
- http:
- - route:
- - destination:
- host: reviews
- subset: v1
- weight: 50
- - destination:
- host: reviews
- subset: v3
- weight: 50
----
-
-```
-
-Now, if we reload the `/productpage` in your browser several times, you should now see red-colored star ratings approximately 50% of the time.
-
-
Shift 100% to v3
-
-When version v3 of the reviews microservice is considered stable, we can route 100% of the traffic to reviews:v3:
-
-Using Meshery, navigate to the Istio management page:
-
-1. Enter `default` in the `Namespace` field.
-2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
-
-This will update the existing virtual service definition for reviews to route 100% of all traffic to review V3.
-
-In a few, we should be able to verify the virtual service by using the command below:
-
-```sh
-kubectl get virtualservice reviews -o yaml
-```
-
-Config:
-
-```yaml
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
- name: reviews
-spec:
- hosts:
- - reviews
- http:
- - route:
- - destination:
- host: reviews
- subset: v3
----
-
-```
-
-Now, if we reload the `/productpage` in your browser several times, you should now see red-colored star ratings 100% of the time.
-
-
-
Alternative: Manual installation
-Follow these steps if the above steps did not work
-
-
-
-
Default destination rules
-
-Run the following command to create default destination rules for the Bookinfo services:
-
-```sh
-kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml
-```
-
-
- {" "}
- Route all traffic to version V1 of all services
-
- {" "}
- Route 100% of traffic to version V3 of reviews service
-
-
-```sh
-kubectl apply -f samples/bookinfo/networking/virtual-service-reviews-v3.yaml
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Request Routing and Canary Testing"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 5
+---
+
+
+
+
+In this chapter, we are going to get our hands on some of the traffic management capabilities of Istio.
+
+
+
+
Apply default destination rules
+
+
+Before we start playing with Istio's traffic management capabilities, we need to define the available versions of the deployed services. In Istio parlance, versions are called subsets. Subsets are defined in destination rules.
+
+Run the following in the custom yaml section to create default destination rules for the Bookinfo services:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+ name: productpage
+spec:
+ host: productpage
+ subsets:
+ - name: v1
+ labels:
+ version: v1
+---
+
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+name: reviews
+spec:
+host: reviews
+subsets: - name: v1
+labels:
+version: v1 - name: v2
+labels:
+version: v2 - name: v3
+labels:
+version: v3
+
+---
+
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+name: ratings
+spec:
+host: ratings
+subsets: - name: v1
+labels:
+version: v1 - name: v2
+labels:
+version: v2 - name: v2-mysql
+labels:
+version: v2-mysql - name: v2-mysql-vm
+labels:
+version: v2-mysql-vm
+
+---
+
+apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+name: details
+spec:
+host: details
+subsets: - name: v1
+labels:
+version: v1 - name: v2
+labels:
+version: v2
+
+---
+
+```
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+1. Click the (+) icon on the `Apply Service Mesh Configuration` card and select `Bookinfo subsets` from the list.
+
+This will deploy the destination rules for all the Book info services defining their subsets. Verify the destination rules created by using the command below:
+
+```sh
+kubectl get destinationrules
+
+
+kubectl get destinationrules -o yaml
+```
+
+
+ Configure the default route for all services to V1
+
+
+
+As part of the bookinfo sample app, there are multiple versions of reviews service. When we load the `/productpage` in the browser multiple times we have seen the reviews service round robin between v1, v2 or v3. As the first exercise, let us first restrict traffic to just V1 of all the services.
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+To view the applied rule:
+
+```sh
+kubectl get virtualservice
+```
+
+To take a look at a specific one:
+
+```sh
+kubectl get virtualservice reviews -o yaml
+```
+
+_Please note:_ In the place of the above command, we can either use kubectl or istioctl.
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: reviews
+spec:
+ hosts:
+ - reviews
+ http:
+ - route:
+ - destination:
+ host: reviews
+ subset: v1
+---
+
+```
+
+Now when we reload the `/productpage` several times, we will ONLY be viewing the data from v1 of all the services, which means we will not see any ratings (any stars).
+
+
Content-based routing
+
+
+Let's replace our first rules with a new set. Enable the `ratings` service for a
+user `jason` by routing `productpage` traffic to `reviews` v2:
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+This will update the existing virtual service definition for reviews to route all traffic for user `jason` to review V2.
+
+In a few, we should be able to verify the virtual service by using the command below:
+
+```sh
+kubectl get virtualservice reviews -o yaml
+```
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: reviews
+spec:
+ hosts:
+ - reviews
+ http:
+ - match:
+ - headers:
+ end-user:
+ exact: jason
+ route:
+ - destination:
+ host: reviews
+ subset: v2
+ - route:
+ - destination:
+ host: reviews
+ subset: v1
+---
+
+```
+
+Now if we login as your `jason`, you will be able to see data from `reviews` v2. While if you NOT logged in or logged in as a different user, you will see data from `reviews` v1.
+
+
Canary Testing - Traffic Shifting
+
+
+
Canary testing w/50% load
+
+To start canary testing, let's begin by transferring 50% of the traffic from reviews:v1 to reviews:v3 with the following command:
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+This will update the existing virtual service definition for reviews to route 50% of all traffic to review V3.
+
+In a few, we should be able to verify the virtual service by using the command below:
+
+```sh
+kubectl get virtualservice reviews -o yaml
+```
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: reviews
+spec:
+ hosts:
+ - reviews
+ http:
+ - route:
+ - destination:
+ host: reviews
+ subset: v1
+ weight: 50
+ - destination:
+ host: reviews
+ subset: v3
+ weight: 50
+---
+
+```
+
+Now, if we reload the `/productpage` in your browser several times, you should now see red-colored star ratings approximately 50% of the time.
+
+
Shift 100% to v3
+
+When version v3 of the reviews microservice is considered stable, we can route 100% of the traffic to reviews:v3:
+
+Using Meshery, navigate to the Istio management page:
+
+1. Enter `default` in the `Namespace` field.
+2. Click the (+) icon on the `Apply Custom Configuration` card and paste the configuration below.
+
+This will update the existing virtual service definition for reviews to route 100% of all traffic to review V3.
+
+In a few, we should be able to verify the virtual service by using the command below:
+
+```sh
+kubectl get virtualservice reviews -o yaml
+```
+
+Config:
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+ name: reviews
+spec:
+ hosts:
+ - reviews
+ http:
+ - route:
+ - destination:
+ host: reviews
+ subset: v3
+---
+
+```
+
+Now, if we reload the `/productpage` in your browser several times, you should now see red-colored star ratings 100% of the time.
+
+
+
Alternative: Manual installation
+Follow these steps if the above steps did not work
+
+
+
+
Default destination rules
+
+Run the following command to create default destination rules for the Bookinfo services:
+
+```sh
+kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml
+```
+
+
+ {" "}
+ Route all traffic to version V1 of all services
+
+ You have successfully completed the course on{" "}
+ "Introduction to service meshes - Hands on" using{" "}
+
+ Linkerd
+
+ .
+
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/dashboard.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/dashboard.mdx
index b678e8016966..772d0ec19592 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/dashboard.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/dashboard.mdx
@@ -1,109 +1,109 @@
----
-docType: "Chapter"
-chapterTitle: "Linkerd Dashboard"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 4
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import Top from "../../../../src/assets/images/learn-layer5/linkerd/top.webp";
-import Tap from "../../../../src/assets/images/learn-layer5/linkerd/tap.webp";
-
-
-
-
Introduction to Linkerd Dashboard
-
-The Dashboard provides a clickable user interface for administration of Linkerd. The Dashboard provides measurements of success rate, requests/second and latency for services on the mesh. Run the Linkerd Dashboard, by executing:
-
-```sh
-linkerd dashboard &
-```
-
-This command port-forwards from your local system to the `linkerd-web` service. You can also expose the dashboard using Kubernetes `ingress`, which we will see later in this section.
-
-Since Linkerd's control plane components have the Linkerd proxy sidecarred, you can examine statistics of the traffic you are generating by looking at the dashboard. Execute:
-
-```sh
-linkerd -n linkerd top deploy/linkerd-web
-```
-
-
Exposing the dashboard
-
-Instead of using linkerd dashboard & every time you'd like to see what's going on, you can expose the dashboard via an ingress. We will use the Nginx ingress, which we had deployed and used in Lab 3.
-
-We will be applying Nginx ingress-traffic rule with basic authentication protocol
-
-```sh
-apiVersion: v1
-kind: Secret
-type: Opaque
-metadata:
- name: web-ingress-auth
- namespace: linkerd
-data:
- auth: YWRtaW46JGFwcjEkbjdDdTZnSGwkRTQ3b2dmN0NPOE5SWWpFakJPa1dNLgoK
----
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
- name: web-ingress
- namespace: linkerd
- annotations:
- kubernetes.io/ingress.class: "nginx"
- nginx.ingress.kubernetes.io/upstream-vhost: $service_name.$namespace.svc.cluster.local:8084
- nginx.ingress.kubernetes.io/configuration-snippet: |
- proxy_set_header Origin "";
- proxy_hide_header l5d-remote-ip;
- proxy_hide_header l5d-server-id;
- nginx.ingress.kubernetes.io/auth-type: basic
- nginx.ingress.kubernetes.io/auth-secret: web-ingress-auth
- nginx.ingress.kubernetes.io/auth-realm: "Authentication Required"
-spec:
- rules:
- - host: dashboard.example.com
- http:
- paths:
- - backend:
- serviceName: linkerd-web
- servicePort: 8084
-```
-
-This exposes the dashboard at `dashboard.example.com` and protects it with basic auth with credentials admin,admin.
-
-From here you may need to modify your resolv.conf to add `dashboard.example.com` to localhost or use an alternative approach in order to see the dashboard deployment. We will not cover this in the workshop.
-
-
Tools exposed by dashboard
-
-Linkerd dashboard exposes various CLI tools which may come handy while you debug your application running on mesh.
-
-Mainly there are three tools which Linkerd exposes as an extension to it's CLI commands
-
-**stat**
-
-This will show the “golden” metrics for each deployment:
-
-1. Success rates
-1. Request rates
-1. Latency distribution percentiles
-
-**top**
-
-To get a real-time view of which paths are being called.
-
-{" "}
-
-
-
-
-**tap**
-
-Shows the stream of requests across a single pod, deployment, or even everything in the emojivoto namespace.
-
-{" "}
-
-
-
-
-
+---
+docType: "Chapter"
+chapterTitle: "Linkerd Dashboard"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 4
+---
+
+
+import Top from "../../../../src/assets/images/learn-layer5/linkerd/top.webp";
+import Tap from "../../../../src/assets/images/learn-layer5/linkerd/tap.webp";
+
+
+
+
Introduction to Linkerd Dashboard
+
+The Dashboard provides a clickable user interface for administration of Linkerd. The Dashboard provides measurements of success rate, requests/second and latency for services on the mesh. Run the Linkerd Dashboard, by executing:
+
+```sh
+linkerd dashboard &
+```
+
+This command port-forwards from your local system to the `linkerd-web` service. You can also expose the dashboard using Kubernetes `ingress`, which we will see later in this section.
+
+Since Linkerd's control plane components have the Linkerd proxy sidecarred, you can examine statistics of the traffic you are generating by looking at the dashboard. Execute:
+
+```sh
+linkerd -n linkerd top deploy/linkerd-web
+```
+
+
Exposing the dashboard
+
+Instead of using linkerd dashboard & every time you'd like to see what's going on, you can expose the dashboard via an ingress. We will use the Nginx ingress, which we had deployed and used in Lab 3.
+
+We will be applying Nginx ingress-traffic rule with basic authentication protocol
+
+```sh
+apiVersion: v1
+kind: Secret
+type: Opaque
+metadata:
+ name: web-ingress-auth
+ namespace: linkerd
+data:
+ auth: YWRtaW46JGFwcjEkbjdDdTZnSGwkRTQ3b2dmN0NPOE5SWWpFakJPa1dNLgoK
+---
+apiVersion: extensions/v1beta1
+kind: Ingress
+metadata:
+ name: web-ingress
+ namespace: linkerd
+ annotations:
+ kubernetes.io/ingress.class: "nginx"
+ nginx.ingress.kubernetes.io/upstream-vhost: $service_name.$namespace.svc.cluster.local:8084
+ nginx.ingress.kubernetes.io/configuration-snippet: |
+ proxy_set_header Origin "";
+ proxy_hide_header l5d-remote-ip;
+ proxy_hide_header l5d-server-id;
+ nginx.ingress.kubernetes.io/auth-type: basic
+ nginx.ingress.kubernetes.io/auth-secret: web-ingress-auth
+ nginx.ingress.kubernetes.io/auth-realm: "Authentication Required"
+spec:
+ rules:
+ - host: dashboard.example.com
+ http:
+ paths:
+ - backend:
+ serviceName: linkerd-web
+ servicePort: 8084
+```
+
+This exposes the dashboard at `dashboard.example.com` and protects it with basic auth with credentials admin,admin.
+
+From here you may need to modify your resolv.conf to add `dashboard.example.com` to localhost or use an alternative approach in order to see the dashboard deployment. We will not cover this in the workshop.
+
+
Tools exposed by dashboard
+
+Linkerd dashboard exposes various CLI tools which may come handy while you debug your application running on mesh.
+
+Mainly there are three tools which Linkerd exposes as an extension to it's CLI commands
+
+**stat**
+
+This will show the “golden” metrics for each deployment:
+
+1. Success rates
+1. Request rates
+1. Latency distribution percentiles
+
+**top**
+
+To get a real-time view of which paths are being called.
+
+{" "}
+
+
+
+
+**tap**
+
+Shows the stream of requests across a single pod, deployment, or even everything in the emojivoto namespace.
+
+{" "}
+
+
+
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/debugging.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/debugging.mdx
index 66c92495e4ef..fd6546c7d3b4 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/debugging.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/debugging.mdx
@@ -1,61 +1,61 @@
----
-docType: "Chapter"
-chapterTitle: "Debugging (Optional)"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 5
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import Octopus from "../../../../src/assets/images/learn-layer5/linkerd/octopus.webp";
-import WebTop from "../../../../src/assets/images/learn-layer5/linkerd/webtop.webp";
-import WebTap from "../../../../src/assets/images/learn-layer5/linkerd/webtap.webp";
-
-
-
-
Debugging application using Linkerd
-
-We will be using Linkerd to debug the sample application, we had deployed earlier in the workshop. The demo application emojivoto has some issues. Let's use that and Linkerd to diagnose an application that fails in ways which are a little more subtle than the entire service crashing.
-
-Let's jump into debugging the Emojivoto application right away.
-
-
-
-
Exploring the Linkerd Dashboard
-
-In the event that you look at the Linkerd dashboard (by running the `linkerd dashboard` command), you should see all the resources in the emojivoto namespace, including the deployments. Every deployments running Linkerd shows success rate, requests per second and latency percentiles. If you see closely, you will observe success rate is below 100% because of some buggy endpoint present in the service.
-
-
-
-
-
-The first thing you'll see here is that the web deployment is taking traffic from vote-bot (a deployment included with emojivoto to continually generate a low level of live traffic). The web deployment also has two outgoing dependencies, emoji and voting.
-
-While the emoji deployment is handling every request from web successfully, it looks like the voting deployment is failing some requests! A failure in a dependent deployment may be exactly what is causing the errors that web is returning.
-
-
Debugging the application
-
-Scrolling down a little from the deployment page, we'll see a live list of all traffic that is incoming to and outgoing from web.
-
-
-
-
-
-There are two calls that are not at 100%: the first is vote-bot's call to the '/api/vote' endpoint. The second is the 'VoteDoughnut' call from the web organization to its needy arrangement, casting a ballot.
-
-Since '/api/vote' is an approaching call, and 'VoteDoughnut' is an active call, this is a decent sign that this endpoint is what's causing the issue!
-
-To burrow somewhat more profound, we can click on the `tap` symbol in the extreme right section. This will take us to the live rundown of requests that match just this endpoint. You'll see 'Unknown under the GRPC status section'.
-
-
-
-
-
-This is because the requests are failing with a [gRPC status code 2](https://pkg.go.dev/google.golang.org/grpc/codes#Code), which is a common error response.
-
-_Note: Linkerd is aware of gRPC's response classification without any other configuration._
-
-Now at this point we have all the necessary debugging information which can help us to restore the application to stable/working state.
-
-
+---
+docType: "Chapter"
+chapterTitle: "Debugging (Optional)"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 5
+---
+
+
+import Octopus from "../../../../src/assets/images/learn-layer5/linkerd/octopus.webp";
+import WebTop from "../../../../src/assets/images/learn-layer5/linkerd/webtop.webp";
+import WebTap from "../../../../src/assets/images/learn-layer5/linkerd/webtap.webp";
+
+
+
+
Debugging application using Linkerd
+
+We will be using Linkerd to debug the sample application, we had deployed earlier in the workshop. The demo application emojivoto has some issues. Let's use that and Linkerd to diagnose an application that fails in ways which are a little more subtle than the entire service crashing.
+
+Let's jump into debugging the Emojivoto application right away.
+
+
+
+
Exploring the Linkerd Dashboard
+
+In the event that you look at the Linkerd dashboard (by running the `linkerd dashboard` command), you should see all the resources in the emojivoto namespace, including the deployments. Every deployments running Linkerd shows success rate, requests per second and latency percentiles. If you see closely, you will observe success rate is below 100% because of some buggy endpoint present in the service.
+
+
+
+
+
+The first thing you'll see here is that the web deployment is taking traffic from vote-bot (a deployment included with emojivoto to continually generate a low level of live traffic). The web deployment also has two outgoing dependencies, emoji and voting.
+
+While the emoji deployment is handling every request from web successfully, it looks like the voting deployment is failing some requests! A failure in a dependent deployment may be exactly what is causing the errors that web is returning.
+
+
Debugging the application
+
+Scrolling down a little from the deployment page, we'll see a live list of all traffic that is incoming to and outgoing from web.
+
+
+
+
+
+There are two calls that are not at 100%: the first is vote-bot's call to the '/api/vote' endpoint. The second is the 'VoteDoughnut' call from the web organization to its needy arrangement, casting a ballot.
+
+Since '/api/vote' is an approaching call, and 'VoteDoughnut' is an active call, this is a decent sign that this endpoint is what's causing the issue!
+
+To burrow somewhat more profound, we can click on the `tap` symbol in the extreme right section. This will take us to the live rundown of requests that match just this endpoint. You'll see 'Unknown under the GRPC status section'.
+
+
+
+
+
+This is because the requests are failing with a [gRPC status code 2](https://pkg.go.dev/google.golang.org/grpc/codes#Code), which is a common error response.
+
+_Note: Linkerd is aware of gRPC's response classification without any other configuration._
+
+Now at this point we have all the necessary debugging information which can help us to restore the application to stable/working state.
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/deploy-an-application.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/deploy-an-application.mdx
index 88584098cffb..7aa64b843ce2 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/deploy-an-application.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/deploy-an-application.mdx
@@ -1,197 +1,197 @@
----
-docType: "Chapter"
-chapterTitle: "Deploy a sample application"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 2
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-To play with Linkerd and demonstrate some of it's capabilities, you will deploy the sample application, EmojiVoto.
-
-
What is the EmojiVoto Application
-
-
-Emojivoto is a sample microservice application that allows users to vote for their favorite emoji.
-It displays votes received on a leaderboard. Emojivoto has no dependencies on Linkerd, but will run
-fine either on or off the service mesh.
-
-A sidecar injector is used for automating the injection of the Linkerd proxy into your application's pod spec. The Kubernetes admission controller enforces this behavior send
-sending a webhook request the the sidecar injector every time a pod is to be scheduled. This injector inspects resources for a Linkerd-specific annotation (linkerd.io/inject: enabled).
-When that annotation exists, the injector mutates the pod's specification and adds both an init container as well as a sidecar containing the proxy itself.
-
-The Linkerd sidecar proxy can be either manually or automatically injected into your application's pods. This can be done from the meshery dashboard for namespace globally by,
-
-1. Using Meshery, navigate to the Linkerd management page.
-1. Click the (+) icon on the `Configure Application` card and select `Annotate Namespace` from the list.
-
-As part of Linkerd deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
-To verify, execute this command:
-
-```sh
-kubectl get deployment linkerd-proxy-injector -n linkerd
-```
-
-Output:
-
-```sh
-NAME READY UP-TO-DATE AVAILABLE AGE
-linkerd-proxy-injector 1/1 1 1 9m49s
-```
-
-Examine the annotation added to the `linkerd` namespace:
-
-```sh
-kubectl describe namespace linkerd
-```
-
-Output:
-
-```sh
-Name: linkerd
-Labels: config.linkerd.io/admission-webhooks=disabled
- linkerd.io/control-plane-ns=linkerd
- linkerd.io/is-control-plane=true
-Annotations: linkerd.io/inject: disabled
-Status: Active
-
-No resource quota.
-
-No LimitRange resource.
-```
-
-
Deploy the application
-
-Using Meshery, navigate to the Linkerd management page.
-
-1. Enter `default` in the `Namespace` field.
-1. Click the (+) icon on the `Sample Application` card and select `Emojivoto Application` from the list.
-
-This will do 3 things:
-
-1. Label the `emojivoto` namespace for sidecar injection.
-1. Deploys all the Emojivoto services and replica's in the `emojivoto` namespace.
-
-
-
Alternative: Manual installation
-Follow this if the above steps did not work for you
-
-
-
-
Deploy emojivoto application
-
-Install emojivoto into the emojivoto namespace by running:
-
-```sh
-curl -sL https://run.linkerd.io/emojivoto.yml \
- | kubectl apply -f -
-```
-
-Before we mesh it, let's take a look at the app.
-If you're using Docker Desktop at this point you can visit http://localhost directly.
-If you're not using Docker Desktop, we'll need to forward the web-svc service.
-To forward web-svc locally to port 8080, you can run:
-
-```sh
-kubectl -n emojivoto port-forward svc/web-svc 8080:80
-```
-
-
- Verify EmojiVoto deployment{" "}
-
-
-1. Verify that the deployments are all in a state of AVAILABLE before continuing.
-
- ```sh
- watch kubectl get deployment -n emojivoto
- ```
-
-2. Inspect the details of the pods
-
- Examine details of the pods:
-
- ```sh
- watch kubectl get po -n emojivoto
- ```
-
- Examine details of the services:
-
- ```sh
- watch kubectl get svc -n emojivoto
- ```
-
- Choose one of EmojiVoto's services (e.g. `web-svc`), and view it's sidecar configuration:
-
- ```sh
- kubectl get svc -n emojivoto
-
- kubectl describe service svc/web-svc -n emojivoto
- ```
-
-Let's look at the application deployment by port-forwarding the `web-svc` service:
-
-```sh
-kubectl port-forward svc/web-svc 8080:80 -n emojivoto
-```
-
-You have onboarded emojivoto to the service mesh. Verify your data plane environment with this check:
-
-```sh
-linkerd -n emojivoto check --proxy
-```
-
-Linkerd, in contrast to Istio annotates the resources (namespaces, deployment workloads) rather than labelling them.
-
-
Deploy EmojiVoto
-
-Applying this yaml file included in the Linkerd package you collected in https://run.linkerd.io/emojivoto.yml
-will deploy the sample app into your cluster.
-
-```sh
-kubectl apply -f https://run.linkerd.io/emojivoto.yml
-```
-
-
- Inject Linkerd proxy into the sample application
-
-
-The emojivoto application is a standalone Kubernetes application that uses a mix of gRPC and
-HTTP calls to allow the users to vote on their favorite emojis, which means the
-application can run standalone without support from linkerd service mesh. Now we will
-be injecting linkerd into our sample application
-
-```sh
-kubectl get -n emojivoto deploy -o yaml \
- | linkerd inject - \
- | kubectl apply -f -
-```
-
-Or...
-
-```sh
-kubectl -n emojivoto patch -f https://run.linkerd.io/emojivoto.yml -p '
-spec:
- template:
- metadata:
- annotations:
- linkerd.io/inject: enabled
-'
-```
-
-Either of these commands retrieve all of the deployments running in the emojivoto namespace, runs the manifest
-through linkerd inject, and then reapplies it to the cluster. The linkerd inject command adds annotations to the pod spec
-instructing Linkerd to add (“inject”) the proxy as a container to the pod spec.
-
-You've now added Linkerd to existing services! Just as with the control plane, it
-is possible to verify that everything worked the way it should with the data plane.
-To do this check, run:
-
-```sh
-linkerd -n emojivoto check --proxy
-```
-
-
+---
+docType: "Chapter"
+chapterTitle: "Deploy a sample application"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 2
+---
+
+
+
+
+
+To play with Linkerd and demonstrate some of it's capabilities, you will deploy the sample application, EmojiVoto.
+
+
What is the EmojiVoto Application
+
+
+Emojivoto is a sample microservice application that allows users to vote for their favorite emoji.
+It displays votes received on a leaderboard. Emojivoto has no dependencies on Linkerd, but will run
+fine either on or off the service mesh.
+
+A sidecar injector is used for automating the injection of the Linkerd proxy into your application's pod spec. The Kubernetes admission controller enforces this behavior send
+sending a webhook request the the sidecar injector every time a pod is to be scheduled. This injector inspects resources for a Linkerd-specific annotation (linkerd.io/inject: enabled).
+When that annotation exists, the injector mutates the pod's specification and adds both an init container as well as a sidecar containing the proxy itself.
+
+The Linkerd sidecar proxy can be either manually or automatically injected into your application's pods. This can be done from the meshery dashboard for namespace globally by,
+
+1. Using Meshery, navigate to the Linkerd management page.
+1. Click the (+) icon on the `Configure Application` card and select `Annotate Namespace` from the list.
+
+As part of Linkerd deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
+To verify, execute this command:
+
+```sh
+kubectl get deployment linkerd-proxy-injector -n linkerd
+```
+
+Output:
+
+```sh
+NAME READY UP-TO-DATE AVAILABLE AGE
+linkerd-proxy-injector 1/1 1 1 9m49s
+```
+
+Examine the annotation added to the `linkerd` namespace:
+
+```sh
+kubectl describe namespace linkerd
+```
+
+Output:
+
+```sh
+Name: linkerd
+Labels: config.linkerd.io/admission-webhooks=disabled
+ linkerd.io/control-plane-ns=linkerd
+ linkerd.io/is-control-plane=true
+Annotations: linkerd.io/inject: disabled
+Status: Active
+
+No resource quota.
+
+No LimitRange resource.
+```
+
+
Deploy the application
+
+Using Meshery, navigate to the Linkerd management page.
+
+1. Enter `default` in the `Namespace` field.
+1. Click the (+) icon on the `Sample Application` card and select `Emojivoto Application` from the list.
+
+This will do 3 things:
+
+1. Label the `emojivoto` namespace for sidecar injection.
+1. Deploys all the Emojivoto services and replica's in the `emojivoto` namespace.
+
+
+
Alternative: Manual installation
+Follow this if the above steps did not work for you
+
+
+
+
Deploy emojivoto application
+
+Install emojivoto into the emojivoto namespace by running:
+
+```sh
+curl -sL https://run.linkerd.io/emojivoto.yml \
+ | kubectl apply -f -
+```
+
+Before we mesh it, let's take a look at the app.
+If you're using Docker Desktop at this point you can visit http://localhost directly.
+If you're not using Docker Desktop, we'll need to forward the web-svc service.
+To forward web-svc locally to port 8080, you can run:
+
+```sh
+kubectl -n emojivoto port-forward svc/web-svc 8080:80
+```
+
+
+ Verify EmojiVoto deployment{" "}
+
+
+1. Verify that the deployments are all in a state of AVAILABLE before continuing.
+
+ ```sh
+ watch kubectl get deployment -n emojivoto
+ ```
+
+2. Inspect the details of the pods
+
+ Examine details of the pods:
+
+ ```sh
+ watch kubectl get po -n emojivoto
+ ```
+
+ Examine details of the services:
+
+ ```sh
+ watch kubectl get svc -n emojivoto
+ ```
+
+ Choose one of EmojiVoto's services (e.g. `web-svc`), and view it's sidecar configuration:
+
+ ```sh
+ kubectl get svc -n emojivoto
+
+ kubectl describe service svc/web-svc -n emojivoto
+ ```
+
+Let's look at the application deployment by port-forwarding the `web-svc` service:
+
+```sh
+kubectl port-forward svc/web-svc 8080:80 -n emojivoto
+```
+
+You have onboarded emojivoto to the service mesh. Verify your data plane environment with this check:
+
+```sh
+linkerd -n emojivoto check --proxy
+```
+
+Linkerd, in contrast to Istio annotates the resources (namespaces, deployment workloads) rather than labelling them.
+
+
Deploy EmojiVoto
+
+Applying this yaml file included in the Linkerd package you collected in https://run.linkerd.io/emojivoto.yml
+will deploy the sample app into your cluster.
+
+```sh
+kubectl apply -f https://run.linkerd.io/emojivoto.yml
+```
+
+
+ Inject Linkerd proxy into the sample application
+
+
+The emojivoto application is a standalone Kubernetes application that uses a mix of gRPC and
+HTTP calls to allow the users to vote on their favorite emojis, which means the
+application can run standalone without support from linkerd service mesh. Now we will
+be injecting linkerd into our sample application
+
+```sh
+kubectl get -n emojivoto deploy -o yaml \
+ | linkerd inject - \
+ | kubectl apply -f -
+```
+
+Or...
+
+```sh
+kubectl -n emojivoto patch -f https://run.linkerd.io/emojivoto.yml -p '
+spec:
+ template:
+ metadata:
+ annotations:
+ linkerd.io/inject: enabled
+'
+```
+
+Either of these commands retrieve all of the deployments running in the emojivoto namespace, runs the manifest
+through linkerd inject, and then reapplies it to the cluster. The linkerd inject command adds annotations to the pod spec
+instructing Linkerd to add (“inject”) the proxy as a container to the pod spec.
+
+You've now added Linkerd to existing services! Just as with the control plane, it
+is possible to verify that everything worked the way it should with the data plane.
+To do this check, run:
+
+```sh
+linkerd -n emojivoto check --proxy
+```
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/expose-services.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/expose-services.mdx
index 3518a4a02e4a..b03845d5d500 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/expose-services.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/expose-services.mdx
@@ -1,119 +1,119 @@
----
-docType: "Chapter"
-chapterTitle: "Exposing services through Linkerd Ingress"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 3
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-
Ingressing and Egressing with Linkerd
-
-Linkerd's control plane does not include ingress or egress gateways. Linkerd allows you choice of your preferred ingress (and egress) controller.
-
-
How to use Ingress with Linkerd
-
-In case you're anticipating infusing Linkerd into your ingress controller's pods there is some setup required. Linkerd discovers
-services dependent on the `:authority` or `Host` header. This permits Linkerd to comprehend what service a request is bound for without
-being subject to DNS or IPs.
-
-In this workshop, you will use the NGINX Ingress Controller with Linkerd.
-
-
Installing NGINX Ingress Controller
-
-Using Meshery, select the Linkerd from the Management menu, and:
-
-1. Enter ingress-nginx into the namespace field.
-1. Click the (+) icon on the Apply Service Mesh Configuration card and select NGINX Ingress Controller to install the latest version of KIC.
-
-
Alternative: Manual installation
-Follow this if the above steps did not work for you
-
-
-
-
-
Installing NGINX Ingress Controller
-
-Install ingress controller using Docker Desktop
-
-```sh
-kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.40.2/deploy/static/provider/cloud/deploy.yaml
-```
-
-Install the ingress controller using Minikube
-
-```sh
-minikube addons enable ingress
-```
-
-
- {" "}
- Setting up Ingress controller with the sample application deployed
-
-
-Using Meshery, click the ➡️ icon on the `Apply Custom Configuration` card and apply the following manifest to your cluster:
-
-```sh
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
- name: web-ingress
- namespace: emojivoto
- annotations:
- kubernetes.io/ingress.class: "nginx"
- nginx.ingress.kubernetes.io/configuration-snippet: |
- proxy_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
- grpc_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
-
-spec:
- rules:
- - host: example.com
- http:
- paths:
- - backend:
- serviceName: web-svc
- servicePort: 80
-```
-
-Nginx ingress will include the `l5d-dst-override` header to tell Linkerd where to direct the request.
-You'll need to include both the Kubernetes administration FQDN (web-svc.emojivoto.svc.cluster.local) and the destination servicePort.
-
-To test this, you need to get the external IP of your controller.
-
-
Docker Desktop
-
-You may use http://localhost or http://kubernetes.docker.internal or your host's IP address.
-
-
Minikube
-
-Expose your Kubernetes's cluster services to your localhost network:
-
-```sh
-minikube tunnel
-```
-
-You may use http://localhost or You may use http://localhost: provided by the output of `minikube tunnel`.
-
-
Hosted Kubernetes
-
-Retrieve the external IP address by running:
-
-```sh
-kubectl get svc --all-namespaces \
- -l app=nginx-ingress,component=controller \
- -o=custom-columns=EXTERNAL-IP:.status.loadBalancer.ingress[0].ip
-```
-
-You can now curl to your service without using port-forward, like this:
-
-```sh
-curl -H "Host: example.com" http://{external-ip}
-```
-
-
-
-
+---
+docType: "Chapter"
+chapterTitle: "Exposing services through Linkerd Ingress"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 3
+---
+
+
+
+
+
+
Ingressing and Egressing with Linkerd
+
+Linkerd's control plane does not include ingress or egress gateways. Linkerd allows you choice of your preferred ingress (and egress) controller.
+
+
How to use Ingress with Linkerd
+
+In case you're anticipating infusing Linkerd into your ingress controller's pods there is some setup required. Linkerd discovers
+services dependent on the `:authority` or `Host` header. This permits Linkerd to comprehend what service a request is bound for without
+being subject to DNS or IPs.
+
+In this workshop, you will use the NGINX Ingress Controller with Linkerd.
+
+
Installing NGINX Ingress Controller
+
+Using Meshery, select the Linkerd from the Management menu, and:
+
+1. Enter ingress-nginx into the namespace field.
+1. Click the (+) icon on the Apply Service Mesh Configuration card and select NGINX Ingress Controller to install the latest version of KIC.
+
+
Alternative: Manual installation
+Follow this if the above steps did not work for you
+
+
+
+
+
Installing NGINX Ingress Controller
+
+Install ingress controller using Docker Desktop
+
+```sh
+kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.40.2/deploy/static/provider/cloud/deploy.yaml
+```
+
+Install the ingress controller using Minikube
+
+```sh
+minikube addons enable ingress
+```
+
+
+ {" "}
+ Setting up Ingress controller with the sample application deployed
+
+
+Using Meshery, click the ➡️ icon on the `Apply Custom Configuration` card and apply the following manifest to your cluster:
+
+```sh
+apiVersion: extensions/v1beta1
+kind: Ingress
+metadata:
+ name: web-ingress
+ namespace: emojivoto
+ annotations:
+ kubernetes.io/ingress.class: "nginx"
+ nginx.ingress.kubernetes.io/configuration-snippet: |
+ proxy_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
+ grpc_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
+
+spec:
+ rules:
+ - host: example.com
+ http:
+ paths:
+ - backend:
+ serviceName: web-svc
+ servicePort: 80
+```
+
+Nginx ingress will include the `l5d-dst-override` header to tell Linkerd where to direct the request.
+You'll need to include both the Kubernetes administration FQDN (web-svc.emojivoto.svc.cluster.local) and the destination servicePort.
+
+To test this, you need to get the external IP of your controller.
+
+
Docker Desktop
+
+You may use http://localhost or http://kubernetes.docker.internal or your host's IP address.
+
+
Minikube
+
+Expose your Kubernetes's cluster services to your localhost network:
+
+```sh
+minikube tunnel
+```
+
+You may use http://localhost or You may use http://localhost: provided by the output of `minikube tunnel`.
+
+
Hosted Kubernetes
+
+Retrieve the external IP address by running:
+
+```sh
+kubectl get svc --all-namespaces \
+ -l app=nginx-ingress,component=controller \
+ -o=custom-columns=EXTERNAL-IP:.status.loadBalancer.ingress[0].ip
+```
+
+You can now curl to your service without using port-forward, like this:
+
+```sh
+curl -H "Host: example.com" http://{external-ip}
+```
+
+
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/fault-injection.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/fault-injection.mdx
index 6ab8241d6bf9..240c0b20558e 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/fault-injection.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/fault-injection.mdx
@@ -1,175 +1,175 @@
----
-docType: "Chapter"
-chapterTitle: "Fault Injection"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 8
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-
-
-
-
Fault Injection using SMI in Linkerd
-
-Application failure injection is a form of chaos engineering where we artificially increase the error rate of certain services in a microservice application to see what impact that has on the system as a whole. Traditionally, you would need to add some kind of failure injection library into your service code in order to do application failure injection. Thankfully, the service mesh gives us a way to inject application failures without needing to modify or rebuild our services at all.
-
-
- Using SMI Traffic Split API to inject errors
-
-
-We can easily inject application failures by using the Traffic Split API of the Service Mesh Interface. This allows us to do failure injection in a way that is implementation agnostic and works across service meshes.
-
-We will do this first by deploying a new service which only return errored responses. We will be using a simple NGINX service which has configured to only return HTTP 500 responses.
-
-We will then create a traffic split which would redirect the service mesh to send a sample percentage of traffic to the error service instead, let's say 20% of service's traffic to error, then we would have injected an artificial 20% error rate in service.
-
-
Deploy Linkerd Books Application
-
-We will be deploying [Linkerd Books application](https://github.com/BuoyantIO/booksapp) for this part of the demo
-
-Use meshery to deploy the bookinfo application :
-
-- In Meshery, navigate to the Linkerd adapter's management page from the left nav menu.
-- On the Linkerd adapter's management page, please enter `default` in the `Namespace` field.
-- Then, click the (+) icon on the `Sample Application` card and select `Books Application` from the list.
-
-Inject linkerd into sample application using
-
-```sh
-linkerd inject https://run.linkerd.io/booksapp.yml | kubectl apply -f -
-```
-
-In the following, one of the service has already beeen configured with the error let's remove the error rate from the same :
-
-```sh
-kubectl edit deploy/authors
-```
-
-Remove the lines
-
-```sh
-- name: FAILURE_RATE
- value: "0.5
-```
-
-Now if you will see `linkerd stat`, the success rate would be 100%
-
-```sh
-linkerd stat deploy
-```
-
-
Create the errored service
-
-Now we will create our error service, we have NGINX pre-configured to only respond with HTTP 500 status code
-
-```sh
-apiVersion: apps/v1
-kind: Deployment
-metadata:
- name: error-injector
- labels:
- app: error-injector
-spec:
- selector:
- matchLabels:
- app: error-injector
- replicas: 1
- template:
- metadata:
- labels:
- app: error-injector
- spec:
- containers:
- - name: nginx
- image: nginx:alpine
- ports:
- - containerPort: 80
- name: nginx
- protocol: TCP
- volumeMounts:
- - name: nginx-config
- mountPath: /etc/nginx/nginx.conf
- subPath: nginx.conf
- volumes:
- - name: nginx-config
- configMap:
- name: error-injector-config
----
-apiVersion: v1
-kind: Service
-metadata:
- labels:
- app: error-injector
- name: error-injector
-spec:
- clusterIP: None
- ports:
- - name: service
- port: 7002
- protocol: TCP
- targetPort: nginx
- selector:
- app: error-injector
- type: ClusterIP
----
-apiVersion: v1
-data:
- nginx.conf: |2
-
- events {
- worker_connections 1024;
- }
-
- http {
- server {
- location / {
- return 500;
- }
- }
- }
-kind: ConfigMap
-metadata:
- name: error-injector-config
-```
-
-After deploying the above errored service, we will create a traffic split resource which will be responsible to direct 20% of the book service to the error.
-
-```sh
-apiVersion: split.smi-spec.io/v1alpha3
-kind: TrafficSplit
-metadata:
- name: fault-inject
-spec:
- service: books
- backends:
- - service: books
- weight: 800m
- - service: error-injector
- weight: 200m
-```
-
-You can now see an 20% error rate for calls from webapp to books
-
-```sh
-linkerd routes deploy/webapp --to service/books
-```
-
-You can also see the error on the web browser
-
-```sh
-kubectl port-forward deploy/webapp 7000 && open http://localhost:7000
-```
-
-If you refresh page few times, you will see `Internal Server Error`.
-
-
Cleanup
-
-```sh
-kubectl delete trafficsplit/error-split
-```
-
-- Remove the book info application from the `Meshery Dashboard` by clicking on the `trash icon` in the `sample application` card on the linkerd adapters' page.
-
-
+---
+docType: "Chapter"
+chapterTitle: "Fault Injection"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 8
+---
+
+
+
+
+
+
Fault Injection using SMI in Linkerd
+
+Application failure injection is a form of chaos engineering where we artificially increase the error rate of certain services in a microservice application to see what impact that has on the system as a whole. Traditionally, you would need to add some kind of failure injection library into your service code in order to do application failure injection. Thankfully, the service mesh gives us a way to inject application failures without needing to modify or rebuild our services at all.
+
+
+ Using SMI Traffic Split API to inject errors
+
+
+We can easily inject application failures by using the Traffic Split API of the Service Mesh Interface. This allows us to do failure injection in a way that is implementation agnostic and works across service meshes.
+
+We will do this first by deploying a new service which only return errored responses. We will be using a simple NGINX service which has configured to only return HTTP 500 responses.
+
+We will then create a traffic split which would redirect the service mesh to send a sample percentage of traffic to the error service instead, let's say 20% of service's traffic to error, then we would have injected an artificial 20% error rate in service.
+
+
Deploy Linkerd Books Application
+
+We will be deploying [Linkerd Books application](https://github.com/BuoyantIO/booksapp) for this part of the demo
+
+Use meshery to deploy the bookinfo application :
+
+- In Meshery, navigate to the Linkerd adapter's management page from the left nav menu.
+- On the Linkerd adapter's management page, please enter `default` in the `Namespace` field.
+- Then, click the (+) icon on the `Sample Application` card and select `Books Application` from the list.
+
+Inject linkerd into sample application using
+
+```sh
+linkerd inject https://run.linkerd.io/booksapp.yml | kubectl apply -f -
+```
+
+In the following, one of the service has already beeen configured with the error let's remove the error rate from the same :
+
+```sh
+kubectl edit deploy/authors
+```
+
+Remove the lines
+
+```sh
+- name: FAILURE_RATE
+ value: "0.5
+```
+
+Now if you will see `linkerd stat`, the success rate would be 100%
+
+```sh
+linkerd stat deploy
+```
+
+
Create the errored service
+
+Now we will create our error service, we have NGINX pre-configured to only respond with HTTP 500 status code
+
+```sh
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+ name: error-injector
+ labels:
+ app: error-injector
+spec:
+ selector:
+ matchLabels:
+ app: error-injector
+ replicas: 1
+ template:
+ metadata:
+ labels:
+ app: error-injector
+ spec:
+ containers:
+ - name: nginx
+ image: nginx:alpine
+ ports:
+ - containerPort: 80
+ name: nginx
+ protocol: TCP
+ volumeMounts:
+ - name: nginx-config
+ mountPath: /etc/nginx/nginx.conf
+ subPath: nginx.conf
+ volumes:
+ - name: nginx-config
+ configMap:
+ name: error-injector-config
+---
+apiVersion: v1
+kind: Service
+metadata:
+ labels:
+ app: error-injector
+ name: error-injector
+spec:
+ clusterIP: None
+ ports:
+ - name: service
+ port: 7002
+ protocol: TCP
+ targetPort: nginx
+ selector:
+ app: error-injector
+ type: ClusterIP
+---
+apiVersion: v1
+data:
+ nginx.conf: |2
+
+ events {
+ worker_connections 1024;
+ }
+
+ http {
+ server {
+ location / {
+ return 500;
+ }
+ }
+ }
+kind: ConfigMap
+metadata:
+ name: error-injector-config
+```
+
+After deploying the above errored service, we will create a traffic split resource which will be responsible to direct 20% of the book service to the error.
+
+```sh
+apiVersion: split.smi-spec.io/v1alpha3
+kind: TrafficSplit
+metadata:
+ name: fault-inject
+spec:
+ service: books
+ backends:
+ - service: books
+ weight: 800m
+ - service: error-injector
+ weight: 200m
+```
+
+You can now see an 20% error rate for calls from webapp to books
+
+```sh
+linkerd routes deploy/webapp --to service/books
+```
+
+You can also see the error on the web browser
+
+```sh
+kubectl port-forward deploy/webapp 7000 && open http://localhost:7000
+```
+
+If you refresh page few times, you will see `Internal Server Error`.
+
+
Cleanup
+
+```sh
+kubectl delete trafficsplit/error-split
+```
+
+- Remove the book info application from the `Meshery Dashboard` by clicking on the `trash icon` in the `sample application` card on the linkerd adapters' page.
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/getting-started.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/getting-started.mdx
index 4082120358c4..0f7b3a1f8059 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/getting-started.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/getting-started.mdx
@@ -1,117 +1,118 @@
----
-doctype: "Chapter"
-chapterTitle: "Getting Started"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 6
-lectures: 8
-order: 1
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import LinkerdAdapter from "../../../../src/assets/images/learn-layer5/linkerd/linkerd-adapter.webp";
-import InstallLinkerd from "../../../../src/assets/images/learn-layer5/linkerd/install-linkerd.webp";
-
-
-
-
Setup Linkerd
-
-Now that we have a Kubernetes cluster and Meshery, we are ready to download and deploy Linkerd resources.
-
-
-
-Using Meshery, select `Linkerd` from the `Management` menu.
-
-
-
-
-
-In the Linkerd management page:
-
-1. Type `linkerd` into the namespace field.
-1. Click the (+) icon on the `Install` card and select `Latest Linkerd` to install the latest version of Linkerd.
-
-
-
- {" "}
-
-
Alternative: Manual Installation
-
-Perform the below steps if the above steps doesn't work for you.
-
-
Download `linkerd` CLI
-
-On a \*nix system, you can setup linkerd by doing the following:
-
-The above command will get the latest Linkerd package and untar it in the same folder.
-
-Change into the Linkerd package directory and add the linkerd client to your PATH environment variable.
-
-```sh
-curl -sL https://run.linkerd.io/install | sh
-export PATH=$PATH:$HOME/.linkerd2/bin
-```
-
-Alternatively, on MacOS you can sue `HomeBrew` to install `linkerd`
-
-```sh
-brew install linkerd
-```
-
-To verify `linkerd` is setup lets try to print out the command help
-
-```sh
-linkerd version
-```
-
-We can use a new feature in linkerd to check if the cluster is ready for install:
-
-```sh
-linkerd check --pre
-```
-
-
-
-Linkerd is deployed in the `linkerd` Kubernetes namespace. Verify that Linkerd and its components are deployed, execute the command:
-
-```sh
-linkerd check
-```
-
-
-
-By establishing mutually-authenticated connections between Linkerd proxies , Linkerd automatically enables mutual Transport Layer Security (mTLS) by default for most HTTP-based communication between services.
-
-
+
+Using Meshery, select `Linkerd` from the `Management` menu.
+
+
+
+
+
+In the Linkerd management page:
+
+1. Type `linkerd` into the namespace field.
+1. Click the (+) icon on the `Install` card and select `Latest Linkerd` to install the latest version of Linkerd.
+
+
+
+
+{" "}
+
+
Alternative: Manual Installation
+
+Perform the below steps if the above steps doesn't work for you.
+
+
Download `linkerd` CLI
+
+On a \*nix system, you can setup linkerd by doing the following:
+
+The above command will get the latest Linkerd package and untar it in the same folder.
+
+Change into the Linkerd package directory and add the linkerd client to your PATH environment variable.
+
+```sh
+curl -sL https://run.linkerd.io/install | sh
+export PATH=$PATH:$HOME/.linkerd2/bin
+```
+
+Alternatively, on MacOS you can sue `HomeBrew` to install `linkerd`
+
+```sh
+brew install linkerd
+```
+
+To verify `linkerd` is setup lets try to print out the command help
+
+```sh
+linkerd version
+```
+
+We can use a new feature in linkerd to check if the cluster is ready for install:
+
+```sh
+linkerd check --pre
+```
+
+
+
+Linkerd is deployed in the `linkerd` Kubernetes namespace. Verify that Linkerd and its components are deployed, execute the command:
+
+```sh
+linkerd check
+```
+
+
+
+By establishing mutually-authenticated connections between Linkerd proxies , Linkerd automatically enables mutual Transport Layer Security (mTLS) by default for most HTTP-based communication between services.
+
+
+
+Linkerd, as part of this workshop, is installed with several optional addons like:
+
+1. Prometheus (site)
+2. Grafana (site)
+3. Jaeger (site)
+4. Dashboard (site)
+
+You will use Meshery for collecting and viewing metrics, and Jaeger for viewing distributed traces.
+
+
diff --git a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/observability.mdx b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/observability.mdx
index 84aa3d895df9..828cfa92f5e8 100644
--- a/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/observability.mdx
+++ b/content-learn/mastering-service-meshes-for-developers/introduction-to-service-meshes/linkerd/observability.mdx
@@ -1,130 +1,130 @@
----
-docType: "Chapter"
-chapterTitle: "Observability"
-description: "Meshery, collaborative Kubernetes manager"
-videos: 4
-lectures: 12
-order: 6
----
-
-import { ChapterStyle } from "../../../../src/components/Learn-Components/Chapters-Style/chapters.style.js";
-import Tracing from "../../../../src/assets/images/learn-layer5/linkerd/emojivoto-tracing.webp";
-import JaegerUI from "../../../../src/assets/images/learn-layer5/linkerd/linkerd-jaeger-ui.webp";
-
-
-
-
Linkerd Telemetry and Distributed Tracing
-
-
-
-
Linkerd Telemetry
-
-Linkerd's telemetry and monitoring features function automatically, without requiring any work on the part of the developer.
-
-We have already looked at Linkerd Telemetry, not by name but by concept. Using stat, top and tap is one of the major and characteristic feature which Linkerd offers out of the box. All of this metrics are also accessible through Grafana Dashboard which Linkerd provides.
-
-Expose Grafana dashboard:
-
-```sh
-linkerd dashboard &
-```
-
-- Start `linkerd dashboard` & navigate over the service you would want to see Grafana Dashboard for.
-- In the last column, click of the `Grafana Icon` to access the metrics dashboard for the following deployment.
-
-
Distributed tracing with Linkerd
-
-Linkerd added support for Distributed Tracing, which means that if your application has enabled tracing based on B3 Propagation, Linkerd proxies would automatically recognize that (as the trace-id is propagated through http headers) and send their spans, provided that the proxies are configured regarding the meshed trace collector endpoint.
-
-To enable tracing onto your cluster :
-
-```sh
-cat >> config.yaml << EOF
-tracing:
- enabled: true
-EOF
-```
-
-This configuration file can also be used to apply Add-On configuration (not just specific to tracing Add-On).
-
-Let us apply that configuration to the linkerd upgrade command using the --addon-config flag and pipe that output to kubectl apply.
-
-```sh
-linkerd upgrade --addon-config config.yaml | kubectl apply -f -
-```
-
-Before moving onto the next step, make sure everything is up and running with kubectl:
-
-```sh
-kubectl -n linkerd rollout status deploy/linkerd-collector
-kubectl -n linkerd rollout status deploy/linkerd-jaeger
-```
-
-
Configure your sample application
-
-Apply the tracing configuration to the `emojivoto application`:
-
-```sh
-kubectl -n emojivoto patch -f https://run.linkerd.io/emojivoto.yml -p '
-spec:
- template:
- metadata:
- annotations:
- config.linkerd.io/trace-collector: linkerd-collector.linkerd:55678
- config.alpha.linkerd.io/trace-collector-service-account: linkerd-collector
-'
-```
-
-Before moving onto the next step, make sure everything is up and running with kubectl:
-
-```sh
-kubectl -n emojivoto rollout status deploy/web
-```
-
-The above command enables tracing in the linkerd proxies but the application containers still don’t have it enabled. Tracing can be enabled in the sample application can be enabled by
-
-To enable tracing in emojivoto, run:
-
-```sh
- kubectl -n emojivoto set env --all deploy OC_AGENT_HOST=linkerd-collector.linkerd:55678
-```
-
-
Explore Jaeger
-
-Now, you can port-forward the `linkerd-jaeger` service to checkout the traces.
-
-```sh
-kubectl -n linkerd port-forward svc/linkerd-jaeger 16686:16686
-```
-
-Now let's explore traces of the `vote-bot` endpoint:
-
-
-
-
-
-So, As you can see there are spans of the linkerd-proxy. For each request between two meshed components, you can see there are four linkerd-proxy spans.
-
-The first two spans would be the spans sent from the proxy of the client component and will be marked as outbound. Again, in these two spans, the first one is the span of the application -> proxy, and the second one is the proxy->otherside. They are differentiated by the server and client tags respectively.
-
-
-
-
Jaeger and Linkerd
-
-In Linkerd, as told above Grafana Integration is present in the `linkerd-web` ui
-through which which you can directly jump onto the dashboards of any workload
-like deployment, pod, etc.
-
-Linkerd has done similar thing with Jaeger, if you have `tracing` enabled, if you navigate the Linkerd Dashboard, you should see a Jaeger icon on the right.
-
-
-
-
-
-
+
+Linkerd's telemetry and monitoring features function automatically, without requiring any work on the part of the developer.
+
+We have already looked at Linkerd Telemetry, not by name but by concept. Using stat, top and tap is one of the major and characteristic feature which Linkerd offers out of the box. All of this metrics are also accessible through Grafana Dashboard which Linkerd provides.
+
+Expose Grafana dashboard:
+
+```sh
+linkerd dashboard &
+```
+
+- Start `linkerd dashboard` & navigate over the service you would want to see Grafana Dashboard for.
+- In the last column, click of the `Grafana Icon` to access the metrics dashboard for the following deployment.
+
+
Distributed tracing with Linkerd
+
+Linkerd added support for Distributed Tracing, which means that if your application has enabled tracing based on B3 Propagation, Linkerd proxies would automatically recognize that (as the trace-id is propagated through http headers) and send their spans, provided that the proxies are configured regarding the meshed trace collector endpoint.
+
+To enable tracing onto your cluster :
+
+```sh
+cat >> config.yaml << EOF
+tracing:
+ enabled: true
+EOF
+```
+
+This configuration file can also be used to apply Add-On configuration (not just specific to tracing Add-On).
+
+Let us apply that configuration to the linkerd upgrade command using the --addon-config flag and pipe that output to kubectl apply.
+
+```sh
+linkerd upgrade --addon-config config.yaml | kubectl apply -f -
+```
+
+Before moving onto the next step, make sure everything is up and running with kubectl:
+
+```sh
+kubectl -n linkerd rollout status deploy/linkerd-collector
+kubectl -n linkerd rollout status deploy/linkerd-jaeger
+```
+
+
Configure your sample application
+
+Apply the tracing configuration to the `emojivoto application`:
+
+```sh
+kubectl -n emojivoto patch -f https://run.linkerd.io/emojivoto.yml -p '
+spec:
+ template:
+ metadata:
+ annotations:
+ config.linkerd.io/trace-collector: linkerd-collector.linkerd:55678
+ config.alpha.linkerd.io/trace-collector-service-account: linkerd-collector
+'
+```
+
+Before moving onto the next step, make sure everything is up and running with kubectl:
+
+```sh
+kubectl -n emojivoto rollout status deploy/web
+```
+
+The above command enables tracing in the linkerd proxies but the application containers still don’t have it enabled. Tracing can be enabled in the sample application can be enabled by
+
+To enable tracing in emojivoto, run:
+
+```sh
+ kubectl -n emojivoto set env --all deploy OC_AGENT_HOST=linkerd-collector.linkerd:55678
+```
+
+
Explore Jaeger
+
+Now, you can port-forward the `linkerd-jaeger` service to checkout the traces.
+
+```sh
+kubectl -n linkerd port-forward svc/linkerd-jaeger 16686:16686
+```
+
+Now let's explore traces of the `vote-bot` endpoint:
+
+
+
+
+
+So, As you can see there are spans of the linkerd-proxy. For each request between two meshed components, you can see there are four linkerd-proxy spans.
+
+The first two spans would be the spans sent from the proxy of the client component and will be marked as outbound. Again, in these two spans, the first one is the span of the application -> proxy, and the second one is the proxy->otherside. They are differentiated by the server and client tags respectively.
+
+
+
+
Jaeger and Linkerd
+
+In Linkerd, as told above Grafana Integration is present in the `linkerd-web` ui
+through which which you can directly jump onto the dashboards of any workload
+like deployment, pod, etc.
+
+Linkerd has done similar thing with Jaeger, if you have `tracing` enabled, if you navigate the Linkerd Dashboard, you should see a Jaeger icon on the right.
+
+
+
+
+
+
-
-
-
-
-
-The destination component of the control plane looks for changes in configuration of linkerd (actualized as Kubernetes Custom Resource Definitions) and afterward pushes the right config for
-
-proxies to follow. As opposed to presenting its own configuration format for traffic splitting, Linkerd follows the [SMI spec](https://smi-spec.io/), which plans to give a brought together, summed up setup model for service meshes (simply like ingress, CRI, and so on in Kubernetes).
-
-
Deploying sample application
-
-We will be deploying [istio's bookinfo application](https://istio.io/latest/docs/examples/bookinfo/) for this part of the demo
-
-Use meshery to deploy the bookinfo application :
-
-- In Meshery, navigate to the Linkerd adapter's management page from the left nav menu.
-- On the Linkerd adapter's management page, please enter `default` in the `Namespace` field.
-- Then, click the (+) icon on the `Sample Application` card and select `Bookinfo Application` from the list.
-
-OR...
-
-- Download the [./sample/bookinfo.yaml](https://raw.githubusercontent.com/layer5io/linkerd-service-mesh-workshop/master/lab-7/sample/book-info.yaml)
-- Inject linkerd into the sample application.
-
-```sh
-linkerd inject ./sample/bookinfo.yaml | kubectl apply -f -
-```
-
-This will give you the if the Linkerd injection was successful or not.
-
-```sh
-linkerd stat deploy
-```
-
-You will see the following services running in your cluster
-
-```sh
- kubectl get svc
- NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
- details ClusterIP 10.96.115.62 9080/TCP 13m
- kubernetes ClusterIP 10.96.0.1 443/TCP 7h56m
- productpage ClusterIP 10.109.31.20 9080/TCP 13m
- ratings ClusterIP 10.101.57.168 9080/TCP 13m
- reviews ClusterIP 10.105.52.139 9080/TCP 13m
-```
-
-You can access the producpage by port-forwarding
-
-```sh
- kubectl port-forward svc/productpage 9080:9080
-```
-
-Checking localhost:9080 would show you a product page, with a list of reviews on the right. Those reviews are being loaded from the reviews service which is backed by the 3 reviews pods. The requests to the reviews service are randomly sent to one of the 3 review pods, as they represent different versions of this service.
-
-The three different versions provide different output:
-
-- v1 with No stars
-- v2 with Orange stars
-- v3 with Black stars
-
-We will have reviews service only split traffic between v1 and v2 of the application.
-
-In Linkerd’s approach to traffic splitting, services are used as the core primitives. Hence we need to create two new services corresponding to v1 & v2 pods.
-
-```sh
-kubectl apply -f ./sample/service.yaml
-```
-
-There are two new services created
-
-```sh
- kubectl get svc
- NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
- details ClusterIP 10.96.115.62 9080/TCP 35m
- kubernetes ClusterIP 10.96.0.1 443/TCP 8h
- productpage ClusterIP 10.109.31.20 9080/TCP 35m
- ratings ClusterIP 10.101.57.168 9080/TCP 35m
- reviews ClusterIP 10.105.52.139 9080/TCP 35m
- reviews-v2 ClusterIP 10.106.174.219 9080/TCP 7s
- reviews-v3 ClusterIP 10.96.125.224 9080/TCP 7s
-```
-
-Now, let's apply traffic-split CRD from SMI :
-
-```sh
-apiVersion: split.smi-spec.io/v1alpha1
-kind: TrafficSplit
-metadata:
- name: reviews-split
-spec:
- service: reviews
- backends:
- - service: reviews-v1
- weight: 500m
- - service: reviews-v2
- weight: 500m
-```
-
-This tells Linkerd’s control plane that whenever there are requests to the reviews service, to split them across the `reviews-v1` and `reviews-v2` based on the weights provided.
-
-If we now go back to our product page, we can only see the reviews with orange or no stars appear on each refresh.
-
-
Cleanup
-
-```sh
-kubectl delete trafficsplit/reviews-split
-kubectl delete -f ./sample/service.yaml
-```
-
-- Remove the bookinfo application from the `Meshery Dashboard` by clicking on the `trash icon` in the `sample application` card on the linkerd adapters' page.
-
-
+---
+docType: "Chapter"
+chapterTitle: "Traffic Splitting using SMI and Linkerd"
+description: "Meshery, collaborative Kubernetes manager"
+videos: 4
+lectures: 12
+order: 7
+---
+
+
+import ControlPlane from "../../../../src/assets/images/learn-layer5/linkerd/control-plane-c.webp";
+
+
+
+
How Linkerd handles traffic splitting
+
+
+
+
+
+The destination component of the control plane looks for changes in configuration of linkerd (actualized as Kubernetes Custom Resource Definitions) and afterward pushes the right config for
+
+proxies to follow. As opposed to presenting its own configuration format for traffic splitting, Linkerd follows the [SMI spec](https://smi-spec.io/), which plans to give a brought together, summed up setup model for service meshes (simply like ingress, CRI, and so on in Kubernetes).
+
+
Deploying sample application
+
+We will be deploying [istio's bookinfo application](https://istio.io/latest/docs/examples/bookinfo/) for this part of the demo
+
+Use meshery to deploy the bookinfo application :
+
+- In Meshery, navigate to the Linkerd adapter's management page from the left nav menu.
+- On the Linkerd adapter's management page, please enter `default` in the `Namespace` field.
+- Then, click the (+) icon on the `Sample Application` card and select `Bookinfo Application` from the list.
+
+OR...
+
+- Download the [./sample/bookinfo.yaml](https://raw.githubusercontent.com/layer5io/linkerd-service-mesh-workshop/master/lab-7/sample/book-info.yaml)
+- Inject linkerd into the sample application.
+
+```sh
+linkerd inject ./sample/bookinfo.yaml | kubectl apply -f -
+```
+
+This will give you the if the Linkerd injection was successful or not.
+
+```sh
+linkerd stat deploy
+```
+
+You will see the following services running in your cluster
+
+```sh
+ kubectl get svc
+ NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+ details ClusterIP 10.96.115.62 9080/TCP 13m
+ kubernetes ClusterIP 10.96.0.1 443/TCP 7h56m
+ productpage ClusterIP 10.109.31.20 9080/TCP 13m
+ ratings ClusterIP 10.101.57.168 9080/TCP 13m
+ reviews ClusterIP 10.105.52.139 9080/TCP 13m
+```
+
+You can access the producpage by port-forwarding
+
+```sh
+ kubectl port-forward svc/productpage 9080:9080
+```
+
+Checking localhost:9080 would show you a product page, with a list of reviews on the right. Those reviews are being loaded from the reviews service which is backed by the 3 reviews pods. The requests to the reviews service are randomly sent to one of the 3 review pods, as they represent different versions of this service.
+
+The three different versions provide different output:
+
+- v1 with No stars
+- v2 with Orange stars
+- v3 with Black stars
+
+We will have reviews service only split traffic between v1 and v2 of the application.
+
+In Linkerd’s approach to traffic splitting, services are used as the core primitives. Hence we need to create two new services corresponding to v1 & v2 pods.
+
+```sh
+kubectl apply -f ./sample/service.yaml
+```
+
+There are two new services created
+
+```sh
+ kubectl get svc
+ NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+ details ClusterIP 10.96.115.62 9080/TCP 35m
+ kubernetes ClusterIP 10.96.0.1 443/TCP 8h
+ productpage ClusterIP 10.109.31.20 9080/TCP 35m
+ ratings ClusterIP 10.101.57.168 9080/TCP 35m
+ reviews ClusterIP 10.105.52.139 9080/TCP 35m
+ reviews-v2 ClusterIP 10.106.174.219 9080/TCP 7s
+ reviews-v3 ClusterIP 10.96.125.224 9080/TCP 7s
+```
+
+Now, let's apply traffic-split CRD from SMI :
+
+```sh
+apiVersion: split.smi-spec.io/v1alpha1
+kind: TrafficSplit
+metadata:
+ name: reviews-split
+spec:
+ service: reviews
+ backends:
+ - service: reviews-v1
+ weight: 500m
+ - service: reviews-v2
+ weight: 500m
+```
+
+This tells Linkerd’s control plane that whenever there are requests to the reviews service, to split them across the `reviews-v1` and `reviews-v2` based on the weights provided.
+
+If we now go back to our product page, we can only see the reviews with orange or no stars appear on each refresh.
+
+
-
-Before we start having *real* fun with Meshery, I will quickly list the different components I used for this blog post and ensure I define what could be optional for your own setup:
-1. [Meshery](https://layer5.io/cloud-native-management/meshery)
-2. [Docker](https://docs.docker.com/install/)
- - Docker is of course mandatory and as Meshery is based on a Compose file, which means that [docker-compose](https://docs.docker.com/compose/install/) is also mandatory.
-3. [k3d](https://github.com/rancher/k3d)
- - k3d or any k3s/K8s cluster that you might have already configured.
-4. [WSL2](https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/)
- - For the (few) ones who know me, my "OS base" is WSL2, which means that without much/any change, it should run fine for any Linux/MacOS setup.
-5. [Grafana](https://grafana.com/) *(optional)*
- - Grafana is not mandatory however is strongly recommend. We will setup a dockerized instance, but feel free to plug Meshery with your existing instance.
-
-
Nothing is taken for granted
-
-For the sake of making the blog post around Meshery, I won't explain how to install each component and will focus only on getting k3d and Meshery working.
-
-That said, I do not take anything for granted and as Scott Hanselman once taught me: there is no "just have to ..." or "by simply doing ...".
-
-If you face any issue with your setup (hopefully WSL2), just let me know on [Twitter](https://twitter.com/nunixtech) or on the [Layer5 Slack channel](http://slack.layer5.io).
-
-
Meshery Installation
-
-For the following steps, I will use the Ubuntu 18.04 WSL2 distro:
-
-- Start docker and confirm it's running:
-
-```bash
-sudo service docker start
-docker version
-```
-
-- Using Docker, install Meshery on your local machine by running the following:
-
-```bash
-curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
-```
-
-
-
-
-- Create a new k3d cluster with the WSL2 IP
-
-```bash
-export mainIP=`hostname -I | awk '{ print $1 }'`
-k3d list
-k3d create --workers 3 --api-port ${mainIP}:6443
-export KUBECONFIG="$(k3d get-kubeconfig --name='k3s-default')"
-kubectl cluster-info
-```
-
-
-
-
-
-- Start Meshery on the newly created cluster
-
-```bash
-mesheryctl system start
-```
-
-
-
-
-- Once Meshery is fully started, login in your preferred browser using the WSL2 IP instead of localhost
-
-```bash
-export BROWSER=/mnt/c/Firefox/firefox.exe
-$BROWSER $mainIP:9081 &
-```
-
-
-
-
-
-
-
-
-
-#### [Optional] More analytics with Grafana
-As stated above, Meshery can leverage the analytics provided by Grafana. For this blog post, as everything is built from scratch. Here is the setup for a new Grafana dockerized instance.
-
-Start a new Grafana on docker instance
-
-```bash
-docker run \
--d \
--p 3000:3000 \
---name=grafana \
--e "GF_SERVER_ROOT_URL=http://$mainIP" \
--e "GF_SECURITY_ADMIN_PASSWORD=MesheryInstance" \
-grafana/grafana
-```
-
-
-
-
-
-- Access the new instance with the admin password that you set in the docker environment variable
-```bash
-$BROWSER $mainIP:3000 &
-```
-
-
-
-
-
-
-
-
-
-### An inside look
-While everything should run fine, it's always good to have a look at what has been deployed.
-
-In this case, we are almost exclusively working with Docker and the "inside look" should look something like this:
-
-
-
-
-
-#### Conclusion
-As [Lee Calcote](https://twitter.com/lcalcote) put it, this is a lot of buzz words: Meshery > k3s (deployed via k3d) > Docker > WSL2 > Windows 10. And he's totally right, still the "beauty" here, is that it "simply works".
-
-Since the begin of the Docker era, new tooling has appeard for simplifying complex workflows.
-Even Kubernetes (K8s) as a much lighter version with k3s by Rancher.
-
-And of course, Meshery which integrates and simplifies the installation and benchmarking of different Kubernetes configurations. Hope you had fun assembling all these pieces and stay tunned for the "Bonuses", more fun to come!
-
- > > > Nunix out
-
-
-
+---
+title: "Getting started with Meshery, WSL2 and k3d"
+subtitle: ""
+date: 2019-07-09 12:00:00 +0000
+author: Nuno do Carmo
+thumbnail: ./cnab-logo.webp
+darkthumbnail: ./cnab-logo.webp
+category: Meshery
+tags:
+ - Community
+ - Meshery
+ - mesheryctl
+published: true
+type: Blog
+technology: Docker
+product: Meshery
+resource: true
+redirect_from:
+ - /blog/2019-07-09-getting-started-with-Meshery-WSL2-k3d/
+---
+
+
+import wsldockerstart from "./wsl-docker-start.webp";
+import wslgrafanalogin from "./wsl-grafana-login.webp";
+import wslgrafanaloginsuccess from "./wsl-grafana-login-success.webp";
+import wslgrafanastart from "./wsl-grafana-start.webp";
+import wslk3dstart from "./wsl-k3d-start.webp";
+import wslmesherycomplete from "./wsl-meshery-complete.webp";
+import wslmesherylogin from "./wsl-meshery-login.webp";
+import wslmesheryloginsuccess from "./wsl-meshery-login-success.webp";
+import wslmesherystart from "./wsl-meshery-start.webp";
+
+
+
+During KubeCon EU 2019, I had the chance to discover two new softwares that simply amazed me:
+1. [Meshery](https://layer5.io/cloud-native-management/meshery), which is the multi-cluster Kubernetes management plane.
+2. [k3d](https://github.com/rancher/k3d), which is used to create a dockerized [k3s](https://k3s.io) server.
+
+And, what really appealed to me about both of them is that everything from the installation to the usage was just *simple!*
+And cream on the top, both softwares are used with or inside containers, making each ideal for a create/try/delete workflow.
+
+
Environment Setup
+
+Before we start having *real* fun with Meshery, I will quickly list the different components I used for this blog post and ensure I define what could be optional for your own setup:
+1. [Meshery](https://layer5.io/cloud-native-management/meshery)
+2. [Docker](https://docs.docker.com/install/)
+ - Docker is of course mandatory and as Meshery is based on a Compose file, which means that [docker-compose](https://docs.docker.com/compose/install/) is also mandatory.
+3. [k3d](https://github.com/rancher/k3d)
+ - k3d or any k3s/K8s cluster that you might have already configured.
+4. [WSL2](https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/)
+ - For the (few) ones who know me, my "OS base" is WSL2, which means that without much/any change, it should run fine for any Linux/MacOS setup.
+5. [Grafana](https://grafana.com/) *(optional)*
+ - Grafana is not mandatory however is strongly recommend. We will setup a dockerized instance, but feel free to plug Meshery with your existing instance.
+
+
Nothing is taken for granted
+
+For the sake of making the blog post around Meshery, I won't explain how to install each component and will focus only on getting k3d and Meshery working.
+
+That said, I do not take anything for granted and as Scott Hanselman once taught me: there is no "just have to ..." or "by simply doing ...".
+
+If you face any issue with your setup (hopefully WSL2), just let me know on [Twitter](https://twitter.com/nunixtech) or on the [Layer5 Slack channel](http://slack.layer5.io).
+
+
Meshery Installation
+
+For the following steps, I will use the Ubuntu 18.04 WSL2 distro:
+
+- Start docker and confirm it's running:
+
+```bash
+sudo service docker start
+docker version
+```
+
+- Using Docker, install Meshery on your local machine by running the following:
+
+```bash
+curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
+```
+
+
+
+
+- Create a new k3d cluster with the WSL2 IP
+
+```bash
+export mainIP=`hostname -I | awk '{ print $1 }'`
+k3d list
+k3d create --workers 3 --api-port ${mainIP}:6443
+export KUBECONFIG="$(k3d get-kubeconfig --name='k3s-default')"
+kubectl cluster-info
+```
+
+
+
+
+
+- Start Meshery on the newly created cluster
+
+```bash
+mesheryctl system start
+```
+
+
+
+
+- Once Meshery is fully started, login in your preferred browser using the WSL2 IP instead of localhost
+
+```bash
+export BROWSER=/mnt/c/Firefox/firefox.exe
+$BROWSER $mainIP:9081 &
+```
+
+
+
+
+
+
+
+
+
+#### [Optional] More analytics with Grafana
+As stated above, Meshery can leverage the analytics provided by Grafana. For this blog post, as everything is built from scratch. Here is the setup for a new Grafana dockerized instance.
+
+Start a new Grafana on docker instance
+
+```bash
+docker run \
+-d \
+-p 3000:3000 \
+--name=grafana \
+-e "GF_SERVER_ROOT_URL=http://$mainIP" \
+-e "GF_SECURITY_ADMIN_PASSWORD=MesheryInstance" \
+grafana/grafana
+```
+
+
+
+
+
+- Access the new instance with the admin password that you set in the docker environment variable
+```bash
+$BROWSER $mainIP:3000 &
+```
+
+
+
+
+
+
+
+
+
+### An inside look
+While everything should run fine, it's always good to have a look at what has been deployed.
+
+In this case, we are almost exclusively working with Docker and the "inside look" should look something like this:
+
+
+
+
+
+#### Conclusion
+As [Lee Calcote](https://twitter.com/lcalcote) put it, this is a lot of buzz words: Meshery > k3s (deployed via k3d) > Docker > WSL2 > Windows 10. And he's totally right, still the "beauty" here, is that it "simply works".
+
+Since the begin of the Docker era, new tooling has appeard for simplifying complex workflows.
+Even Kubernetes (K8s) as a much lighter version with k3s by Rancher.
+
+And of course, Meshery which integrates and simplifies the installation and benchmarking of different Kubernetes configurations. Hope you had fun assembling all these pieces and stay tunned for the "Bonuses", more fun to come!
+
+ > > > Nunix out
+
+
+
diff --git a/src/collections/blog/2019/2019-10-02-hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/index.mdx b/src/collections/blog/2019/2019-10-02-hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/index.mdx
index d2e1daede8b8..8c05659fd44e 100644
--- a/src/collections/blog/2019/2019-10-02-hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/index.mdx
+++ b/src/collections/blog/2019/2019-10-02-hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/index.mdx
@@ -1,141 +1,141 @@
----
-title: "Hacktoberfest 2019: documenting my first-ever Hacktoberfest contribution"
-date: 2019-10-02 18:19:00 +0000
-author: Rafi Ungar
-thumbnail: ./hacktoberfest.webp
-darkthumbnail: ./hacktoberfest.webp
-category: Internship Programs
-tags:
- - Landscape
- - Community
-published: true
-redirect_from:
- - /blog/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/
- - /blog/landscape/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/
- - /blog/landscape/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
-In [my last post](https://raungar.wordpress.com/2019/09/27/planning-for-hacktoberfest-2019/), I identified three GitHub issues to kick off my participation in Hacktoberfest 2019. Today, I am happy to showcase my resolution of one of those issues, marking my first-ever Hacktoberfest contribution!
-
-* * *
-
-#### [Layer5.io](https://github.com/layer5io/layer5)
-
-Before I continue on, I want to acknowledge the project that I have contributed to. In [an article](/programs/gsod) discussing their participating in the Google Summer of Code 2019 program, [**Layer5**](https://github.com/layer5io/layer5)'s open source community is described cloud native tools for devops engineers. My project was on [service mesh](/resources/service-mesh/service-mesh-fundamentals) helpfully defines a service mesh as "a dedicated infrastructure layer" of an application that controls how different parts of that application ("services") share data with one another (i.e. 'mesh together').
-
-* * *
-
-### Selecting my first Hacktoberfest issue
-
-As I mentioned my last post, I came into contact with Layer5 after discovering (through the [Hacktoberfest Issue Finder](https://hacktoberfest-finder.netlify.com/)) its [issue regarding table filtering](https://github.com/layer5io/layer5/issues/65)—and subsequently discovered an unreported styling issue. [](https://user-images.githubusercontent.com/13500769/66007380-2d643700-e480-11e9-8bda-e81dd0e166d9.webp)
-
-A styling issue affected a collection of lists hosted on Layer5's [Landscape page](https://layer5.io/landscape).
-
-Of the three GitHub issues I've scoped out, the resolution of this styling issue (i.e. tweaking CSS) represents the simplest of tasks that I have lined up—and an ideal candidate for a first-time Hacktoberfest contribution!
-
-As far as I could tell, no open issues concerned the styling problem that I discovered. So, as instructed both Layer5's website (and encouraged its extremely-welcoming development team), I opened _my own issue_ - [Enhance landscape categories section wrapping (#191)](https://github.com/layer5io/layer5/issues/191).
-
-[](https://raungar.files.wordpress.com/2019/10/image-1.webp?w=1024)
-
-### Identifying a solution
-
-To address this issue, I came up with the idea of realigning the category list items horizontally, transforming the poorly-behaving columns of category 'cards' into rows in a responsive and easily-scalable vertical stack.
-
-Implementating this idea proved quite simple, requiring only [a few added CSS rules](https://github.com/layer5io/layer5/issues/191#issuecomment-537304508), which I first accomplished by tinkering with the live webpage's styling (with the help of the [Stylish](https://addons.mozilla.org/en-US/firefox/addon/stylish/) browser extension):
-
-
-```css
-.card .card-content li {
- float: right;
- width: 200px;
-}
-.card .card-content {
- border-right: unset;
- padding: 0 0 5px 0;
-}
-.card .card-content:not(:last-child) {
- border-bottom-width: 1px;
- border-bottom-style: dashed;
- border-bottom-color: var(--main-dark-grey);
-}
-```
-
-The vertical stack is implemented by the rules in the first selector: list items are floated right and assigned a fixed width, which aligns them neatly. The dashed borders and padding used to separate category lists was also adjusted to accomodate the new design (pictured below):
-
-[](https://user-images.githubusercontent.com/13500769/66013483-5e049a80-e499-11e9-8920-52c3da81ece7.webp)
-
-The above image is one of the [two mockups of the redesign](https://github.com/layer5io/layer5/issues/191#issuecomment-537304508) that I produced for the consideration of the project's developers. As luck would have it, Layer5 project lead [Lee Calcote](https://github.com/leecalcote) provided [a lightning-quick response](https://github.com/layer5io/layer5/issues/191#issuecomment-537310179), welcoming a pull request to it!
-
-[](https://raungar.files.wordpress.com/2019/10/image-2.webp?w=1024)
-
-#### Future research area: Materialize CSS
-
-I discovered that the 'cards' comprising the category section are styled using [Materialize CSS](https://materializecss.com/). I considered using this framework in my solution, but ultimately decided to opt for a simple, intuitive solution. This framework appears interesting, and would definitely merits research were this a more-involved styling task.
-
-## Implementing the solution
-
-While using my browser's developer tools to tinker with styling, I discovered an inline `style` tag that serviced the categories section. I determined that this tag would present the best place to add the styling rules that I wrote (following the coding style of a prior contributor).
-
-Finding the location of this `style` tag (i.e. of the "Service Mesh Landscape" page) in the source code was a lot more trouble than I thought it would be. After paging through too many HTML documents, I gave in and used Visual Studio's global search functionality to locate it.
-
-## Testing the solution
-
-Although I knew that my styling worked well when loaded from a browser extension, before I could contribute code, I needed to ensure that the styling worked equally-well when loaded inline from an HTML document. Little did I know, at that time, what I would be getting myself into...
-
-#### Ruby, Gems and Jekyll? `rvm`, `bundle` and `make`?
-
-Picking through my ~/.bash\_history file, here is the sequence of Bash shell commands that I issued (via WSL Ubuntu) in order to execute a local copy of the layer5 website (annotated for your convenience):
-```sh
-## Install dependency packages ##
-sudo apt-get install build-essential
-sudo apt-get install software-properties-common
-
-## Install specific version of Ruby via Ruby Version Manager ##
-sudo apt-add-repository -y ppa:rael-gc/rvm
-sudo apt-get update
-sudo apt-get install rvm
-rvm install "ruby-2.6.3" # install specific version of Ruby specified in Layer5's Gemfile
- # (Yes, it must be that exact version.)
-
-## Configure RubyGems ##
-echo 'export GEM\_HOME="$HOME/gems"' >> ~/.bashrc
-echo 'export PATH="$HOME/gems/bin:$PATH"' >> ~/.bashrc
-source ~/.bashrc
-
-## Install Jekyll and dependencies ##
-gem install jekyll bundler
-bundle install # install dependencies listed in Gemfile
-
-## Execute project! ##
-make site # references Layer5's Makefile
- # alias for "bundle exec jekyll serve --drafts --livereload"
-```
-#### Stray thoughts on documentation
-
-Reflecting back on the process, a question has stuck with me: how much should projects hold the hands of novice contributors? Setting up the means to run `make site` is not included within Layer5's [CONTRIBUTING.md file](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md). As such, for the most novice of contributors, like myself (who have never even heard of `make` before), setting up the prerequisite development environment presented a lengthy and piecemeal (albeit ultimately valuable) learning experience.
-
-How much documentation is too little? Too much? How high should the bar be set for contribution? I suppose it is up to the project's community to decide upon the answers to these questions themselves (and write documentation, accordingly).
-
-## Creating a pull request
-
-After successfully testing and fixing the styling on my local fork, I created [a pull request](https://github.com/layer5io/layer5/pull/192):
-
-[](https://raungar.files.wordpress.com/2019/10/image-3.webp?w=1024)
-
-Pull request – [Restyle landscape categories (#192)](https://github.com/layer5io/layer5/pull/192)
-
-...and it got merged! First Hacktoberfest contribution, completed!
-
-## Up next!
-
-I ended [my last post](https://raungar.wordpress.com/2019/09/27/planning-for-hacktoberfest-2019/) by stating that I have yet to gain any experience with makefiles. Well, thanks to my work on Layer5, that is no longer true: I have since used a makefile (to launch a Jekyll executable)! This experience will undoubtedly save me some time with resolving [the Comcast issue I found](https://github.com/Comcast/RestfulHttpsProxy/issues/5)! However, the next Hacktoberfest issue I resolve will be [_the first one I blogged about_](https://github.com/layer5io/layer5/issues/65).
-
-Stay tuned!
-
-
-
+---
+title: "Hacktoberfest 2019: documenting my first-ever Hacktoberfest contribution"
+date: 2019-10-02 18:19:00 +0000
+author: Rafi Ungar
+thumbnail: ./hacktoberfest.webp
+darkthumbnail: ./hacktoberfest.webp
+category: Internship Programs
+tags:
+ - Landscape
+ - Community
+published: true
+redirect_from:
+ - /blog/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/
+ - /blog/landscape/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/
+ - /blog/landscape/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution
+---
+
+
+
+
+
+
+In [my last post](https://raungar.wordpress.com/2019/09/27/planning-for-hacktoberfest-2019/), I identified three GitHub issues to kick off my participation in Hacktoberfest 2019. Today, I am happy to showcase my resolution of one of those issues, marking my first-ever Hacktoberfest contribution!
+
+* * *
+
+#### [Layer5.io](https://github.com/layer5io/layer5)
+
+Before I continue on, I want to acknowledge the project that I have contributed to. In [an article](/programs/gsod) discussing their participating in the Google Summer of Code 2019 program, [**Layer5**](https://github.com/layer5io/layer5)'s open source community is described cloud native tools for devops engineers. My project was on [service mesh](/resources/service-mesh/service-mesh-fundamentals) helpfully defines a service mesh as "a dedicated infrastructure layer" of an application that controls how different parts of that application ("services") share data with one another (i.e. 'mesh together').
+
+* * *
+
+### Selecting my first Hacktoberfest issue
+
+As I mentioned my last post, I came into contact with Layer5 after discovering (through the [Hacktoberfest Issue Finder](https://hacktoberfest-finder.netlify.com/)) its [issue regarding table filtering](https://github.com/layer5io/layer5/issues/65)—and subsequently discovered an unreported styling issue. [](https://user-images.githubusercontent.com/13500769/66007380-2d643700-e480-11e9-8bda-e81dd0e166d9.webp)
+
+A styling issue affected a collection of lists hosted on Layer5's [Landscape page](https://layer5.io/landscape).
+
+Of the three GitHub issues I've scoped out, the resolution of this styling issue (i.e. tweaking CSS) represents the simplest of tasks that I have lined up—and an ideal candidate for a first-time Hacktoberfest contribution!
+
+As far as I could tell, no open issues concerned the styling problem that I discovered. So, as instructed both Layer5's website (and encouraged its extremely-welcoming development team), I opened _my own issue_ - [Enhance landscape categories section wrapping (#191)](https://github.com/layer5io/layer5/issues/191).
+
+[](https://raungar.files.wordpress.com/2019/10/image-1.webp?w=1024)
+
+### Identifying a solution
+
+To address this issue, I came up with the idea of realigning the category list items horizontally, transforming the poorly-behaving columns of category 'cards' into rows in a responsive and easily-scalable vertical stack.
+
+Implementating this idea proved quite simple, requiring only [a few added CSS rules](https://github.com/layer5io/layer5/issues/191#issuecomment-537304508), which I first accomplished by tinkering with the live webpage's styling (with the help of the [Stylish](https://addons.mozilla.org/en-US/firefox/addon/stylish/) browser extension):
+
+
+```css
+.card .card-content li {
+ float: right;
+ width: 200px;
+}
+.card .card-content {
+ border-right: unset;
+ padding: 0 0 5px 0;
+}
+.card .card-content:not(:last-child) {
+ border-bottom-width: 1px;
+ border-bottom-style: dashed;
+ border-bottom-color: var(--main-dark-grey);
+}
+```
+
+The vertical stack is implemented by the rules in the first selector: list items are floated right and assigned a fixed width, which aligns them neatly. The dashed borders and padding used to separate category lists was also adjusted to accomodate the new design (pictured below):
+
+[](https://user-images.githubusercontent.com/13500769/66013483-5e049a80-e499-11e9-8920-52c3da81ece7.webp)
+
+The above image is one of the [two mockups of the redesign](https://github.com/layer5io/layer5/issues/191#issuecomment-537304508) that I produced for the consideration of the project's developers. As luck would have it, Layer5 project lead [Lee Calcote](https://github.com/leecalcote) provided [a lightning-quick response](https://github.com/layer5io/layer5/issues/191#issuecomment-537310179), welcoming a pull request to it!
+
+[](https://raungar.files.wordpress.com/2019/10/image-2.webp?w=1024)
+
+#### Future research area: Materialize CSS
+
+I discovered that the 'cards' comprising the category section are styled using [Materialize CSS](https://materializecss.com/). I considered using this framework in my solution, but ultimately decided to opt for a simple, intuitive solution. This framework appears interesting, and would definitely merits research were this a more-involved styling task.
+
+## Implementing the solution
+
+While using my browser's developer tools to tinker with styling, I discovered an inline `style` tag that serviced the categories section. I determined that this tag would present the best place to add the styling rules that I wrote (following the coding style of a prior contributor).
+
+Finding the location of this `style` tag (i.e. of the "Service Mesh Landscape" page) in the source code was a lot more trouble than I thought it would be. After paging through too many HTML documents, I gave in and used Visual Studio's global search functionality to locate it.
+
+## Testing the solution
+
+Although I knew that my styling worked well when loaded from a browser extension, before I could contribute code, I needed to ensure that the styling worked equally-well when loaded inline from an HTML document. Little did I know, at that time, what I would be getting myself into...
+
+#### Ruby, Gems and Jekyll? `rvm`, `bundle` and `make`?
+
+Picking through my ~/.bash\_history file, here is the sequence of Bash shell commands that I issued (via WSL Ubuntu) in order to execute a local copy of the layer5 website (annotated for your convenience):
+```sh
+## Install dependency packages ##
+sudo apt-get install build-essential
+sudo apt-get install software-properties-common
+
+## Install specific version of Ruby via Ruby Version Manager ##
+sudo apt-add-repository -y ppa:rael-gc/rvm
+sudo apt-get update
+sudo apt-get install rvm
+rvm install "ruby-2.6.3" # install specific version of Ruby specified in Layer5's Gemfile
+ # (Yes, it must be that exact version.)
+
+## Configure RubyGems ##
+echo 'export GEM\_HOME="$HOME/gems"' >> ~/.bashrc
+echo 'export PATH="$HOME/gems/bin:$PATH"' >> ~/.bashrc
+source ~/.bashrc
+
+## Install Jekyll and dependencies ##
+gem install jekyll bundler
+bundle install # install dependencies listed in Gemfile
+
+## Execute project! ##
+make site # references Layer5's Makefile
+ # alias for "bundle exec jekyll serve --drafts --livereload"
+```
+#### Stray thoughts on documentation
+
+Reflecting back on the process, a question has stuck with me: how much should projects hold the hands of novice contributors? Setting up the means to run `make site` is not included within Layer5's [CONTRIBUTING.md file](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md). As such, for the most novice of contributors, like myself (who have never even heard of `make` before), setting up the prerequisite development environment presented a lengthy and piecemeal (albeit ultimately valuable) learning experience.
+
+How much documentation is too little? Too much? How high should the bar be set for contribution? I suppose it is up to the project's community to decide upon the answers to these questions themselves (and write documentation, accordingly).
+
+## Creating a pull request
+
+After successfully testing and fixing the styling on my local fork, I created [a pull request](https://github.com/layer5io/layer5/pull/192):
+
+[](https://raungar.files.wordpress.com/2019/10/image-3.webp?w=1024)
+
+Pull request – [Restyle landscape categories (#192)](https://github.com/layer5io/layer5/pull/192)
+
+...and it got merged! First Hacktoberfest contribution, completed!
+
+## Up next!
+
+I ended [my last post](https://raungar.wordpress.com/2019/09/27/planning-for-hacktoberfest-2019/) by stating that I have yet to gain any experience with makefiles. Well, thanks to my work on Layer5, that is no longer true: I have since used a makefile (to launch a Jekyll executable)! This experience will undoubtedly save me some time with resolving [the Comcast issue I found](https://github.com/Comcast/RestfulHttpsProxy/issues/5)! However, the next Hacktoberfest issue I resolve will be [_the first one I blogged about_](https://github.com/layer5io/layer5/issues/65).
+
+Stay tuned!
+
+
+
diff --git a/src/collections/blog/2019/2019-10-12-hacktoberfest-2019-is-heating-up/index.mdx b/src/collections/blog/2019/2019-10-12-hacktoberfest-2019-is-heating-up/index.mdx
index 486778931892..e67be4011cf0 100644
--- a/src/collections/blog/2019/2019-10-12-hacktoberfest-2019-is-heating-up/index.mdx
+++ b/src/collections/blog/2019/2019-10-12-hacktoberfest-2019-is-heating-up/index.mdx
@@ -1,92 +1,89 @@
----
-title: "Hacktoberfest 2019: Heating up!"
-date: 2019-10-12 21:58:00 +0000
-author: Rafi Ungar
-thumbnail: ./hacktoberfestw2.webp
-darkthumbnail: ./hacktoberfestw2.webp
-category: Internship Programs
-tags:
- - Community
- - Landscape
-published: true
-redirect_from:
- - /blog/hacktoberfest-2019-heating-up/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
-(ICYMI: [I've made my first-ever Hacktoberfest contribution](https://raungar.wordpress.com/2019/10/02/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/)!)_
-
-[Hacktoberfest 2019](https://hacktoberfest.digitalocean.com/) is now well underway, and I am happy to report that I have made my second contribution to my new favorite open source community, [**Layer5**](https://layer5.io/) ([on GitHub](https://github.com/layer5io))!
-
-_Before I continue on, I want to extend a huge thank-you to Layer5's lead developer, Lee Calcote, as well as the Layer5 community managers for welcoming me into the Layer5 Slack channel, allowing me to introduce myself in their weekly community meeting, and even giving my blog [an awesome shout out on Twitter](https://twitter.com/layer5/status/1180317604168306688?s=12)!_
-
-* * *
-
-This week, I helped resolve the very first issue that I outlined in my [Planning for #Hacktoberfest 2019](https://raungar.wordpress.com/2019/09/27/planning-for-hacktoberfest-2019/) post:
-
-[](https://raungar.files.wordpress.com/2019/10/image-4.webp?w=1024)
-
-Issue [layerio#65](https://github.com/layer5io/layer5/issues/65): enhancements for the [Layer5 Landscape page](https://layer5.io/landscape)
-
-At the time I found this issue, the second requested enhancement (concerning table row coloration) [was already handled](https://github.com/layer5io/layer5/commit/b313268cb578e762d1212c9910b522af2869b57b) by another contributor, leaving me with two tasks:
-
-1. Implementing the specified sorting functionalities (for the three tables on the [Landscape page](https://layer5.io/landscape))
-2. Restyling the font color of site hyperlinks (an enhancement [requested later on](https://github.com/layer5io/layer5/issues/65#issuecomment-483912458) in the issue)
-
-### The strange case of Jekyll
-
-Fortunately, thanks to my previous work with Layer5's website, I was already all set up with an offline development environment. However, going into my first task, I knew very little about Jekyll except how to install it.
-
-_[Jekyll](https://jekyllrb.com/) and [Liquid](https://shopify.github.io/liquid/)... it's got to be like React or Angular, right? I mean, all I need to do is slap in [sort](https://shopify.github.io/liquid/filters/sort/) and [reverse filters](https://shopify.github.io/liquid/filters/reverse/) and toggle them onclick, right_...?
-
-_...Wait, what's a "static site generator"?_
-
-* * *
-
-After discovering what Jekyll and Liquid actually were, I determined that I would have to resort to DOM manipulation to fully accomplish my first task. However, I did succeed in accomplishing the default sorting behaviour by enhancing the Liquid tags being used by several tables.
-
-To do so, I followed coding style on the issue's previous contributor by encapsulating my work within a new JavaScript file in the project's assets folder: a simple bubble sort function.
-
-I chose to implement the [simplest of sorting algorithms](https://github.com/layer5io/layer5/blob/master/assets/js/table-sort.js#L13) in JavaScript (which I count as study for my _Data Structures and Algorithms_ midterm):
-
-
-```js
-// Excerpted from https://github.com/layer5io/layer5/blob/master/assets/js/table-sort.js
-let bubbleSort = () => {
- for (i = 0; i < rows.length-1; i++) {
- for (j = 0; j < rows.length-i-1; j++) {
- if (shouldSwap(text(j), text(j+1))) {
- rows[j].parentNode.insertBefore(rows[j+1], rows[j]);
- didSort = true;
- }
- }
- }
-};
-```
-
-### Painting over Pumpkin Bread
-
-[Encycolorpedia.com](https://encycolorpedia.com) lists the hex color code `#fdac40` as "[Valspar Paint Pumpkin Bread](https://encycolorpedia.com/fdac40)". Although Layer5.io's then-difficult-to-read hyperlinks were colored `#ffa_b_40`, I'd still like to think that the second task of my second Hacktoberfest contribution was festively-themed!
-
-In [my last blog post](https://raungar.wordpress.com/2019/10/02/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/), I mentioned that [Materialize CSS](https://materializecss.com) was worth further research. Well, after some poking around, I discovered that all of Layer5.io's pumpkin-colored hyperlink styling (both deliberate, and incidental) originated from its materialize.css asset.
-
-Although this asset has been [frequently modified](https://github.com/layer5io/layer5/commits/master/assets/css/materialize.css), I was still hesitant to globally alter the site's styling (in case a return to Pumpkin Bread was desired in the future), so I instead opted to [add a new inline style tag](https://github.com/layer5io/layer5/pull/209/files#diff-48443fc170100677376b7ee11324494b) to override [a styling rule](https://github.com/layer5io/layer5/blob/master/assets/css/materialize.css#L5149) (on top of removing the 'orange-text' class from individual anchor elements).
-
-* * *
-
-All of the changes I've made can be viewed through [my (merged) pull request](https://github.com/layer5io/layer5/pull/209):
-
-[](https://raungar.files.wordpress.com/2019/10/image-6.webp?w=1024)
-
-Pull request [layer5io#209](https://github.com/layer5io/layer5/pull/209): resolved the remainder of issue [layerio#65](https://github.com/layer5io/layer5/issues/65)
-
-* * *
-
-I am very fortunate to be so well-supported by the open source communities I have worked with so far, both on-campus and abroad. With their support behind me, I feel equipped to start learning what I need to know to resolve the next two more-difficult issues that lie ahead of me!
-
-
-
+---
+title: "Hacktoberfest 2019: Heating up!"
+date: 2019-10-12 21:58:00 +0000
+author: Rafi Ungar
+thumbnail: ./hacktoberfestw2.webp
+darkthumbnail: ./hacktoberfestw2.webp
+category: Internship Programs
+tags:
+ - Community
+ - Landscape
+published: true
+redirect_from:
+ - /blog/hacktoberfest-2019-heating-up/
+---
+
+
+
+(ICYMI: [I've made my first-ever Hacktoberfest contribution](https://raungar.wordpress.com/2019/10/02/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/)!)_
+
+[Hacktoberfest 2019](https://hacktoberfest.digitalocean.com/) is now well underway, and I am happy to report that I have made my second contribution to my new favorite open source community, [**Layer5**](https://layer5.io/) ([on GitHub](https://github.com/layer5io))!
+
+_Before I continue on, I want to extend a huge thank-you to Layer5's lead developer, Lee Calcote, as well as the Layer5 community managers for welcoming me into the Layer5 Slack channel, allowing me to introduce myself in their weekly community meeting, and even giving my blog [an awesome shout out on Twitter](https://twitter.com/layer5/status/1180317604168306688?s=12)!_
+
+* * *
+
+This week, I helped resolve the very first issue that I outlined in my [Planning for #Hacktoberfest 2019](https://raungar.wordpress.com/2019/09/27/planning-for-hacktoberfest-2019/) post:
+
+[](https://raungar.files.wordpress.com/2019/10/image-4.webp?w=1024)
+
+Issue [layerio#65](https://github.com/layer5io/layer5/issues/65): enhancements for the [Layer5 Landscape page](https://layer5.io/landscape)
+
+At the time I found this issue, the second requested enhancement (concerning table row coloration) [was already handled](https://github.com/layer5io/layer5/commit/b313268cb578e762d1212c9910b522af2869b57b) by another contributor, leaving me with two tasks:
+
+1. Implementing the specified sorting functionalities (for the three tables on the [Landscape page](https://layer5.io/landscape))
+2. Restyling the font color of site hyperlinks (an enhancement [requested later on](https://github.com/layer5io/layer5/issues/65#issuecomment-483912458) in the issue)
+
+### The strange case of Jekyll
+
+Fortunately, thanks to my previous work with Layer5's website, I was already all set up with an offline development environment. However, going into my first task, I knew very little about Jekyll except how to install it.
+
+_[Jekyll](https://jekyllrb.com/) and [Liquid](https://shopify.github.io/liquid/)... it's got to be like React or Angular, right? I mean, all I need to do is slap in [sort](https://shopify.github.io/liquid/filters/sort/) and [reverse filters](https://shopify.github.io/liquid/filters/reverse/) and toggle them onclick, right_...?
+
+_...Wait, what's a "static site generator"?_
+
+* * *
+
+After discovering what Jekyll and Liquid actually were, I determined that I would have to resort to DOM manipulation to fully accomplish my first task. However, I did succeed in accomplishing the default sorting behaviour by enhancing the Liquid tags being used by several tables.
+
+To do so, I followed coding style on the issue's previous contributor by encapsulating my work within a new JavaScript file in the project's assets folder: a simple bubble sort function.
+
+I chose to implement the [simplest of sorting algorithms](https://github.com/layer5io/layer5/blob/master/assets/js/table-sort.js#L13) in JavaScript (which I count as study for my _Data Structures and Algorithms_ midterm):
+
+
+```
+// Excerpted from https://github.com/layer5io/layer5/blob/master/assets/js/table-sort.js
+let bubbleSort = () => {
+ for (i = 0; i < rows.length-1; i++) {
+ for (j = 0; j < rows.length-i-1; j++) {
+ if (shouldSwap(text(j), text(j+1))) {
+ rows[j].parentNode.insertBefore(rows[j+1], rows[j]);
+ didSort = true;
+ }
+ }
+ }
+};
+```
+
+### Painting over Pumpkin Bread
+
+[Encycolorpedia.com](https://encycolorpedia.com) lists the hex color code `#fdac40` as "[Valspar Paint Pumpkin Bread](https://encycolorpedia.com/fdac40)". Although Layer5.io's then-difficult-to-read hyperlinks were colored `#ffa_b_40`, I'd still like to think that the second task of my second Hacktoberfest contribution was festively-themed!
+
+In [my last blog post](https://raungar.wordpress.com/2019/10/02/hacktoberfest-2019-documenting-my-first-ever-hacktoberfest-contribution/), I mentioned that [Materialize CSS](https://materializecss.com) was worth further research. Well, after some poking around, I discovered that all of Layer5.io's pumpkin-colored hyperlink styling (both deliberate, and incidental) originated from its materialize.css asset.
+
+Although this asset has been [frequently modified](https://github.com/layer5io/layer5/commits/master/assets/css/materialize.css), I was still hesitant to globally alter the site's styling (in case a return to Pumpkin Bread was desired in the future), so I instead opted to [add a new inline style tag](https://github.com/layer5io/layer5/pull/209/files#diff-48443fc170100677376b7ee11324494b) to override [a styling rule](https://github.com/layer5io/layer5/blob/master/assets/css/materialize.css#L5149) (on top of removing the 'orange-text' class from individual anchor elements).
+
+* * *
+
+All of the changes I've made can be viewed through [my (merged) pull request](https://github.com/layer5io/layer5/pull/209):
+
+[](https://raungar.files.wordpress.com/2019/10/image-6.webp?w=1024)
+
+Pull request [layer5io#209](https://github.com/layer5io/layer5/pull/209): resolved the remainder of issue [layerio#65](https://github.com/layer5io/layer5/issues/65)
+
+* * *
+
+I am very fortunate to be so well-supported by the open source communities I have worked with so far, both on-campus and abroad. With their support behind me, I feel equipped to start learning what I need to know to resolve the next two more-difficult issues that lie ahead of me!
+
+
+
diff --git a/src/collections/blog/2019/2019-11-15-introducing-comparative-spectrums-to-the-layer5-landscape/index.mdx b/src/collections/blog/2019/2019-11-15-introducing-comparative-spectrums-to-the-layer5-landscape/index.mdx
index 6dfea939c071..79d761dd8bb0 100644
--- a/src/collections/blog/2019/2019-11-15-introducing-comparative-spectrums-to-the-layer5-landscape/index.mdx
+++ b/src/collections/blog/2019/2019-11-15-introducing-comparative-spectrums-to-the-layer5-landscape/index.mdx
@@ -1,117 +1,117 @@
----
-title: "Introducing Comparative Spectrums to the Layer5 Landscape"
-subtitle: ""
-date: 2019-11-15 05:43:00 +0000
-author: Rafi Ungar
-thumbnail: ./landscape_green.svg
-darkthumbnail: ./landscape_green.svg
-category: Internship Programs
-tags:
- - Community
- - Landscape
-published: true
-type: Blog
-product: Service Mesh Landscape
-resource: true
-redirect_from:
- - /blog/introducing-comparative-spectrums-to-the-layer5-landscape/
- - /blog/introducing-comparative-spectrums-to-the-layer5-landscape
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import pr211 from "./PR-211.webp";
-import pr2112 from "./PR-211-2.webp";
-import card1 from "./card1.webp";
-import card2 from "./card2.webp";
-import arrow from "./arrow.webp";
-import gtable from "./graphical-table.webp";
-import gcomp from "./graph-compare.webp";
-import image21 from "./image.webp";
-import comment from "./comment.webp";
-
-
-
-During [Hacktoberfest 2019](https://raungar.wordpress.com/tag/layer5/), I worked on the website of [Layer5](https://layer5.io/), open source community. More specifically, my contributions concerned one specific page of that website: its [Service Mesh Landscape page](https://layer5.io/landscape).
-
-Shortly after making these contributions, I was graciously welcomed into the Layer5 community by its lead developer [Lee Calcote](https://twitter.com/lcalcote?lang=en), who later directly approached me to assist him in furthering his vision for the Landscape page by implementing "comparative spectrums". Wishing to focus on my remaining two Hacktoberfest contributions at the time, I suggested surveying the interest of other potential contributors for this project. As such, an informative issue was opened:
-
-
-
-Issue [layer5#211](https://github.com/layer5io/layer5/issues/211): add comparative spectrums to the Landscape page
-
-A month later, I fortunately found time enough to make some major progress into this issue.
-
-* * *
-
-This issue is quite highly conceptual, much moreso than any other issue I have thus far worked on. I decided that the best way to approach this issue would be to focus on establishing a set of tools that could be used by more-knowledgeable contributors to later construct comparative spectrums—opinionated data visualizations. As such, my first step was to build a set of responsive graphical elements that resembled [those provided as examples](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6). These include:
-
-#### (1) _Sleek information cards:_
-
-
-
-
-
-
or this
-
-
-
-
-
-_(Source: [ONIF Container Networking Panel, slides 5 and 6](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6))_
-
-#### (2) _Gradiented, labelable double-arrow banners:_
-
-
-
-_(Source: [ONIF Container Networking Panel, slide 5](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6))_
-
-#### (3) _Graphically-augmented tables:_
-
-
-
-_(Source: [ONIF Container Networking Panel, slide 8](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p12))_
-
-#### (4) _Spectrum-like graphical comparisons:_
-
-
-
-_(Source: [ONIF Container Networking Panel, slide 7](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6))_
-
-* * *
-
-(1) Although there may exist libraries that may help construct such graphical elements, I did not want to introduce additional libraries to accomplish my work. Instead, I wanted to make good use of Layer5io's preexisting [Materialize](https://materializecss.com/) library. Fortunately, Materialize strongly supports the design of card-like structures, allowing me to more easily [implement some](https://github.com/layer5io/layer5/pull/238/files#diff-20fc098534d6aab31ad8e5c9db51bde0R10).
-
-(2) Unfortunately, it does not seem that Materialize supports the creation of graphical arrows, so I just ended up [styling my own](https://github.com/layer5io/layer5/pull/238/files#diff-1d5fe92e61759723c94b009b32e9e1b7R2).
-
-(3) These tables can be quite easily implemented and styled with or without the use of `
` tags. I anticipate these will be given a proper fleshing out after the other graphical elements are further developed.
-
-(4) These unique spectrum graphics present the most challenging, of all the comparison tools, to implement. Snaking spectrum bar aside, I needed to develop a _responsive_ solution that (a) allowed contributors to programmatically place image thumbnails at preset horizontal positions, while (b) ensuring those thumbnails placed at the same position do not overlap with one another (and instead align vertically atop each other).
-
-This presented a problem to solve: I required a means to 'float' elements toward a horizontal line; to 'stack' thumbnails atop one another, without overlap, if they are given the same horizontal position. After researching quite deeply into potential solutions to this problem, I ended up stumbling across some CSS property-value pairings that I had never heard of before: [`display: grid`](https://www.w3schools.com/css/css_grid.asp) and [`grid-auto-flow: row dense`](https://www.w3schools.com/cssref/pr_grid-auto-flow.asp). Miraculously, I discovered that these could actually function as [a basis for a solution](https://github.com/layer5io/layer5/pull/238/files#diff-1d5fe92e61759723c94b009b32e9e1b7R76).
-
-* * *
-
-After styling the graphical elements, I continued the website's trend of using [Liquid](https://help.shopify.com/en/themes/liquid) tags (e.g. [`for`](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)) and [YAML lists](https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html) to help modularize my solutions, which should aid future contributors in generalizing them.
-
-* * *
-
-I opened [a pull request](https://github.com/layer5io/layer5/pull/238) to share my work as well as invite collaboration:
-
-
-
-Pull request [layer5#238](https://github.com/layer5io/layer5/pull/238): description of tooling introduced
-
-
-
-Pull request [layer5#238](https://github.com/layer5io/layer5/pull/238): example images of tooling introduced
-
-The pull request was quite well-recieved:
-
-
-
-[Comment](https://github.com/layer5io/layer5/pull/238#issuecomment-554181763) by Layer5 team lead on pull request [layer5#238](https://github.com/layer5io/layer5/pull/238)
-
-As I mentioned in a recent Layer5 community meeting, I am very excited to continue working with Layer5; to refine and expand upon this set of new, visionary tooling for their landscape!
-
-
-
+---
+title: "Introducing Comparative Spectrums to the Layer5 Landscape"
+subtitle: ""
+date: 2019-11-15 05:43:00 +0000
+author: Rafi Ungar
+thumbnail: ./landscape_green.svg
+darkthumbnail: ./landscape_green.svg
+category: Internship Programs
+tags:
+ - Community
+ - Landscape
+published: true
+type: Blog
+product: Service Mesh Landscape
+resource: true
+redirect_from:
+ - /blog/introducing-comparative-spectrums-to-the-layer5-landscape/
+ - /blog/introducing-comparative-spectrums-to-the-layer5-landscape
+---
+
+
+import pr211 from "./PR-211.webp";
+import pr2112 from "./PR-211-2.webp";
+import card1 from "./card1.webp";
+import card2 from "./card2.webp";
+import arrow from "./arrow.webp";
+import gtable from "./graphical-table.webp";
+import gcomp from "./graph-compare.webp";
+import image21 from "./image.webp";
+import comment from "./comment.webp";
+
+
+
+During [Hacktoberfest 2019](https://raungar.wordpress.com/tag/layer5/), I worked on the website of [Layer5](https://layer5.io/), open source community. More specifically, my contributions concerned one specific page of that website: its [Service Mesh Landscape page](https://layer5.io/landscape).
+
+Shortly after making these contributions, I was graciously welcomed into the Layer5 community by its lead developer [Lee Calcote](https://twitter.com/lcalcote?lang=en), who later directly approached me to assist him in furthering his vision for the Landscape page by implementing "comparative spectrums". Wishing to focus on my remaining two Hacktoberfest contributions at the time, I suggested surveying the interest of other potential contributors for this project. As such, an informative issue was opened:
+
+
+
+Issue [layer5#211](https://github.com/layer5io/layer5/issues/211): add comparative spectrums to the Landscape page
+
+A month later, I fortunately found time enough to make some major progress into this issue.
+
+* * *
+
+This issue is quite highly conceptual, much moreso than any other issue I have thus far worked on. I decided that the best way to approach this issue would be to focus on establishing a set of tools that could be used by more-knowledgeable contributors to later construct comparative spectrums—opinionated data visualizations. As such, my first step was to build a set of responsive graphical elements that resembled [those provided as examples](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6). These include:
+
+#### (1) _Sleek information cards:_
+
+
+
+
+
+
or this
+
+
+
+
+
+_(Source: [ONIF Container Networking Panel, slides 5 and 6](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6))_
+
+#### (2) _Gradiented, labelable double-arrow banners:_
+
+
+
+_(Source: [ONIF Container Networking Panel, slide 5](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6))_
+
+#### (3) _Graphically-augmented tables:_
+
+
+
+_(Source: [ONIF Container Networking Panel, slide 8](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p12))_
+
+#### (4) _Spectrum-like graphical comparisons:_
+
+
+
+_(Source: [ONIF Container Networking Panel, slide 7](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6))_
+
+* * *
+
+(1) Although there may exist libraries that may help construct such graphical elements, I did not want to introduce additional libraries to accomplish my work. Instead, I wanted to make good use of Layer5io's preexisting [Materialize](https://materializecss.com/) library. Fortunately, Materialize strongly supports the design of card-like structures, allowing me to more easily [implement some](https://github.com/layer5io/layer5/pull/238/files#diff-20fc098534d6aab31ad8e5c9db51bde0R10).
+
+(2) Unfortunately, it does not seem that Materialize supports the creation of graphical arrows, so I just ended up [styling my own](https://github.com/layer5io/layer5/pull/238/files#diff-1d5fe92e61759723c94b009b32e9e1b7R2).
+
+(3) These tables can be quite easily implemented and styled with or without the use of `
` tags. I anticipate these will be given a proper fleshing out after the other graphical elements are further developed.
+
+(4) These unique spectrum graphics present the most challenging, of all the comparison tools, to implement. Snaking spectrum bar aside, I needed to develop a _responsive_ solution that (a) allowed contributors to programmatically place image thumbnails at preset horizontal positions, while (b) ensuring those thumbnails placed at the same position do not overlap with one another (and instead align vertically atop each other).
+
+This presented a problem to solve: I required a means to 'float' elements toward a horizontal line; to 'stack' thumbnails atop one another, without overlap, if they are given the same horizontal position. After researching quite deeply into potential solutions to this problem, I ended up stumbling across some CSS property-value pairings that I had never heard of before: [`display: grid`](https://www.w3schools.com/css/css_grid.asp) and [`grid-auto-flow: row dense`](https://www.w3schools.com/cssref/pr_grid-auto-flow.asp). Miraculously, I discovered that these could actually function as [a basis for a solution](https://github.com/layer5io/layer5/pull/238/files#diff-1d5fe92e61759723c94b009b32e9e1b7R76).
+
+* * *
+
+After styling the graphical elements, I continued the website's trend of using [Liquid](https://help.shopify.com/en/themes/liquid) tags (e.g. [`for`](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)) and [YAML lists](https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html) to help modularize my solutions, which should aid future contributors in generalizing them.
+
+* * *
+
+I opened [a pull request](https://github.com/layer5io/layer5/pull/238) to share my work as well as invite collaboration:
+
+
+
+Pull request [layer5#238](https://github.com/layer5io/layer5/pull/238): description of tooling introduced
+
+
+
+Pull request [layer5#238](https://github.com/layer5io/layer5/pull/238): example images of tooling introduced
+
+The pull request was quite well-recieved:
+
+
+
+[Comment](https://github.com/layer5io/layer5/pull/238#issuecomment-554181763) by Layer5 team lead on pull request [layer5#238](https://github.com/layer5io/layer5/pull/238)
+
+As I mentioned in a recent Layer5 community meeting, I am very excited to continue working with Layer5; to refine and expand upon this set of new, visionary tooling for their landscape!
+
+
+
diff --git a/src/collections/blog/2019/2019-12-04-layer5-landscape-spectrums-revisited/index.mdx b/src/collections/blog/2019/2019-12-04-layer5-landscape-spectrums-revisited/index.mdx
index 2c7ba7447aeb..9510ee30c1ca 100644
--- a/src/collections/blog/2019/2019-12-04-layer5-landscape-spectrums-revisited/index.mdx
+++ b/src/collections/blog/2019/2019-12-04-layer5-landscape-spectrums-revisited/index.mdx
@@ -1,72 +1,72 @@
----
-title: "Layer5: Landscape Spectrums Revisited"
-subtitle: ""
-date: 2019-12-04 18:10:00 +0000
-author: Rafi Ungar
-thumbnail: ./landscape_green.svg
-darkthumbnail: ./landscape_green.svg
-category: Internship Programs
-tags:
- - Community
- - Landscape
-published: true
-type: Blog
-product: Service Mesh Landscape
-resource: true
-redirect_from:
- - /blog/layer5-landscape-spectrums-revisited/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import issueImage from "./issue.webp";
-
-
-
-Several weeks ago, I wrote [a blog post](https://raungar.wordpress.com/2019/11/15/introducing-comparative-spectrums-to-the-layer5-landscape/) about introducing "comparative spectrum" tools to [the Layer5 landscape](https://layer5.io/landscape)—a webpage which I have transformed multiple times, now!
-
-Up until now, the contents of each blog post I have written were centered upon a freshly-opened pull request. Shortly before writing my last post, I did open [one such pull request (layer5#238)](https://github.com/layer5io/layer5/pull/238). However, since my PR remains open, and since I am still working on the same issue my PR addresses, I have opted to instead push [a new commit](https://github.com/layer5io/layer5/pull/238/commits/4d396aaa6d3ca46add71531daedc8c0e2a5d2495) to the aformentioned (but, now, renamed) PR instead of creating a whole new one. This newest commit introduces a major step towards resolving the issue at hand, and will be the subject of this blog post!
-
-
-
-The issue at hand: [layer5#211](https://github.com/layer5io/layer5/issues/211) - add comparative spectrums to the Landscape page
-
-* * *
-
-_**Note:** this blog post will frequently reference [the update and documentation comment that I made](https://github.com/layer5io/layer5/pull/238#issuecomment-561613644) to accompany my last commit to my PR. I consider this hefty comment to be an extension of this blog post, so I strongly recommend giving it a read!_
-
-* * *
-
-My initial commit towards introducing comparative spectrum tooling did not represent a full solution. Thinking about what might constitute a full solution for the issue at hand, I came up with three criteria:
-
-## What was still needed:
-
-#### 1\. A complete toolset
-
-Within [Issue #211](https://github.com/layer5io/layer5/issues/211), Layer5 lead developer Lee indicates [four slides](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6) upon which comparative spectrum graphics may be based upon. During my initial commit, I created graphics that emulated those found within the first three of those four slides, but I had yet to implement the graphic found in [the fourth](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p12): a table. I was also less-than-satisfied with the 'grid' design I had implemented in response to [slide 7](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p10).
-
-#### 2\. A modular design
-
-The designs I am implementing are meant to be used to present opinionated information. As I am not nearly knowledgeable to form opinionated comparisons between service meshes and related technologies, I have instead made my goal to make it as easy as possible for other Layer5 contributors to utilize the graphics ("\[comparative\] spectrums") that I am designing. Doing so would require encapsulating (templating) the spectrums I design (new and old), within their own HTML files, and providing a means to easily invoke (and customize) instances of those templates into the Landscape page.
-
-#### 3\. Documentation
-
-Because the templates I design are intended to be implemented and customized by other contributors, it is _especially_ critical that those contributors have access to complete and thorough documentation detailing the intended use of each templated design.
-
-* * *
-
-## What I delivered:
-
-#### 1\. A complete toolset
-
-As documented in my [update comment](https://github.com/layer5io/layer5/pull/238#issuecomment-561613644), I designed a table that very closely resembles that of Lee's slides. Implementing the table was interesting, as it ended up requiring [quite a few nested Liquid for-loops](https://github.com/layer5io/layer5/blob/4d396aaa6d3ca46add71531daedc8c0e2a5d2495/_includes/partials/spectrum/table.html#L23). Also as documented, I revamped the grid-based tooling and am quite pleased with the improvements made. The end result of these efforts is a complete set of comparative spectrums.
-
-#### 2, 3. A modular design and documentation
-
-The bulk of the documentation I wrote details how to deal with the modular solution that I designed and implemented to enable comparative spectrums to be included into the Landscape page (through the use of Liquid `include` tags). The documentation speaks for itself; [check it out!](https://github.com/layer5io/layer5/pull/238#issuecomment-561613644)
-
-## What's next?
-
-I would not have considered the documentation I delivered to be complete if I did not report on the issues still present in the work I delivered. I denoted these as 'Current issues' in the documentation, and they represent work that still remains to be done. I know that I can count on the Layer5 community to assist me with small issues like these, and, once this pull request receives some forward motion, I hope to start zeroing in on its smaller issues. Fortunately, I have made plans to continue working with open source well into the new year!
-
-
-
+---
+title: "Layer5: Landscape Spectrums Revisited"
+subtitle: ""
+date: 2019-12-04 18:10:00 +0000
+author: Rafi Ungar
+thumbnail: ./landscape_green.svg
+darkthumbnail: ./landscape_green.svg
+category: Internship Programs
+tags:
+ - Community
+ - Landscape
+published: true
+type: Blog
+product: Service Mesh Landscape
+resource: true
+redirect_from:
+ - /blog/layer5-landscape-spectrums-revisited/
+---
+
+
+import issueImage from "./issue.webp";
+
+
+
+Several weeks ago, I wrote [a blog post](https://raungar.wordpress.com/2019/11/15/introducing-comparative-spectrums-to-the-layer5-landscape/) about introducing "comparative spectrum" tools to [the Layer5 landscape](https://layer5.io/landscape)—a webpage which I have transformed multiple times, now!
+
+Up until now, the contents of each blog post I have written were centered upon a freshly-opened pull request. Shortly before writing my last post, I did open [one such pull request (layer5#238)](https://github.com/layer5io/layer5/pull/238). However, since my PR remains open, and since I am still working on the same issue my PR addresses, I have opted to instead push [a new commit](https://github.com/layer5io/layer5/pull/238/commits/4d396aaa6d3ca46add71531daedc8c0e2a5d2495) to the aformentioned (but, now, renamed) PR instead of creating a whole new one. This newest commit introduces a major step towards resolving the issue at hand, and will be the subject of this blog post!
+
+
+
+The issue at hand: [layer5#211](https://github.com/layer5io/layer5/issues/211) - add comparative spectrums to the Landscape page
+
+* * *
+
+_**Note:** this blog post will frequently reference [the update and documentation comment that I made](https://github.com/layer5io/layer5/pull/238#issuecomment-561613644) to accompany my last commit to my PR. I consider this hefty comment to be an extension of this blog post, so I strongly recommend giving it a read!_
+
+* * *
+
+My initial commit towards introducing comparative spectrum tooling did not represent a full solution. Thinking about what might constitute a full solution for the issue at hand, I came up with three criteria:
+
+## What was still needed:
+
+#### 1\. A complete toolset
+
+Within [Issue #211](https://github.com/layer5io/layer5/issues/211), Layer5 lead developer Lee indicates [four slides](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p6) upon which comparative spectrum graphics may be based upon. During my initial commit, I created graphics that emulated those found within the first three of those four slides, but I had yet to implement the graphic found in [the fourth](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p12): a table. I was also less-than-satisfied with the 'grid' design I had implemented in response to [slide 7](https://docs.google.com/presentation/d/1P6LzzG0_alAxshpdfLnix53S9WU4vjbpSCrHJQoWPqc/edit#slide=id.p10).
+
+#### 2\. A modular design
+
+The designs I am implementing are meant to be used to present opinionated information. As I am not nearly knowledgeable to form opinionated comparisons between service meshes and related technologies, I have instead made my goal to make it as easy as possible for other Layer5 contributors to utilize the graphics ("\[comparative\] spectrums") that I am designing. Doing so would require encapsulating (templating) the spectrums I design (new and old), within their own HTML files, and providing a means to easily invoke (and customize) instances of those templates into the Landscape page.
+
+#### 3\. Documentation
+
+Because the templates I design are intended to be implemented and customized by other contributors, it is _especially_ critical that those contributors have access to complete and thorough documentation detailing the intended use of each templated design.
+
+* * *
+
+## What I delivered:
+
+#### 1\. A complete toolset
+
+As documented in my [update comment](https://github.com/layer5io/layer5/pull/238#issuecomment-561613644), I designed a table that very closely resembles that of Lee's slides. Implementing the table was interesting, as it ended up requiring [quite a few nested Liquid for-loops](https://github.com/layer5io/layer5/blob/4d396aaa6d3ca46add71531daedc8c0e2a5d2495/_includes/partials/spectrum/table.html#L23). Also as documented, I revamped the grid-based tooling and am quite pleased with the improvements made. The end result of these efforts is a complete set of comparative spectrums.
+
+#### 2, 3. A modular design and documentation
+
+The bulk of the documentation I wrote details how to deal with the modular solution that I designed and implemented to enable comparative spectrums to be included into the Landscape page (through the use of Liquid `include` tags). The documentation speaks for itself; [check it out!](https://github.com/layer5io/layer5/pull/238#issuecomment-561613644)
+
+## What's next?
+
+I would not have considered the documentation I delivered to be complete if I did not report on the issues still present in the work I delivered. I denoted these as 'Current issues' in the documentation, and they represent work that still remains to be done. I know that I can count on the Layer5 community to assist me with small issues like these, and, once this pull request receives some forward motion, I hope to start zeroing in on its smaller issues. Fortunately, I have made plans to continue working with open source well into the new year!
+
+
+
diff --git a/src/collections/blog/2020/2020-03-11-deploying-linkerd-with-meshery/index.mdx b/src/collections/blog/2020/2020-03-11-deploying-linkerd-with-meshery/index.mdx
index 793b9edf0b11..d905e19a9fbc 100644
--- a/src/collections/blog/2020/2020-03-11-deploying-linkerd-with-meshery/index.mdx
+++ b/src/collections/blog/2020/2020-03-11-deploying-linkerd-with-meshery/index.mdx
@@ -1,152 +1,150 @@
----
-title: "Deploying Linkerd with Meshery"
-subtitle: ""
-date: 2020-03-11 08:15:05 +0000
-author: Anton Weiss
-thumbnail: ./Linkerd-with-Meshery.webp
-darkthumbnail: ./Linkerd-with-Meshery.webp
-category: Meshery
-tags:
- - Linkerd
- - Meshery
-published: true
-type: Blog
-mesh: Linkerd
-product: Meshery
-resource: true
-redirect_from:
- - /blog/deploying-linkerd-with-meshery/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import awsappmesh from '../../../../assets/images/service-mesh-icons/aws-app-mesh.webp';
-import consul from '../../../../assets/images/service-mesh-icons/consul.svg';
-import istio from '../../../../assets/images/service-mesh-icons/istio.svg';
-import linkerd from '../../../../assets/images/service-mesh-icons/linkerd.svg';
-import maesh from '../../../../assets/images/service-mesh-icons/maesh.webp';
-import nsm from '../../../../assets/images/service-mesh-icons/nsm.svg';
-import octarine from '../../../../assets/images/service-mesh-icons/octarine.svg';
-import kuma from '../../../../assets/images/service-mesh-icons/kuma.svg';
-import {Link} from "gatsby"
-
-
-
-It’s no secret that service mesh tech is boiling hot. Microservice architectures brought on as many challenges as they have advantages. With operational complexity being one of the most acute pains. Service meshes do offer solutions to a number of these operational concerns. Including but not limited to: resilience, improved observability, security and advanced service discovery.
-
-
-
-
-
-But with so many mesh options around - how do we choose, evaluate and compare them? And once we’ve chosen a solution - how do we make it accessible to all our engineers? It is to provide an answer to these questions that the Layer5 community has created Meshery, the open-source, service mesh management plane. Meshery already supports a number of leading mesh providers with adapters for additional meshes on the way. In today’s video, I’ll show how to use Meshery for rolling out and evaluating Linkerd.
-
- Linkerd is a system that comes from the service mesh pioneers - the company called Buoyant. They were the first to realise the need for a distributed network of smart, centrally configured proxies and coin the term “service mesh” back in 2016. Today, we’ll be looking at Linkerd 2.x - the second generation of this now CNCF project.
-
Featuring custom-built, highly performant proxies written in Rust
-
Zero-config option (works out-of-the-box)
-
Network telemetry built-in (includes a pre-configured, optimised Prometheus instance)
-
Low-overhead control-plane
-
Operational simplicity (when compared to Istio, for example, even though Istio is getting better in this regard)
-
-So what is covered in the video? More or less the following:
-
-
What service mesh tech allows us to do
-
What a typical service mesh architecture looks like
-
What Layer5 is about (Lookout - it may surprise you! 😯)
-
What Meshery is. What Linkerd is.
-
How easy it is to install Meshery on your PC (be it Linux, Mac or Windows)
-
All it takes is:
-
-```sh
-$ curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
-```
-
-
-
How Meshery connects to your Kubernetes cluster (nothing to be done if it’s in your kubectl config current-context)
-
How to correctly install and remove Linkerd on your Kubernetes cluster using Meshery
-
How to install one of included Linkerd sample applications and verify the installation
-
-That’s quite a lot of content for a 20 minute clip. In the follow-up videos, we’ll dive deeper into many of these concepts. And also show how to use Meshery with other service mesh providers.
-
-This video is also the opening shot of Layer5's [Learn to Service Mesh](https://www.youtube.com/playlist?list=PL3A-A6hPO2IN_HSU0pSfijBboiHggs5mC) playlist, which is specifically dedicated to tutorials and webinars. If service mesh tech interests you and you’re willing to learn more about it, then make sure to [subscribe to the channel](https://www.youtube.com/channel/UCFL1af7_wdnhHXL1InzaMvA?sub_confirmation=1) and watch for updates.
-
-And let us know if there’s any specific content you want us to create. Or maybe anything you’ve created yourself and would like to share? Layer5 is all about knowledge sharing and we want to talk to you, so please [join the cloud native community](http://slack.layer5.io)!
-
-Happy meshing!
-
-
-
-
+---
+title: "Deploying Linkerd with Meshery"
+subtitle: ""
+date: 2020-03-11 08:15:05 +0000
+author: Anton Weiss
+thumbnail: ./Linkerd-with-Meshery.webp
+darkthumbnail: ./Linkerd-with-Meshery.webp
+category: Meshery
+tags:
+ - Linkerd
+ - Meshery
+published: true
+type: Blog
+mesh: Linkerd
+product: Meshery
+resource: true
+redirect_from:
+ - /blog/deploying-linkerd-with-meshery/
+---
+
+
+import awsappmesh from "../../../../assets/images/service-mesh-icons/aws-app-mesh.webp";
+import consul from "../../../../assets/images/service-mesh-icons/consul.svg";
+import istio from "../../../../assets/images/service-mesh-icons/istio.svg";
+import linkerd from "../../../../assets/images/service-mesh-icons/linkerd.svg";
+import maesh from "../../../../assets/images/service-mesh-icons/maesh.webp";
+import nsm from "../../../../assets/images/service-mesh-icons/nsm.svg";
+import octarine from "../../../../assets/images/service-mesh-icons/octarine.svg";
+import kuma from "../../../../assets/images/service-mesh-icons/kuma.svg";
+
+
+
+
+It’s no secret that service mesh tech is boiling hot. Microservice architectures brought on as many challenges as they have advantages. With operational complexity being one of the most acute pains. Service meshes do offer solutions to a number of these operational concerns. Including but not limited to: resilience, improved observability, security and advanced service discovery.
+
+
+
+
+
+But with so many mesh options around - how do we choose, evaluate and compare them? And once we’ve chosen a solution - how do we make it accessible to all our engineers? It is to provide an answer to these questions that the Layer5 community has created Meshery, the open-source, service mesh management plane. Meshery already supports a number of leading mesh providers with adapters for additional meshes on the way. In today’s video, I’ll show how to use Meshery for rolling out and evaluating Linkerd.
+
+ Linkerd is a system that comes from the service mesh pioneers - the company called Buoyant. They were the first to realise the need for a distributed network of smart, centrally configured proxies and coin the term “service mesh” back in 2016. Today, we’ll be looking at Linkerd 2.x - the second generation of this now CNCF project.
+
Featuring custom-built, highly performant proxies written in Rust
+
Zero-config option (works out-of-the-box)
+
Network telemetry built-in (includes a pre-configured, optimised Prometheus instance)
+
Low-overhead control-plane
+
Operational simplicity (when compared to Istio, for example, even though Istio is getting better in this regard)
+
+So what is covered in the video? More or less the following:
+
+
What service mesh tech allows us to do
+
What a typical service mesh architecture looks like
+
What Layer5 is about (Lookout - it may surprise you! 😯)
+
What Meshery is. What Linkerd is.
+
How easy it is to install Meshery on your PC (be it Linux, Mac or Windows)
+
+
+All it takes is:
+
+```sh
+$ curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
+```
+
+
+
How Meshery connects to your Kubernetes cluster (nothing to be done if it’s in your kubectl config current-context)
+
How to correctly install and remove Linkerd on your Kubernetes cluster using Meshery
+
How to install one of included Linkerd sample applications and verify the installation
+
+That’s quite a lot of content for a 20 minute clip. In the follow-up videos, we’ll dive deeper into many of these concepts. And also show how to use Meshery with other service mesh providers.
+
+This video is also the opening shot of Layer5's [Learn to Service Mesh](https://www.youtube.com/playlist?list=PL3A-A6hPO2IN_HSU0pSfijBboiHggs5mC) playlist, which is specifically dedicated to tutorials and webinars. If service mesh tech interests you and you’re willing to learn more about it, then make sure to [subscribe to the channel](https://www.youtube.com/channel/UCFL1af7_wdnhHXL1InzaMvA?sub_confirmation=1) and watch for updates.
+
+And let us know if there’s any specific content you want us to create. Or maybe anything you’ve created yourself and would like to share? Layer5 is all about knowledge sharing and we want to talk to you, so please [join the cloud native community](http://slack.layer5.io)!
+
+Happy meshing!
+
+
+
+
diff --git a/src/collections/blog/2020/2020-05-21-getting-started-with-mesheryctl/index.mdx b/src/collections/blog/2020/2020-05-21-getting-started-with-mesheryctl/index.mdx
index 6c28cd5e7322..486a222bbe21 100644
--- a/src/collections/blog/2020/2020-05-21-getting-started-with-mesheryctl/index.mdx
+++ b/src/collections/blog/2020/2020-05-21-getting-started-with-mesheryctl/index.mdx
@@ -1,228 +1,228 @@
----
-title: "Getting started with mesheryctl"
-subtitle: "No easier way to get started with a Cloud Native"
-date: 2020-05-21 08:00:05 -0530
-author: Layer5 Team
-thumbnail: ./mesheryctl.webp
-darkthumbnail: ./mesheryctl.webp
-category: Meshery
-tags:
- - Meshery
- - mesheryctl
-published: true
-type: Blog
-product: Meshery
-resource: true
-redirect_from:
- - /blog/getting-started-with-mesheryctl/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-
-
-
-
-### Introduction to Meshery
-
-For all those who are unaware of Meshery, Meshery is a cloud native management plane which provides users with operational best practices, lifecycle and configuration management, but also interoperates between various infrastructure, while enabling you with the tools and knowledge to glean the most of out your infrastructure performance, while keeping your overhead to a minimum.
-
-Meshery's vision is to make the operating of any cloud infrastructure simplified. Meshery is created by the Layer5.
-
-Layer5 is a community-first, Cloud Native company which has technology partnerships with various tech giants like Microsoft, CNCF, RedHat and many more to enlist. The community consists of open source leaders like maintainers of trending open-source projects, Google SoCers, Docker Captains, Cloud Native Ambassadors and many more (join in!).
-
-
-### What is mesheryctl?
-
-Meshery provides you with a clean, robust, streamlined command-line interface to manage and benchmark your infrastructure, `mesheryctl`. With `mesheryctl`, not only you can manage your adapters & containers but you can also benchmark your mesh using the command line. `mesheryctl` provides support to a number of platforms so that we never miss out users. `mesheryctl` can be installed with a single bash command by simply executing:
-
-```bash
-$ curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
-````
-
-in your terminal. You will see Meshery getting installed & fired up on port: 9081.
-You will see the output as
-
-
-```
-Extracting mesheryctl-v0.3.14...
-Archive: /Users/user/meshery.zip
- inflating: LICENSE
- inflating: README.md
- inflating: mesheryctl
-
-Installing mesheryctl in /usr/local/bin.
-mesheryctl installed.
-permissions moved to user
-Removing installation files and opening Meshery...Updating Meshery now...
-Pulling meshery ... download complete
-Pulling meshery-istio ... done
-Pulling meshery-linkerd ... done
-Pulling meshery-consul ... done
-Pulling meshery-octarine ... done
-Pulling meshery-nsm ... done
-Pulling meshery-cpx ... done
-Pulling watchtower ... done
-```
-
-and you will be able to see the Meshery UI on `https://localhost:9081`.
-
-If you are wondering if bash is only way to get `mesheryctl`, then here is the list of platforms which you can get `mesheryctl` describing all the different ways to get it.
-
-
-
-
-We believe we have not missed any of the popular platforms for what it’s worth, we will be rolling out support for RaspberryPi and OpenShift soon 🎉🎉🎉.
-
-If you are thinking about the requirements you would have to run `mesheryctl`, so to your surprise, to successfully run `mesheryctl` you will only need :
-
-
a running Docker daemon
-
-### Into the MesheryCTL
-
-Once you have successfully installed, you will be having the power of a new CLI Command MesheryCTL. As you type `mesheryctl` into your terminal, you will be shown with the various sub-commands and flags `mesheryctl` can support.
-
-```
-Meshery is the cloud native management plane, providing lifecycle, performance, and configuration management of cloud infrastructure and their workloads.
-
-Usage:
- mesheryctl [command]
-
-Available Commands:
- help Help about any command
- perf Performance Management
- system Meshery Lifecyle Management
- version Print mesheryctl version
-
-
-Flags:
- --config string config file (default location is: $HOME/.meshery//meshery.yaml)
- -h, --help help for mesheryctl
- -v, --version Version of mesheryctl
-
-Use "mesheryctl [command] --help" for more information about a command.
-```
-
-Once you do `mesheryctl system start`, Meshery will pull its adapters and latest docker images. Meshery will also detect your Kubernetes configuration and will let you know if Kubernetes is running. Meshery will run it’s web-based user interface on localhost port `9081` and will let you select your choice of Provider before you can start managing your infrastructure with this powerful utility.
-
-
One of the most interesting sub-commands of mesheryctl is perf.
-
-The `perf` subcommand enables you to being managing the performance of your cloud native deployment and your workloads running atop of them. It lets you benchmark your infrastructure without using the Meshery UI from the command line interface itself. Once you type `mesheryctl perf`, it will present you with all the powerful flags you can control with CLI, including providing it with a `--file` flag that points to any of a number of performance test profiles that you may have saved.
-
-```
-Performance Management and Benchmarking using Meshery CLI.
-
-Usage:
- mesheryctl perf --[flags]
-
-Available Flags for Performance Command:
- name[string] (optional) A short descriptor to serve as reference for this test. If not provided, a random name will be generate.
- url[string] (required) URL endpoint to send requests.
- duration[string] (required) Length of time to perform test (e.g 30s, 15m, 1hr). See standard notation https://golang.org/pkg/time/#ParseDuration
- load-generator[string] (optional) Name of load generator to be used to perform test (default: "fortio")
- provider[string] (required) Choice of Provider (default: "Meshery")
- concurrent-requests[string] (optional) Number of parallel requests to be sent (default: "1")
- qps[string] (required) Queries per second (default: "0")
- file[string] (optional) file containing SMPS-compatible test configuration.
- help Help for perf subcommand
-
-url, duration, concurrent-requests, and qps can be considered optional flags if specified through an SMPS compatible yaml file using --file
-```
-
-An example usage of `mesheryctl perf --[flags]` can be
-
-```bash
- mesheryctl perf --name "a quick stress test" --url http://192.168.1.15/productpage --qps 300 --concurrent-requests 2 --duration 30s --token "provider=Meshery"
-```
-
-You can also provide a SMPS Configuration file with `perf` subcommand, with this file provided you will not have to specify url, duration, concurrent-requests & qps. However, if specified the value provided through file will be over-rided by value through CLI. For more info about file configuration, see [here](https://github.com/service-mesh-performance/service-mesh-performance/blob/master/docs/assets/spec/readme/service%20mesh%20performance%20specification%20result.yaml).
-
-```bash
- mesheryctl perf --name "a quick stress test" --file {path}/smps.yaml --token "provider=Meshery"
-```
-
-### What's next?
-
-Meshery is an ever-growing community with attracting contributors from across the globe. We always have a role for everyone whether to be a code-writer, a community manager or a marketer. Layer5 community is always open to welcome you warmly.
-
-If this makes you excited, [join the Layer5 community](http://slack.layer5.io) with just a click & someone will be there to make sure you do not get missed.
-
-
-
+---
+title: "Getting started with mesheryctl"
+subtitle: "No easier way to get started with a Cloud Native"
+date: 2020-05-21 08:00:05 -0530
+author: Layer5 Team
+thumbnail: ./mesheryctl.webp
+darkthumbnail: ./mesheryctl.webp
+category: Meshery
+tags:
+ - Meshery
+ - mesheryctl
+published: true
+type: Blog
+product: Meshery
+resource: true
+redirect_from:
+ - /blog/getting-started-with-mesheryctl/
+---
+
+
+
+
+
+
+
+### Introduction to Meshery
+
+For all those who are unaware of Meshery, Meshery is a cloud native management plane which provides users with operational best practices, lifecycle and configuration management, but also interoperates between various infrastructure, while enabling you with the tools and knowledge to glean the most of out your infrastructure performance, while keeping your overhead to a minimum.
+
+Meshery's vision is to make the operating of any cloud infrastructure simplified. Meshery is created by the Layer5.
+
+Layer5 is a community-first, Cloud Native company which has technology partnerships with various tech giants like Microsoft, CNCF, RedHat and many more to enlist. The community consists of open source leaders like maintainers of trending open-source projects, Google SoCers, Docker Captains, Cloud Native Ambassadors and many more (join in!).
+
+
+### What is mesheryctl?
+
+Meshery provides you with a clean, robust, streamlined command-line interface to manage and benchmark your infrastructure, `mesheryctl`. With `mesheryctl`, not only you can manage your adapters & containers but you can also benchmark your mesh using the command line. `mesheryctl` provides support to a number of platforms so that we never miss out users. `mesheryctl` can be installed with a single bash command by simply executing:
+
+```bash
+$ curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
+````
+
+in your terminal. You will see Meshery getting installed & fired up on port: 9081.
+You will see the output as
+
+
+```
+Extracting mesheryctl-v0.3.14...
+Archive: /Users/user/meshery.zip
+ inflating: LICENSE
+ inflating: README.md
+ inflating: mesheryctl
+
+Installing mesheryctl in /usr/local/bin.
+mesheryctl installed.
+permissions moved to user
+Removing installation files and opening Meshery...Updating Meshery now...
+Pulling meshery ... download complete
+Pulling meshery-istio ... done
+Pulling meshery-linkerd ... done
+Pulling meshery-consul ... done
+Pulling meshery-octarine ... done
+Pulling meshery-nsm ... done
+Pulling meshery-cpx ... done
+Pulling watchtower ... done
+```
+
+and you will be able to see the Meshery UI on `https://localhost:9081`.
+
+If you are wondering if bash is only way to get `mesheryctl`, then here is the list of platforms which you can get `mesheryctl` describing all the different ways to get it.
+
+
+
+
+We believe we have not missed any of the popular platforms for what it’s worth, we will be rolling out support for RaspberryPi and OpenShift soon 🎉🎉🎉.
+
+If you are thinking about the requirements you would have to run `mesheryctl`, so to your surprise, to successfully run `mesheryctl` you will only need :
+
+
a running Docker daemon
+
+### Into the MesheryCTL
+
+Once you have successfully installed, you will be having the power of a new CLI Command MesheryCTL. As you type `mesheryctl` into your terminal, you will be shown with the various sub-commands and flags `mesheryctl` can support.
+
+```
+Meshery is the cloud native management plane, providing lifecycle, performance, and configuration management of cloud infrastructure and their workloads.
+
+Usage:
+ mesheryctl [command]
+
+Available Commands:
+ help Help about any command
+ perf Performance Management
+ system Meshery Lifecyle Management
+ version Print mesheryctl version
+
+
+Flags:
+ --config string config file (default location is: $HOME/.meshery//meshery.yaml)
+ -h, --help help for mesheryctl
+ -v, --version Version of mesheryctl
+
+Use "mesheryctl [command] --help" for more information about a command.
+```
+
+Once you do `mesheryctl system start`, Meshery will pull its adapters and latest docker images. Meshery will also detect your Kubernetes configuration and will let you know if Kubernetes is running. Meshery will run it’s web-based user interface on localhost port `9081` and will let you select your choice of Provider before you can start managing your infrastructure with this powerful utility.
+
+
One of the most interesting sub-commands of mesheryctl is perf.
+
+The `perf` subcommand enables you to being managing the performance of your cloud native deployment and your workloads running atop of them. It lets you benchmark your infrastructure without using the Meshery UI from the command line interface itself. Once you type `mesheryctl perf`, it will present you with all the powerful flags you can control with CLI, including providing it with a `--file` flag that points to any of a number of performance test profiles that you may have saved.
+
+```
+Performance Management and Benchmarking using Meshery CLI.
+
+Usage:
+ mesheryctl perf --[flags]
+
+Available Flags for Performance Command:
+ name[string] (optional) A short descriptor to serve as reference for this test. If not provided, a random name will be generate.
+ url[string] (required) URL endpoint to send requests.
+ duration[string] (required) Length of time to perform test (e.g 30s, 15m, 1hr). See standard notation https://golang.org/pkg/time/#ParseDuration
+ load-generator[string] (optional) Name of load generator to be used to perform test (default: "fortio")
+ provider[string] (required) Choice of Provider (default: "Meshery")
+ concurrent-requests[string] (optional) Number of parallel requests to be sent (default: "1")
+ qps[string] (required) Queries per second (default: "0")
+ file[string] (optional) file containing SMPS-compatible test configuration.
+ help Help for perf subcommand
+
+url, duration, concurrent-requests, and qps can be considered optional flags if specified through an SMPS compatible yaml file using --file
+```
+
+An example usage of `mesheryctl perf --[flags]` can be
+
+```bash
+ mesheryctl perf --name "a quick stress test" --url http://192.168.1.15/productpage --qps 300 --concurrent-requests 2 --duration 30s --token "provider=Meshery"
+```
+
+You can also provide a SMPS Configuration file with `perf` subcommand, with this file provided you will not have to specify url, duration, concurrent-requests & qps. However, if specified the value provided through file will be over-rided by value through CLI. For more info about file configuration, see [here](https://github.com/service-mesh-performance/service-mesh-performance/blob/master/docs/assets/spec/readme/service%20mesh%20performance%20specification%20result.yaml).
+
+```bash
+ mesheryctl perf --name "a quick stress test" --file {path}/smps.yaml --token "provider=Meshery"
+```
+
+### What's next?
+
+Meshery is an ever-growing community with attracting contributors from across the globe. We always have a role for everyone whether to be a code-writer, a community manager or a marketer. Layer5 community is always open to welcome you warmly.
+
+If this makes you excited, [join the Layer5 community](http://slack.layer5.io) with just a click & someone will be there to make sure you do not get missed.
+
+
+
diff --git a/src/collections/blog/2020/2020-06-01-meshery-accepted-into-cncf-landscape/index.mdx b/src/collections/blog/2020/2020-06-01-meshery-accepted-into-cncf-landscape/index.mdx
index b35122a76131..6b3b4c1ed863 100644
--- a/src/collections/blog/2020/2020-06-01-meshery-accepted-into-cncf-landscape/index.mdx
+++ b/src/collections/blog/2020/2020-06-01-meshery-accepted-into-cncf-landscape/index.mdx
@@ -1,71 +1,71 @@
----
-title: "Meshery lands in the CNCF Landscape"
-subtitle: "This is a story about growing together as a community and building a project that matters."
-date: 2020-06-01 10:30:05 -0530
-author: Anton Weiss
-thumbnail: ./cncf-meshery.webp
-darkthumbnail: ./cncf-meshery.webp
-category: Announcements
-tags:
- - Meshery
- - Landscape
-published: true
-type: Blog
-product: Meshery
-resource: true
-redirect_from:
- - /blog/meshery-lands-in-the-cncf-landscape/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import cncf from "./cncf-landscape-stacked-color.svg"
-import cncfmeshery from "./cncf-meshery-landscape.webp"
-
-
-
-
-
-### Digging into Service Meshes
-
-About a year and a half ago I got interested in service mesh technology. A customer needed some advanced routing capabilities and we started looking at Envoy and Istio. Then - invitations to talk about Istio at meetups and conferences started flowing in. That's when I got excited about progressive delivery capabilities that service meshes enable. I even wrote a Kubernetes Istio canary controller - BirdWatch.
-
-### Finding Meshery
-
-Digging deeper into what service meshes had to offer I discovered Meshery - the universal service mesh management plane. And immediately joined Layer5 - the great, welcoming open-source community that created it.
-
-### Community Matters
-
-Being a member of Layer5 was one of the nicest community experiences I've ever had. Mainly thanks to community's founder and captain - Lee Calcote. He always makes sure everybody feels significant, included and motivated to participate. And this spirit spreads out to all community activities.
-
-In no time, I had my first commits approved and merged and started joining weekly community and development video calls.
-
-### We're on CNCF Landscape!
-
-Now - I won't be reviewing Meshery in this post. I've spoken about it in this video and some great introductory articles by community members can be found here and here. This post is more of a celebration, because last week...
-
-
Meshery now featured in the CNCF Landscape!
-
-
-
-And this is only the first step - there's already an application filed for Meshery to become a full-fledged CNCF sandbox project. I had a chance to collaborate on the sandbox proposal and am so eager for this to happen.
-
-### Getting Meshy
-
-This is also an invitation to participate - Meshery is a young, ambitious project - it requires a ton of work to make it what it aims to become. Integrating with all of the leading service mesh solutions asks for extensive expertise. In many areas Meshery's functionality is still young. But these are normal growth stages, aren't they? To put it simple - the community and the project need more hands! And these should be your hands!
-
-
As already mentioned - Layer5 is a very welcoming bunch!
-
-Open source contributions are a must-do for becoming a true cloud native hero. Cloud native is all about the community and one can't be a part of a community by only taking and never giving back. So if you were looking for a promising and welcoming project to join - look no further! Hop on to Layer5 Slack and we'll happily embrace you and help you get started.
-
-And it's not only coding! Documentation, testing, UI design, logos, blogs, videos - you decide where to apply your talent.
-
-For example - I sometimes wish I had more time and motivation to code new Meshery features or fix existing bugs. But instead I'm writing this post. Because lately I enjoy writing texts more than coding. Coding for longer than a couple of days at a time throws me into a coding fatigue… Actually also many other activities do. I'm just not very good at keeping a routine. But I'm sure many of you out there aren't like me. So why not join forces?
-
-### Join the cloud native community!
-
-* Meshery is an exciting opportunity to learn more about service meshes.
-* We're already on CNCF Landscape and are headed for the sandbox.
-* Now is a great time to hop on board. Are you ready? Get into the mesh pit!
-
-
-
+---
+title: "Meshery lands in the CNCF Landscape"
+subtitle: "This is a story about growing together as a community and building a project that matters."
+date: 2020-06-01 10:30:05 -0530
+author: Anton Weiss
+thumbnail: ./cncf-meshery.webp
+darkthumbnail: ./cncf-meshery.webp
+category: Announcements
+tags:
+ - Meshery
+ - Landscape
+published: true
+type: Blog
+product: Meshery
+resource: true
+redirect_from:
+ - /blog/meshery-lands-in-the-cncf-landscape/
+---
+
+
+import cncf from "./cncf-landscape-stacked-color.svg"
+import cncfmeshery from "./cncf-meshery-landscape.webp"
+
+
+
+
+
+### Digging into Service Meshes
+
+About a year and a half ago I got interested in service mesh technology. A customer needed some advanced routing capabilities and we started looking at Envoy and Istio. Then - invitations to talk about Istio at meetups and conferences started flowing in. That's when I got excited about progressive delivery capabilities that service meshes enable. I even wrote a Kubernetes Istio canary controller - BirdWatch.
+
+### Finding Meshery
+
+Digging deeper into what service meshes had to offer I discovered Meshery - the universal service mesh management plane. And immediately joined Layer5 - the great, welcoming open-source community that created it.
+
+### Community Matters
+
+Being a member of Layer5 was one of the nicest community experiences I've ever had. Mainly thanks to community's founder and captain - Lee Calcote. He always makes sure everybody feels significant, included and motivated to participate. And this spirit spreads out to all community activities.
+
+In no time, I had my first commits approved and merged and started joining weekly community and development video calls.
+
+### We're on CNCF Landscape!
+
+Now - I won't be reviewing Meshery in this post. I've spoken about it in this video and some great introductory articles by community members can be found here and here. This post is more of a celebration, because last week...
+
+
Meshery now featured in the CNCF Landscape!
+
+
+
+And this is only the first step - there's already an application filed for Meshery to become a full-fledged CNCF sandbox project. I had a chance to collaborate on the sandbox proposal and am so eager for this to happen.
+
+### Getting Meshy
+
+This is also an invitation to participate - Meshery is a young, ambitious project - it requires a ton of work to make it what it aims to become. Integrating with all of the leading service mesh solutions asks for extensive expertise. In many areas Meshery's functionality is still young. But these are normal growth stages, aren't they? To put it simple - the community and the project need more hands! And these should be your hands!
+
+
As already mentioned - Layer5 is a very welcoming bunch!
+
+Open source contributions are a must-do for becoming a true cloud native hero. Cloud native is all about the community and one can't be a part of a community by only taking and never giving back. So if you were looking for a promising and welcoming project to join - look no further! Hop on to Layer5 Slack and we'll happily embrace you and help you get started.
+
+And it's not only coding! Documentation, testing, UI design, logos, blogs, videos - you decide where to apply your talent.
+
+For example - I sometimes wish I had more time and motivation to code new Meshery features or fix existing bugs. But instead I'm writing this post. Because lately I enjoy writing texts more than coding. Coding for longer than a couple of days at a time throws me into a coding fatigue… Actually also many other activities do. I'm just not very good at keeping a routine. But I'm sure many of you out there aren't like me. So why not join forces?
+
+### Join the cloud native community!
+
+* Meshery is an exciting opportunity to learn more about service meshes.
+* We're already on CNCF Landscape and are headed for the sandbox.
+* Now is a great time to hop on board. Are you ready? Get into the mesh pit!
+
+
+
diff --git a/src/collections/blog/2020/2020-06-23-google-summer-of-code-2020-service-mesh-performance-with-envoy-nighthawk/index.mdx b/src/collections/blog/2020/2020-06-23-google-summer-of-code-2020-service-mesh-performance-with-envoy-nighthawk/index.mdx
index 7762529fa91a..75cf323d9efb 100644
--- a/src/collections/blog/2020/2020-06-23-google-summer-of-code-2020-service-mesh-performance-with-envoy-nighthawk/index.mdx
+++ b/src/collections/blog/2020/2020-06-23-google-summer-of-code-2020-service-mesh-performance-with-envoy-nighthawk/index.mdx
@@ -1,56 +1,56 @@
----
-title: "Google Summer of Code 2020: Service Mesh Performance with Envoy Nighthawk"
-subtitle: "One of the greatest learning experiences yet."
-date: 2020-06-23 10:30:05 -0530
-author: Kush Trivedi
-thumbnail: ./gsoc-wide.webp
-darkthumbnail: ./gsoc-wide.webp
-category: Programs
-tags:
- - GSoC
- - Programs
- - Performance
- - Nighthawk
- - Service Mesh Performance
-published: true
-redirect_from:
- - /blog/google-summer-of-code-2020-service-mesh-performance-with-envoy-nighthawk/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import gsocLogo from "./gsoc.webp";
-import { Link } from "gatsby";
-
-
-
-
How did it all start?
-
-
-I was introduced to the Layer5 community by our very own Lee Calcote, and since then I have been exploring the vast world of service meshes and their performance characteristics. Before being accepted as a Google Summer of Code intern, I had been working with the Layer5 community as an active contributor, exploring various new DevOps tooling like service meshes, the sidecar concept, and performance benchmarking of services. I have had a run-in with the Kubernetes community before and initially believed Kubernetes to be the final stage of DevOps, but I was happily surprised when I found out that the end of Kubernetes merely marked the entrypoint to a whole new world of service meshes.
-
-
-And so, we reach the beginning of my GSoC 2020 internship, which began on the night of May 3rd, 2020 when I learned that I had been selected as a GSoC Participant with the Cloud Native Computing Foundation (CNCF). Admittedly, I had tried my best an year ago to get into GSoC’19 with another organisation but due to reasons only Google can tell you, I was not accepted. Everything happens for a reason though, right?
-Six months ago, if you would have told me that I would be working with service meshes, gRPC, load testing, performance benchmarking alongside prominent members of the open source world of Cloud Native, I would have ignored you with the least possible amount of prudence I could muster.
-
-
-
What is my project about?
-
-My GSoC project is to Enable Distributed Load Testing for various Service Mesh Planes using Envoy Nighthawk. For those who are not familiar with Nighthawk, it is a performance benchmark tool written and maintained by the Envoy community. We are in the process of incorporating Nighthawk into Meshery - the cloud native management plane.Meshery already supports performance testing of service meshes using fortio & wrk2 and is maintained by the Layer5 community and is also a member of CNCF Landscape. Alongside this effort, we are creating a new industry standard: Service Mesh Performance Specification which is another initiative of the Layer5 community to establish a common format for describing and capturing service mesh performance.
-
-
-It has been a month since I have started my GSoC’20 tenure with the Layer5 community, and in this month, I have learned a lot from my code contributions and mentor. I began with setting up the project roadmap and discussing the potential use cases of Nighthawk with its maintainers during my community bonding period. I came to know some incredible people during the community bonding from big tech giants like Google, Facebook, Microsoft, Affirmed Networks, Red Hat and many more to list. Before incorporating Nighthawk, we had to make various enhancements in Meshery, like adding user preferences for performance settings, specifying the SMPS format for exporting and importing of load-test preferences, load-generator interface and more.
-
-
-I have learned a hoard of new things, like gRPC services and how they communicate using protocol buffers, load generation using fortio, writing handlers for various endpoints using golang, and some frontend architecture with Nextjs.
-
-
-
-
About the community
-
-Layer5 has one of the healthiest open source communities that I have ever worked with. In the past, I have worked with a variety of well-maintained and large scale open source communities but I have never experienced a more welcoming and nurturing environment than Layer5. At Layer5, we respect each contributor and their contributions, whether it is a new adapter or just a typo fix. If you can contribute, please do. It’s that simple! With many awesome initiatives like SMPS, Distributed Load Testing, Performance Benchmarking, Learn Layer5, and Image Hub, the exponential increase of Layer5 and its various projects is inevitable.
-
-
-
-_**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!**_
-
-
+---
+title: "Google Summer of Code 2020: Service Mesh Performance with Envoy Nighthawk"
+subtitle: "One of the greatest learning experiences yet."
+date: 2020-06-23 10:30:05 -0530
+author: Kush Trivedi
+thumbnail: ./gsoc-wide.webp
+darkthumbnail: ./gsoc-wide.webp
+category: Programs
+tags:
+ - GSoC
+ - Programs
+ - Performance
+ - Nighthawk
+ - Service Mesh Performance
+published: true
+redirect_from:
+ - /blog/google-summer-of-code-2020-service-mesh-performance-with-envoy-nighthawk/
+---
+
+
+import gsocLogo from "./gsoc.webp";
+
+
+
+
+
How did it all start?
+
+
+I was introduced to the Layer5 community by our very own Lee Calcote, and since then I have been exploring the vast world of service meshes and their performance characteristics. Before being accepted as a Google Summer of Code intern, I had been working with the Layer5 community as an active contributor, exploring various new DevOps tooling like service meshes, the sidecar concept, and performance benchmarking of services. I have had a run-in with the Kubernetes community before and initially believed Kubernetes to be the final stage of DevOps, but I was happily surprised when I found out that the end of Kubernetes merely marked the entrypoint to a whole new world of service meshes.
+
+
+And so, we reach the beginning of my GSoC 2020 internship, which began on the night of May 3rd, 2020 when I learned that I had been selected as a GSoC Participant with the Cloud Native Computing Foundation (CNCF). Admittedly, I had tried my best an year ago to get into GSoC’19 with another organisation but due to reasons only Google can tell you, I was not accepted. Everything happens for a reason though, right?
+Six months ago, if you would have told me that I would be working with service meshes, gRPC, load testing, performance benchmarking alongside prominent members of the open source world of Cloud Native, I would have ignored you with the least possible amount of prudence I could muster.
+
+
+
What is my project about?
+
+My GSoC project is to Enable Distributed Load Testing for various Service Mesh Planes using Envoy Nighthawk. For those who are not familiar with Nighthawk, it is a performance benchmark tool written and maintained by the Envoy community. We are in the process of incorporating Nighthawk into Meshery - the cloud native management plane.Meshery already supports performance testing of service meshes using fortio & wrk2 and is maintained by the Layer5 community and is also a member of CNCF Landscape. Alongside this effort, we are creating a new industry standard: Service Mesh Performance Specification which is another initiative of the Layer5 community to establish a common format for describing and capturing service mesh performance.
+
+
+It has been a month since I have started my GSoC’20 tenure with the Layer5 community, and in this month, I have learned a lot from my code contributions and mentor. I began with setting up the project roadmap and discussing the potential use cases of Nighthawk with its maintainers during my community bonding period. I came to know some incredible people during the community bonding from big tech giants like Google, Facebook, Microsoft, Affirmed Networks, Red Hat and many more to list. Before incorporating Nighthawk, we had to make various enhancements in Meshery, like adding user preferences for performance settings, specifying the SMPS format for exporting and importing of load-test preferences, load-generator interface and more.
+
+
+I have learned a hoard of new things, like gRPC services and how they communicate using protocol buffers, load generation using fortio, writing handlers for various endpoints using golang, and some frontend architecture with Nextjs.
+
+
+
+
About the community
+
+Layer5 has one of the healthiest open source communities that I have ever worked with. In the past, I have worked with a variety of well-maintained and large scale open source communities but I have never experienced a more welcoming and nurturing environment than Layer5. At Layer5, we respect each contributor and their contributions, whether it is a new adapter or just a typo fix. If you can contribute, please do. It’s that simple! With many awesome initiatives like SMPS, Distributed Load Testing, Performance Benchmarking, Learn Layer5, and Image Hub, the exponential increase of Layer5 and its various projects is inevitable.
+
+
+
+_**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/2020/2020-06-25-SMI-conformance-testing-with-meshery/index.mdx b/src/collections/blog/2020/2020-06-25-SMI-conformance-testing-with-meshery/index.mdx
index 7ce9bd56fc1a..67b9a9ca0ac1 100644
--- a/src/collections/blog/2020/2020-06-25-SMI-conformance-testing-with-meshery/index.mdx
+++ b/src/collections/blog/2020/2020-06-25-SMI-conformance-testing-with-meshery/index.mdx
@@ -1,81 +1,81 @@
----
-title: "Starting SMI Conformance Testing with Meshery"
-subtitle: ""
-date: 2020-06-25 10:30:05 -0530
-author: Naveen Kumar
-thumbnail: ./smi-conformance.svg
-darkthumbnail: ./smi-conformance.svg
-category: Programs
-tags:
- - Community
- - Programs
- - "Service Mesh Interface"
-published: true
-type: Blog
-product: Meshery
-resource: true
-redirect_from:
- - /blog/community/SMI-conformance-testing-with-meshery/
- - /blog/community/blog/smi-conformance-testing-with-meshery/
- - /blog/smi-conformance-testing-with-meshery/
----
-import { Link } from "gatsby";
-import { BlogWrapper } from "../../Blog.style.js";
-import smilogo from "./smi-logo.webp";
-import checklist from "./checklist.svg"
-
-
-
-
-
-### About SMI
-
-The Service Mesh Interface (SMI) is a specification for service meshes that run on Kubernetes. It utilizes CRDs to modify the behavior of service meshes. The project is under development at [SMI Github Repository](https://github.com/servicemeshinterface/smi-spec). Please visit the github repository page to know the latest advancements in the characteristics. The complete spec can be found [here](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md).
-
-### APIs in SMI
-
-Currently SMI supports 4 set of APIs:
-
-- [Traffic Specs](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-specs) - Used to define traffic, currently only supports TCP, HTTP traffic.
-- [Traffic Access Control](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-access-control) - Used to specify whether a particular form of traffic is allowed or not
-- [Traffic Split](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-split) - Used to redirect/divide a request for a resource between 2 or more resources. Useful in canary testing
-- [Traffic Metrics](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-metrics) - Used to expose common traffic metrics like p99 in a specific format that can be utilized by single dashboard for all the service meshes.
-
-### About SMI Conformance Tests
-
-**SMI Conformance Tests** check whether the service mesh that is installed in the kubernetes cluster, conforms to SMI specs or not. This involves asking some major questions. Does it have the required CRDs? Do these CRDs perform as they should when applied or not applied? Are we able to get metrics in a proper format?
-
-All these questions will be answered by SMI conformance tests. The biggest benefit of your service mesh conforming to SMI is that it makes building tools an easier process.Also, one time development of any tool would in turn support all the meshes that conform to SMI.
-
-Sounds fun, right? Let's dig deeper into the SMI conformance project and find out.
-
-### Meshery'ing with Conformance Tests
-
-
-
-Meshery is _the cloud native management plane__. It supports all the popular meshes, teaches you how to manage them, assists you in applying custom or recommended configurations, tests for compatibility, performs performance tests for meshes and a lot more. The SMI conformance testing requires performance testing capabilities, load generation (Meshery is about to support distributed load generation as well), and other functionalities such that these conformance tests can be easily used in the pipelines of all the popular service meshes. mesheryctl does have a perf command that can be used in the pipelines of service meshes. I aim at making such capabilities for SMI conformance as well.
-
-As you have made your way halfway through the post (thank you for your patience), you should now be aware of SMI, its conformance practices and how Meshery’s incredible engineering can be utilized for conformance tests. We can now tackle the larger questions and hope to see the bigger picture.
-
-### The Bigger Picture
-
-Do you know that almost all of the test cases that we would write in this project would be raw YAML files? To those doing traditional unit and integration tests, we might sound unhinged at this point. We assure you that we are completely sober and serious (if you don’t count the temporary euphoria from geeky jokes).
-
-#### Forking [kuttl](https://kuttl.dev/)
-
-`kuttl` is a tool for writing tests against Kubernetes operators and controllers. It can ascertain whether any kind of resources exist or not in the Kubernetes cluster, spring up a kind cluster and do other convenient things. Another plus is that It's entirely declarative. Consider a scenario in which we have a special use case where we wanted to run some go code after each individual step in the test case was executed. To accomplish this, we forked `kuttl` and modified it a little. You can see our modified version [here](https://github.com/kanishkarj/kuttl).
-
-
-We are planning to use `kuttl` for all the APIs in SMI. We are also planning to use the Meshery load generator with the modified version of `kuttl`.
-
-#### [Learn Layer5](https://github.com/layer5io/learn-layer5/)
-
-Learn Layer5 is a sample app which is very lightweight and simple to deploy. It is a simple sample app for learning about service meshes. We are planning to use the same app for testing for SMI conformance. The app is deployed when we test for SMI conformance and traffic is generated from one service/deployment/pod to another. This is a great tool for playing around with service meshes and the tools provided by Layer5 and its projects without investing any personal resources.
-
-This is where all the test cases along with the code will be placed. Currently, there is a large overlap in the learn-layer5 and `smi-conformance` testing files. All those changes will be transferred here.
-
-If any of this sounds remotely exciting, I implore you to give this a chance. You won’t regret it.
-Head over to our [Slack Channel](http://slack.layer5.io) and join the #smi channel where everything related to conformance testing is discussed. We would love to hear your feedback. Stay tuned for more blogs related to SMI Conformance and all things meshy!!!
-
-
-
+---
+title: "Starting SMI Conformance Testing with Meshery"
+subtitle: ""
+date: 2020-06-25 10:30:05 -0530
+author: Naveen Kumar
+thumbnail: ./smi-conformance.svg
+darkthumbnail: ./smi-conformance.svg
+category: Programs
+tags:
+ - Community
+ - Programs
+ - "Service Mesh Interface"
+published: true
+type: Blog
+product: Meshery
+resource: true
+redirect_from:
+ - /blog/community/SMI-conformance-testing-with-meshery/
+ - /blog/community/blog/smi-conformance-testing-with-meshery/
+ - /blog/smi-conformance-testing-with-meshery/
+---
+
+
+import smilogo from "./smi-logo.webp";
+import checklist from "./checklist.svg"
+
+
+
+
+
+### About SMI
+
+The Service Mesh Interface (SMI) is a specification for service meshes that run on Kubernetes. It utilizes CRDs to modify the behavior of service meshes. The project is under development at [SMI Github Repository](https://github.com/servicemeshinterface/smi-spec). Please visit the github repository page to know the latest advancements in the characteristics. The complete spec can be found [here](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md).
+
+### APIs in SMI
+
+Currently SMI supports 4 set of APIs:
+
+- [Traffic Specs](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-specs) - Used to define traffic, currently only supports TCP, HTTP traffic.
+- [Traffic Access Control](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-access-control) - Used to specify whether a particular form of traffic is allowed or not
+- [Traffic Split](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-split) - Used to redirect/divide a request for a resource between 2 or more resources. Useful in canary testing
+- [Traffic Metrics](https://github.com/servicemeshinterface/smi-spec/blob/master/SPEC.md#traffic-metrics) - Used to expose common traffic metrics like p99 in a specific format that can be utilized by single dashboard for all the service meshes.
+
+### About SMI Conformance Tests
+
+**SMI Conformance Tests** check whether the service mesh that is installed in the kubernetes cluster, conforms to SMI specs or not. This involves asking some major questions. Does it have the required CRDs? Do these CRDs perform as they should when applied or not applied? Are we able to get metrics in a proper format?
+
+All these questions will be answered by SMI conformance tests. The biggest benefit of your service mesh conforming to SMI is that it makes building tools an easier process.Also, one time development of any tool would in turn support all the meshes that conform to SMI.
+
+Sounds fun, right? Let's dig deeper into the SMI conformance project and find out.
+
+### Meshery'ing with Conformance Tests
+
+
+
+Meshery is _the cloud native management plane__. It supports all the popular meshes, teaches you how to manage them, assists you in applying custom or recommended configurations, tests for compatibility, performs performance tests for meshes and a lot more. The SMI conformance testing requires performance testing capabilities, load generation (Meshery is about to support distributed load generation as well), and other functionalities such that these conformance tests can be easily used in the pipelines of all the popular service meshes. mesheryctl does have a perf command that can be used in the pipelines of service meshes. I aim at making such capabilities for SMI conformance as well.
+
+As you have made your way halfway through the post (thank you for your patience), you should now be aware of SMI, its conformance practices and how Meshery’s incredible engineering can be utilized for conformance tests. We can now tackle the larger questions and hope to see the bigger picture.
+
+### The Bigger Picture
+
+Do you know that almost all of the test cases that we would write in this project would be raw YAML files? To those doing traditional unit and integration tests, we might sound unhinged at this point. We assure you that we are completely sober and serious (if you don’t count the temporary euphoria from geeky jokes).
+
+#### Forking [kuttl](https://kuttl.dev/)
+
+`kuttl` is a tool for writing tests against Kubernetes operators and controllers. It can ascertain whether any kind of resources exist or not in the Kubernetes cluster, spring up a kind cluster and do other convenient things. Another plus is that It's entirely declarative. Consider a scenario in which we have a special use case where we wanted to run some go code after each individual step in the test case was executed. To accomplish this, we forked `kuttl` and modified it a little. You can see our modified version [here](https://github.com/kanishkarj/kuttl).
+
+
+We are planning to use `kuttl` for all the APIs in SMI. We are also planning to use the Meshery load generator with the modified version of `kuttl`.
+
+#### [Learn Layer5](https://github.com/layer5io/learn-layer5/)
+
+Learn Layer5 is a sample app which is very lightweight and simple to deploy. It is a simple sample app for learning about service meshes. We are planning to use the same app for testing for SMI conformance. The app is deployed when we test for SMI conformance and traffic is generated from one service/deployment/pod to another. This is a great tool for playing around with service meshes and the tools provided by Layer5 and its projects without investing any personal resources.
+
+This is where all the test cases along with the code will be placed. Currently, there is a large overlap in the learn-layer5 and `smi-conformance` testing files. All those changes will be transferred here.
+
+If any of this sounds remotely exciting, I implore you to give this a chance. You won’t regret it.
+Head over to our [Slack Channel](http://slack.layer5.io) and join the #smi channel where everything related to conformance testing is discussed. We would love to hear your feedback. Stay tuned for more blogs related to SMI Conformance and all things meshy!!!
+
+
+
diff --git a/src/collections/blog/2020/2020-07-03-my-meshy-journey/index.mdx b/src/collections/blog/2020/2020-07-03-my-meshy-journey/index.mdx
index 22608bd770af..f17b5078b9c2 100644
--- a/src/collections/blog/2020/2020-07-03-my-meshy-journey/index.mdx
+++ b/src/collections/blog/2020/2020-07-03-my-meshy-journey/index.mdx
@@ -1,51 +1,51 @@
----
-title: "My Meshy Journey"
-subtitle: ""
-date: 2020-07-03 12:15:05 +0000
-author: Ishita Kumar
-thumbnail: ./ishita-kumar.webp
-darkthumbnail: ./ishita-kumar.webp
-category: Internship Programs
-tags:
- - Community
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import IshitaProfile from "./ishita-kumar-profile.webp";
-
-
-
-
-
-As a graduate student at the Indiana University Bloomington, studying for my Masters in Computer Science, little did I consider that my thesis project would lead me on this amazing journey to becoming an open source contributor.
-
-My adventure with Layer5 has been a highly informative and invigorating experience, from coming aboard as a Meshery user to becoming an open source contributor. My initial interest in Layer5 was sparked when, for a project in my Masters course, I was required to build a microservice architecture and develop a service layer on top of it.
-A basic Google search led me to a plethora of resources, which in turn led me to understand how different service meshes could be compared. Comparison and selection of a service mesh was my first step to deploying one on my VM cluster. Amidst the varied resources available to me, stumbling onto Layer5 and Meshery was a happy boon.
-
-## Why Meshery?
-
-From the beginning, Meshery proved to be an intuitive and easy-to-use application. Among other benefits, it could be implemented into my project with ease which was also a major contributing factor behind my choice of taking advantage of its features for my project thesis.
-There are tons of resources online that compare different service meshes for your deployment however meshery was the only project that actually offered a practical way of comparing service meshes. In just a few easy steps, I could download and deploy Meshery into my VM instance and compare the performance of my microservice application running atop two different service meshes: Istio and Linkerd, thereby gathering various statistics on how they worked on my application.
-
-What really got my hooked though was Meshery's intuitive UI and the amazing open platform support, which made me strive to rise above and beyond my project goals, to truly understand and value the underlying idea.
-
-## Insights While Meshing Around
-
-While using Meshery to deploy both Istio and Linkerd, I came to the understanding that while Meshery uses common methods for interfacing with and managing service meshes, that Meshery is also capable of exposing service mesh-specific features. This became apparent by how robust Meshery’s adapter for Istio is, which includes the ability to analyze and validate my deployment’s configuration against best practices. Each adapter includes a set of sample applications that makes it convenient to explore the functionality of different meshes, using the same application across them.
-
-The behavior that was of keen interest to me, however, was that of my custom, microservices. When deploying my microservices application, Meshery helped me understand how different service meshes were interacting with my software application.
-
-I learned that in addition to the easy integration of Meshery in my application, it also provides one of the best platforms out there to manage service meshes and gives you a fair assessment of your deployment, which can otherwise prove to be a daunting task.
-
-While presenting my findings to my class and professor, they were able to gauge the brilliancy each service mesh would bring into the microservice application.
-
-## Shout out to the Community
-
-The Layer5 community has proved to be incredibly helpful in my journey. Communicating mainly through Slack channels, the community is vibrant and very welcoming. Any integration issues that arose for me were quickly and efficiently solved.
-I am thankful that my experiences as a user, as well as a contributor, has allowed me to be a valued part of this wholesome group. Layer5 has truly made me understand the significance of an open source "community" and I’ll admit - I’m hooked. The number and variety of novel projects that are pushing the envelope of emerging technology within this community is enthralling.
-I’m here for the long-haul, so expect to hear from me again as I wrap my arms around these projects. If the suite of Layer5 projects interests you, please [join the community](http://slack.layer5.io)!
-Then, drop me a line as I work toward becoming a [MeshMate](https://layer5.io/community/meshmates).
-
-
-
+---
+title: "My Meshy Journey"
+subtitle: ""
+date: 2020-07-03 12:15:05 +0000
+author: Ishita Kumar
+thumbnail: ./ishita-kumar.webp
+darkthumbnail: ./ishita-kumar.webp
+category: Internship Programs
+tags:
+ - Community
+published: true
+---
+
+
+import IshitaProfile from "./ishita-kumar-profile.webp";
+
+
+
+
+
+As a graduate student at the Indiana University Bloomington, studying for my Masters in Computer Science, little did I consider that my thesis project would lead me on this amazing journey to becoming an open source contributor.
+
+My adventure with Layer5 has been a highly informative and invigorating experience, from coming aboard as a Meshery user to becoming an open source contributor. My initial interest in Layer5 was sparked when, for a project in my Masters course, I was required to build a microservice architecture and develop a service layer on top of it.
+A basic Google search led me to a plethora of resources, which in turn led me to understand how different service meshes could be compared. Comparison and selection of a service mesh was my first step to deploying one on my VM cluster. Amidst the varied resources available to me, stumbling onto Layer5 and Meshery was a happy boon.
+
+## Why Meshery?
+
+From the beginning, Meshery proved to be an intuitive and easy-to-use application. Among other benefits, it could be implemented into my project with ease which was also a major contributing factor behind my choice of taking advantage of its features for my project thesis.
+There are tons of resources online that compare different service meshes for your deployment however meshery was the only project that actually offered a practical way of comparing service meshes. In just a few easy steps, I could download and deploy Meshery into my VM instance and compare the performance of my microservice application running atop two different service meshes: Istio and Linkerd, thereby gathering various statistics on how they worked on my application.
+
+What really got my hooked though was Meshery's intuitive UI and the amazing open platform support, which made me strive to rise above and beyond my project goals, to truly understand and value the underlying idea.
+
+## Insights While Meshing Around
+
+While using Meshery to deploy both Istio and Linkerd, I came to the understanding that while Meshery uses common methods for interfacing with and managing service meshes, that Meshery is also capable of exposing service mesh-specific features. This became apparent by how robust Meshery’s adapter for Istio is, which includes the ability to analyze and validate my deployment’s configuration against best practices. Each adapter includes a set of sample applications that makes it convenient to explore the functionality of different meshes, using the same application across them.
+
+The behavior that was of keen interest to me, however, was that of my custom, microservices. When deploying my microservices application, Meshery helped me understand how different service meshes were interacting with my software application.
+
+I learned that in addition to the easy integration of Meshery in my application, it also provides one of the best platforms out there to manage service meshes and gives you a fair assessment of your deployment, which can otherwise prove to be a daunting task.
+
+While presenting my findings to my class and professor, they were able to gauge the brilliancy each service mesh would bring into the microservice application.
+
+## Shout out to the Community
+
+The Layer5 community has proved to be incredibly helpful in my journey. Communicating mainly through Slack channels, the community is vibrant and very welcoming. Any integration issues that arose for me were quickly and efficiently solved.
+I am thankful that my experiences as a user, as well as a contributor, has allowed me to be a valued part of this wholesome group. Layer5 has truly made me understand the significance of an open source "community" and I’ll admit - I’m hooked. The number and variety of novel projects that are pushing the envelope of emerging technology within this community is enthralling.
+I’m here for the long-haul, so expect to hear from me again as I wrap my arms around these projects. If the suite of Layer5 projects interests you, please [join the community](http://slack.layer5.io)!
+Then, drop me a line as I work toward becoming a [MeshMate](https://layer5.io/community/meshmates).
+
+
+
diff --git a/src/collections/blog/2020/2020-07-16-communitybridge-2020-teaching-service-meshes-to-be-compliant/index.mdx b/src/collections/blog/2020/2020-07-16-communitybridge-2020-teaching-service-meshes-to-be-compliant/index.mdx
index d8f5f3aff8cb..9c492cdb9b99 100644
--- a/src/collections/blog/2020/2020-07-16-communitybridge-2020-teaching-service-meshes-to-be-compliant/index.mdx
+++ b/src/collections/blog/2020/2020-07-16-communitybridge-2020-teaching-service-meshes-to-be-compliant/index.mdx
@@ -1,72 +1,72 @@
----
-title: "CommunityBridge 2020: Teaching service meshes to be compliant"
-subtitle: ""
-date: 2020-07-16 10:30:05 -0530
-author: Kanishkar J
-thumbnail: ./communitybridge.webp
-darkthumbnail: ./communitybridge.webp
-category: Internship Programs
-tags:
- - Programs
- - "Service Mesh Interface"
- - "Internship"
-published: true
-redirect_from:
- - /blog/programs/community/communitybridge-2020-teaching-service-meshes-to-be-compliant
- - /blog/programs/communitybridge-2020-teaching-service-meshes-to-be-compliant
- - /blog/community-bridge-with-layer5/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import cblogo from "./cblogo.webp";
-import smiLogo from "./smi.webp";
-
-
-
-
-
-My journey into service meshes began on April 27, 2020 when I was selected to be a mentee under the banner of Community Bridge for the Summer of 2020. The Community Bridge Mentorship is a structured remote learning opportunity for aspiring open source software developers. The projects they host are mentored by experienced open source project developers and maintainers.
-
-
Stumbling into Service Mesh Interface (SMI)
-
-I began working on SMI Conformance testing under the guidance of Lee Calcote, Founder of Layer5, in February 2020. Since then, my path into the world of service meshes has brought me an avalanche of opportunities and has helped me grow by leaps and bounds as a developer.
-The Service Mesh Interface (SMI) is a standard interface that encapsulates various common service mesh functionalities. It explains several Custom Resource Definitions (CRDs), their configuration variables, and their corresponding effect on the service mesh underneath in full detail. What makes SMI vital is that these CRDs are generic, and the specifications are implemented and actively followed up by various service meshes. Some of these service meshes have developed adapters that define SMI CRDs as a wrapper over the APIs they already provide, instead of adhering to the SMI spec internally. SMI specifications address essential features for the most common service mesh use cases:
-
-
-
-- Traffic policy – To apply policies like identity and transport encryption across services
-- Traffic telemetry – To capture key metrics like error rate and latency between services
-- Traffic management – To shift traffic between different services
-
-However, at the moment, no service meshes adhere to the SMI specifications completely. Service meshes are rapidly developing and making active efforts to extend their feature set. Simultaneously, SMI has also been working towards adding more features to its specifications.
-
-Consequently, it becomes a necessity for continual validation of service mesh conformance with respect to SMI specifications and the various versions of those specifications. The process of verifying conformance needs to be standardized and tooling made available. Hence, our project efforts to create an SMI conformance tool.
-
-
Meshery to the Rescue
-
-Meshery is the multi-service mesh management plane, offering lifecycle, configuration, and performance management of service meshes and their workloads. It is closely connected to the Kubernetes cluster and allows easy deployment of various service meshes and sample applications onto those meshes. Meshery enables operators to run performance tests on workloads, collect, store, and manage the test results.
-
-
-We had found our solution. By leveraging the features provided in Meshery, we would be able to focus on the conformance validation and testing instead of sweating over the complexity in deployments. We can also use the performance management infrastructure to manage the conformance tests and their results. And so, the tool will be developed as an integral part of Meshery to aid and abate SMI conformance woes.
-We are now enhancing Meshery to automate the process of verifying conformance against a standard set of tests against a sample workload designed specifically for SMI conformance testing. By the time we’re through, this capability of Meshery will allow each service mesh project to validate its conformance to each version of the SMI specifications and will provide a detailed report.
-
-
My Projects
-
-The goals accomplished in my tenure at Layer5 are summarized as follows:
-
-1. **[Meshery Providers](https://docs.meshery.io/extensibility)** - Ported Meshery and its remote provider from using session based authentication to JWT based auth. This opened doors to:
- - Usage of refresh tokens for longevity of sessions instead of asking user to re-login frequently.
- - CLI based authentication (not done yet, but is on the roadmap)
-2. **[Image Hub](https://github.com/layer5io/image-hub)** - WASM based envoy network packet filters in Rust-lang. Built a demo app demonstrating its potentials; we also built a WASM filter which performs custom user specific rate limiting. This app was demo’ed in Dockercon 2020 under the header “Service Meshing with Docker Desktop and WebAssembly”.
-3. **[Implementing the Service Mesh Performance Specification](/projects/cloud-native-performance)** - Enhanced Meshery’s performance testing and profile management capabilities. Added support for customizing the requests made by the load generator, and added the capability of using performance test profiles in the tool.
-
-You can find my code in the [**Learn Layer5 repository**](https://github.com/layer5io/learn-layer5/).
-
-
Love for the Community
-
-I have been actively involved in the Layer5 community for a number of months now and am proud of the contributions I have made to various projects under the Layer5 banner. The Layer5 community represents an eclectic mix of geeky developers, out of the box thinkers, sassy writers and some of the most amazing people I have met so far in the open source community. We build projects to provide learning environments, deployment, and operational best practices, performance benchmarks, create documentation, and more. I am truly ecstatic to be a part of such an enthusiastic and welcoming community.
-
-As you’ve made it to the end of my post, why not stick around and take a look at the amazing projects I just described? You might just find your dream project and if not, I can promise that you will at least end up becoming a part of one of the best open source communities out there.
-To stay tuned with the progress of the project, please join us in the [Slack](http://slack.layer5.io) channel!
-
-
+---
+title: "CommunityBridge 2020: Teaching service meshes to be compliant"
+subtitle: ""
+date: 2020-07-16 10:30:05 -0530
+author: Kanishkar J
+thumbnail: ./communitybridge.webp
+darkthumbnail: ./communitybridge.webp
+category: Internship Programs
+tags:
+ - Programs
+ - "Service Mesh Interface"
+ - "Internship"
+published: true
+redirect_from:
+ - /blog/programs/community/communitybridge-2020-teaching-service-meshes-to-be-compliant
+ - /blog/programs/communitybridge-2020-teaching-service-meshes-to-be-compliant
+ - /blog/community-bridge-with-layer5/
+---
+
+
+import cblogo from "./cblogo.webp";
+import smiLogo from "./smi.webp";
+
+
+
+
+
+My journey into service meshes began on April 27, 2020 when I was selected to be a mentee under the banner of Community Bridge for the Summer of 2020. The Community Bridge Mentorship is a structured remote learning opportunity for aspiring open source software developers. The projects they host are mentored by experienced open source project developers and maintainers.
+
+
Stumbling into Service Mesh Interface (SMI)
+
+I began working on SMI Conformance testing under the guidance of Lee Calcote, Founder of Layer5, in February 2020. Since then, my path into the world of service meshes has brought me an avalanche of opportunities and has helped me grow by leaps and bounds as a developer.
+The Service Mesh Interface (SMI) is a standard interface that encapsulates various common service mesh functionalities. It explains several Custom Resource Definitions (CRDs), their configuration variables, and their corresponding effect on the service mesh underneath in full detail. What makes SMI vital is that these CRDs are generic, and the specifications are implemented and actively followed up by various service meshes. Some of these service meshes have developed adapters that define SMI CRDs as a wrapper over the APIs they already provide, instead of adhering to the SMI spec internally. SMI specifications address essential features for the most common service mesh use cases:
+
+
+
+- Traffic policy – To apply policies like identity and transport encryption across services
+- Traffic telemetry – To capture key metrics like error rate and latency between services
+- Traffic management – To shift traffic between different services
+
+However, at the moment, no service meshes adhere to the SMI specifications completely. Service meshes are rapidly developing and making active efforts to extend their feature set. Simultaneously, SMI has also been working towards adding more features to its specifications.
+
+Consequently, it becomes a necessity for continual validation of service mesh conformance with respect to SMI specifications and the various versions of those specifications. The process of verifying conformance needs to be standardized and tooling made available. Hence, our project efforts to create an SMI conformance tool.
+
+
Meshery to the Rescue
+
+Meshery is the multi-service mesh management plane, offering lifecycle, configuration, and performance management of service meshes and their workloads. It is closely connected to the Kubernetes cluster and allows easy deployment of various service meshes and sample applications onto those meshes. Meshery enables operators to run performance tests on workloads, collect, store, and manage the test results.
+
+
+We had found our solution. By leveraging the features provided in Meshery, we would be able to focus on the conformance validation and testing instead of sweating over the complexity in deployments. We can also use the performance management infrastructure to manage the conformance tests and their results. And so, the tool will be developed as an integral part of Meshery to aid and abate SMI conformance woes.
+We are now enhancing Meshery to automate the process of verifying conformance against a standard set of tests against a sample workload designed specifically for SMI conformance testing. By the time we’re through, this capability of Meshery will allow each service mesh project to validate its conformance to each version of the SMI specifications and will provide a detailed report.
+
+
My Projects
+
+The goals accomplished in my tenure at Layer5 are summarized as follows:
+
+1. **[Meshery Providers](https://docs.meshery.io/extensibility)** - Ported Meshery and its remote provider from using session based authentication to JWT based auth. This opened doors to:
+ - Usage of refresh tokens for longevity of sessions instead of asking user to re-login frequently.
+ - CLI based authentication (not done yet, but is on the roadmap)
+2. **[Image Hub](https://github.com/layer5io/image-hub)** - WASM based envoy network packet filters in Rust-lang. Built a demo app demonstrating its potentials; we also built a WASM filter which performs custom user specific rate limiting. This app was demo’ed in Dockercon 2020 under the header “Service Meshing with Docker Desktop and WebAssembly”.
+3. **[Implementing the Service Mesh Performance Specification](/projects/cloud-native-performance)** - Enhanced Meshery’s performance testing and profile management capabilities. Added support for customizing the requests made by the load generator, and added the capability of using performance test profiles in the tool.
+
+You can find my code in the [**Learn Layer5 repository**](https://github.com/layer5io/learn-layer5/).
+
+
Love for the Community
+
+I have been actively involved in the Layer5 community for a number of months now and am proud of the contributions I have made to various projects under the Layer5 banner. The Layer5 community represents an eclectic mix of geeky developers, out of the box thinkers, sassy writers and some of the most amazing people I have met so far in the open source community. We build projects to provide learning environments, deployment, and operational best practices, performance benchmarks, create documentation, and more. I am truly ecstatic to be a part of such an enthusiastic and welcoming community.
+
+As you’ve made it to the end of my post, why not stick around and take a look at the amazing projects I just described? You might just find your dream project and if not, I can promise that you will at least end up becoming a part of one of the best open source communities out there.
+To stay tuned with the progress of the project, please join us in the [Slack](http://slack.layer5.io) channel!
+
+
diff --git a/src/collections/blog/2020/2020-07-16-growing-as-an-open-source-contributor-with-layer5/index.mdx b/src/collections/blog/2020/2020-07-16-growing-as-an-open-source-contributor-with-layer5/index.mdx
index 2af2109366bf..c72f39832964 100644
--- a/src/collections/blog/2020/2020-07-16-growing-as-an-open-source-contributor-with-layer5/index.mdx
+++ b/src/collections/blog/2020/2020-07-16-growing-as-an-open-source-contributor-with-layer5/index.mdx
@@ -1,56 +1,56 @@
----
-title: "Growing as an open source contributor with Layer5"
-subtitle: ""
-date: 2020-07-16 10:30:06 -0530
-author: Ashis Kumar Singh
-thumbnail: ./the-enterprise-path-to-service-mesh-book-signed-by-lee-calcote.webp
-darkthumbnail: ./the-enterprise-path-to-service-mesh-book-signed-by-lee-calcote.webp
-category: Community
-tags:
- - Community
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import pic1 from "./pic1.webp";
-import pic2 from "./pic2.jpeg";
-import pic3 from "./pic3.webp";
-import pic4 from "./pic4.webp";
-import pic5 from "./pic5.webp";
-
-
-It all started 9 months ago when I stumbled across the following LinkedIn post, written by a college senior who had recently scored an internship with Redhat.
-
-
-
-This led me to a long-winding conversation with Subham Kumar Rai and Anand Kumar Singh about Layer5 and how amazing an opportunity it would be to be a part of this emerging community. I did some research on service meshes and made my way to the Layer5 Github repo. From there, it was a swift journey to the Layer5 Slack Channel where I truly understood what Subham had meant about the warm welcome. I was amazed by how helpful and willing the entire community was. Armed with the resources I needed, I delved into the projects and churned out a few PRs and I was hooked. I dove aggressively into the projects and handled any curve balls with the help of my mentors. My participation in the Layer5 community drove me to a well earned obsession with open source projects which led me to make my own contributions in the FOSSASIA and GATSBY projects and take part in many open-source contests such as Hacktoberfest, DevopsCember, Kharagpur Winter Of Code (KWOC), NJACK Winter Of Code (NWOC), Girlscript Summer Of Code (GSSOC).
-
-
-
-#### What is Meshery?
-
-Meshery is a multi-service mesh management plane that offers lifecycle, configuration, and performance management of service meshes and applications running on top of those meshes.
-
-
-
-Meshery uses a common service mesh performance specification to describe and capture performance benchmarks and results. The spec contains general information about the performance test (e.g. start/end times), service mesh and proxy build numbers, Kubernetes cluster details (nodes, type of nodes, memory information), and the actual results. One of the ideas behind Meshery is to be a vendor and project-neutral tool that can benchmark the performance of different service meshes.
-It is a one stop for all your service meshing needs. Service meshes are still a novel concept for both, developers and users. Meshery steps in to bridge this gap and allows you to have a better understanding of what a service mesh can provide by helping you judge service mesh for your personal and professional needs. Meshery accomplishes this by providing you a thorough analysis of the options available so that you can make an informed choice.
-
-
-
-#### Lee Calcote
-
-Lee Calcote is an innovative leader and has previously made waves in the tech community as a Docker Captain and a Cloud Native Ambassador and that is just a milestone in his impressive journey, which consists of his admirable work with developer platforms, cloud technology, containers, functions, and applications. Advanced and emerging technologies have been a consistent focus through Calcote’s tenure at SolarWinds, Seagate, Cisco, and Pelco. In my tenure at Layer5, Lee has been an amazing mentor, someone you can always look towards for encouragement, inspiration and a kind word, especially when you’re melting under the heat to make that late night deadline.
-
-
-#### Layer5 and UEM Jaipur Partnership Program
-In an effort to foster the open source community in my college, I along with four of my batchmates (Anand, Subham, Nikhil, Gunjan) decided to start an open source partnership program, encouraged by Lee and Rupayan Das (Faculty, UEM Jaipur). This will hopefully lead to making future batches more aware about the essence of open source and encourage them to participate in communities like Layer5.
-
-
-
-#### Community Love
-
-The Layer5 community has welcomed me with patience and has given me a sense of purpose, which is more than I could have asked for at the beginning as a novice developer. The warm welcome and a sincere string of mentors can do wonders in building your confidence and enabling you to put in your best foot forward. Open source has introduced me to a horde of essential qualities, such as the importance of teamwork, candor and earnestness.
-It has been a prodigious journey so far and I don’t intend to stop here. The pace at which the projects under the Layer5 community are unwinding is awe-inspiring. It is my aim to be a witness and a partner in crime in its future endeavors. If you’re looking for an opportunity to be a part of the Layer5 family, check out our projects and head over to our [Slack](http://slack.layer5.io) channel!
-
-
+---
+title: "Growing as an open source contributor with Layer5"
+subtitle: ""
+date: 2020-07-16 10:30:06 -0530
+author: Ashis Kumar Singh
+thumbnail: ./the-enterprise-path-to-service-mesh-book-signed-by-lee-calcote.webp
+darkthumbnail: ./the-enterprise-path-to-service-mesh-book-signed-by-lee-calcote.webp
+category: Community
+tags:
+ - Community
+published: true
+---
+
+
+import pic1 from "./pic1.webp";
+import pic2 from "./pic2.jpeg";
+import pic3 from "./pic3.webp";
+import pic4 from "./pic4.webp";
+import pic5 from "./pic5.webp";
+
+
+It all started 9 months ago when I stumbled across the following LinkedIn post, written by a college senior who had recently scored an internship with Redhat.
+
+
+
+This led me to a long-winding conversation with Subham Kumar Rai and Anand Kumar Singh about Layer5 and how amazing an opportunity it would be to be a part of this emerging community. I did some research on service meshes and made my way to the Layer5 Github repo. From there, it was a swift journey to the Layer5 Slack Channel where I truly understood what Subham had meant about the warm welcome. I was amazed by how helpful and willing the entire community was. Armed with the resources I needed, I delved into the projects and churned out a few PRs and I was hooked. I dove aggressively into the projects and handled any curve balls with the help of my mentors. My participation in the Layer5 community drove me to a well earned obsession with open source projects which led me to make my own contributions in the FOSSASIA and GATSBY projects and take part in many open-source contests such as Hacktoberfest, DevopsCember, Kharagpur Winter Of Code (KWOC), NJACK Winter Of Code (NWOC), Girlscript Summer Of Code (GSSOC).
+
+
+
+#### What is Meshery?
+
+Meshery is a multi-service mesh management plane that offers lifecycle, configuration, and performance management of service meshes and applications running on top of those meshes.
+
+
+
+Meshery uses a common service mesh performance specification to describe and capture performance benchmarks and results. The spec contains general information about the performance test (e.g. start/end times), service mesh and proxy build numbers, Kubernetes cluster details (nodes, type of nodes, memory information), and the actual results. One of the ideas behind Meshery is to be a vendor and project-neutral tool that can benchmark the performance of different service meshes.
+It is a one stop for all your service meshing needs. Service meshes are still a novel concept for both, developers and users. Meshery steps in to bridge this gap and allows you to have a better understanding of what a service mesh can provide by helping you judge service mesh for your personal and professional needs. Meshery accomplishes this by providing you a thorough analysis of the options available so that you can make an informed choice.
+
+
+
+#### Lee Calcote
+
+Lee Calcote is an innovative leader and has previously made waves in the tech community as a Docker Captain and a Cloud Native Ambassador and that is just a milestone in his impressive journey, which consists of his admirable work with developer platforms, cloud technology, containers, functions, and applications. Advanced and emerging technologies have been a consistent focus through Calcote’s tenure at SolarWinds, Seagate, Cisco, and Pelco. In my tenure at Layer5, Lee has been an amazing mentor, someone you can always look towards for encouragement, inspiration and a kind word, especially when you’re melting under the heat to make that late night deadline.
+
+
+#### Layer5 and UEM Jaipur Partnership Program
+In an effort to foster the open source community in my college, I along with four of my batchmates (Anand, Subham, Nikhil, Gunjan) decided to start an open source partnership program, encouraged by Lee and Rupayan Das (Faculty, UEM Jaipur). This will hopefully lead to making future batches more aware about the essence of open source and encourage them to participate in communities like Layer5.
+
+
+
+#### Community Love
+
+The Layer5 community has welcomed me with patience and has given me a sense of purpose, which is more than I could have asked for at the beginning as a novice developer. The warm welcome and a sincere string of mentors can do wonders in building your confidence and enabling you to put in your best foot forward. Open source has introduced me to a horde of essential qualities, such as the importance of teamwork, candor and earnestness.
+It has been a prodigious journey so far and I don’t intend to stop here. The pace at which the projects under the Layer5 community are unwinding is awe-inspiring. It is my aim to be a witness and a partner in crime in its future endeavors. If you’re looking for an opportunity to be a part of the Layer5 family, check out our projects and head over to our [Slack](http://slack.layer5.io) channel!
+
+
diff --git a/src/collections/blog/2020/2020-07-18-service-mesh-patterns-for-multitenancy/index.mdx b/src/collections/blog/2020/2020-07-18-service-mesh-patterns-for-multitenancy/index.mdx
index 3ef71b10d20e..44be0ad8a4a2 100644
--- a/src/collections/blog/2020/2020-07-18-service-mesh-patterns-for-multitenancy/index.mdx
+++ b/src/collections/blog/2020/2020-07-18-service-mesh-patterns-for-multitenancy/index.mdx
@@ -1,280 +1,278 @@
----
-title: "Service Mesh (Istio) patterns for Multitenancy"
-subtitle: ""
-date: 2020-07-18 10:30:05 -0530
-author: Sudeep Batra
-thumbnail: ./image2.webp
-darkthumbnail: ./image2.webp
-category: Service Mesh
-tags:
- - Service Mesh
- - Open Source
- - Istio
-published: true
-type: Blog
-technology: Kubernetes
-mesh: Istio
-resource: true
-redirect_from:
- - /blog/service-mesh-patterns-for-multitenancy/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import listioLayer5 from "./layer5-and-istio.webp";
-import img1 from "./image1.webp";
-import img2 from "./image2.webp";
-import img3 from "./image3.webp";
-import img4 from "./image4.webp";
-
-
-
-
-
-Recently, I started learning on Service Mesh and it was a very interesting journey as I explored the Service Mesh
-landscape starting with [Layer5 tutorials](https://github.com/layer5io/istio-service-mesh-workshop) and by exploring
-the blogs at [Istio.io](https://istio.io/).
-
-Our organization decided to use the features of Istio for securing, managing and automating microservices. However, we have to support a multi-tenant environment and that became a challenge due to lack of sufficient documentation and clarity. To give a little bit of background on the problem, we have a single cluster with multiple tenants in different namespaces sharing the same cluster . We do not want to provide each tenant their own separate Kubernetes Cluster because that would be additional provisioning overhead, management overhead and also additional resource overhead on the platform.
-
-In this blog, I will go over the concepts and visual representation as well as the steps to learn and build your setup.
-Now there are different combinations possible depending on the requirements. These could be :
-
-1. Single Istio Control Plane with its own Ingress-Gateway to ensure traffic for the control plane is coming via the same control plane Ingress-Gateway.
-1. One or more Workspace namespaces for the workload applications and each with its own instance of the ingress gateway
-1. More advanced scenario would be multiple Control Plane and its associated Data Plane or essentially Multiple Service Mesh within a single Kubernetes Cluster. This is presently feasible using the Maistra Istio Operator, but its not fully supported using the upstream Istio at present. I intend to go over this use case in a later article.
-
-Here by Ingress Gateway we mean the Istio Ingress Gateway and not the Kubernetes Ingress Gateway.
-Now, before we get into the steps for building an Istio Multi-tenant setup, lets quickly review the prerequisite :
-
-- Kubernetes setup (in the steps below I am using v1.18 on ubuntu 18.04)
-
- ```sh
- $ sudo apt-get install -y docker.io
- $ sudo sh -c “echo ‘deb http://apt.kubernetes.io/ kubernetes-xenial main’ >> /etc/apt/sources.list.d/kubernetes.list”
- $ sudo sh -c “curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -”
- $ sudo apt-get update
- $ sudo apt-get install -y kubeadm=1.18.1–00 kubelet=1.18.1–00 kubectl=1.18.1–00
- $ sudo kubeadm init — kubernetes-version 1.18.1 — pod-network-cidr 192.168.0.0/16
- $ mkdir -p $HOME/.kube
- $ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
- $ sudo chown $(id -u):$(id -g) $HOME/.kube/config
- $ kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
- ```
-
-- Get the latest istioctl binary
-
- ```sh
- $ curl -L https://git.io/getLatestIstio | sh -
- cd istio-*
- export PATH=$PWD/bin:$PATH
- istioctl version
- ```
-
-- Initialize the Istio Operator
- ```sh
- $ istioctl operator init
- Using operator Deployment image: docker.io/istio/operator:1.6.3
- ✔ Istio operator installed
- ✔ Installation complete
- $ kubectl get all -n istio-operator
- NAME READY STATUS RESTARTS AGE
- pod/istio-operator-5998f6c744-vrkbk 1/1 Running 1 78m
- NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
- service/istio-operator ClusterIP 10.107.183.94 8383/TCP 78m
- NAME READY UP-TO-DATE AVAILABLE AGE
- deployment.apps/istio-operator 1/1 1 1 78m
- NAME DESIRED CURRENT READY AGE
- replicaset.apps/istio-operator-5998f6c744 1 1 1 78m
- ```
-
-Next we will look into the details of the multitenancy scenarios; but before that a few word on the Istio operator would be nice. The Istio Operator follows the Kubernetes Controller and Custom Resource Definition mechanism and basically the above steps create an Istio operator controller in the istio-operator namespace and also registers the CRDs in the Kubernetes Registry. Basically, it extends the API for Kubernetes and allows management of a Custom Resource(CR). A word of caution, the existing upstream Istio Operator does not follow any Operator Framework like kubebuilder or Operator SDK. Hence, many of the expected behavior fail like trying to create two Istio Operator Custom Resource(the community mentions it as `iop` instances) in different namespaces or multiple `iop` instances and are under heavy development.
-
-Ok, so now lets jump into action. We will build our Istio Setup for the scenario 1 &2 above shown in the diagram below. There are three different instances of Ingress Gateway(and it could be egress gateway as well) :
-
-a. Ingress Gateway in Control Plane for traffic entry point to the Control plane Observability Components like `Kiali`(for the Service Mesh Graph), `Prometheus`(for metrics),Grafana(for visual charts of the metrics)and `Jaeger` (for distributed tracing between the services)
-b. Ingress Gateway in the Worskpace 1 namespace for traffic entry point to the workspace 1 microservices.
-c. Ingress Gateway in the Worskpace 2 namespace for traffic entry point to the workspace 2 microservices.
-
-
-
- Single Control Plane with Multiple Data Plane each with separate Ingress
- Gateway
-
-
-- Creation of Control Plane CR and Data Plane CR
- A sample CR for creation of the Control plane and Data Plane CR can be referred below :
- ```sh
- $ cat iop-platform.yaml
- apiVersion: install.istio.io/v1alpha1
- kind: IstioOperator
- metadata:
- namespace: istio-system
- name: platform-istiocontrolplane
- spec:
- profile: demo
- $ cat iop-wk1-gw.yaml
- apiVersion: install.istio.io/v1alpha1
- kind: IstioOperator
- metadata:
- namespace: istio-system
- name: wk1-gwconfig
- spec:
- profile: empty
- components:
- ingressGateways:
- — name: wk1-ingressgw
- namespace: workspace-1
- enabled: true
- label:
- istio: ingressgateway-1
- app: istio-ingressgateway-1
- values:
- gateways:
- istio-ingressgateway:
- debug: error
- $ cat iop-wk2-gw.yaml
- apiVersion: install.istio.io/v1alpha1
- kind: IstioOperator
- metadata:
- namespace: istio-system
- name: wk2-gwconfig
- spec:
- profile: empty
- components:
- ingressGateways:
- — name: wk2-ingressgw
- namespace: workspace-2
- enabled: true
- label:
- istio: ingressgateway-2
- app: istio-ingressgateway-2
- values:
- gateways:
- istio-ingressgateway:
- debug: error
- ```
-
-It is important to make sure the indentation is correct ,otherwise it would lead to errors.
-Reference: [Istio Website](https://istio.io/latest/docs/setup/install/)
-
-Deploy the CRs using kubectl:
-
-```sh
-$ kubectl create ns istio-system
-$ kubectl create ns workspace-1
-$ kubectl create ns workspace-2
-$ kubectl apply -f ../iop-platform.yaml
-istiooperator.install.istio.io/platform-istiocontrolplane created
-$ kubectl apply -f ../iop-wk1-gw.yaml
-istiooperator.install.istio.io/wk1-gwconfig configured
-$ kubectl apply -f ../iop-wk2-gw.yaml
-istiooperator.install.istio.io/wk2-gwconfig configured
-```
-
-- Troubleshooting the Istio Operator Controller.
- Its a good idea to run another window and execute the below command to observe the running logs on the controller pod.
- ```sh
- $ kubectl logs -f -n istio-operator
- $(kubectl get pods -n istio-operator -lname=istio-operator -o jsonpath=’{.items[0].metadata.name}’)
- ```
-
-
-
-- Observe the created objects in istio-system and the workspace namespaces for all pods to be in running state.
-
- ```sh
- $ kubectl get all -n istio-system
- NAME READY STATUS RESTARTS AGE
- pod/grafana-b54bb57b9-k84xf 1/1 Running 0 79s
- pod/istio-egressgateway-77c7d594c5-fr79j 1/1 Running 0 83s
- pod/istio-ingressgateway-766c84dfdc-p6g6t 1/1 Running 0 83s
- pod/istio-tracing-9dd6c4f7c-ndjvn 1/1 Running 0 79s
- pod/istiod-7b69ff6f8c-9gwp8 1/1 Running 0 94s
- pod/kiali-d45468dc4–4sww2 1/1 Running 0 79s
- pod/prometheus-5fdfc44fb7–67khx 2/2 Running 0 78s
-
- esudbat@istio:~/istio$ kubectl get all -n workspace-1
- NAME READY STATUS RESTARTS AGE
- pod/wk1-ingressgw-5674488c8b-fg2w5 1/1 Running 0 21s
-
- esudbat@istio:~/istio$ kubectl get all -n workspace-2
- ```
-
-- Now we will label the namespaces for istio-injection
-
- ```sh
- $kubectl label namespace workspace-1 istio-injection=enabled
- $kubectl label namespace workspace-2 istio-injection=enabled
- ```
-
-- Now we will deploy the bookinfo sample application in both namespaces but before that we need to make sure that the Gateway resource is updated with the correct label selector as below :
-
- ```sh
- $ cat istio/bookinfo-gateway-1.yaml
- apiVersion: networking.istio.io/v1alpha3
- kind: Gateway
- metadata:
- name: bookinfo-gateway
- spec:
- selector:
- istio: ingressgateway-1 # use istio gateway-1 controller in workspace-1
- servers:
- — port:
- number: 80
- name: http
- protocol: HTTP
- hosts:
- — “*”
- $ cat istio/bookinfo-gateway-2.yaml
- apiVersion: networking.istio.io/v1alpha3
- kind: Gateway
- metadata:
- name: bookinfo-gateway
- spec:
- selector:
- istio: ingressgateway-2 # use istio gateway-2 controller in workspace-1
- servers:
- — port:
- number: 80
- name: http
- protocol: HTTP
- hosts:
- — “*”
- ```
-
-Deploy the applications in workspace-1 and workspace-2 and deploy the Gateway,VirtualService and DestinationRules.
-
-```sh
-$kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml -n workspace-1
-$kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml -n workspace-2
-$kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml -n workspace-1
-$kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml -n workspace-2
-$kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml -n workspace-1
-$kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml -n workspace-2
-```
-
-Essentially what is happening is the Gateway CR is configuring the traffic to come via the ingress-gateway, it specifies the label selector based on which the ingress-gateway is selected and the host from where the traffic is allowed and port on which the traffic is allowed. It is important to ensure the label maps the label on the ingress-gateway.
-Once this is done the traffic will start flowing the intended gateway and it could be observed on the Kiali dashboard.
-Please note that in this scenario the Kiali is also accessed via the default control plane ingress-gateway running in the istio-system control plane namespace.
-
-
-
Kiali view for Workspace-1
-
-
-
Kiali view for Workspace-2
-
-Shortly, we will go over the 3rd scenario which is to run multiple Istio Control Planes (Multiple Service Meshes) within the same Kubernetes Cluster. For that, we will need to build an open-shift setup and deploy the Maistra Istio Operator.
-Special thanks to the [Istio Community](https://istio.slack.com/) for helping me understand the concepts and also answering my queries and of course to [Lee Calcote](https://calcotestudios.com/talks/), who helped me embark on my Istio journey.
-
-
-
-
+---
+title: "Service Mesh (Istio) patterns for Multitenancy"
+subtitle: ""
+date: 2020-07-18 10:30:05 -0530
+author: Sudeep Batra
+thumbnail: ./image2.webp
+darkthumbnail: ./image2.webp
+category: Service Mesh
+tags:
+ - Service Mesh
+ - Open Source
+ - Istio
+published: true
+type: Blog
+technology: Kubernetes
+mesh: Istio
+resource: true
+redirect_from:
+ - /blog/service-mesh-patterns-for-multitenancy/
+---
+
+
+import listioLayer5 from "./layer5-and-istio.webp";
+import img1 from "./image1.webp";
+import img2 from "./image2.webp";
+import img3 from "./image3.webp";
+import img4 from "./image4.webp";
+
+
+
+
+
+Recently, I started learning on Service Mesh and it was a very interesting journey as I explored the Service Mesh
+landscape starting with [Layer5 tutorials](https://github.com/layer5io/istio-service-mesh-workshop) and by exploring
+the blogs at [Istio.io](https://istio.io/).
+
+Our organization decided to use the features of Istio for securing, managing and automating microservices. However, we have to support a multi-tenant environment and that became a challenge due to lack of sufficient documentation and clarity. To give a little bit of background on the problem, we have a single cluster with multiple tenants in different namespaces sharing the same cluster . We do not want to provide each tenant their own separate Kubernetes Cluster because that would be additional provisioning overhead, management overhead and also additional resource overhead on the platform.
+
+In this blog, I will go over the concepts and visual representation as well as the steps to learn and build your setup.
+Now there are different combinations possible depending on the requirements. These could be :
+
+1. Single Istio Control Plane with its own Ingress-Gateway to ensure traffic for the control plane is coming via the same control plane Ingress-Gateway.
+1. One or more Workspace namespaces for the workload applications and each with its own instance of the ingress gateway
+1. More advanced scenario would be multiple Control Plane and its associated Data Plane or essentially Multiple Service Mesh within a single Kubernetes Cluster. This is presently feasible using the Maistra Istio Operator, but its not fully supported using the upstream Istio at present. I intend to go over this use case in a later article.
+
+Here by Ingress Gateway we mean the Istio Ingress Gateway and not the Kubernetes Ingress Gateway.
+Now, before we get into the steps for building an Istio Multi-tenant setup, lets quickly review the prerequisite :
+
+- Kubernetes setup (in the steps below I am using v1.18 on ubuntu 18.04)
+
+ ```sh
+ $ sudo apt-get install -y docker.io
+ $ sudo sh -c “echo ‘deb http://apt.kubernetes.io/ kubernetes-xenial main’ >> /etc/apt/sources.list.d/kubernetes.list”
+ $ sudo sh -c “curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -”
+ $ sudo apt-get update
+ $ sudo apt-get install -y kubeadm=1.18.1–00 kubelet=1.18.1–00 kubectl=1.18.1–00
+ $ sudo kubeadm init — kubernetes-version 1.18.1 — pod-network-cidr 192.168.0.0/16
+ $ mkdir -p $HOME/.kube
+ $ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
+ $ sudo chown $(id -u):$(id -g) $HOME/.kube/config
+ $ kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
+ ```
+
+- Get the latest istioctl binary
+
+ ```sh
+ $ curl -L https://git.io/getLatestIstio | sh -
+ cd istio-*
+ export PATH=$PWD/bin:$PATH
+ istioctl version
+ ```
+
+- Initialize the Istio Operator
+ ```sh
+ $ istioctl operator init
+ Using operator Deployment image: docker.io/istio/operator:1.6.3
+ ✔ Istio operator installed
+ ✔ Installation complete
+ $ kubectl get all -n istio-operator
+ NAME READY STATUS RESTARTS AGE
+ pod/istio-operator-5998f6c744-vrkbk 1/1 Running 1 78m
+ NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+ service/istio-operator ClusterIP 10.107.183.94 8383/TCP 78m
+ NAME READY UP-TO-DATE AVAILABLE AGE
+ deployment.apps/istio-operator 1/1 1 1 78m
+ NAME DESIRED CURRENT READY AGE
+ replicaset.apps/istio-operator-5998f6c744 1 1 1 78m
+ ```
+
+Next we will look into the details of the multitenancy scenarios; but before that a few word on the Istio operator would be nice. The Istio Operator follows the Kubernetes Controller and Custom Resource Definition mechanism and basically the above steps create an Istio operator controller in the istio-operator namespace and also registers the CRDs in the Kubernetes Registry. Basically, it extends the API for Kubernetes and allows management of a Custom Resource(CR). A word of caution, the existing upstream Istio Operator does not follow any Operator Framework like kubebuilder or Operator SDK. Hence, many of the expected behavior fail like trying to create two Istio Operator Custom Resource(the community mentions it as `iop` instances) in different namespaces or multiple `iop` instances and are under heavy development.
+
+Ok, so now lets jump into action. We will build our Istio Setup for the scenario 1 &2 above shown in the diagram below. There are three different instances of Ingress Gateway(and it could be egress gateway as well) :
+
+a. Ingress Gateway in Control Plane for traffic entry point to the Control plane Observability Components like `Kiali`(for the Service Mesh Graph), `Prometheus`(for metrics),Grafana(for visual charts of the metrics)and `Jaeger` (for distributed tracing between the services)
+b. Ingress Gateway in the Worskpace 1 namespace for traffic entry point to the workspace 1 microservices.
+c. Ingress Gateway in the Worskpace 2 namespace for traffic entry point to the workspace 2 microservices.
+
+
+
+ Single Control Plane with Multiple Data Plane each with separate Ingress
+ Gateway
+
+
+- Creation of Control Plane CR and Data Plane CR
+ A sample CR for creation of the Control plane and Data Plane CR can be referred below :
+ ```sh
+ $ cat iop-platform.yaml
+ apiVersion: install.istio.io/v1alpha1
+ kind: IstioOperator
+ metadata:
+ namespace: istio-system
+ name: platform-istiocontrolplane
+ spec:
+ profile: demo
+ $ cat iop-wk1-gw.yaml
+ apiVersion: install.istio.io/v1alpha1
+ kind: IstioOperator
+ metadata:
+ namespace: istio-system
+ name: wk1-gwconfig
+ spec:
+ profile: empty
+ components:
+ ingressGateways:
+ — name: wk1-ingressgw
+ namespace: workspace-1
+ enabled: true
+ label:
+ istio: ingressgateway-1
+ app: istio-ingressgateway-1
+ values:
+ gateways:
+ istio-ingressgateway:
+ debug: error
+ $ cat iop-wk2-gw.yaml
+ apiVersion: install.istio.io/v1alpha1
+ kind: IstioOperator
+ metadata:
+ namespace: istio-system
+ name: wk2-gwconfig
+ spec:
+ profile: empty
+ components:
+ ingressGateways:
+ — name: wk2-ingressgw
+ namespace: workspace-2
+ enabled: true
+ label:
+ istio: ingressgateway-2
+ app: istio-ingressgateway-2
+ values:
+ gateways:
+ istio-ingressgateway:
+ debug: error
+ ```
+
+It is important to make sure the indentation is correct ,otherwise it would lead to errors.
+Reference: [Istio Website](https://istio.io/latest/docs/setup/install/)
+
+Deploy the CRs using kubectl:
+
+```sh
+$ kubectl create ns istio-system
+$ kubectl create ns workspace-1
+$ kubectl create ns workspace-2
+$ kubectl apply -f ../iop-platform.yaml
+istiooperator.install.istio.io/platform-istiocontrolplane created
+$ kubectl apply -f ../iop-wk1-gw.yaml
+istiooperator.install.istio.io/wk1-gwconfig configured
+$ kubectl apply -f ../iop-wk2-gw.yaml
+istiooperator.install.istio.io/wk2-gwconfig configured
+```
+
+- Troubleshooting the Istio Operator Controller.
+ Its a good idea to run another window and execute the below command to observe the running logs on the controller pod.
+ ```sh
+ $ kubectl logs -f -n istio-operator
+ $(kubectl get pods -n istio-operator -lname=istio-operator -o jsonpath=’{.items[0].metadata.name}’)
+ ```
+
+
+
+- Observe the created objects in istio-system and the workspace namespaces for all pods to be in running state.
+
+ ```sh
+ $ kubectl get all -n istio-system
+ NAME READY STATUS RESTARTS AGE
+ pod/grafana-b54bb57b9-k84xf 1/1 Running 0 79s
+ pod/istio-egressgateway-77c7d594c5-fr79j 1/1 Running 0 83s
+ pod/istio-ingressgateway-766c84dfdc-p6g6t 1/1 Running 0 83s
+ pod/istio-tracing-9dd6c4f7c-ndjvn 1/1 Running 0 79s
+ pod/istiod-7b69ff6f8c-9gwp8 1/1 Running 0 94s
+ pod/kiali-d45468dc4–4sww2 1/1 Running 0 79s
+ pod/prometheus-5fdfc44fb7–67khx 2/2 Running 0 78s
+
+ esudbat@istio:~/istio$ kubectl get all -n workspace-1
+ NAME READY STATUS RESTARTS AGE
+ pod/wk1-ingressgw-5674488c8b-fg2w5 1/1 Running 0 21s
+
+ esudbat@istio:~/istio$ kubectl get all -n workspace-2
+ ```
+
+- Now we will label the namespaces for istio-injection
+
+ ```sh
+ $kubectl label namespace workspace-1 istio-injection=enabled
+ $kubectl label namespace workspace-2 istio-injection=enabled
+ ```
+
+- Now we will deploy the bookinfo sample application in both namespaces but before that we need to make sure that the Gateway resource is updated with the correct label selector as below :
+
+ ```sh
+ $ cat istio/bookinfo-gateway-1.yaml
+ apiVersion: networking.istio.io/v1alpha3
+ kind: Gateway
+ metadata:
+ name: bookinfo-gateway
+ spec:
+ selector:
+ istio: ingressgateway-1 # use istio gateway-1 controller in workspace-1
+ servers:
+ — port:
+ number: 80
+ name: http
+ protocol: HTTP
+ hosts:
+ — “*”
+ $ cat istio/bookinfo-gateway-2.yaml
+ apiVersion: networking.istio.io/v1alpha3
+ kind: Gateway
+ metadata:
+ name: bookinfo-gateway
+ spec:
+ selector:
+ istio: ingressgateway-2 # use istio gateway-2 controller in workspace-1
+ servers:
+ — port:
+ number: 80
+ name: http
+ protocol: HTTP
+ hosts:
+ — “*”
+ ```
+
+Deploy the applications in workspace-1 and workspace-2 and deploy the Gateway,VirtualService and DestinationRules.
+
+```sh
+$kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml -n workspace-1
+$kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml -n workspace-2
+$kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml -n workspace-1
+$kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml -n workspace-2
+$kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml -n workspace-1
+$kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml -n workspace-2
+```
+
+Essentially what is happening is the Gateway CR is configuring the traffic to come via the ingress-gateway, it specifies the label selector based on which the ingress-gateway is selected and the host from where the traffic is allowed and port on which the traffic is allowed. It is important to ensure the label maps the label on the ingress-gateway.
+Once this is done the traffic will start flowing the intended gateway and it could be observed on the Kiali dashboard.
+Please note that in this scenario the Kiali is also accessed via the default control plane ingress-gateway running in the istio-system control plane namespace.
+
+
+
Kiali view for Workspace-1
+
+
+
Kiali view for Workspace-2
+
+Shortly, we will go over the 3rd scenario which is to run multiple Istio Control Planes (Multiple Service Meshes) within the same Kubernetes Cluster. For that, we will need to build an open-shift setup and deploy the Maistra Istio Operator.
+Special thanks to the [Istio Community](https://istio.slack.com/) for helping me understand the concepts and also answering my queries and of course to [Lee Calcote](https://calcotestudios.com/talks/), who helped me embark on my Istio journey.
+
+
+
+
diff --git a/src/collections/blog/2020/2020-08-04-how-i-schooled-my-seniors/index.mdx b/src/collections/blog/2020/2020-08-04-how-i-schooled-my-seniors/index.mdx
index df53555bb452..c9209716bb0d 100644
--- a/src/collections/blog/2020/2020-08-04-how-i-schooled-my-seniors/index.mdx
+++ b/src/collections/blog/2020/2020-08-04-how-i-schooled-my-seniors/index.mdx
@@ -1,36 +1,36 @@
----
-title: "How I schooled my seniors"
-subtitle: "and why I swear by the experience"
-date: 2020-08-04 10:15:05 +0000
-author: Nupur Thakur
-thumbnail: ./feature-image.svg
-darkthumbnail: ./feature-image.svg
-category: Community
-tags:
- - Community
- - MeshMate
-published: true
-redirect_from:
- - /blog/how-i-schooled-my-seniors/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-I started a new job at [RemoteState](https://www.linkedin.com/company/remotestate/) as a software development engineer in May of 2020.
-Post the initial plunge, settling into the role was relatively easier for me due to the experience I had gained in working on open source contributions in the Layer5 community. My experience with open source had also been a big plus for me throughout the application and interview process. As a direct result, my colleagues and seniors became genuinely inquisitive about Meshery and its functionality as the Kubernetes Manager. So when asked, I happily agreed to deliver a session on the subject to the entire team.
-
-I pitched my idea to [Lee Calcote](https://layer5.io/community/members/lee-calcote) and in his usual supportive form, he was as excited as I was about the session. A brainstorm session led to creating an entire presentation with suggestions from Lee. The Layer5 community offers a number of resources to contributors, including these two decks ([Meshery - the cloud native management plane](https://layer5.io/meshery) and [Layer5](https://docs.google.com/presentation/d/1tLcMcyQ-Z6YYISYyR0Eyb30dojQiKHIjs7Rt5m8kcag/edit?usp=sharing) that I drew from as a basis for a personalized presentation and demonstration to my new team.
-
-
-
-
-When the day arrived to present the concepts of service meshes, Meshery, and other cloud native initiatives to my team, I held a Google Meet with a full attendance. I started the session with a reader’s digest version of microservices and service meshes to set the stage for any newcomers to the world of cloud native, I went on to elaborate on Layer5 ‘s contributions to the CNCF landscape and the SMI project. This was followed by an in-depth discussion on data planes, control planes, and management planes. I spoke at-length about Meshery’s functionality including, its features for facilitating the benchmarking, interoperability and standardization of service meshes. I wrapped up the session with some insider tips that I have learned in my months as an open source contributor in the Layer5 community. In the stream of feedback received from my colleagues, the session seems to have been a success.
-
-This whole experience has been an amazing journey for me. From being a complete noob to utilizing my expertise in the service mesh domain to landing an actual job, the experience has been a maze of ups and downs. But, I feel like I have finally arrived and arrived with a pot of gold. I’m eternally grateful to Lee Calcote for motivating me and providing me with the appropriate resources. Entering and exploring an open source community can be a daunting task and the [resources provided by Layer5](https://layer5.io/community/newcomers) helped them in overcoming that challenge and enabled them to learn more about the widespread work of [Meshery](https://meshery.io).
-
-I’m glad to have found a community that not only feeds my professional success, but also my personal growth. It’s not out of obligation, but out of a sense of gratitude and paying it forward to others (a tenant of the Layer5 community) that I now spend much of my time as a MeshMate. I help welcome and guide other new contributors along their open source path as they learn and grow. Giving to others and while continuing to grow professionally and personally is time well spent. I encourage you to join me and others in the Layer5 community by jumping into our [Slack](https://slack.layer5.io/) to start meshing around!
-
-
-
+---
+title: "How I schooled my seniors"
+subtitle: "and why I swear by the experience"
+date: 2020-08-04 10:15:05 +0000
+author: Nupur Thakur
+thumbnail: ./feature-image.svg
+darkthumbnail: ./feature-image.svg
+category: Community
+tags:
+ - Community
+ - MeshMate
+published: true
+redirect_from:
+ - /blog/how-i-schooled-my-seniors/
+---
+
+
+
+
+
+I started a new job at [RemoteState](https://www.linkedin.com/company/remotestate/) as a software development engineer in May of 2020.
+Post the initial plunge, settling into the role was relatively easier for me due to the experience I had gained in working on open source contributions in the Layer5 community. My experience with open source had also been a big plus for me throughout the application and interview process. As a direct result, my colleagues and seniors became genuinely inquisitive about Meshery and its functionality as the Kubernetes Manager. So when asked, I happily agreed to deliver a session on the subject to the entire team.
+
+I pitched my idea to [Lee Calcote](https://layer5.io/community/members/lee-calcote) and in his usual supportive form, he was as excited as I was about the session. A brainstorm session led to creating an entire presentation with suggestions from Lee. The Layer5 community offers a number of resources to contributors, including these two decks ([Meshery - the cloud native management plane](https://layer5.io/meshery) and [Layer5](https://docs.google.com/presentation/d/1tLcMcyQ-Z6YYISYyR0Eyb30dojQiKHIjs7Rt5m8kcag/edit?usp=sharing) that I drew from as a basis for a personalized presentation and demonstration to my new team.
+
+
+
+
+When the day arrived to present the concepts of service meshes, Meshery, and other cloud native initiatives to my team, I held a Google Meet with a full attendance. I started the session with a reader’s digest version of microservices and service meshes to set the stage for any newcomers to the world of cloud native, I went on to elaborate on Layer5 ‘s contributions to the CNCF landscape and the SMI project. This was followed by an in-depth discussion on data planes, control planes, and management planes. I spoke at-length about Meshery’s functionality including, its features for facilitating the benchmarking, interoperability and standardization of service meshes. I wrapped up the session with some insider tips that I have learned in my months as an open source contributor in the Layer5 community. In the stream of feedback received from my colleagues, the session seems to have been a success.
+
+This whole experience has been an amazing journey for me. From being a complete noob to utilizing my expertise in the service mesh domain to landing an actual job, the experience has been a maze of ups and downs. But, I feel like I have finally arrived and arrived with a pot of gold. I’m eternally grateful to Lee Calcote for motivating me and providing me with the appropriate resources. Entering and exploring an open source community can be a daunting task and the [resources provided by Layer5](https://layer5.io/community/newcomers) helped them in overcoming that challenge and enabled them to learn more about the widespread work of [Meshery](https://meshery.io).
+
+I’m glad to have found a community that not only feeds my professional success, but also my personal growth. It’s not out of obligation, but out of a sense of gratitude and paying it forward to others (a tenant of the Layer5 community) that I now spend much of my time as a MeshMate. I help welcome and guide other new contributors along their open source path as they learn and grow. Giving to others and while continuing to grow professionally and personally is time well spent. I encourage you to join me and others in the Layer5 community by jumping into our [Slack](https://slack.layer5.io/) to start meshing around!
+
+
+
diff --git a/src/collections/blog/2020/2020-08-07-announcing-meshery-v0.4/index.mdx b/src/collections/blog/2020/2020-08-07-announcing-meshery-v0.4/index.mdx
index c511c4b9b41c..4e10107ef423 100644
--- a/src/collections/blog/2020/2020-08-07-announcing-meshery-v0.4/index.mdx
+++ b/src/collections/blog/2020/2020-08-07-announcing-meshery-v0.4/index.mdx
@@ -1,98 +1,98 @@
----
-title: "Announcing Meshery v0.4.0"
-subtitle: ""
-date: 2020-08-07 08:00:00 +0000
-author: Layer5 Team
-thumbnail: ./meshery-v040.webp
-darkthumbnail: ./meshery-v040.webp
-category: Announcements
-tags:
- - Meshery
- - Projects
-published: true
-type: Blog
-product: Meshery
-resource: true
-redirect_from:
- - /blog/meshery/announcing-meshery-v0.4.0/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import operator from "./meshery-operator-dark.svg";
-import MesheryArchitecture from "./meshery-architecture.webp";
-
-
-
-[Meshery](https://meshery.io) is the cloud native management plane offering lifecycle, configuration and performance management of service meshes and their workloads.
-
-Layer5 community members are hard at work providing our users with easy access to any service mesh and myriad management features. New releases for Meshery are published on a frequent cadence with new features and bug fixes. Today, we are announcing version 0.4.0 of Meshery. This summary highlights Meshery's latest developments and elucidates new features.
-
-## What's New?
-
-The v0.4.0 release of Meshery introduces a plethora of new features and bug fixes across service mesh environments spanning Meshery and it's various adapters.
-
-### Meshery's CLI: `mesheryctl`
-**New Command Structure**
-`mesheryctl` commands and subcommands have been restructured in v0.4.0 into the categories:
-- Global Commands and Flags
-- Meshery Lifecycle Management
-- Performance Management
-- Service Mesh Lifecycle Management
-- Workload Lifecycle Management
-
-Organizing commnands [under these categories](https://docs.meshery.io/reference/mesheryctl) is done with both the intention to make `mesheryctl` functions intuitively at your fingertips, but also to make room for forthcoming functionality.
-
-**Exposing Performance Management in the CLI**
-`perf:` a new `mesheryctl`command. Introduction of new performance sub-commands, now benchmark your service mesh at the tip of your fingers using our new CLI command `perf`.
-
-**Support for Scoop**
-Support extended to Scoop Bucket. You can now install mesheryctl on your Windows machine with Scoop Bucket. Visit the [Meshery Scoop Bucket](https://github.com/layer5io/scoop-bucket) to install Meshery on Windows.
-
-**Rename `cleanup` to `reset`**
-The `cleanup` is used to reset your Meshery deployment configuration back to its default settings. This command has been renamed to `reset` to more appropriately reflect its purpose.
-
-### MeshSync
-
-
-- A component of the [Meshery Operator](https://github.com/layer5io/meshery-operator), MeshSync can scan the environment to get the deployment details of specific types of service meshes and the connected Kubernetes cluster.
-- MeshSync is a new component addition to Meshery. Meshery needs to be constantly updated given that service meshes and their underlying infrastructure are dynamic, constantly changing. Meshery operations should be resilient in the face of this change.
-- MeshSync brings a service mesh agnostic object model that defines relationships between all objects under management.
-
-### Meshery Adapter for Citrix Service Mesh (beta)
-
-
-
-- [Citrix Service Mesh](https://github.com/layer5io/meshery-cpx) is now a supported service mesh. Meshery incorporates support for the Citrix ADC CPX, which is a cloud-ready, container-based application delivery controller that can be provisioned on a Docker host.
-- CPX runs as the Istio Data Plane component, displacing Envoy as the default data plane service proxy.
-
-### Security & Authentication
-
-- Meshery has moved from using session authentication to JWT authentication. Meshery's JWT authentication is powered by Hydra Auth.
-- You can now opt to authenticate yourself on mesheryctl while performing performance tests using `mesheryctl`, you can authenticate yourself by getting the JWT Token from Meshery UI.
-
-### Meshery Server
-
-- Support provided for [wrk2 as an alternative load generator](https://docs.meshery.io/functionality/performance-management#load-generators).
-- [Providers](https://docs.meshery.io/extensibility) - A new project construct that allows users to select authentication, long-term storage etc.
-- Ad-hoc [connectivity tests for Prometheus and Grafana](https://docs.meshery.io/functionality/performance-management#grafana-and-meshery) are now supported.
-- Extraneous information beyond IP address and port in Grafana and Prometheus endpoints have been stripped off.
-
-### Meshery UI
-
-- ES-Lint has been added to the client side to ensure the quality of code and increase maintainaiblity of code.
-- Cypress has been set-up to enable end-to-end tests and integration tests for Meshery UI.
-
-
-
-
-### Other notable changes
-
-- From within the [Meshery Continuous Integration Working Group](https://www.youtube.com/watch?v=ds9D2KgZKxo&list=PL3A-A6hPO2IM7rYiKxG4l3eQNc6X3IUex), we have strengthened our continuous integration (CI) actions & tests by introducing new workflows like `static check`, `vet check`, `security check` for our server code.
-- ReleaseDrafter & WelcomeBot has been added to the repository to enable automation of release notes and for welcoming new contributors, respectively.
-
-To get a more comprehensive list of the bug fixes and enhancements packaged in the v0.4.0 release, see the [Meshery Documentation](https://docs.meshery.io/project/releases)
-
-
-_**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!**_
-
-
+---
+title: "Announcing Meshery v0.4.0"
+subtitle: ""
+date: 2020-08-07 08:00:00 +0000
+author: Layer5 Team
+thumbnail: ./meshery-v040.webp
+darkthumbnail: ./meshery-v040.webp
+category: Announcements
+tags:
+ - Meshery
+ - Projects
+published: true
+type: Blog
+product: Meshery
+resource: true
+redirect_from:
+ - /blog/meshery/announcing-meshery-v0.4.0/
+---
+
+
+import operator from "./meshery-operator-dark.svg";
+import MesheryArchitecture from "./meshery-architecture.webp";
+
+
+
+[Meshery](https://meshery.io) is the cloud native management plane offering lifecycle, configuration and performance management of service meshes and their workloads.
+
+Layer5 community members are hard at work providing our users with easy access to any service mesh and myriad management features. New releases for Meshery are published on a frequent cadence with new features and bug fixes. Today, we are announcing version 0.4.0 of Meshery. This summary highlights Meshery's latest developments and elucidates new features.
+
+## What's New?
+
+The v0.4.0 release of Meshery introduces a plethora of new features and bug fixes across service mesh environments spanning Meshery and it's various adapters.
+
+### Meshery's CLI: `mesheryctl`
+**New Command Structure**
+`mesheryctl` commands and subcommands have been restructured in v0.4.0 into the categories:
+- Global Commands and Flags
+- Meshery Lifecycle Management
+- Performance Management
+- Service Mesh Lifecycle Management
+- Workload Lifecycle Management
+
+Organizing commnands [under these categories](https://docs.meshery.io/reference/mesheryctl) is done with both the intention to make `mesheryctl` functions intuitively at your fingertips, but also to make room for forthcoming functionality.
+
+**Exposing Performance Management in the CLI**
+`perf:` a new `mesheryctl`command. Introduction of new performance sub-commands, now benchmark your service mesh at the tip of your fingers using our new CLI command `perf`.
+
+**Support for Scoop**
+Support extended to Scoop Bucket. You can now install mesheryctl on your Windows machine with Scoop Bucket. Visit the [Meshery Scoop Bucket](https://github.com/layer5io/scoop-bucket) to install Meshery on Windows.
+
+**Rename `cleanup` to `reset`**
+The `cleanup` is used to reset your Meshery deployment configuration back to its default settings. This command has been renamed to `reset` to more appropriately reflect its purpose.
+
+### MeshSync
+
+
+- A component of the [Meshery Operator](https://github.com/layer5io/meshery-operator), MeshSync can scan the environment to get the deployment details of specific types of service meshes and the connected Kubernetes cluster.
+- MeshSync is a new component addition to Meshery. Meshery needs to be constantly updated given that service meshes and their underlying infrastructure are dynamic, constantly changing. Meshery operations should be resilient in the face of this change.
+- MeshSync brings a service mesh agnostic object model that defines relationships between all objects under management.
+
+### Meshery Adapter for Citrix Service Mesh (beta)
+
+
+
+- [Citrix Service Mesh](https://github.com/layer5io/meshery-cpx) is now a supported service mesh. Meshery incorporates support for the Citrix ADC CPX, which is a cloud-ready, container-based application delivery controller that can be provisioned on a Docker host.
+- CPX runs as the Istio Data Plane component, displacing Envoy as the default data plane service proxy.
+
+### Security & Authentication
+
+- Meshery has moved from using session authentication to JWT authentication. Meshery's JWT authentication is powered by Hydra Auth.
+- You can now opt to authenticate yourself on mesheryctl while performing performance tests using `mesheryctl`, you can authenticate yourself by getting the JWT Token from Meshery UI.
+
+### Meshery Server
+
+- Support provided for [wrk2 as an alternative load generator](https://docs.meshery.io/functionality/performance-management#load-generators).
+- [Providers](https://docs.meshery.io/extensibility) - A new project construct that allows users to select authentication, long-term storage etc.
+- Ad-hoc [connectivity tests for Prometheus and Grafana](https://docs.meshery.io/functionality/performance-management#grafana-and-meshery) are now supported.
+- Extraneous information beyond IP address and port in Grafana and Prometheus endpoints have been stripped off.
+
+### Meshery UI
+
+- ES-Lint has been added to the client side to ensure the quality of code and increase maintainaiblity of code.
+- Cypress has been set-up to enable end-to-end tests and integration tests for Meshery UI.
+
+
+
+
+### Other notable changes
+
+- From within the [Meshery Continuous Integration Working Group](https://www.youtube.com/watch?v=ds9D2KgZKxo&list=PL3A-A6hPO2IM7rYiKxG4l3eQNc6X3IUex), we have strengthened our continuous integration (CI) actions & tests by introducing new workflows like `static check`, `vet check`, `security check` for our server code.
+- ReleaseDrafter & WelcomeBot has been added to the repository to enable automation of release notes and for welcoming new contributors, respectively.
+
+To get a more comprehensive list of the bug fixes and enhancements packaged in the v0.4.0 release, see the [Meshery Documentation](https://docs.meshery.io/project/releases)
+
+
+_**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/2020/2020-08-11-20-learn-how-to-write-wasm-filters-for-envoy-in-rust-and-deploy-with-consul/index.mdx b/src/collections/blog/2020/2020-08-11-20-learn-how-to-write-wasm-filters-for-envoy-in-rust-and-deploy-with-consul/index.mdx
index 4306a69a7804..ee04a4764a3c 100644
--- a/src/collections/blog/2020/2020-08-11-20-learn-how-to-write-wasm-filters-for-envoy-in-rust-and-deploy-with-consul/index.mdx
+++ b/src/collections/blog/2020/2020-08-11-20-learn-how-to-write-wasm-filters-for-envoy-in-rust-and-deploy-with-consul/index.mdx
@@ -1,28 +1,28 @@
----
-title: "Learn How to Write WASM Filters"
-subtitle: "for Envoy in Rust and Deploy with Consul"
-date: 2020-08-11 08:00:00 -0530
-author: Lee Calcote
-thumbnail: ./layer5-white-bg.webp
-darkthumbnail: ./layer5-white-bg.webp
-category: WebAssembly
-tags:
- - WASM
- - WebAssembly
- - Rust
- - Envoy
- - Consul
-published: false
-redirect_from:
- - /blog/webassembly/learn-how-to-write-wasm-filters-for-envoy-in-rust-and-deploy-with-consul/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
- [Image Hub](/projects/image-hub) was built under the vision that most people are not deriving the full potential of a service mesh.
-
- Whether you identify as a service owner or a product owner, you stand to significantly benefit from the use of a service mesh as the infrastructure running your application.
-
-
+---
+title: "Learn How to Write WASM Filters"
+subtitle: "for Envoy in Rust and Deploy with Consul"
+date: 2020-08-11 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./layer5-white-bg.webp
+darkthumbnail: ./layer5-white-bg.webp
+category: WebAssembly
+tags:
+ - WASM
+ - WebAssembly
+ - Rust
+ - Envoy
+ - Consul
+published: false
+redirect_from:
+ - /blog/webassembly/learn-how-to-write-wasm-filters-for-envoy-in-rust-and-deploy-with-consul/
+---
+
+
+
+
+
+ [Image Hub](/projects/image-hub) was built under the vision that most people are not deriving the full potential of a service mesh.
+
+ Whether you identify as a service owner or a product owner, you stand to significantly benefit from the use of a service mesh as the infrastructure running your application.
+
+
diff --git a/src/collections/blog/2020/2020-08-11-my-journey-from-a-contributor-to-a-maintainer/index.mdx b/src/collections/blog/2020/2020-08-11-my-journey-from-a-contributor-to-a-maintainer/index.mdx
index ed4acc75128c..6024c7457129 100644
--- a/src/collections/blog/2020/2020-08-11-my-journey-from-a-contributor-to-a-maintainer/index.mdx
+++ b/src/collections/blog/2020/2020-08-11-my-journey-from-a-contributor-to-a-maintainer/index.mdx
@@ -1,63 +1,63 @@
----
-title: "My journey from a contributor to a maintainer!"
-subtitle: ""
-date: 2020-08-11 10:55:05 -0530
-author: Nikhil Ladha
-thumbnail: ./pic1.webp
-darkthumbnail: ./pic1.webp
-category: Community
-tags:
- - MeshMate
- - Community
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import SignedBook from "./pic2.jpeg";
-
-
-
-Getting involved in something new and essentially avant garde, can be a messy challenge to navigate through. But, when it comes to contributing to Meshery it only gets more and more meshy!
-
-### Get set go!
-
-
I was introduced to the world of open source through the Meshery project in the august of 2019 and have since then been continuously exploring the farthest reaches of Meshery, Layer5, the parent SMI project and consecutively the CNCF landscape.
-
-At the time of writing this, I have been a part of the Meshery project for about a year. Fascinated by the concept and further lured in by the welcoming community at Layer5, I was soon dipping my toes into the tidal wave of code. Starting out with small contributions to improve the UI, I stumbled on to my first issue, which was to open a page in a new tab instead of opening it in the same tab. Basic, right?
-
-I’m pointing this out to unravel the myth and smoke clouds around open source projects. Contributing can be as easy as altering a few lines of code and can be as meaningful as writing a whole new feature adapter. Since then, I have crossed small and big hurdles, meandering through countless issues and have become a part of the wholesome community, gaining friends and mentors along the way.
-
-### Stepping stones
-
-Let’s begin with the basics. What is Layer5?
-
-Layer5 is the service mesh company, which has built (or is in the process of building) an exhaustive set of projects to delve into the world of cloud native and service meshes with in-depth analyses. Intrigued? Checkout the [Layer5](https://layer5.io/) site and hop on to our [GitHub](https://github.com/layer5io) bandwagon. Before you do me the favor of reading on, make sure to click on the little star :star: button to help us stir up some more delectable meshiness.
-
-### Roadblocks
-
-Coming to my contributions at Layer5, I have mostly been involved in improving the UI and shaping the company site’s present outlook. I have also tried my hand at other projects, including the `mesheryctl` and the `landscape` at Layer5. In fact, here is a comprehensive list of **[my contributions across Layer5 projects](https://github.com/issues?page=1&q=is%3Aclosed+author%3ANikhil-Ladha+org%3Alayer5io)**.
-
-The above mentioned links are just the **visible** contributions made by me. With time, I have grown and was soon approached to become a [MeshMate](/community/meshmates), an initiative which involves few seasoned contributors like me who will hold the hand of a new member and help him/her bridge the gap and take the leap into open source.
-
-### Tricks of the Trade
-
-The benefits of being a UI engineer?
-
-Web developers are required in every company in one meaningful way or the other as every single project needs a frontend to showcase it’s capabilities to the user. Coming to Layer5, the frontend of Meshery is built on React( another masterpiece from Facebook! ), which I learned from scratch when I joined the community.
-
-
-
-Now, months have passed and with some healthy dedication and hours of staring at thousands of lines of code, I have a good base and practical experience with React, something which you can’t hope to gain from personal projects and require a community for.
-
-The Layer5 and Meshery websites are built using Jekyll, another technology about which I didn’t have any practical knowledge a couple of months ago. Easier than react and harder than CSS, Jekyll is perfect for the aspiring web developers out there and is also another reason for you to pop over to the Layer5 repo after reading this article.
-
-### Meshy goodness
-
-My experience at Layer5 has made me proud of the work that we do and has challenged me time and again to reach for higher goals. I still have a hunch that someway or the other my contributions are responsible for getting me an internship at Red Hat! All heads bowed to [Lee Calcote](https://www.linkedin.com/in/leecalcote/) for his presence and guidance and to the Layer5 community for being as amazing as it is. My journey at Layer5 has been an ever growing curve to be honest from just a contributor to a MeshMate to the maintainer of few projects at Layer5. And, true to god this wouldn’t have been possible without the combined effort from me and our very own Lee Calcote. His trust and confidence in me is what encourages me to contribute more and more at Layer5 and see it grow to some next level in the coming future.
-Motivated or moved or still confused?
-
-Want to experience the same feeling and see yourself recognized as an Open-source contributor?
-
-_**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!**_
-
-
+---
+title: "My journey from a contributor to a maintainer!"
+subtitle: ""
+date: 2020-08-11 10:55:05 -0530
+author: Nikhil Ladha
+thumbnail: ./pic1.webp
+darkthumbnail: ./pic1.webp
+category: Community
+tags:
+ - MeshMate
+ - Community
+published: true
+---
+
+
+import SignedBook from "./pic2.jpeg";
+
+
+
+Getting involved in something new and essentially avant garde, can be a messy challenge to navigate through. But, when it comes to contributing to Meshery it only gets more and more meshy!
+
+### Get set go!
+
+I was introduced to the world of open source through the Meshery project in the august of 2019 and have since then been continuously exploring the farthest reaches of Meshery, Layer5, the parent SMI project and consecutively the CNCF landscape.
+
+At the time of writing this, I have been a part of the Meshery project for about a year. Fascinated by the concept and further lured in by the welcoming community at Layer5, I was soon dipping my toes into the tidal wave of code. Starting out with small contributions to improve the UI, I stumbled on to my first issue, which was to open a page in a new tab instead of opening it in the same tab. Basic, right?
+
+I’m pointing this out to unravel the myth and smoke clouds around open source projects. Contributing can be as easy as altering a few lines of code and can be as meaningful as writing a whole new feature adapter. Since then, I have crossed small and big hurdles, meandering through countless issues and have become a part of the wholesome community, gaining friends and mentors along the way.
+
+### Stepping stones
+
+Let’s begin with the basics. What is Layer5?
+
+Layer5 is the service mesh company, which has built (or is in the process of building) an exhaustive set of projects to delve into the world of cloud native and service meshes with in-depth analyses. Intrigued? Checkout the [Layer5](https://layer5.io/) site and hop on to our [GitHub](https://github.com/layer5io) bandwagon. Before you do me the favor of reading on, make sure to click on the little star :star: button to help us stir up some more delectable meshiness.
+
+### Roadblocks
+
+Coming to my contributions at Layer5, I have mostly been involved in improving the UI and shaping the company site’s present outlook. I have also tried my hand at other projects, including the `mesheryctl` and the `landscape` at Layer5. In fact, here is a comprehensive list of **[my contributions across Layer5 projects](https://github.com/issues?page=1&q=is%3Aclosed+author%3ANikhil-Ladha+org%3Alayer5io)**.
+
+The above mentioned links are just the **visible** contributions made by me. With time, I have grown and was soon approached to become a [MeshMate](/community/meshmates), an initiative which involves few seasoned contributors like me who will hold the hand of a new member and help him/her bridge the gap and take the leap into open source.
+
+### Tricks of the Trade
+
+The benefits of being a UI engineer?
+
+Web developers are required in every company in one meaningful way or the other as every single project needs a frontend to showcase it’s capabilities to the user. Coming to Layer5, the frontend of Meshery is built on React( another masterpiece from Facebook! ), which I learned from scratch when I joined the community.
+
+
+
+Now, months have passed and with some healthy dedication and hours of staring at thousands of lines of code, I have a good base and practical experience with React, something which you can’t hope to gain from personal projects and require a community for.
+
+The Layer5 and Meshery websites are built using Jekyll, another technology about which I didn’t have any practical knowledge a couple of months ago. Easier than react and harder than CSS, Jekyll is perfect for the aspiring web developers out there and is also another reason for you to pop over to the Layer5 repo after reading this article.
+
+### Meshy goodness
+
+My experience at Layer5 has made me proud of the work that we do and has challenged me time and again to reach for higher goals. I still have a hunch that someway or the other my contributions are responsible for getting me an internship at Red Hat! All heads bowed to [Lee Calcote](https://www.linkedin.com/in/leecalcote/) for his presence and guidance and to the Layer5 community for being as amazing as it is. My journey at Layer5 has been an ever growing curve to be honest from just a contributor to a MeshMate to the maintainer of few projects at Layer5. And, true to god this wouldn’t have been possible without the combined effort from me and our very own Lee Calcote. His trust and confidence in me is what encourages me to contribute more and more at Layer5 and see it grow to some next level in the coming future.
+Motivated or moved or still confused?
+
+Want to experience the same feeling and see yourself recognized as an Open-source contributor?
+
+_**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/2020/2020-08-20-announcing-the-meshery-adapter-for-open-service-mesh/index.mdx b/src/collections/blog/2020/2020-08-20-announcing-the-meshery-adapter-for-open-service-mesh/index.mdx
index 5a635d7a8583..0c3979b3990b 100644
--- a/src/collections/blog/2020/2020-08-20-announcing-the-meshery-adapter-for-open-service-mesh/index.mdx
+++ b/src/collections/blog/2020/2020-08-20-announcing-the-meshery-adapter-for-open-service-mesh/index.mdx
@@ -1,47 +1,47 @@
----
-title: "Announcing the Meshery Adapter for Open Service Mesh"
-subtitle: "Adding another service mesh to the landscape and another adapter to Meshery"
-date: 2020-08-20 10:17:05 +0000
-author: Lee Calcote
-thumbnail: ./meshery-open-service.webp
-darkthumbnail: ./meshery-open-service.webp
-category: "Service Mesh"
-tags:
- - Meshery
- - Service Mesh
-published: true
-resource: true
-type: Blog
-product: Meshery
-mesh: Open Service Mesh
-redirect_from:
- - /blog/meshery/announcing-the-meshery-adapter-for-open-service-mesh/
- - /blog/open-service-mesh/announcing-the-meshery-adapter-for-open-service-mesh
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import conformance from "./conformance-results.webp";
-
-
-
-Released on August 5th, 2020 by Microsoft, [Open Service Mesh](https://openservicemesh.io/) (OSM) is a lightweight and [Service Mesh Interace conformant](https://layer5.io/smi) (SMI). Open Service Mesh is a contemporary addition to the [service mesh landscape](/service-mesh-landscape). Using Envoy as its data plane proxy component and SMI specifications as it's control plane APIs, OSM draws lessons and code from existing service mesh projects, like Linkerd. The Open Service Mesh project has some miles to go as it is one of a growing list of choices available in the service mesh landscape.
-
-First pronounced to be SMI compliant by [Meshery](https://meshery.io/), the cloud native management plane, the first release of OSM supports a myriad of basic
-
-
-
Securing service to service links
-
Supporting traffic shifting
-
Managing observability for your services
-
Validating and Implementing access control policies
-
Auto addition of applications and services
-
-
-### Get started with OSM using Meshery
-In Layer5's effort to support our multi-mesh world, our Meshery project provides an effortless way for Kubernetes operators to install, maintain and run service meshes. [Meshery v0.4.3](https://github.com/layer5io/meshery/releases/tag/v0.4.3) includes the [Meshery Adapter for Open Service Mesh](https://github.com/layer5io/meshery-osm), enabling you to quickly provision OSM, run any number of sample applications, manage its performance using [Service Mesh Performance](https://smp-spec.io/) (SMP), validate OSM's compliance to SMI using a suite of conformance tests. Meshery offers configuraiton management with builtin best practice configuration analysis giving you confidence in applying custom configuration to OSM. Meshery's documenation on the [Open Service Mesh integation](https://docs.meshery.io/service-meshes/adapters/osm) provides a complete walkthrough on how to get set up, install, deploy and configure OSM according to your needs.
-
-
-
-Try Open Service Mesh now, by [getting started with Meshery](/cloud-native-management/meshery/getting-started).
-
-
-
+---
+title: "Announcing the Meshery Adapter for Open Service Mesh"
+subtitle: "Adding another service mesh to the landscape and another adapter to Meshery"
+date: 2020-08-20 10:17:05 +0000
+author: Lee Calcote
+thumbnail: ./meshery-open-service.webp
+darkthumbnail: ./meshery-open-service.webp
+category: "Service Mesh"
+tags:
+ - Meshery
+ - Service Mesh
+published: true
+resource: true
+type: Blog
+product: Meshery
+mesh: Open Service Mesh
+redirect_from:
+ - /blog/meshery/announcing-the-meshery-adapter-for-open-service-mesh/
+ - /blog/open-service-mesh/announcing-the-meshery-adapter-for-open-service-mesh
+---
+
+
+import conformance from "./conformance-results.webp";
+
+
+
+Released on August 5th, 2020 by Microsoft, [Open Service Mesh](https://openservicemesh.io/) (OSM) is a lightweight and [Service Mesh Interace conformant](https://layer5.io/smi) (SMI). Open Service Mesh is a contemporary addition to the [service mesh landscape](/service-mesh-landscape). Using Envoy as its data plane proxy component and SMI specifications as it's control plane APIs, OSM draws lessons and code from existing service mesh projects, like Linkerd. The Open Service Mesh project has some miles to go as it is one of a growing list of choices available in the service mesh landscape.
+
+First pronounced to be SMI compliant by [Meshery](https://meshery.io/), the cloud native management plane, the first release of OSM supports a myriad of basic
+
+
+
Securing service to service links
+
Supporting traffic shifting
+
Managing observability for your services
+
Validating and Implementing access control policies
+
Auto addition of applications and services
+
+
+### Get started with OSM using Meshery
+In Layer5's effort to support our multi-mesh world, our Meshery project provides an effortless way for Kubernetes operators to install, maintain and run service meshes. [Meshery v0.4.3](https://github.com/layer5io/meshery/releases/tag/v0.4.3) includes the [Meshery Adapter for Open Service Mesh](https://github.com/layer5io/meshery-osm), enabling you to quickly provision OSM, run any number of sample applications, manage its performance using [Service Mesh Performance](https://smp-spec.io/) (SMP), validate OSM's compliance to SMI using a suite of conformance tests. Meshery offers configuraiton management with builtin best practice configuration analysis giving you confidence in applying custom configuration to OSM. Meshery's documenation on the [Open Service Mesh integation](https://docs.meshery.io/service-meshes/adapters/osm) provides a complete walkthrough on how to get set up, install, deploy and configure OSM according to your needs.
+
+
+
+Try Open Service Mesh now, by [getting started with Meshery](/cloud-native-management/meshery/getting-started).
+
+
+
diff --git a/src/collections/blog/2020/2020-09-19-performance-benchmarking-using-meshery-and-nighthawk/index.mdx b/src/collections/blog/2020/2020-09-19-performance-benchmarking-using-meshery-and-nighthawk/index.mdx
index 3e1d5e31e59b..cd8dcb42a738 100644
--- a/src/collections/blog/2020/2020-09-19-performance-benchmarking-using-meshery-and-nighthawk/index.mdx
+++ b/src/collections/blog/2020/2020-09-19-performance-benchmarking-using-meshery-and-nighthawk/index.mdx
@@ -1,76 +1,76 @@
----
-title: "Performance benchmarking using Meshery and Nighthawk"
-subtitle: ""
-date: 2020-09-19 11:00:05 +0530
-author: Layer5 Team
-thumbnail: ./mesheryctl.webp
-darkthumbnail: ./mesheryctl.webp
-category: Performance
-tags:
- - Nighthawk
- - Performance
- - Service Mesh Performance
- - Meshery
-published: true
-type: Blog
-product: Nighthawk
-resource: true
-redirect_from:
- - /blog/performance-benchmarking-using-meshery-and-nighthawk/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import smpImg from "./smp.webp";
-
-
-
-### What is performance benchmarking and why should you care?
-
-Many of you may remember that the HBO streaming service crashed when the final season of the popular sitcom, Game of Thrones went live on the service. Unable to engage all the user requests, the streaming service and the website broke down and ultimately resulted in DoS (Denial of Service). There are numerous examples of service crashes across different platforms, which has forced developers to take a closer look at performance benchmarking and pre-launch performance checks.
-
-There are several advantages of preliminary service benchmarking, which may extensively enhance the response time, resolve glitches, enhance the application's robustness, and bring together several other commendable factors, including but not limited to stability and dependability within an application.
-
-There are several tools for performance benchmarking. A major one is the interconnected relationship between load generators and benchmarks. Some of the well-known load generators in the cloud native realm are:
-
-
-
-The conclusion can be encapsulated as following, Meshery, the cloud native management plane possesses the ability to generate load and benchmark services in/out of your service mesh using Fortio, Wrk2 and now, Nighthawk too.
-
-### Meshery + Nighthawk = Robust Distributed and Scalable Services
-
-Nighthawk, written and maintained by the Envoy Community, is a L7 (HTTP/HTTPS/HTTP2) performance characterization tool that supports performance benchmarking using HTTP or gRPC services.
-
-Nighthawk is built using open-source builds and test tool Bazel and supports output formatting to well-known formats, allowing integration with other systems and dashboards. To add more to the list, it will soon support distributed performance benchmarking which is currently under an active development stage.
-
-On the other hand, Meshery, written and maintainer by Layer5 Community is the multi-service mesh management plane offering lifecycle, configuration and performance management of service meshes and their workloads. With Meshery, you can both, manage your service mesh's lifecycle, and benchmark them with industry-grade tools to let you know how much under or over-utilized your services are.
-
-
-
-Soon, Meshery is going to be a canonical implementation for [Service Mesh Performance](https://github.com/layer5io/service-mesh-performance) which is a common and standardised format to describe : - Performance test configuration - Service mesh configuration - Environment configuration - Workload configuration - Performance test results.
-
-### How did we achieve it ?
-The following project was proposed as a Google Summer of Code Idea, I was selected as a student mentee to draft the design, architecture and code my way from scratch. On my journey, I received guidance from some amazing mentors, colleagues and open-source stake holders. I discussed the design proposal with Envoy Team as well as Layer5 Team and from suggestions from both, I was able to complete my project.
-
-In the course of the project, I came up with the idea of invoking Nighthawk as a separate container with which Meshery will communicate using a go-lang based middleware.
-
-To my elation, the project was a huge success and Nighthawk is now invoked as a load-generator in Meshery. Soon, the public release for the new version will be made and users will be able to utilize Nighthawk as a performance-benchamark tool alongside with Fortio and Wrk2.
-
-### What's next?
-This is just the first relay, in the long run, there are many more milestones to come. The following is a list of projects which will be completed in upcoming months:
-
-- Invoke Nighthawk as an gRPC Service and support gRPC connection between Nighthawk & Meshery.
-- Implement user-profiles for performance benchmarking which may store some preset preferred values according to users.
-- Enhance Nighthawk to support distributed load generation and performance benchmarking.
-- NATS & gRPC Performance Benchmarking for gRPC and NATS services invoked in Meshery.
-
-and many more awesome and bleeding-edge ideas.
-
-### How can I get involved?
-If any of this sounds remotely exciting, I implore you to give this a chance. You won’t regret it. Head over to our [Slack Channel](http://slack.layer5.io) and join the #performance channel where everything related to performance testing is discussed. We would love to hear your feedback. Stay tuned for more blogs related to Performance Benchmarking, SMI Conformance and all things meshy!!!
-
-
-
+---
+title: "Performance benchmarking using Meshery and Nighthawk"
+subtitle: ""
+date: 2020-09-19 11:00:05 +0530
+author: Layer5 Team
+thumbnail: ./mesheryctl.webp
+darkthumbnail: ./mesheryctl.webp
+category: Performance
+tags:
+ - Nighthawk
+ - Performance
+ - Service Mesh Performance
+ - Meshery
+published: true
+type: Blog
+product: Nighthawk
+resource: true
+redirect_from:
+ - /blog/performance-benchmarking-using-meshery-and-nighthawk/
+---
+
+
+import smpImg from "./smp.webp";
+
+
+
+### What is performance benchmarking and why should you care?
+
+Many of you may remember that the HBO streaming service crashed when the final season of the popular sitcom, Game of Thrones went live on the service. Unable to engage all the user requests, the streaming service and the website broke down and ultimately resulted in DoS (Denial of Service). There are numerous examples of service crashes across different platforms, which has forced developers to take a closer look at performance benchmarking and pre-launch performance checks.
+
+There are several advantages of preliminary service benchmarking, which may extensively enhance the response time, resolve glitches, enhance the application's robustness, and bring together several other commendable factors, including but not limited to stability and dependability within an application.
+
+There are several tools for performance benchmarking. A major one is the interconnected relationship between load generators and benchmarks. Some of the well-known load generators in the cloud native realm are:
+
+
+
+The conclusion can be encapsulated as following, Meshery, the cloud native management plane possesses the ability to generate load and benchmark services in/out of your service mesh using Fortio, Wrk2 and now, Nighthawk too.
+
+### Meshery + Nighthawk = Robust Distributed and Scalable Services
+
+Nighthawk, written and maintained by the Envoy Community, is a L7 (HTTP/HTTPS/HTTP2) performance characterization tool that supports performance benchmarking using HTTP or gRPC services.
+
+Nighthawk is built using open-source builds and test tool Bazel and supports output formatting to well-known formats, allowing integration with other systems and dashboards. To add more to the list, it will soon support distributed performance benchmarking which is currently under an active development stage.
+
+On the other hand, Meshery, written and maintainer by Layer5 Community is the multi-service mesh management plane offering lifecycle, configuration and performance management of service meshes and their workloads. With Meshery, you can both, manage your service mesh's lifecycle, and benchmark them with industry-grade tools to let you know how much under or over-utilized your services are.
+
+
+
+Soon, Meshery is going to be a canonical implementation for [Service Mesh Performance](https://github.com/layer5io/service-mesh-performance) which is a common and standardised format to describe : - Performance test configuration - Service mesh configuration - Environment configuration - Workload configuration - Performance test results.
+
+### How did we achieve it ?
+The following project was proposed as a Google Summer of Code Idea, I was selected as a student mentee to draft the design, architecture and code my way from scratch. On my journey, I received guidance from some amazing mentors, colleagues and open-source stake holders. I discussed the design proposal with Envoy Team as well as Layer5 Team and from suggestions from both, I was able to complete my project.
+
+In the course of the project, I came up with the idea of invoking Nighthawk as a separate container with which Meshery will communicate using a go-lang based middleware.
+
+To my elation, the project was a huge success and Nighthawk is now invoked as a load-generator in Meshery. Soon, the public release for the new version will be made and users will be able to utilize Nighthawk as a performance-benchamark tool alongside with Fortio and Wrk2.
+
+### What's next?
+This is just the first relay, in the long run, there are many more milestones to come. The following is a list of projects which will be completed in upcoming months:
+
+- Invoke Nighthawk as an gRPC Service and support gRPC connection between Nighthawk & Meshery.
+- Implement user-profiles for performance benchmarking which may store some preset preferred values according to users.
+- Enhance Nighthawk to support distributed load generation and performance benchmarking.
+- NATS & gRPC Performance Benchmarking for gRPC and NATS services invoked in Meshery.
+
+and many more awesome and bleeding-edge ideas.
+
+### How can I get involved?
+If any of this sounds remotely exciting, I implore you to give this a chance. You won’t regret it. Head over to our [Slack Channel](http://slack.layer5.io) and join the #performance channel where everything related to performance testing is discussed. We would love to hear your feedback. Stay tuned for more blogs related to Performance Benchmarking, SMI Conformance and all things meshy!!!
+
+
+
diff --git a/src/collections/blog/2020/2020-09-25-announcing-meshmates/index.mdx b/src/collections/blog/2020/2020-09-25-announcing-meshmates/index.mdx
index bbe89e595a65..b5e2bbcb0446 100644
--- a/src/collections/blog/2020/2020-09-25-announcing-meshmates/index.mdx
+++ b/src/collections/blog/2020/2020-09-25-announcing-meshmates/index.mdx
@@ -1,137 +1,137 @@
----
-title: "Announcing a new line of MeshMates"
-date: 2020-09-25 08:00:00 +0000
-author: Our MeshMates with 🤍
-thumbnail: ./meshmate-announcement.webp
-darkthumbnail: ./meshmate-announcement.webp
-category: Announcements
-tags:
- - Community
- - MeshMate
-published: true
-redirect_from:
- - /blog/community/announcing-meshmates/
----
-
-import { Link } from "gatsby";
-
-import Ruth from "./meshmate-ruth-ikegah.webp";
-import Kelechi from "./meshmate-kelechi-precious.webp";
-import Tanuj from "./meshmate-tanuj-agarwal.webp";
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
Layer5 MeshMates are committed to helping community members be successful contributors. MeshMates aid in identifying areas of projects to engage within, working groups to join, and in helping community members grow in their open source and cloud native knowledge. By connecting one-on-one, MeshMates will share tips on how to have the best community experience possible.
-
-
-
- Tanuj Agarwal
-
-
-
-
- I was introduced to the Layer5 community three months back. Being fairly new
- to the world of open source and looking for new communities and technology to
- delve into, I hopped onto the Layer5 bandwagon and was amazed by the warm
- welcome I received from the wholesome community. I had done video animation
- jobs on a small scale before, which is what led me to confidently take up the
- task of creating a short intro jingle for the various community meetings
- hosted on the Layer5 youtube channel. After iterating for about a week, I
- finally came up with something worthwhile. And to my elation, it was accepted!
- It still warms my heart to see the intro flash before every meeting.
-
-
- Next up I started work on a next generation model of the layer5.io site. Being
- a new project based on Gatsby and heavily relying on React, Javascript and
- GraphQL, the site project was a perfect and challenging opportunity for me to
- expand on my skill set. Speed learning my way through Gatsby, with a
- continuous influx of help and helpful suggestions from my MeshMate, Kush
- Trivedi and others within the community, I soon mastered the platform and have
- spent weeks on creating countless issues and PRs in hopes of achieving the
- project goals. A few months down the line, I started reviewing PRs and began
- helping others contribute, something which I had never had the opportunity to
- do before! After months of continuous effort, I am proud to write that I
- recently joined as a maintainer on the project and was soon approached to be a
- MeshMate, which I happily accepted. My learning graph has seen a soaring
- positive tangent in the months I have been at Layer5 and I’m looking forward
- to an even more educative and rewarding journey ahead 😊
-
-
-
-
- Kelechi Precious Nwachukwu
-
-
-
-
- It was the middle of the COVID-19 pandemic and being unproductive wasn't
- something I can stomach. Wanting to expand on my technical domain knowledge, I
- stumbled across an open-source challenge for women in tech with lists of
- projects to contribute to by the Women of Open Source Community Africa
- (WOSCA). My eyes landed on Layer5 and I haven’t looked back since.
-
-
- A quick look through the repositories left me quaking in my boots. To give you
- some much needed context and to give some hope to all the newbies out there, I
- recently transitioned to working in technical domains from accounting and
- managing construction site projects. Forever getting stuck trying to get my
- hands on new tech and trying to find a way into the bewildering and humongous
- tech domains , I didn't even understand some of the jargon, and was too
- ashamed to ask questions. Stumbling through my first contribution, I somehow
- made it to the finish line and to my happiness, was soon assigned another
- task. Instead of complaining, I set out to study up on the issue and took a
- peek at the other assignees in the repository to ensure that I was not the
- only one taking inordinate amounts of time on an issue. To my surprise, I was
- not.
-
-
- I got working on the assignment and soon encountered issues that would
- previously have made me quit. Thankfully, I decided to take a different
- approach this time. I shared my challenge with the Layer5 community, and was
- amazed at the immediate and abundant response I received. Since then, I have
- helped other contributors get through their challenges, and have received an
- invitation to join the organization as a member, and then as a MeshMate 😎 I
- have been wholly satisfied with the learning opportunities and the friendly
- environment that the Layer5 community has to offer. I have learned that I may
- not be perfect, but by making full use of the resources provided to me, having
- a supportive community by my side and by being open to learning and showing
- determined courage in the face of difficulties, I can achieve anything!
-
-
- Ruth Ikegah
-
-
-
- The field of open source had always been intriguing to me. The idea of a
- close-knit community working with an aim had me wanting to contribute myself.
- Considering the fact that I have a small skill set (Donned the coder hat only
- 6 months ago), Layer5 was a great community for me to start out with. I came
- to know about the Layer5 community from the She Code Africa slack channel,
- after which I visited the GitHub repository and hopped on to the Layer5 slack channel.
-
-
- To my good luck, I received a warm welcome from the community and was able to attend a community meeting the day I joined. I made my way through the Github repos and stumbled across a beginner friendly issue. I started work but to my dismay, my PR failed to pass the DCO check at the final rung. Stuck and with low spirits, I talked to Lee (Layer5 Maintainer) and related my problems with the DCO check fail. He patiently assured me that first-time checks can be hard to get right and assigned me a MeshMate, Ashis Singh (read saviour 😳). I sent a message to Ashis and told him about the issues I was having in submitting my Pull Request. He led me through a step by step tutorial on committing and signing off my changes, after which my first PR passed all the checks. I was thrilled at this point, waiting for my PR to be merged. I soon received two emails, the first relaying that my PR had been merged and a few pull requests later, a second one with an invitation to join the Layer5 organization on Github.
-
-
- Impressed by the process and being passionate about helping others, I soon
- began helping out with welcoming newcomers in the Layer5 Community and a happy two months later, I am elated to write that I have helped and held the hand of many-a contributors into Open-Source, offering them the same warm welcome that I had received. I was soon promoted to become a MeshMate. Apart from adding another feather to my cap, this also helped me enhance my own skill set and reach in a dozen different directions.The most intriguing fact about the Layer5 community is how welcoming it is. You can contribute something, even as a beginner, no matter how small your skillset is. I have been through the same journey and I recommend it to everyone reading. Experience an open-source community with Layer5 today! Once you’re set up on Slack, do send me a ping to
- say hi. The exciting part, we might even meet as MeshMates 😉
-
-
- \- Tanuj, Ruth, and Kelechi
-
-
+---
+title: "Announcing a new line of MeshMates"
+date: 2020-09-25 08:00:00 +0000
+author: Our MeshMates with 🤍
+thumbnail: ./meshmate-announcement.webp
+darkthumbnail: ./meshmate-announcement.webp
+category: Announcements
+tags:
+ - Community
+ - MeshMate
+published: true
+redirect_from:
+ - /blog/community/announcing-meshmates/
+---
+
+
+
+import Ruth from "./meshmate-ruth-ikegah.webp";
+import Kelechi from "./meshmate-kelechi-precious.webp";
+import Tanuj from "./meshmate-tanuj-agarwal.webp";
+
+
+
+
+
+
Layer5 MeshMates are committed to helping community members be successful contributors. MeshMates aid in identifying areas of projects to engage within, working groups to join, and in helping community members grow in their open source and cloud native knowledge. By connecting one-on-one, MeshMates will share tips on how to have the best community experience possible.
+
+
+
+ Tanuj Agarwal
+
+
+
+
+ I was introduced to the Layer5 community three months back. Being fairly new
+ to the world of open source and looking for new communities and technology to
+ delve into, I hopped onto the Layer5 bandwagon and was amazed by the warm
+ welcome I received from the wholesome community. I had done video animation
+ jobs on a small scale before, which is what led me to confidently take up the
+ task of creating a short intro jingle for the various community meetings
+ hosted on the Layer5 youtube channel. After iterating for about a week, I
+ finally came up with something worthwhile. And to my elation, it was accepted!
+ It still warms my heart to see the intro flash before every meeting.
+
+
+ Next up I started work on a next generation model of the layer5.io site. Being
+ a new project based on Gatsby and heavily relying on React, Javascript and
+ GraphQL, the site project was a perfect and challenging opportunity for me to
+ expand on my skill set. Speed learning my way through Gatsby, with a
+ continuous influx of help and helpful suggestions from my MeshMate, Kush
+ Trivedi and others within the community, I soon mastered the platform and have
+ spent weeks on creating countless issues and PRs in hopes of achieving the
+ project goals. A few months down the line, I started reviewing PRs and began
+ helping others contribute, something which I had never had the opportunity to
+ do before! After months of continuous effort, I am proud to write that I
+ recently joined as a maintainer on the project and was soon approached to be a
+ MeshMate, which I happily accepted. My learning graph has seen a soaring
+ positive tangent in the months I have been at Layer5 and I’m looking forward
+ to an even more educative and rewarding journey ahead 😊
+
+
+
+
+ Kelechi Precious Nwachukwu
+
+
+
+
+ It was the middle of the COVID-19 pandemic and being unproductive wasn't
+ something I can stomach. Wanting to expand on my technical domain knowledge, I
+ stumbled across an open-source challenge for women in tech with lists of
+ projects to contribute to by the Women of Open Source Community Africa
+ (WOSCA). My eyes landed on Layer5 and I haven’t looked back since.
+
+
+ A quick look through the repositories left me quaking in my boots. To give you
+ some much needed context and to give some hope to all the newbies out there, I
+ recently transitioned to working in technical domains from accounting and
+ managing construction site projects. Forever getting stuck trying to get my
+ hands on new tech and trying to find a way into the bewildering and humongous
+ tech domains , I didn't even understand some of the jargon, and was too
+ ashamed to ask questions. Stumbling through my first contribution, I somehow
+ made it to the finish line and to my happiness, was soon assigned another
+ task. Instead of complaining, I set out to study up on the issue and took a
+ peek at the other assignees in the repository to ensure that I was not the
+ only one taking inordinate amounts of time on an issue. To my surprise, I was
+ not.
+
+
+ I got working on the assignment and soon encountered issues that would
+ previously have made me quit. Thankfully, I decided to take a different
+ approach this time. I shared my challenge with the Layer5 community, and was
+ amazed at the immediate and abundant response I received. Since then, I have
+ helped other contributors get through their challenges, and have received an
+ invitation to join the organization as a member, and then as a MeshMate 😎 I
+ have been wholly satisfied with the learning opportunities and the friendly
+ environment that the Layer5 community has to offer. I have learned that I may
+ not be perfect, but by making full use of the resources provided to me, having
+ a supportive community by my side and by being open to learning and showing
+ determined courage in the face of difficulties, I can achieve anything!
+
+
+ Ruth Ikegah
+
+
+
+ The field of open source had always been intriguing to me. The idea of a
+ close-knit community working with an aim had me wanting to contribute myself.
+ Considering the fact that I have a small skill set (Donned the coder hat only
+ 6 months ago), Layer5 was a great community for me to start out with. I came
+ to know about the Layer5 community from the She Code Africa slack channel,
+ after which I visited the GitHub repository and hopped on to the Layer5 slack channel.
+
+
+ To my good luck, I received a warm welcome from the community and was able to attend a community meeting the day I joined. I made my way through the Github repos and stumbled across a beginner friendly issue. I started work but to my dismay, my PR failed to pass the DCO check at the final rung. Stuck and with low spirits, I talked to Lee (Layer5 Maintainer) and related my problems with the DCO check fail. He patiently assured me that first-time checks can be hard to get right and assigned me a MeshMate, Ashis Singh (read saviour 😳). I sent a message to Ashis and told him about the issues I was having in submitting my Pull Request. He led me through a step by step tutorial on committing and signing off my changes, after which my first PR passed all the checks. I was thrilled at this point, waiting for my PR to be merged. I soon received two emails, the first relaying that my PR had been merged and a few pull requests later, a second one with an invitation to join the Layer5 organization on Github.
+
+
+ Impressed by the process and being passionate about helping others, I soon
+ began helping out with welcoming newcomers in the Layer5 Community and a happy two months later, I am elated to write that I have helped and held the hand of many-a contributors into Open-Source, offering them the same warm welcome that I had received. I was soon promoted to become a MeshMate. Apart from adding another feather to my cap, this also helped me enhance my own skill set and reach in a dozen different directions.The most intriguing fact about the Layer5 community is how welcoming it is. You can contribute something, even as a beginner, no matter how small your skillset is. I have been through the same journey and I recommend it to everyone reading. Experience an open-source community with Layer5 today! Once you’re set up on Slack, do send me a ping to
+ say hi. The exciting part, we might even meet as MeshMates 😉
+
+
+ \- Tanuj, Ruth, and Kelechi
+
+
diff --git a/src/collections/blog/2020/2020-09-25-announcing-meshmates/meshmates.webp b/src/collections/blog/2020/2020-09-25-announcing-meshmates/meshmates.webp
new file mode 100644
index 000000000000..de157ff26b79
Binary files /dev/null and b/src/collections/blog/2020/2020-09-25-announcing-meshmates/meshmates.webp differ
diff --git a/src/collections/blog/2020/2020-11-17-layer5-at-kubecon-2020/index.mdx b/src/collections/blog/2020/2020-11-17-layer5-at-kubecon-2020/index.mdx
index bb4535fce805..e00eed8b1244 100644
--- a/src/collections/blog/2020/2020-11-17-layer5-at-kubecon-2020/index.mdx
+++ b/src/collections/blog/2020/2020-11-17-layer5-at-kubecon-2020/index.mdx
@@ -1,92 +1,91 @@
----
-title: "Layer5 at KubeCon NA"
-subtitle: "Join us at KubeCon North America 2020"
-date: 2020-11-17 11:10:00 +0000
-author: Lee Calcote
-thumbnail: ./kubecon-layer5.webp
-darkthumbnail: ./kubecon-layer5.webp
-category: Announcements
-tags:
- - KubeCon
-published: true
-redirect_from:
- - /blog/layer5-at-kubecon-na-2020/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import kubecon1 from "./kubecon1.webp";
-import kubecon2 from "./kubecon2.webp";
-import kubecon3 from "./kubecon3.webp";
-
-
-
-
- Thanks to our open source contributors, Layer5 projects are well represented
- at KubeCon. Attend our talks to help you get started with managing your own
- service mesh!
-
-
-
- KubeCon + CloudNativeCon NA 2020 is here and Layer5 is in the spotlight!
-
-As the ubiquity of service meshes unfolds so does the need for vendor and technology-agnostic
-interfaces to interact with them. The following three open specifications solving
-the challenge of interoperability, workload and performance management between service
-meshes: Service Mesh Performance (SMP) and Service Mesh Interface (SMI), Multi-Vendor
-Service Mesh Interoperation (Hamlet). Attend to learn what makes each of these specifications
-unique and why they are very much needed.
-
-
-
-
-
- CNCF SIG Network: Intro and Deep-Dive
-
-
-
November 20, 2020
-It’s the network! is the cry of every system administrator, every
-developer. With the increased prevalence of
- {" "}
-
-microservice-based distributed systems, it’s true - networking as a discipline
-has never been more critical in the efficient operation of cloud native
-deployments. Networking primitives, including load balancing, observability,
-authentication, authorization, policy, rate limiting, QoS, mesh networks, legacy
-infrastructure bridging, and so on are now receiving substantial development and
-investment throughout the industry and are the subject of focus of the CNCF SIG
-Network.
-
-See what the CNCF's Service Mesh Working Group has been up to. Join this talk for an intro to the SIG, its charter and a deeper discussion of current cloud native networking topics being advanced in this SIG. Current CNCF projects in-scope: Open Service Mesh, Kuma, Chaos Mesh, Ambassador, CNI, CoreDNS, Envoy, gRPC, Linkerd, NATS, Network Service Mesh.
-
-
-
-
-
-
-
- Meet the Maintainers: Service Mesh Interface
-
-
-
November 17, 2020
-Join the Service Mesh Interface (SMI) and Meshery maintainers for a Meet the Maintainers
-office hours. Learn all about Service Mesh Interface and how Meshery is the service
-mesh manager to determine the conformance of all service meshes in or out of compliance
-with the specification.
-
-
-
-
-
- We hope to see you at KubeCon + CloudNativeCon NA 2020. Be sure to say hello
- in the Layer5 Community!
-
-
-
-
+---
+title: "Layer5 at KubeCon NA"
+subtitle: "Join us at KubeCon North America 2020"
+date: 2020-11-17 11:10:00 +0000
+author: Lee Calcote
+thumbnail: ./kubecon-layer5.webp
+darkthumbnail: ./kubecon-layer5.webp
+category: Announcements
+tags:
+ - KubeCon
+published: true
+redirect_from:
+ - /blog/layer5-at-kubecon-na-2020/
+---
+
+
+import kubecon1 from "./kubecon1.webp";
+import kubecon2 from "./kubecon2.webp";
+import kubecon3 from "./kubecon3.webp";
+
+
+
+
+ Thanks to our open source contributors, Layer5 projects are well represented
+ at KubeCon. Attend our talks to help you get started with managing your own
+ service mesh!
+
+
+
+ KubeCon + CloudNativeCon NA 2020 is here and Layer5 is in the spotlight!
+
+As the ubiquity of service meshes unfolds so does the need for vendor and technology-agnostic
+interfaces to interact with them. The following three open specifications solving
+the challenge of interoperability, workload and performance management between service
+meshes: Service Mesh Performance (SMP) and Service Mesh Interface (SMI), Multi-Vendor
+Service Mesh Interoperation (Hamlet). Attend to learn what makes each of these specifications
+unique and why they are very much needed.
+
+
+
+
+
+ CNCF SIG Network: Intro and Deep-Dive
+
+
+
November 20, 2020
+It’s the network! is the cry of every system administrator, every
+developer. With the increased prevalence of
+ {" "}
+microservice-based distributed systems, it’s true - networking as a discipline
+has never been more critical in the efficient operation of cloud native
+deployments. Networking primitives, including load balancing, observability,
+authentication, authorization, policy, rate limiting, QoS, mesh networks, legacy
+infrastructure bridging, and so on are now receiving substantial development and
+investment throughout the industry and are the subject of focus of the CNCF SIG
+Network.
+
+See what the CNCF's Service Mesh Working Group has been up to. Join this talk for an intro to the SIG, its charter and a deeper discussion of current cloud native networking topics being advanced in this SIG. Current CNCF projects in-scope: Open Service Mesh, Kuma, Chaos Mesh, Ambassador, CNI, CoreDNS, Envoy, gRPC, Linkerd, NATS, Network Service Mesh.
+
+
+
+
+
+
+
+ Meet the Maintainers: Service Mesh Interface
+
+
+
November 17, 2020
+Join the Service Mesh Interface (SMI) and Meshery maintainers for a Meet the Maintainers
+office hours. Learn all about Service Mesh Interface and how Meshery is the service
+mesh manager to determine the conformance of all service meshes in or out of compliance
+with the specification.
+
+
+
+
+
+ We hope to see you at KubeCon + CloudNativeCon NA 2020. Be sure to say hello
+ in the Layer5 Community!
+
+
+
+
diff --git a/src/collections/blog/2020/2020-12-16-functional-testing-with-cypress-in-Meshery-ui/index.mdx b/src/collections/blog/2020/2020-12-16-functional-testing-with-cypress-in-Meshery-ui/index.mdx
index e6bc64ffebd4..620a720d6d4f 100644
--- a/src/collections/blog/2020/2020-12-16-functional-testing-with-cypress-in-Meshery-ui/index.mdx
+++ b/src/collections/blog/2020/2020-12-16-functional-testing-with-cypress-in-Meshery-ui/index.mdx
@@ -1,113 +1,113 @@
----
-title: "Functional Testing with Cypress in Meshery UI"
-subtitle: ""
-date: 2020-12-16 11:10:00 +0000
-author: Rodolfo Martinez Vega
-thumbnail: ./cypress-logo.webp
-darkthumbnail: ./cypress-logo.webp
-category: Meshery
-tags:
- - Testing
- - UI
-type: Blog
-product: Meshery
-resource: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import bestPracticesSelectingElementsImg from './best-practices-selecting-elements.webp';
-import cypressTestRunnerImg from './cypress-test-runner.webp';
-
-
-
-Cypress is the functional test tool used in development of Meshery UI. As a reliably test tool, Cypress works with ReactJS, VueJS, AngularJS and so on; it is agnostic of the framework you use. You can write all types of tests: end-to-end, integration, and unit tests.
-
-Tests allow you to ensure that the new code do not break the current one. They help you to develop and integrate new features faster and ensure everything will work after including your changes. The more tests you have, the more coverage you will have (and less likelihood of issues in production).
-
-### UI tests in Meshery
-
-Meshery has two web projects:
-
-- provider-ui: A ReactJS app that allows you to select the Provider to be used for Meshery
-- ui: Also a ReactJS app where you can do everything related with Meshery. It is the cloud native management plane.
-
-We create UI tests for both projects using Cypress. Also, we write two types of UI tests at the moment:
-- Integration: Test a specific functionality without backend communication (mocking requests and responses)
-- End-to-end: Test a whole flow like setting up Linkerd Service Mesh or running a SMI Performance Test sending requests and validating the responses from the back-end
-
-### How to write UI tests for Meshery
-
-If you are writting your first test, you can read and watch the great getting started from Cypress blog.
-
-Then, you have to add your test below `"provider-ui/cypress/integration"` or `"ui/cypress/integration"` folders (do not forget adding _spec in the filename).
-
-Here is a basic example of a test validating that Provider UI component exists:
-
-```javascript
-describe('Provider UI', () => {
- it('renders provider component', () => {
- cy
- .get('[data-cy=root]')
- .should('exist')
- })
-})
-```
-
-Please follow the best practices recommended by Cypress.
-One of the most important is to use or add the `"data-cy"` attribute to the element you want to interact to:
-
-
-
Best Practices Selecting Elements
-
-### Run your test!
-
-Once you have written your test, it is time to execute it locally:
-
-1. First, you have to run the back-end executing this command at the root project folder:
-
-```bash
-$ make run-local
-```
-
-2. Then, run the front-end project (i.e. provider-ui)
-
-```bash
-$ make run-provider-ui-dev
-```
-
-3. Finally, in `"provider-ui"` folder, run all the tests with:
-
-```bash
-$ npm run cy:run
-```
-
-If everything went well, you will see "All specs passed!" message. Congrats!
-
-You can also execute, debug and see in real time your test by executing:
-
-```bash
-$ npm run cy:open
-```
-
-this will open the Cypress Test Runner:
-
-
-
Cypress Test Runner
-
-just double-click on your test and a window browser will be opened and you will see your testing running!
-
-#### What’s next?
-
-To improve writting better tests, I recommend that you watch:
-
-- Watch the Meshery Development Meeting (Nov 4th, 2020) where I gave a demo running UI tests on the Meshery project (slides)
-- Tutorial Videos from Cypress blog.
-- The Brian Mann – I see your point, but… (Part 1) YouTube video where he gives pro tips writting tests in Cypress.
-
-If you have questions, do not hesitate to ask to the Meshery community on Slack :)
-
-Happy testing!
-
-
-
+---
+title: "Functional Testing with Cypress in Meshery UI"
+subtitle: ""
+date: 2020-12-16 11:10:00 +0000
+author: Rodolfo Martinez Vega
+thumbnail: ./cypress-logo.webp
+darkthumbnail: ./cypress-logo.webp
+category: Meshery
+tags:
+ - Testing
+ - UI
+type: Blog
+product: Meshery
+resource: true
+published: true
+---
+
+
+import bestPracticesSelectingElementsImg from "./best-practices-selecting-elements.webp";
+import cypressTestRunnerImg from "./cypress-test-runner.webp";
+
+
+
+Cypress is the functional test tool used in development of Meshery UI. As a reliably test tool, Cypress works with ReactJS, VueJS, AngularJS and so on; it is agnostic of the framework you use. You can write all types of tests: end-to-end, integration, and unit tests.
+
+Tests allow you to ensure that the new code do not break the current one. They help you to develop and integrate new features faster and ensure everything will work after including your changes. The more tests you have, the more coverage you will have (and less likelihood of issues in production).
+
+### UI tests in Meshery
+
+Meshery has two web projects:
+
+- provider-ui: A ReactJS app that allows you to select the Provider to be used for Meshery
+- ui: Also a ReactJS app where you can do everything related with Meshery. It is the cloud native management plane.
+
+We create UI tests for both projects using Cypress. Also, we write two types of UI tests at the moment:
+- Integration: Test a specific functionality without backend communication (mocking requests and responses)
+- End-to-end: Test a whole flow like setting up Linkerd Service Mesh or running a SMI Performance Test sending requests and validating the responses from the back-end
+
+### How to write UI tests for Meshery
+
+If you are writting your first test, you can read and watch the great getting started from Cypress blog.
+
+Then, you have to add your test below `"provider-ui/cypress/integration"` or `"ui/cypress/integration"` folders (do not forget adding _spec in the filename).
+
+Here is a basic example of a test validating that Provider UI component exists:
+
+```
+describe('Provider UI', () => {
+ it('renders provider component', () => {
+ cy
+ .get('[data-cy=root]')
+ .should('exist')
+ })
+})
+```
+
+Please follow the best practices recommended by Cypress.
+One of the most important is to use or add the `"data-cy"` attribute to the element you want to interact to:
+
+
+
Best Practices Selecting Elements
+
+### Run your test!
+
+Once you have written your test, it is time to execute it locally:
+
+1. First, you have to run the back-end executing this command at the root project folder:
+
+```bash
+$ make run-local
+```
+
+2. Then, run the front-end project (i.e. provider-ui)
+
+```bash
+$ make run-provider-ui-dev
+```
+
+3. Finally, in `"provider-ui"` folder, run all the tests with:
+
+```bash
+$ npm run cy:run
+```
+
+If everything went well, you will see "All specs passed!" message. Congrats!
+
+You can also execute, debug and see in real time your test by executing:
+
+```bash
+$ npm run cy:open
+```
+
+this will open the Cypress Test Runner:
+
+
+
Cypress Test Runner
+
+just double-click on your test and a window browser will be opened and you will see your testing running!
+
+#### What’s next?
+
+To improve writting better tests, I recommend that you watch:
+
+- Watch the Meshery Development Meeting (Nov 4th, 2020) where I gave a demo running UI tests on the Meshery project (slides)
+- Tutorial Videos from Cypress blog.
+- The Brian Mann – I see your point, but… (Part 1) YouTube video where he gives pro tips writting tests in Cypress.
+
+If you have questions, do not hesitate to ask to the Meshery community on Slack :)
+
+Happy testing!
+
+
+
diff --git a/src/collections/blog/2021/2021-02-04-meet-the-maintainer-michael-gfeller/index.mdx b/src/collections/blog/2021/2021-02-04-meet-the-maintainer-michael-gfeller/index.mdx
index c6d2f838658a..a520c898f8c5 100644
--- a/src/collections/blog/2021/2021-02-04-meet-the-maintainer-michael-gfeller/index.mdx
+++ b/src/collections/blog/2021/2021-02-04-meet-the-maintainer-michael-gfeller/index.mdx
@@ -1,193 +1,181 @@
----
-title: "Meet the Maintainer: Michael Gfeller"
-subtitle: "An interview series with Layer5 Maintainers"
-date: 2021-02-04 10:30:05 -0530
-author: Shriti Chandra
-thumbnail: "./michael-gfeller-layer5-maintainer.webp"
-darkthumbnail: "./michael-gfeller-layer5-maintainer.webp"
-category: "Community"
-tags:
- - Community
-published: true
-interviewer: Shriti Chandra
-interviewee: Michael Gfeller
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import img from "./michael-gfeller-layer5-maintainer.webp";
-import { MeetTheMaintainer } from "../../MeetTheMaintainer.style";
-import { Link } from "gatsby";
-import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-import MoireCircles from "./Line Moire.svg";
-import MoireLines from "./Circle Moire.svg";
-
-
-
-
-
-
Kicking off Layer5's Meet the Maintainer series, we have Michael Gfeller. Michael is an avid research enthusiast in addition to holding the title of Chief Engineer at his day job. With exhaustive interests ranging from software architecture to systems security, he has been working with cloud architecture for the past four years.
-
-
-
-Shriti:
-Michael, thank you for joining me today. Many people inside and outside of the Layer5 Community have seen the affects of your contributions, but may not know the backstory as to who Michael is and how you arrived at your maintainer role. Indulge us. How did you come across the Layer5 community? What made you stay?
-
-
-
-Michael:
-Hey Shriti, thank you for having me. If I remember correctly, I was looking for a professional focus area earlier this year, and landed on service meshes. I had worked with service meshes before, which piqued my initial interest. I had worked with Istio as part of my work for some time, and in the same context I stumbled across Meshery. I wasn’t able to dig deep in Meshery back then, but the concept sounded fascinating to me. Additionally, I had been benefiting from open source, both personally and professionally for a long time, but apart from a few minor contributions, I had never been able to give back to the community. I hoped to correct that.
-
-
-I re-discovered Meshery and the Layer5 community, listened to a recording of a community meeting, and read a couple of blog posts describing the community and member experience posts. One that stood out for me was a post by MeshMate Nikhil Ladha. Going by his words, it appeared to be a warm, diverse and active community. My suspicions were confirmed when I joined. Layer5 offers a wholesome, interactive community in addition to unbiasedly providing help and guidance around the virtual corner.
-
-
-
-Shriti:
-
-Layer5 projects has a number of active, open source projects. You’ve been consistently contributing to a few of them. Which one(s) are you currently focusing on?
-
-Psst. Also, which one’s your favorite? I won’t tell.
-
-
-
-Michael:
-
-I’m a technical architect and programmer, which made the backend, especially the adapters, a natural choice for me. It involves both contributing to the management plane, but also looking at and using service meshes from an architectural point of view. The possible implementations of service meshes is an area that has been particularly fascinating for me.
-
-
-I’d probably continue to work with the Meshery adapters for now before moving on to other areas of the project. Haha, I would probably name the Meshery Adapter Library as my favorite Layer5 project till date.
-
-
-
-Shriti:
-
Have you worked with any other open source project? How does Layer5 compare?
-
-
-
-Michael:
-
-I have worked and collaborated with several open source communities before, including Eclipse Modelling Framework and Apache ServiceMix . I couldn’t possibly make a very accurate comparison, given by limited interaction with other communities, but the Layer5 community stands out based on the unique and extremely inclusive approach it takes towards upholding community values.
-
-
-
-Shriti:
-What is so fascinating about service meshes?
-
-
-
-
-
-Michael:
-
-I find meshes intriguing in general. Meshes can look intricate, layered and complicated at a first glance, and yet they are built on the most basic principles. For me, meshes are visual structures, complete with an aesthetic and artistic dimension.
-
-
Fun Fact: Overlapping meshes resulting in Moiré patterns are an example of this. They appealed to me from a young age, and I learned about their mathematics from my mathematics teacher.
-
-
-
-Shriti:
-Fascinating. Why did you pick service meshes specifically though?
-
-
-
-
-Michael:
-An increasing number of applications nowadays consist of distributed services, both in the cloud and on-premises, in mixed and hybrid environments. Many legacy applications are in express need of modernisation, consuming and being consumed by cloud native applications. Introducing microservices, also by refactoring monolithic applications, increases the complexity of the service landscape. By delegating cross-cutting infrastructure concerns like security, traffic management, resilience, and observability to the services mesh, some of the complexity is moved from the applications to the service mesh, allowing application developers to focus on business logic. A concern in these distributed, dynamic and scalable systems is that the security also needs to scale. If security doesn’t scale, it becomes very challenging to handle such systems. Services meshes today are already able to support many of these scenarios, and are continuously improving.
-
-
-
-Service meshes are complex but that is something I enjoy attempting as a challenge, to have control and overview and make it appear simple, investing into automating options. Another field that I’m excited to learn about continuously is related to the security of distributed systems, and how service meshes contribute to implementing a zero trust network architecture.
-
-Haha. Leading on that, what should Meshery dream about next? What can we hope to contribute to the service mesh landscape in your opinion?
-
-
-
-Michael:
-Meshery currently does a great job of providing a neutral platform. Continuing in that direction would be a superb base plan. Enabling innovative applications from vendors, supporting all service meshes, integrating best practice methods, and implementing the SMP and SMI abstractions would probably score the top five positions in Meshery’s new year resolutions in 2021.
-
-
-
-
-Shriti:
-Interesting. Do expand on that. What do you think Meshery could offer, in addition to what it already does?
-
-
-
-
-Michael:
-At the moment, Meshery provides a management plane solution and provides support for the SMI and Service Mesh Performance (SMP) specifications. Helpful additions in the future should be the configuration based best practices, especially with regards to security and to possibly extend to owning up specific routes on security. For instance by verifying that the recommendations outlined in the NIST report “Building Secure Microservices-based Applications Using Service-Mesh Architecture” by Ramaswamy Chandramouli and Zack Butcher.
-
-
-
-
-Shriti:
-What are today's challenges when working with service meshes?
-
-
-
-
-Michael:
-I can’t claim to have worked with many implementations, and to have a good overview and wide experience. A lot of the complexity is already handled, but there is still enough to decide and implement for each solution. The solution makes for a challenging but highly interesting task. Additionally, there are a variety of different solutions from different vendors, which is excellent but it also makes it hard to know which would be the best fit for a given situation. Here, again, Meshery can be of invaluable help.
-
-
-
-
-Shriti:
-That’s good to hear. What do you think we should look forward to with respect to service mesh development?
-
-
-
-
-Michael:
-The service mesh promise holds a lot of potential, for instance for modernization and ease of use. A lot appears to be happening these times. It will be interesting to see how serverless solutions will be integrated. Enabling a seamless implementation experience for solutions embracing multi-cloud, on-prem and legacy systems is also something to look forward to. Additionally, service meshes are aimed at making your architecture more secure and stable, which makes security a big concern for any service mesh provider. Improvements along these points will be topics I’ll be watching out for over the next few years.
-
-
-
-
-Shriti:
- Ah while I have you here, let me get more reading recommendations lined up. Cloud Native and especially, the field of service meshes evolving exceptionally fast. Keeping up with all the developments can be challenging. Which resources do you use to stay up-to-date?
-
-
-
-Michael:
-Service mesh implementations consist of many components, and I try to stay up to date in general. Try to follow as much as possible conferences and vendor announcements, blog posts etc. mainly by following related Twitter accounts. Also, trying to find some time to explore various solutions. Lee’s books are of course an excellent source. Another book I can recommend is Zero Trust Networks book by Gilman and Barth. It really helped me to understand how service meshes relate to zero trust network architecture and can help to move towards it.
-
-
-
-Shriti:
What does being a Meshery maintainer mean to you? How has being a maintainer impacted your full-time role?
-
-
-
-Michael:
-I take my role as a Meshery maintainer with its benefits and responsibilities. For one, it means to be able to give back to the community. I meet a lot of interesting and friendly people from around the globe, learning about their culture at the same time. Additionally, Open Source allows me to work on and dive into tasks as I like, making it easy to integrate the work with my existing work schedule. It also allows me to learn a lot, expanding on my understanding of service meshes, keeping up with the latest developments in the field, and also giving me the opportunity to witness first-hand how others are using them. This has a quite direct impact on my full-time role, complementing the work I do.
-
-
-
-Shriti:
Do you have any advice for individuals hopeful to become Layer5 contributors or potentially maintainers?
-
-
-
-Michael:
-A general love for software development combined with a readiness to help out newcomers and participating in the growing community is the key.
-
-
-Come and visit, there is something for everyone, be it frontend, backend, CI/CD, website, documentation, standards, interfacing with other communities, and more. The friendly community members and the meshmates will provide support and guidance. Browse the Layer5 and Meshery websites and the repositories on GitHub, where issues suitable for newcomers are especially tagged.
-
-
-
-
In his relatively short tenure at Layer5, Michael has already delivered a wave of meshy contributions enhancing the Meshery adapters and improving upon Meshery’s architecture. With a penchant for looking behind the curtain and tightening loose cogs until they run to perfection, Michael's impactful and consistent contributions have him taking his place as Meshery maintainer. The Meshery project moves an impressive pace thanks to maintainers like Michael.
-
-
-
-"Be like Mike". Join the Layer5 Slack and say hi.
-
-
-
+---
+title: "Meet the Maintainer: Michael Gfeller"
+subtitle: "An interview series with Layer5 Maintainers"
+date: 2021-02-04 10:30:05 -0530
+author: Shriti Chandra
+thumbnail: "./michael-gfeller-layer5-maintainer.webp"
+darkthumbnail: "./michael-gfeller-layer5-maintainer.webp"
+category: "Community"
+tags:
+ - Community
+published: true
+interviewer: Shriti Chandra
+interviewee: Michael Gfeller
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import img from "./michael-gfeller-layer5-maintainer.webp";
+import { MeetTheMaintainer } from "../../MeetTheMaintainer.style";
+import { Link } from "gatsby";
+import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
+import MoireCircles from "./Line Moire.svg";
+import MoireLines from "./Circle Moire.svg";
+
+
+
+
+
+
Kicking off Layer5's Meet the Maintainer series, we have Michael Gfeller. Michael is an avid research enthusiast in addition to holding the title of Chief Engineer at his day job. With exhaustive interests ranging from software architecture to systems security, he has been working with cloud architecture for the past four years.
+
+
+Shriti:
+Michael, thank you for joining me today. Many people inside and outside of the Layer5 Community have seen the affects of your contributions, but may not know the backstory as to who Michael is and how you arrived at your maintainer role. Indulge us. How did you come across the Layer5 community? What made you stay?
+
+
+
+Michael:
+Hey Shriti, thank you for having me. If I remember correctly, I was looking for a professional focus area earlier this year, and landed on service meshes. I had worked with service meshes before, which piqued my initial interest. I had worked with Istio as part of my work for some time, and in the same context I stumbled across Meshery. I wasn’t able to dig deep in Meshery back then, but the concept sounded fascinating to me. Additionally, I had been benefiting from open source, both personally and professionally for a long time, but apart from a few minor contributions, I had never been able to give back to the community. I hoped to correct that.
+
+I re-discovered Meshery and the Layer5 community, listened to a recording of a community meeting, and read a couple of blog posts describing the community and member experience posts. One that stood out for me was a post by MeshMate Nikhil Ladha. Going by his words, it appeared to be a warm, diverse and active community. My suspicions were confirmed when I joined. Layer5 offers a wholesome, interactive community in addition to unbiasedly providing help and guidance around the virtual corner.
+
+
+
+Shriti:
+
+Layer5 projects has a number of active, open source projects. You’ve been consistently contributing to a few of them. Which one(s) are you currently focusing on?
+
+Psst. Also, which one’s your favorite? I won’t tell.
+
+
+
+Michael:
+
+I’m a technical architect and programmer, which made the backend, especially the adapters, a natural choice for me. It involves both contributing to the management plane, but also looking at and using service meshes from an architectural point of view. The possible implementations of service meshes is an area that has been particularly fascinating for me.
+
+
+I’d probably continue to work with the Meshery adapters for now before moving on to other areas of the project. Haha, I would probably name the Meshery Adapter Library as my favorite Layer5 project till date.
+
+
+
+Shriti:
+
Have you worked with any other open source project? How does Layer5 compare?
+
+
+
+Michael:
+
+I have worked and collaborated with several open source communities before, including Eclipse Modelling Framework and Apache ServiceMix . I couldn’t possibly make a very accurate comparison, given by limited interaction with other communities, but the Layer5 community stands out based on the unique and extremely inclusive approach it takes towards upholding community values.
+
+
+
+Shriti:
+What is so fascinating about service meshes?
+
+
+
+
+
+Michael:
+
+I find meshes intriguing in general. Meshes can look intricate, layered and complicated at a first glance, and yet they are built on the most basic principles. For me, meshes are visual structures, complete with an aesthetic and artistic dimension.
+
+
Fun Fact: Overlapping meshes resulting in Moiré patterns are an example of this. They appealed to me from a young age, and I learned about their mathematics from my mathematics teacher.
+
+
+
+Shriti:
+Fascinating. Why did you pick service meshes specifically though?
+
+
+
+
+Michael:
+An increasing number of applications nowadays consist of distributed services, both in the cloud and on-premises, in mixed and hybrid environments. Many legacy applications are in express need of modernisation, consuming and being consumed by cloud native applications. Introducing microservices, also by refactoring monolithic applications, increases the complexity of the service landscape. By delegating cross-cutting infrastructure concerns like security, traffic management, resilience, and observability to the services mesh, some of the complexity is moved from the applications to the service mesh, allowing application developers to focus on business logic. A concern in these distributed, dynamic and scalable systems is that the security also needs to scale. If security doesn’t scale, it becomes very challenging to handle such systems. Services meshes today are already able to support many of these scenarios, and are continuously improving.
+
+
+Service meshes are complex but that is something I enjoy attempting as a challenge, to have control and overview and make it appear simple, investing into automating options. Another field that I’m excited to learn about continuously is related to the security of distributed systems, and how service meshes contribute to implementing a zero trust network architecture.
+
+Haha. Leading on that, what should Meshery dream about next? What can we hope to contribute to the service mesh landscape in your opinion?
+
+
+
+Michael:
+Meshery currently does a great job of providing a neutral platform. Continuing in that direction would be a superb base plan. Enabling innovative applications from vendors, supporting all service meshes, integrating best practice methods, and implementing the SMP and SMI abstractions would probably score the top five positions in Meshery’s new year resolutions in 2021.
+
+
+
+Shriti:
+Interesting. Do expand on that. What do you think Meshery could offer, in addition to what it already does?
+
+
+
+Michael:
+At the moment, Meshery provides a management plane solution and provides support for the SMI and Service Mesh Performance (SMP) specifications. Helpful additions in the future should be the configuration based best practices, especially with regards to security and to possibly extend to owning up specific routes on security. For instance by verifying that the recommendations outlined in the NIST report “Building Secure Microservices-based Applications Using Service-Mesh Architecture” by Ramaswamy Chandramouli and Zack Butcher.
+
+
+
+Shriti:
+What are today's challenges when working with service meshes?
+
+
+
+Michael:
+I can’t claim to have worked with many implementations, and to have a good overview and wide experience. A lot of the complexity is already handled, but there is still enough to decide and implement for each solution. The solution makes for a challenging but highly interesting task. Additionally, there are a variety of different solutions from different vendors, which is excellent but it also makes it hard to know which would be the best fit for a given situation. Here, again, Meshery can be of invaluable help.
+
+
+
+Shriti:
+That’s good to hear. What do you think we should look forward to with respect to service mesh development?
+
+
+
+Michael:
+The service mesh promise holds a lot of potential, for instance for modernization and ease of use. A lot appears to be happening these times. It will be interesting to see how serverless solutions will be integrated. Enabling a seamless implementation experience for solutions embracing multi-cloud, on-prem and legacy systems is also something to look forward to. Additionally, service meshes are aimed at making your architecture more secure and stable, which makes security a big concern for any service mesh provider. Improvements along these points will be topics I’ll be watching out for over the next few years.
+
+
+
+Shriti:
+ Ah while I have you here, let me get more reading recommendations lined up. Cloud Native and especially, the field of service meshes evolving exceptionally fast. Keeping up with all the developments can be challenging. Which resources do you use to stay up-to-date?
+
+
+
+Michael:
+Service mesh implementations consist of many components, and I try to stay up to date in general. Try to follow as much as possible conferences and vendor announcements, blog posts etc. mainly by following related Twitter accounts. Also, trying to find some time to explore various solutions. Lee’s books are of course an excellent source. Another book I can recommend is Zero Trust Networks book by Gilman and Barth. It really helped me to understand how service meshes relate to zero trust network architecture and can help to move towards it.
+
+
+
+Shriti:
What does being a Meshery maintainer mean to you? How has being a maintainer impacted your full-time role?
+
+
+
+Michael:
+I take my role as a Meshery maintainer with its benefits and responsibilities. For one, it means to be able to give back to the community. I meet a lot of interesting and friendly people from around the globe, learning about their culture at the same time. Additionally, Open Source allows me to work on and dive into tasks as I like, making it easy to integrate the work with my existing work schedule. It also allows me to learn a lot, expanding on my understanding of service meshes, keeping up with the latest developments in the field, and also giving me the opportunity to witness first-hand how others are using them. This has a quite direct impact on my full-time role, complementing the work I do.
+
+
+
+Shriti:
Do you have any advice for individuals hopeful to become Layer5 contributors or potentially maintainers?
+
+
+
+Michael:
+A general love for software development combined with a readiness to help out newcomers and participating in the growing community is the key.
+
+Come and visit, there is something for everyone, be it frontend, backend, CI/CD, website, documentation, standards, interfacing with other communities, and more. The friendly community members and the meshmates will provide support and guidance. Browse the Layer5 and Meshery websites and the repositories on GitHub, where issues suitable for newcomers are especially tagged.
+
+
+
+
In his relatively short tenure at Layer5, Michael has already delivered a wave of meshy contributions enhancing the Meshery adapters and improving upon Meshery’s architecture. With a penchant for looking behind the curtain and tightening loose cogs until they run to perfection, Michael's impactful and consistent contributions have him taking his place as Meshery maintainer. The Meshery project moves an impressive pace thanks to maintainers like Michael.
+
+
+"Be like Mike". Join the Layer5 Slack and say hi.
+
+
+
diff --git a/src/collections/blog/2021/2021-02-07-meshkit-and-meshery-adapter-library/index.mdx b/src/collections/blog/2021/2021-02-07-meshkit-and-meshery-adapter-library/index.mdx
index f5810c35b758..76d2c59cb468 100644
--- a/src/collections/blog/2021/2021-02-07-meshkit-and-meshery-adapter-library/index.mdx
+++ b/src/collections/blog/2021/2021-02-07-meshkit-and-meshery-adapter-library/index.mdx
@@ -1,6 +1,6 @@
---
title: "Introducing Meshkit and the Meshery Adapter Library"
-subtitle: "Making the DX of cloud native infrastructure management easy."
+subtitle: "Making the DX of service mesh management easy."
date: 2021-02-07 12:12:12 +0002
author: Michael Gfeller
thumbnail: ./meshery-adapter-library-overview.webp
@@ -16,9 +16,9 @@ resource: true
published: true
---
-import { BlogWrapper } from "../../Blog.style.js";
+
import { MeshkitMesheryAdapterLib } from "./MeshkitMesheryAdapterLib.style";
-import { Link } from "gatsby";
+
import mesheryAdapterLibrary from "./meshery-adapter-library.svg";
import malOverview from "./meshery-adapter-library-overview.webp";
@@ -26,20 +26,21 @@ import malOverview from "./meshery-adapter-library-overview.webp";
-
The Meshery v0.5.0 release includes two new libraries: MeshKit and Meshery Adapter Library.
+
+The Meshery v0.5.0 release includes two new libraries: MeshKit and Meshery Adapter Library.
-These two libraries improve contributor experience and development speed by reducing the burden of sustaining the plethora of Meshery adapters, allowing contributors to focus on exposing any given infrastructure component's differentiated value,
-instead of having to redundantly implement plumbing for managing cloud native infrastructure.
+These two libraries improve contributor experience and development speed by reducing the burden of sustaining the plethora of Meshery adapters, allowing contributors to focus on exposing a service mesh's differentiated value,
+instead of having to redundantly implement plumbing for managing service meshes.
## MeshKit
-MeshKit was formerly named `gokit` and was renamed recently to align with the other Meshery components' names (and avoid confusion with the `go-kit` project). MeshKit can be considered a derivative of `go-kit` with specific focus on cloud native management.
+MeshKit was formerly named `gokit` and was renamed recently to align with the other Meshery components' names (and avoid confusion with the `go-kit` project). MeshKit can be considered a derivative of `go-kit` with specific focus on service mesh management.
-In the Meshery v0.5.0 release, MeshKit has been enhanced and expanded substantially. Considering that the MeshKit library provides broadly useful functionality, it is used in a growing number of Meshery components. It is intended to be one of the top level libraries in the Meshery ecosystem.
Meshkit provides functionality useful across all Meshery components.
+In the Meshery v0.5.0 release, MeshKit has been enhanced and expanded substantially. Considering that the MeshKit library provides broadly useful functionality, it is used in a growing number of Meshery components. It is intended to be one of the top level libraries in the Meshery ecosystem.
Meshkit provides functionality useful across all Meshery components.
-MeshKit is a toolkit for Layer5’s microservices, and is positioned to become Layer5’s middleware component for Layer5’s microservices, leveraging other libraries like `go-kit/kit`. In complement to functionality provided by any given cloud native infrastructure component, its purpose is to provide implementations for common cross-cutting concerns like error handling, logging, and tracing. Uniform error handling and logging across all Meshery components helps to implement efficient tooling for observability, monitoring and troubleshooting. The library provides some common data models for Meshery and Meshery's ecosystem of extensions.
+MeshKit is a toolkit for Layer5’s microservices, and is positioned to become Layer5’s middleware component for Layer5’s microservices, leveraging other libraries like `go-kit/kit`. In complement to functionality provided by a service mesh, its purpose is to provide implementations for common cross-cutting concerns like error handling, logging, and tracing. Uniform error handling and logging across all Meshery components helps to implement efficient tooling for observability, monitoring and troubleshooting. The library provides some common data models for Meshery, notably for Service Mesh Interface conformance testing, and Kubernetes' `kubeconfig`.
Another central component in Meshkit is the `utils` package.
@@ -130,7 +131,7 @@ spec:
## Meshery Adapters
-Meshery adapters are management plane components and manage the lifecycle of cloud native infra. This includes installation and deletion, configuration, and verification that an installation follows recommended practices. As example use of Meshery adapters is for purposes of compliance verification, actively attesting whether whether infrastructure complies to an open standard, like that of Service Mesh Interface. Meshery adapters support management of multiple versions of their respective capabilites and also come bundled with sample applications that can be deployed for easy and quick exploration of infrastructure (or other) capabilities.
Meshery adapters extend Meshery's core functionality housed within Meshery Server, often deepening Meshery's ability to manage the lifecycle infratructure, but not limited to those use cases. Adapters have been known to act as engineering workflow facilititors, providing gate reviews, sending emails, and so on.
+Meshery adapters are management plane components and manage the lifecycle of service meshes. This includes installation and deletion, configuration, and verification that an installation follows recommended practices. In addition, Meshery adapters can assess to what extent a service mesh complies to the Service Mesh Interface standard. Meshery adapters support management of multiple versions of their respective service mesh and also come bundled with sample applications that can be deployed for easy and quick exploration of service mesh capabilities.
Meshery adapters manage the lifecycle of service meshes.
A Meshery adapter is a gRPC server that exposes the `MeshServiceServer` interface:
@@ -145,15 +146,15 @@ type MeshServiceServer interface {
}
```
-- `CreateInstance` sets up the Kubernetes client. It does not, as the name might imply, create an instance of an infrastructure component.
-- `Name` returns the name of the infrastructure component, configured in the adapter.
-- `SupportedOperations` returns all supported operations, configured in the adapter. An operation is e.g. the installation of any given cloud native infrastructure component or service.
+- `CreateMeshInstance` sets up the Kubernetes client. It does not, as the name might imply, create an instance of a service mesh.
+- `MeshName` returns the name of the mesh, configured in the adapter.
+- `SupportedOperations` returns all supported operations, configured in the adapter. An operation is e.g. the installation of a service mesh.
- `ApplyOperation` executes the operation specified in the request. It is one of the supported operations.
- `StreamEvents` allows sending events from the server to the client.
-This API is one of the extension points of Meshery, making it easy to add support for new cloud native technologies to Meshery. Meshery adapters abstract away differences in installation and configuration of the various technologies. Various cloud native technologies are installed and configured in their own way. For instance, some projects have their own installer, like `istioctl` for Istio, while others use Helm charts, like Consul. One of the purposes of Meshery adapters is to abstract these differences away.
It's important to note, however, that Meshery Adapters allow Meshery to interface with each managed system uniquely, and not treat those systems uniformly by only offering the lowest common denominator of functionality, but instead by exposing that system's differentiated value to users.
-
+This API is one of the extension points of Meshery, making it easy to add support for new service meshes to Meshery. Meshery adapters abstract away differences in installation and configuration of the various service meshes.
Adapters allow Meshery to interface with the different service meshes, exposing their differentiated value to users.
+In general, the various service mesh implementations are installed and configured in their own way. For instance, some service meshes have their own installer, like `istioctl` for Istio, while others use Helm charts, like Consul. One of the purposes of Meshery adapters is to abstract these differences away.
## Meshery Adapter Library
@@ -165,10 +166,10 @@ It reduces the amount of boilerplate code in the adapters substantially, making
Also, it means new adapters can be implemented quickly, as only configuration and operations that differ between services meshes need to be implemented.
-
+
The Meshery Adapter Library provides a common and consistent set of
functionality that Meshery adapters use for managing the lifecycle of
- cloud infrastructure and their workloads.
+ service meshes and their workloads.
The initial commit was submitted on October 6th, 2020 based on a refactoring effort in the adapter for the Kuma service mesh. Within a few months, several adapters have been refactored or implemented from scratch based on the Meshery Adapter Library.
@@ -209,7 +210,7 @@ The figure below illustrates this and the usage of the library in an adapter.
@@ -224,7 +225,7 @@ The `service` is a struct that holds all the parameters that specify an adapter
Extracting common code from adapters to the two new libraries has proven to be a worthwhile investment. It led to cleaner code as well as cleaner application architecture, shortened implementation time for new adapters considerably, and upleveled the quality of Meshery's adapters through consistency of implementation.
-
P.S. If these topics excite you and you want to explore the beautiful realm of cloud native infrastructure, come and say "Hi" on the community Slack and you are sure to be warmly welcomed. 😀
+
P.S. If these topics excite you and you want to explore the beautiful realm of service meshes, come and say "Hi" on the community Slack and you are sure to be warmly welcomed. 😀
diff --git a/src/collections/blog/2021/2021-04-05-meshmate-of-the-year-2020-nikhil-ladha/index.mdx b/src/collections/blog/2021/2021-04-05-meshmate-of-the-year-2020-nikhil-ladha/index.mdx
index 34f490cb80bb..b8a07b882fa9 100644
--- a/src/collections/blog/2021/2021-04-05-meshmate-of-the-year-2020-nikhil-ladha/index.mdx
+++ b/src/collections/blog/2021/2021-04-05-meshmate-of-the-year-2020-nikhil-ladha/index.mdx
@@ -1,203 +1,194 @@
----
-title: "MeshMate of the Year 2020: Nikhil Ladha"
-subtitle: ""
-date: 2021-04-05 09:10:00 +0000
-author: Lee Calcote
-thumbnail: ./MeshMate-of-the-Year-2020-Nihkil-Ladha.webp
-darkthumbnail: ./MeshMate-of-the-Year-2020-Nihkil-Ladha.webp
-category: Community
-tags:
- - Community
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import MMoY2020 from "./meshmate-of-the-year-2020.webp";
-import Blockquote from "../../../../reusecore/Blockquote";
-import BlockquoteAlt from "../../../../reusecore/Blockquote/Blockquote-alt-style";
-import { Link } from "gatsby";
-
-import MeshMate from "../../../../assets/images/meshmate/meshmate-stack.svg";
-import MMOYNikhil from "./MeshMate-of-the-Year-2020-Nihkil-Ladha.webp";
-
-
-
-
- If you are in the Layer5 Community, no doubt, you've met
-
- Nikhil Ladha
- . If not, I recommend that you join the community and get to know Nikhil.
- He's the Layer5 MeshMate of the Year and here's why: Nikhil consistently volunteers
- to uplift and support others in the community, freely sharing of his time and knowledge.
- His actions embody and espouse the pay-it-forward culture of Layer5.
-
-
-
-
-2020 was a noteworthy year in many ways. Nikhil's committment to the people and projects of the Layer5 community will forever be at the top of list of mentionables I and others will recall of last year. It was in 2019, though, that Nikhil's journey in the Layer5 community started and where he first began helping build our healthy, inclusive, and diverse community and our industry-leading, innovate open source projects. Nikhil's natural disposition to mentoring others and his stewardship on various projects make him a successful MeshMate.
-
-
What is a Layer5 MeshMate?
-
-
-
-
- MeshMate
-
- is a distinction that Layer5 awards select members of the community who innately
- align with our culture of helping others, paying it forward, and a commitment to
- knowledge sharing. MeshMates are Layer5 mentors and ambassadors (not employees).
-
-
-
-
-
- A Layer5 MeshMate is individual who has consistently demonstrated their
- commitment to helping community members. The MeshMate program pairs
- experienced Layer5 community members with community newcomers to ensure a
- smooth onboarding experience. Helping community members takes all forms from
- ensuring the member has access to resources, is introduced to others,
- understands the vision and goals of projects, can build and contribute to
- projects, can use projects and have their feedback heard. MeshMates aid in
- identifying areas of projects and activities within the community to engage
- within, which working groups to join, and in help community members grow in
- their open source and cloud native knowledge.
-
-
-
- There is a lot going in the Layer5 community. Projects and working groups move
- fast. By connecting one-on-one, MeshMates share tips on how to have the best
- community experience possible, but also build a relationship with the
- community member inevitably leaving a lasting mark as is evident from member
- comments about Nikhil.
-
-
-
It's not easy being a MeshMate
-
-
- With thousands of members in the Layer5 community, many come and go. Many take
- and many give. While we hope that each and every individual that joins will
- find a fit in the community and/or on a project, this isn't always the case.
-
- Engaging with and investing in community members can be taxing on mentors in
- terms of both their time and their emotional investment in seeing the newcomer
- plant roots, grow, and blossom.
-
-
-
- One of the goals MeshMates have is that of enabling the newcomer's passion and
- finding their sweetspot in the community and on a project, so that the
- newcomer ultimately achieves their goals - goals that are often similar, but
- different for each person. To help them acheive their goals, each individual
- is engaged 1:1 by their Meshmate, supporting them in becoming a landstanding
- Layer5 community member and contributor. MeshMates understand that many
- mentees start out with the best of intentions, but that not all overcome their
- hurdles in finding an area of the community to call home or aspect of a
- project to own.
-
-
-
-
-
MeshMates are a massive force
-
- In just a year's time, with thousands of people in the Layer5 community and
- 500+ contributors to our projects, it's clear that Layer5 MeshMates
- significantly uplift our collaborative efforts and are steady force in the
- community. In process of confirming Nikhil as the winner of the inaugural
- MeshMate of the Year award, we looked to the community for validation. Little
- did I realize that meant reaching out to nearly a hundred people whom Nikhil
- has mentored or supported in the Layer5 community. More than a few of them had
- something to say about their time with Nikhil:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- In recognition a year's worth of paying it forward, and for the inaugural
- award, a new badge identifies our MeshMate of the Year award winner. Only one
- person carries this badge today. I can only guess as to who this ribbon may be
- awarded to for 2021. In the year and a half that Nikhil has been in the
- community, he has touched the lives of many people, including mine. Nikhil is
- my friend. He is the Layer5 MeshMate of the Year.
-
-
-
-
-
-
-
- The MeshMate badge is a point of pride for individuals participating in the
- program and looked upon with admiration and veneration by many within and
- external to the Layer5 community.
-
-
-
- Wear your MeshMate of the Year badge proudly, Nikhil.
-
-
-
+---
+title: "MeshMate of the Year 2020: Nikhil Ladha"
+subtitle: ""
+date: 2021-04-05 09:10:00 +0000
+author: Lee Calcote
+thumbnail: ./MeshMate-of-the-Year-2020-Nihkil-Ladha.webp
+darkthumbnail: ./MeshMate-of-the-Year-2020-Nihkil-Ladha.webp
+category: Community
+tags:
+ - Community
+published: true
+---
+
+import MMoY2020 from "./meshmate-of-the-year-2020.webp";
+import MeshMate from "../../../../assets/images/meshmate/meshmate-stack.svg";
+import MMOYNikhil from "./MeshMate-of-the-Year-2020-Nihkil-Ladha.webp";
+
+
+
+
+ If you are in the Layer5 Community, no doubt, you've met
+ Nikhil Ladha. If not, I recommend that you join the community and get to know Nikhil.
+ He's the Layer5 MeshMate of the Year and here's why: Nikhil consistently volunteers
+ to uplift and support others in the community, freely sharing of his time and knowledge.
+ His actions embody and espouse the pay-it-forward culture of Layer5.
+
+
+
+
+2020 was a noteworthy year in many ways. Nikhil's committment to the people and projects of the Layer5 community will forever be at the top of list of mentionables I and others will recall of last year. It was in 2019, though, that Nikhil's journey in the Layer5 community started and where he first began helping build our healthy, inclusive, and diverse community and our industry-leading, innovate open source projects. Nikhil's natural disposition to mentoring others and his stewardship on various projects make him a successful MeshMate.
+
+
What is a Layer5 MeshMate?
+
+
+
+
+ MeshMate
+
+ is a distinction that Layer5 awards select members of the community who innately
+ align with our culture of helping others, paying it forward, and a commitment to
+ knowledge sharing. MeshMates are Layer5 mentors and ambassadors (not employees).
+
+
+
+
+
+ A Layer5 MeshMate is individual who has consistently demonstrated their
+ commitment to helping community members. The MeshMate program pairs
+ experienced Layer5 community members with community newcomers to ensure a
+ smooth onboarding experience. Helping community members takes all forms from
+ ensuring the member has access to resources, is introduced to others,
+ understands the vision and goals of projects, can build and contribute to
+ projects, can use projects and have their feedback heard. MeshMates aid in
+ identifying areas of projects and activities within the community to engage
+ within, which working groups to join, and in help community members grow in
+ their open source and cloud native knowledge.
+
+
+
+ There is a lot going in the Layer5 community. Projects and working groups move
+ fast. By connecting one-on-one, MeshMates share tips on how to have the best
+ community experience possible, but also build a relationship with the
+ community member inevitably leaving a lasting mark as is evident from member
+ comments about Nikhil.
+
+
+
It's not easy being a MeshMate
+
+
+ With thousands of members in the Layer5 community, many come and go. Many take
+ and many give. While we hope that each and every individual that joins will
+ find a fit in the community and/or on a project, this isn't always the case.
+
+ Engaging with and investing in community members can be taxing on mentors in
+ terms of both their time and their emotional investment in seeing the newcomer
+ plant roots, grow, and blossom.
+
+
+
+ One of the goals MeshMates have is that of enabling the newcomer's passion and
+ finding their sweetspot in the community and on a project, so that the
+ newcomer ultimately achieves their goals - goals that are often similar, but
+ different for each person. To help them acheive their goals, each individual
+ is engaged 1:1 by their Meshmate, supporting them in becoming a landstanding
+ Layer5 community member and contributor. MeshMates understand that many
+ mentees start out with the best of intentions, but that not all overcome their
+ hurdles in finding an area of the community to call home or aspect of a
+ project to own.
+
+
+
+
+
MeshMates are a massive force
+
+ In just a year's time, with thousands of people in the Layer5 community and
+ 500+ contributors to our projects, it's clear that Layer5 MeshMates
+ significantly uplift our collaborative efforts and are steady force in the
+ community. In process of confirming Nikhil as the winner of the inaugural
+ MeshMate of the Year award, we looked to the community for validation. Little
+ did I realize that meant reaching out to nearly a hundred people whom Nikhil
+ has mentored or supported in the Layer5 community. More than a few of them had
+ something to say about their time with Nikhil:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ In recognition a year's worth of paying it forward, and for the inaugural
+ award, a new badge identifies our MeshMate of the Year award winner. Only one
+ person carries this badge today. I can only guess as to who this ribbon may be
+ awarded to for 2021. In the year and a half that Nikhil has been in the
+ community, he has touched the lives of many people, including mine. Nikhil is
+ my friend. He is the Layer5 MeshMate of the Year.
+
+
+
+
+
+
+
+ The MeshMate badge is a point of pride for individuals participating in the
+ program and looked upon with admiration and veneration by many within and
+ external to the Layer5 community.
+
+
+
+ Wear your MeshMate of the Year badge proudly, Nikhil.
+
+
+
diff --git a/src/collections/blog/2021/2021-04-16-meet-the-maintainer-jash-patel/index.mdx b/src/collections/blog/2021/2021-04-16-meet-the-maintainer-jash-patel/index.mdx
index 0c6ec1f462fd..c21c8d2c9059 100644
--- a/src/collections/blog/2021/2021-04-16-meet-the-maintainer-jash-patel/index.mdx
+++ b/src/collections/blog/2021/2021-04-16-meet-the-maintainer-jash-patel/index.mdx
@@ -9,19 +9,14 @@ category: Community
tags:
- Community
published: true
-interviewer: Ruth Ikegah
-interviewee: Jash Patel
---
-import { BlogWrapper } from "../../Blog.style.js";
import img from "./jash-patel-layer5-maintainer.webp";
-import { MeetTheMaintainer } from "../../MeetTheMaintainer.style.js";
-import { Link } from "gatsby";
-
+
Next on Layer5 Meet the Maintainer’s series, we have Jash Patel. Jash is a
Computer Science undergraduate at the Indian Institute of Technology and a
@@ -29,14 +24,15 @@ import { Link } from "gatsby";
{" "}
Service Mesh Performance
- {" "}
+
+ {" "}
and
Service Mesh Landscape. He works with
React, Gatsby, Jekyll, and Discourse and loves contributing to Open Source.
-
+
Ruth:
Jash, thank you for joining me today. Many people inside and outside of the
@@ -47,7 +43,7 @@ import { Link } from "gatsby";
-
+
Jash:
Back in August 2020, I was looking for an open-source organization. I found
@@ -62,7 +58,7 @@ import { Link } from "gatsby";
-
+
Ruth:
I can totally relate to how amazing the Layer5 onboarding process is unique!
@@ -72,7 +68,7 @@ import { Link } from "gatsby";
-
+
Jash:
I started contributing to docs and soon dived into Layer5 websites. While I
@@ -85,7 +81,7 @@ import { Link } from "gatsby";
-
+
Ruth:
Definitely, winks! Have you worked with any other open source project? How
@@ -93,7 +89,7 @@ import { Link } from "gatsby";
-
+
Jash:
I am a part of my college’s open-source organization. I have contributed to
@@ -104,7 +100,7 @@ import { Link } from "gatsby";
-
+
Ruth:
You know for me, coming to The Next Generation Layer5 Website was done in
@@ -113,7 +109,7 @@ import { Link } from "gatsby";
-
+
Jash:
It was a pretty big task. Many people have worked on it(At the time of
@@ -129,7 +125,7 @@ import { Link } from "gatsby";
-
+
Ruth:
It’s amazing you are in school and still actively contribute to Layer5, how
@@ -137,7 +133,7 @@ import { Link } from "gatsby";
-
+
Jash:
I once mentioned that while my exams were going on, I would study the entire
@@ -149,7 +145,7 @@ import { Link } from "gatsby";
-
+
Ruth:
I’m really curious, what does being a Layer5 maintainer mean to you? How has
@@ -157,7 +153,7 @@ import { Link } from "gatsby";
-
+
Jash:
I still remember my first pull request being reviewed. And now I am on the
@@ -170,7 +166,7 @@ import { Link } from "gatsby";
-
+
Ruth:
I really picked a lot of points on that! Do you have any advice for
@@ -178,7 +174,7 @@ import { Link } from "gatsby";
-
+
Jash:
My advice would be to not look for becoming something. I never thought of
@@ -193,7 +189,7 @@ import { Link } from "gatsby";
-
+
Ruth:
That was some great advice there and tips! Thanks, Jash for all you do for
@@ -201,7 +197,7 @@ import { Link } from "gatsby";
-
+
Ruth:
That was some great advice there and tips! Thanks, Jash for all you do for
@@ -209,8 +205,8 @@ import { Link } from "gatsby";
-
-
+
+
Jash is an impactful contributor and a kind-hearted maintainer. His story is
special, but not unique. Take Jash’s advice and engage in our uplifting
community. Write your own story. Join the Layer5 Community. Be like Jash,
@@ -218,7 +214,7 @@ import { Link } from "gatsby";
diff --git a/src/collections/blog/2021/2021-04-19-announcing-meshery-v0.5/index.mdx b/src/collections/blog/2021/2021-04-19-announcing-meshery-v0.5/index.mdx
index fd5281efd41b..a593635ae21f 100644
--- a/src/collections/blog/2021/2021-04-19-announcing-meshery-v0.5/index.mdx
+++ b/src/collections/blog/2021/2021-04-19-announcing-meshery-v0.5/index.mdx
@@ -1,191 +1,193 @@
----
-title: "Announcing Meshery v0.5.0"
-subtitle: ""
-date: 2021-04-19 08:00:00 +0000
-author: Aisuko Li
-thumbnail: ./v0.5.0.webp
-darkthumbnail: ./v0.5.0.webp
-category: Announcements
-tags:
- - Meshery
- - Projects
-published: true
-resource: true
-type: Blog
-product: Meshery
-redirect_from:
- - /blog/meshery/announcing-meshery-v0.5.0/
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import MesheryOperatorShot from "./meshery-operator-v0.5.0.webp";
-import MesheryOperator from "./meshery-operator-dark.svg";
-import MeshSync from "./meshsync.svg";
-import MesheryDB from "./meshery-database.svg";
-import MesheryAdapterLibrary from "./meshery-adapter-library.svg";
-import Traefik from "./traefik-mesh.svg";
-import MesheryExtensibility from "./meshery-extensibility.svg";
-import NGINXSM from "./nginx-service-mesh.svg";
-import layer5Logo from "../../../../assets/images/layer5/layer5-only/svg/layer5-no-trim.svg";
-
-
-
-
We're pleased to announce the release of Meshery 0.5.0! Consisting of a number of significant architectural enhancements with 8 new capabilities entering alpha, Meshery v0.5.0's feature density is impressive. Previewed in the Using Istio workshop delivered at the inaugural IstioCon 2021 earlier this month, Meshery v0.5.0 provides a strong architectural foundation for cloud native application and service mesh management.
-
-
-## Feature Highlights
-- New GraphQL API
-- Meshery Operator with MeshSync inside
-- Meshery Adapter for Traefik Mesh (beta)
-- MeshKit and the Meshery Adapter Library
-- Meshery Adapter for NGINX Service Mesh (alpha)
-- Meshery Remote Provider extensions with dynamic injection
-- New Meshery CLI commands to manage mutiple Meshery deployments
-
-
-
-
Thank you to the wonderful Layer5 community of open source contributors in making this significant release possible.
-
-
-## New Service Mesh Support
-
-
2 new Meshery service mesh adapters are bundled with this latest version of Meshery: The Meshery Adapter for Traefik Mesh and the Meshery Adapter for NGINX Service Mesh.
-
-
Meshery Adapter for Traefik Mesh (beta)
-
-
-
Traefik Mesh is a straight-forward, easy to configure, and non-invasive service mesh that allows visibility and management of the traffic flows inside any Kubernetes cluster.
-
-
Meshery supports the lifecycle and performance management of Traefik Mesh. Along with support for multiple versions of Traefik Mesh, bundled with this adapter are the Book Info and HttpBin sample applications operations to aid you in familiarizing with the functionality of Traefik Mesh. As a Meshery user, you can apply custom configuration to your instances of Traefik Mesh, managing the onboarding of your own applications onto the service mesh and providing the ability for you as a service mesh manager to customize your service mesh deployment.
NGINX Service Mesh (NSM) is a fully integrated, lightweight service mesh that leverages a data plane powered by NGINX Plus to manage container traffic in Kubernetes environments.
-
-
Meshery supports lifecycle and performance management of NGINX Service Mesh. Bundled with this support are a few sample applications to help users understand the functionality of NGINX Service Mesh. lifecycle management and sample applications operations below:
-
-As the cloud native manager, Meshery, is an extensible platform offering user and integrators well-crafted, extension points. Extension points allow you to augment the behavior of Meshery by either adding entirely new capabilities or affecting the behavior of existing functionality, as see in the figure below.
-
-
-
-
-
-As you can see in the diagram, Meshery offers many types of extension points.
-
-- Extensible Service Mesh Adapters - bring your own service mesh.
-- Extensible APIs - bring your own GraphQL resolvers and expose new, custom endpoints.
-- Extensible Load Generators - Meshery supports three types of load generators, however, you can bring your own and plug it in.
-- Extensible Providers - the v0.5.0 release delivers dynamic injection of Remote Provider extensions. Providers are a powerful mechanism for integrating Meshery into your existing tooling and systems.
-
-There are two types of Providers in Meshery: Local - built into Meshery and Remote - implemented by anyone or any organization that wishes to integrate with Meshery. Remote Provider extensibility includes:
-
- * Pluggable UI functionality
- * Pluggable Backend functionality
- * Pluggable Authentication and Authorization
- * Long-Term Persistence
- * Enhanced Visualization
- * Historical Reporting
-
-Learn more about the platform Meshery provides to extend its funcionality by exploring its extension points. If you have or are building your own Remote Provider, let us know!
-
MeshKit and Meshery Adapter Library
-
-As a service mesh toolkit, MeshKit aims to specifically focus on service mesh management and provides broadly useful functionality, it provides a standard policy for error handling and logging across all Meshery components, and implementations for error handling, logging, and tracing.
-
-
-
MeshKit provides common data models of Service Mesh Interface conformance testing for Meshery.
-
The low-level API abstract by MeshKit to the high-level functions provides out-of-the-box functions.
-
-
-
Meshery Adapter Library
-
-
The Meshery Adapter Library provides a common and consistent set of functionality for managing the lifecycle of service meshes and their workloads.
-
-
-
-
-* The library provides a set of interfaces, some with default implementations like a mini framework implementing the gRPC server that allows plugging in the mesh-specific configuration and operations implemented in the adapters.
-* The default configuration provider we use Viper to reads the adapter specific configuration, and the configuration providers are implementations of an interface, this can be flexible if anyone wants to implement it on their own.
-
-
Read Maintainer Michael Gfeller's blog post Introduction MeshKit and the Meshery Adapter Library for more details.
-
-With the increasing the number and diversity of service meshes supported by Meshery, you might find the list of [Supported Service Meshes](https://docs.meshery.io/service-meshes) a helpful, complete list.
-
-
Meshery Operator
-
-
-As a Kubernetes custom controller, Meshery Operator provides a Kubernetes-native approach to interfacing with Meshery. Kubernetes is where service meshes have gotten their initial foothold, and therefore, important that Meshery interface to Kubernetes natively.
Some service meshes support non-containerized workloads outside of the cluster and will grow in this focus over time. While Meshery Operator is Kubernetes only in the v0.5.0 release, Meshery's arichitecture makes considerations for different workload and platform types.
-
-
-
-
-
-
-
Meshery Operator is the multi-service mesh operator that runs as a Kubernetes Operator and defines two custom resources: MeshSync and Meshery Broker (NATS)
-
Meshery Operator is provides abilities includes cluster discovery, service mesh discovery, and data streaming via NATS.
-
-
-
-
MeshSync
-
MeshSync is available as a Kubernetes custom resource that provides tiered discovery and continual synchronization with Meshery Server as to the state of the Kubernetes cluster, service meshes, and their workloads.
-
-
-
-
-
-
MeshSync is one of a family of custom controllers within Meshery Operator and is the heartbeat of Meshery, pumping information about service meshes and their workloads throughout Meshery's components.
-
MeshSync helps Meshery mesh with meshes by helping define a service mesh agnostic object model.
-
It provides ability to detect service meshes and services deployed on the cluster, and snapshot stored in-memory and refreshed periodically;
-maintain the local snapshot of the cluster and refreshed periodically.
-
MeshSync These abilities above help Meshery operations more resilient.
-
-
-
-
Relational Database
-
-Meshery's relational database serves as a repository for MeshSync data, user preferences, and system settings. This database should be considered ephemeral and given that it operates as a cache. Meshery relational database offers federated datasets for managing multiple Kubernetes cluster and multiple service meshes.
-
-
-
-## GraphQL Support
-
-Meshery now supports GraphQL instances between Meshery UI and Meshery Server offering any GraphQL client the power to ask for exactly what they need from mesh. This new API sets the stage preparing for exciting features in upcoming releases. Extension points are also built into Meshery's GraphQL support allowing integrators to bring their own GraphQL resolvers to the Meshery server runtime.
-
-
-
Meshery Command Line Interface Enhancements
-The beloved `mesheryctl` introduces new commands in the v0.5.0 release expands the CLI's support of multiple Meshery deployments with the `context` command and control over when Meshery auto-updates with the `channel` command.
-
-
Managing Multiple Meshery Deployments
-Introduced in this release is the meshconfig - a configuration file that describes Meshery deployments in separate contexts. A Meshery context describes deployments across Docker hosts and Kubernetes clusters. mesheryctl system context enables user to easy manage multiple deployments of Meshery by quickly switching contexts.
-
-### Subscribing to Meshery Release Channels
-`mesheryctl system channel` allows you to easily set and switch between which Meshery release channel (stable or edge) that you want a particilar Meshery deployment (`context`) to use. Meshery deployments subscribe to one of two release channels and can either automatically self-update the deployment or prompt you to update the deployment. Alternatively, you can pin a given Meshery deployment to a specific release should you want tighter control over when Meshery updates. Read more about Meshery's stable and edge release channels.
-
-
-Review the mesheryctl Command Reference for details on all subcommands, flags, and their behavior.
-
-
On to v0.6.0
-
-To get a more comprehensive list of the bug fixes and enhancements packaged in the v0.5.0 release, see the [Meshery Documentation](https://docs.meshery.io/). With v0.6.0 planning complete these signal of the Layer5 community's innovation cycle trending upward sharply. See Meshery's roadmap for a prelude of what's yet to come.
-
-
If these topics excite you and you want to explore the wonderful world of service meshes, come and say "Hi" on the community Slack and you are sure to be warmly welcomed. 😀
-
-
+---
+title: "Announcing Meshery v0.5.0"
+subtitle: ""
+date: 2021-04-19 08:00:00 +0000
+author: Aisuko Li
+thumbnail: ./v0.5.0.webp
+darkthumbnail: ./v0.5.0.webp
+category: Announcements
+tags:
+ - Meshery
+ - Projects
+published: true
+resource: true
+type: Blog
+product: Meshery
+redirect_from:
+ - /blog/meshery/announcing-meshery-v0.5.0/
+---
+
+
+
+import MesheryOperatorShot from "./meshery-operator-v0.5.0.webp";
+import MesheryOperator from "./meshery-operator-dark.svg";
+import MeshSync from "./meshsync.svg";
+import MesheryDB from "./meshery-database.svg";
+import MesheryAdapterLibrary from "./meshery-adapter-library.svg";
+import Traefik from "./traefik-mesh.svg";
+import MesheryExtensibility from "./meshery-extensibility.svg";
+import NGINXSM from "./nginx-service-mesh.svg";
+import layer5Logo from "../../../../assets/images/layer5/layer5-only/svg/layer5-no-trim.svg";
+
+
+
+
We're pleased to announce the release of Meshery 0.5.0! Consisting of a number of significant architectural enhancements with 8 new capabilities entering alpha, Meshery v0.5.0's feature density is impressive. Previewed in the Using Istio workshop delivered at the inaugural IstioCon 2021 earlier this month, Meshery v0.5.0 provides a strong architectural foundation for cloud native application and service mesh management.
+
+
+## Feature Highlights
+- New GraphQL API
+- Meshery Operator with MeshSync inside
+- Meshery Adapter for Traefik Mesh (beta)
+- MeshKit and the Meshery Adapter Library
+- Meshery Adapter for NGINX Service Mesh (alpha)
+- Meshery Remote Provider extensions with dynamic injection
+- New Meshery CLI commands to manage mutiple Meshery deployments
+
+
+
+
Thank you to the wonderful Layer5 community of open source contributors in making this significant release possible.
+
+
+## New Service Mesh Support
+
+
2 new Meshery service mesh adapters are bundled with this latest version of Meshery: The Meshery Adapter for Traefik Mesh and the Meshery Adapter for NGINX Service Mesh.
+
+
Meshery Adapter for Traefik Mesh (beta)
+
+
+
Traefik Mesh is a straight-forward, easy to configure, and non-invasive service mesh that allows visibility and management of the traffic flows inside any Kubernetes cluster.
+
+
Meshery supports the lifecycle and performance management of Traefik Mesh. Along with support for multiple versions of Traefik Mesh, bundled with this adapter are the Book Info and HttpBin sample applications operations to aid you in familiarizing with the functionality of Traefik Mesh. As a Meshery user, you can apply custom configuration to your instances of Traefik Mesh, managing the onboarding of your own applications onto the service mesh and providing the ability for you as a service mesh manager to customize your service mesh deployment.
NGINX Service Mesh (NSM) is a fully integrated, lightweight service mesh that leverages a data plane powered by NGINX Plus to manage container traffic in Kubernetes environments.
+
+
Meshery supports lifecycle and performance management of NGINX Service Mesh. Bundled with this support are a few sample applications to help users understand the functionality of NGINX Service Mesh. lifecycle management and sample applications operations below:
+
+As the cloud native manager, Meshery, is an extensible platform offering user and integrators well-crafted, extension points. Extension points allow you to augment the behavior of Meshery by either adding entirely new capabilities or affecting the behavior of existing functionality, as see in the figure below.
+
+
+
+
+
+As you can see in the diagram, Meshery offers many types of extension points.
+
+- Extensible Service Mesh Adapters - bring your own service mesh.
+- Extensible APIs - bring your own GraphQL resolvers and expose new, custom endpoints.
+- Extensible Load Generators - Meshery supports three types of load generators, however, you can bring your own and plug it in.
+- Extensible Providers - the v0.5.0 release delivers dynamic injection of Remote Provider extensions. Providers are a powerful mechanism for integrating Meshery into your existing tooling and systems.
+
+There are two types of Providers in Meshery: Local - built into Meshery and Remote - implemented by anyone or any organization that wishes to integrate with Meshery. Remote Provider extensibility includes:
+
+ * Pluggable UI functionality
+ * Pluggable Backend functionality
+ * Pluggable Authentication and Authorization
+ * Long-Term Persistence
+ * Enhanced Visualization
+ * Historical Reporting
+
+Learn more about the platform Meshery provides to extend its funcionality by exploring its extension points. If you have or are building your own Remote Provider, let us know!
+
MeshKit and Meshery Adapter Library
+
+As a service mesh toolkit, MeshKit aims to specifically focus on service mesh management and provides broadly useful functionality, it provides a standard policy for error handling and logging across all Meshery components, and implementations for error handling, logging, and tracing.
+
+
+
MeshKit provides common data models of Service Mesh Interface conformance testing for Meshery.
+
The low-level API abstract by MeshKit to the high-level functions provides out-of-the-box functions.
+
+
+
Meshery Adapter Library
+
+
The Meshery Adapter Library provides a common and consistent set of functionality for managing the lifecycle of service meshes and their workloads.
+
+
+
+
+* The library provides a set of interfaces, some with default implementations like a mini framework implementing the gRPC server that allows plugging in the mesh-specific configuration and operations implemented in the adapters.
+* The default configuration provider we use Viper to reads the adapter specific configuration, and the configuration providers are implementations of an interface, this can be flexible if anyone wants to implement it on their own.
+
+
Read Maintainer Michael Gfeller's blog post Introduction MeshKit and the Meshery Adapter Library for more details.
+
+With the increasing the number and diversity of service meshes supported by Meshery, you might find the list of [Supported Service Meshes](https://docs.meshery.io/service-meshes) a helpful, complete list.
+
+
Meshery Operator
+
+
+As a Kubernetes custom controller, Meshery Operator provides a Kubernetes-native approach to interfacing with Meshery. Kubernetes is where service meshes have gotten their initial foothold, and therefore, important that Meshery interface to Kubernetes natively.
+
+
Some service meshes support non-containerized workloads outside of the cluster and will grow in this focus over time. While Meshery Operator is Kubernetes only in the v0.5.0 release, Meshery's arichitecture makes considerations for different workload and platform types.
+
+
+
+
+
+
+
Meshery Operator is the multi-service mesh operator that runs as a Kubernetes Operator and defines two custom resources: MeshSync and Meshery Broker (NATS)
+
Meshery Operator is provides abilities includes cluster discovery, service mesh discovery, and data streaming via NATS.
+
+
+
+
MeshSync
+
MeshSync is available as a Kubernetes custom resource that provides tiered discovery and continual synchronization with Meshery Server as to the state of the Kubernetes cluster, service meshes, and their workloads.
+
+
+
+
+
+
MeshSync is one of a family of custom controllers within Meshery Operator and is the heartbeat of Meshery, pumping information about service meshes and their workloads throughout Meshery's components.
+
MeshSync helps Meshery mesh with meshes by helping define a service mesh agnostic object model.
+
It provides ability to detect service meshes and services deployed on the cluster, and snapshot stored in-memory and refreshed periodically;
+maintain the local snapshot of the cluster and refreshed periodically.
+
MeshSync These abilities above help Meshery operations more resilient.
+
+
+
+
Relational Database
+
+Meshery's relational database serves as a repository for MeshSync data, user preferences, and system settings. This database should be considered ephemeral and given that it operates as a cache. Meshery relational database offers federated datasets for managing multiple Kubernetes cluster and multiple service meshes.
+
+
+
+## GraphQL Support
+
+Meshery now supports GraphQL instances between Meshery UI and Meshery Server offering any GraphQL client the power to ask for exactly what they need from mesh. This new API sets the stage preparing for exciting features in upcoming releases. Extension points are also built into Meshery's GraphQL support allowing integrators to bring their own GraphQL resolvers to the Meshery server runtime.
+
+
+
Meshery Command Line Interface Enhancements
+The beloved `mesheryctl` introduces new commands in the v0.5.0 release expands the CLI's support of multiple Meshery deployments with the `context` command and control over when Meshery auto-updates with the `channel` command.
+
+
Managing Multiple Meshery Deployments
+Introduced in this release is the meshconfig - a configuration file that describes Meshery deployments in separate contexts. A Meshery context describes deployments across Docker hosts and Kubernetes clusters. mesheryctl system context enables user to easy manage multiple deployments of Meshery by quickly switching contexts.
+
+### Subscribing to Meshery Release Channels
+`mesheryctl system channel` allows you to easily set and switch between which Meshery release channel (stable or edge) that you want a particilar Meshery deployment (`context`) to use. Meshery deployments subscribe to one of two release channels and can either automatically self-update the deployment or prompt you to update the deployment. Alternatively, you can pin a given Meshery deployment to a specific release should you want tighter control over when Meshery updates. Read more about Meshery's stable and edge release channels.
+
+
+Review the mesheryctl Command Reference for details on all subcommands, flags, and their behavior.
+
+
On to v0.6.0
+
+To get a more comprehensive list of the bug fixes and enhancements packaged in the v0.5.0 release, see the [Meshery Documentation](https://docs.meshery.io/). With v0.6.0 planning complete these signal of the Layer5 community's innovation cycle trending upward sharply. See Meshery's roadmap for a prelude of what's yet to come.
+
+
If these topics excite you and you want to explore the wonderful world of service meshes, come and say "Hi" on the community Slack and you are sure to be warmly welcomed. 😀
+
+
diff --git a/src/collections/blog/2021/2021-04-24-buf-protocols/index.mdx b/src/collections/blog/2021/2021-04-24-buf-protocols/index.mdx
index ad1986bbc5af..37cdc9b497d7 100644
--- a/src/collections/blog/2021/2021-04-24-buf-protocols/index.mdx
+++ b/src/collections/blog/2021/2021-04-24-buf-protocols/index.mdx
@@ -1,84 +1,84 @@
----
-title: "Rethinking Protocol Buffers with Buf"
-subtitle: "Buf makes Protocol Buffer APIs easier to create, maintain, and consume"
-date: 2021-05-24 22:19:00
-author: "Adithya Krishna"
-thumbnail: ./buf-protocol.webp
-darkthumbnail: ./buf-protocol.webp
-category: "Cloud Native"
-tags:
- - gRPC
-published: true
-resource: true
-type: Blog
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { BufProtocol } from "./BufProtocol.style";
-import { Link } from "gatsby";
-import Problems from "./problems.webp";
-
-
-
-
-
-
At Layer5, we are continuously evaluating new technologies and incorporating them into our open source projects. Buf is one of those projects. This post presents an overview of Buf.
-
-
-## What is Buf?
-
-
A tool to make Protobuf reliable and easy to use for service owners and clients, while keeping it the obvious choice on the technical merits.
-Our organization should not have to reinvent the wheel to create, maintain, and consume Protobuf APIs efficiently and effectively. It will handle our Protobuf management strategy for us, so we can focus on what matters.
-
-
-
-## Features
-
-- Automatic file discovery.
-- Selectable configuration - 40 lint checkers and 54 breaking checkers
-- Selectable error output - `file:line:col:message`
-- Check anything from anywhere - proto files, tar, git, pre-built images or file descriptors.
-- [Speed](https://docs.buf.build/tour-8/) - Its internal compiler is super fast (approx. 4x then Protoc)
-- Can use buf as a protoc plugin instead of using it as a standalone tool.
-
-## Buf CLI
-
-Buf attempts to simplify your Protocol Buffers workflow using the Buf CLI and protoc plugins. The Buf CLI currently provides:
-
-- A linter that enforces good API design choices and structure.
-- A breaking change detector that enforces compatibility at the source code level or wire level.
-- A generator that invokes your protoc plugins based on a configurable template. A protoc replacement that uses Buf's newly-developed high performance Protobuf compiler.
-- A configurable file builder that produces Images, our extension of FileDescriptorSets.
-
-## Comparison Between Protobuf and Buf
-Layer5 projects currently use protoc as the tool for building their protobuf defintions. The following are some considerations made while determining whether to use Buf.
-
-- Protobuf is not as widely adopted as JSON.
-- API Structure
- - No standards enforcement
- - Inconsistency can arise across an organization's Protobuf APIs,
- - Design decisions can be made that can affect your API's future iterability.
-- Backward Compatibility
-- Stub distribution
-- Tooling
-
-
Buf aims to solve the above problems and it's long-term goal is to enable schema-driven development: A future where APIs are defined consistently, in a way that service owners and us can depend on
-
-## Roadmap to Adopting Buf
-In consideration of the use of Buf, we would adopt it in phases, starting with the following ares of integration.
-
-- **API Structure Enforcements**
- - Linter solves this issue by enforcing standards.
- - Also, we don’t need to use Buf as a standalone tool we can just use linter as plugins.
-
-
-- **Backward Compatibility**
- - It will check for different things that can cause breaking change.
- - For example, type change.
-
-
If these topics excite you and you want to explore more cloud native technolgies, come and say "Hi" on the community Slack and you are sure to be warmly welcomed. 😀
-
-
+---
+title: "Rethinking Protocol Buffers with Buf"
+subtitle: "Buf makes Protocol Buffer APIs easier to create, maintain, and consume"
+date: 2021-05-24 22:19:00
+author: "Adithya Krishna"
+thumbnail: ./buf-protocol.webp
+darkthumbnail: ./buf-protocol.webp
+category: "Cloud Native"
+tags:
+ - gRPC
+published: true
+resource: true
+type: Blog
+---
+
+
+import { BufProtocol } from "./BufProtocol.style";
+
+import Problems from "./problems.webp";
+
+
+
+
+
+
At Layer5, we are continuously evaluating new technologies and incorporating them into our open source projects. Buf is one of those projects. This post presents an overview of Buf.
+
+
+## What is Buf?
+
+
A tool to make Protobuf reliable and easy to use for service owners and clients, while keeping it the obvious choice on the technical merits.
+Our organization should not have to reinvent the wheel to create, maintain, and consume Protobuf APIs efficiently and effectively. It will handle our Protobuf management strategy for us, so we can focus on what matters.
+
+
+
+## Features
+
+- Automatic file discovery.
+- Selectable configuration - 40 lint checkers and 54 breaking checkers
+- Selectable error output - `file:line:col:message`
+- Check anything from anywhere - proto files, tar, git, pre-built images or file descriptors.
+- [Speed](https://docs.buf.build/tour-8/) - Its internal compiler is super fast (approx. 4x then Protoc)
+- Can use buf as a protoc plugin instead of using it as a standalone tool.
+
+## Buf CLI
+
+Buf attempts to simplify your Protocol Buffers workflow using the Buf CLI and protoc plugins. The Buf CLI currently provides:
+
+- A linter that enforces good API design choices and structure.
+- A breaking change detector that enforces compatibility at the source code level or wire level.
+- A generator that invokes your protoc plugins based on a configurable template. A protoc replacement that uses Buf's newly-developed high performance Protobuf compiler.
+- A configurable file builder that produces Images, our extension of FileDescriptorSets.
+
+## Comparison Between Protobuf and Buf
+Layer5 projects currently use protoc as the tool for building their protobuf defintions. The following are some considerations made while determining whether to use Buf.
+
+- Protobuf is not as widely adopted as JSON.
+- API Structure
+ - No standards enforcement
+ - Inconsistency can arise across an organization's Protobuf APIs,
+ - Design decisions can be made that can affect your API's future iterability.
+- Backward Compatibility
+- Stub distribution
+- Tooling
+
+
Buf aims to solve the above problems and it's long-term goal is to enable schema-driven development: A future where APIs are defined consistently, in a way that service owners and us can depend on
+
+## Roadmap to Adopting Buf
+In consideration of the use of Buf, we would adopt it in phases, starting with the following ares of integration.
+
+- **API Structure Enforcements**
+ - Linter solves this issue by enforcing standards.
+ - Also, we don’t need to use Buf as a standalone tool we can just use linter as plugins.
+
+
+- **Backward Compatibility**
+ - It will check for different things that can cause breaking change.
+ - For example, type change.
+
+
If these topics excite you and you want to explore more cloud native technolgies, come and say "Hi" on the community Slack and you are sure to be warmly welcomed. 😀
+
+
\ No newline at end of file
diff --git a/src/collections/blog/2021/2021-06-25-she-code-africa-contributhon-boot-camp/index.mdx b/src/collections/blog/2021/2021-06-25-she-code-africa-contributhon-boot-camp/index.mdx
index eb27584cf045..1f122c3c70f8 100644
--- a/src/collections/blog/2021/2021-06-25-she-code-africa-contributhon-boot-camp/index.mdx
+++ b/src/collections/blog/2021/2021-06-25-she-code-africa-contributhon-boot-camp/index.mdx
@@ -1,130 +1,131 @@
----
-title: "She Code Africa Contributhon Boot Camp Report"
-date: 2021-06-25 16:00:00 +0000
-author: Anita Charles
-thumbnail: ./sca-thumbnail.webp
-darkthumbnail: ./sca-thumbnail.webp
-category: Community
-tags:
- - Community
- - MeshMate
-published: true
----
-
-import { Link } from "gatsby";
-
-import Sandy from "./sandySCA.webp";
-import Abiola from "./abiolaSCA.webp";
-import Cynthia from "./cynthiaSCA.webp";
-import Elizabeth from "./elizabethSCA.webp";
-import Blossom from "./blossomSCA.webp";
-import Joy from "./joySCA.webp";
-import Naimat from "./naimatSCA.webp";
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
- Layer5 participated as a suporting organization in the She Code Africa Contributhon which started on April 1, 2021. It was indeed a pleasant and impactful experience for both the mentors and the mentees from She Code Africa.
-
-
- The She Code Africa hosts their Contributhon as an Africa-wide open source boot camp focused on building more women OSS contributors & creating more diversity in the African open source ecosystem by matching African women in technology with sponsors and mentors from Open Source organizations. During this boot camp, participants work with an open source organisation on a project for 4 weeks with the help of organisation mentors and get rewarded at the end of the boot camp upon successful project completion.
-
-
- During the boot camp, Layer5 received a total of 8 mentees - all from Nigeria. These mentees were teamed up to work on the 3 project ideas selected by Layer5. Each project had an average of 2 members of the community who were delegated as mentors to oversee the contributions of the mentees. Often Layer5 MeshMates volunteer to be mentors.
-
-
Projects
-
Layer5 mentors prepared and organized a few projects in advance of the start of the boot camp, so that mentees might hit the ground running.
-
-
Layer5 Community Handbook
-
-
- Layer5 Community Handbook is a curated Document with the ABC's of the community. In this project, mentees were expected to look for repetition pattern across existing docs thereby, creating a structured guide for interaction across all projects.
-
- This required the contributors to fix existing issues on the GitHub repository, while suggesting ideas to improve the website, which used Gatsbyjs and Reactjs. The layer5.io website is hosted on GitHub Pages and is a collaborative effort of nearly 200 contributors.
-
- mesheryctl is a command-line tool for Meshery, the cloud native management plane. Using Golang, mentees were required to design new CLI commands and attend to existing issues, focusing on enforcing the consistency of user experience with the command line client.
-
-
- Mentors:
-
-
Navendu Pottekkat
-
Chinmay Mehta
-
- Mentee(s):
-
-
Joy Nwaiwu
-
Naimat Oyewale
-
-
-
-
-
-
-
-
- The mentors were in constant communication with the mentees, taking their questions and rendering help when needed. At the end of the Contribution boot camp, it was heartwarming to see the mentees were able to make noticeable contributions to the projects. During the boot camp wrap up call, mentees gave presentations that revealed how impactful it was for them working on Layer5 projects.
-
-
-
Appreciation
-
- In gratitude, we acknowledge the commitment and contributions of the mentees toward the projects and we won't forget our incredible mentors who were devoted to meeting the needs and answering to the mentees during this bootcamp. Also, we would like to appreciate Zainab Abubakar for having facilitated the She Code Africa
- Contribution 2021.
-
-
+---
+title: "She Code Africa Contributhon Boot Camp Report"
+date: 2021-06-25 16:00:00 +0000
+author: Anita Charles
+thumbnail: ./sca-thumbnail.webp
+darkthumbnail: ./sca-thumbnail.webp
+category: Community
+tags:
+ - Community
+ - MeshMate
+published: true
+---
+
+
+
+import Sandy from "./sandySCA.webp";
+import Abiola from "./abiolaSCA.webp";
+import Cynthia from "./cynthiaSCA.webp";
+import Elizabeth from "./elizabethSCA.webp";
+import Blossom from "./blossomSCA.webp";
+import Joy from "./joySCA.webp";
+import Naimat from "./naimatSCA.webp";
+
+
+
+
+
+ Layer5 participated as a suporting organization in the She Code Africa Contributhon which started on April 1, 2021. It was indeed a pleasant and impactful experience for both the mentors and the mentees from She Code Africa.
+
+
+ The She Code Africa hosts their Contributhon as an Africa-wide open source boot camp focused on building more women OSS contributors & creating more diversity in the African open source ecosystem by matching African women in technology with sponsors and mentors from Open Source organizations. During this boot camp, participants work with an open source organisation on a project for 4 weeks with the help of organisation mentors and get rewarded at the end of the boot camp upon successful project completion.
+
+
+ During the boot camp, Layer5 received a total of 8 mentees - all from Nigeria. These mentees were teamed up to work on the 3 project ideas selected by Layer5. Each project had an average of 2 members of the community who were delegated as mentors to oversee the contributions of the mentees. Often Layer5 MeshMates volunteer to be mentors.
+
+
Projects
+
Layer5 mentors prepared and organized a few projects in advance of the start of the boot camp, so that mentees might hit the ground running.
+
+
Layer5 Community Handbook
+
+
+ Layer5 Community Handbook is a curated Document with the ABC's of the community. In this project, mentees were expected to look for repetition pattern across existing docs thereby, creating a structured guide for interaction across all projects.
+
+ This required the contributors to fix existing issues on the GitHub repository, while suggesting ideas to improve the website, which used Gatsbyjs and Reactjs. The layer5.io website is hosted on GitHub Pages and is a collaborative effort of nearly 200 contributors.
+
+ mesheryctl is a command-line tool for Meshery, the cloud native management plane. Using Golang, mentees were required to design new CLI commands and attend to existing issues, focusing on enforcing the consistency of user experience with the command line client.
+
+
+ Mentors:
+
+
Navendu Pottekkat
+
Chinmay Mehta
+
+ Mentee(s):
+
+
Joy Nwaiwu
+
Naimat Oyewale
+
+
+
+
+
+
+
+
+ The mentors were in constant communication with the mentees, taking their questions and rendering help when needed. At the end of the Contribution boot camp, it was heartwarming to see the mentees were able to make noticeable contributions to the projects. During the boot camp wrap up call, mentees gave presentations that revealed how impactful it was for them working on Layer5 projects.
+
+
+
Appreciation
+
+ In gratitude, we acknowledge the commitment and contributions of the mentees toward the projects and we won't forget our incredible mentors who were devoted to meeting the needs and answering to the mentees during this bootcamp. Also, we would like to appreciate Zainab Abubakar for having facilitated the She Code Africa
+ Contribution 2021.
+
+
+
diff --git a/src/collections/blog/2021/2021-06-4-announcing-summer-interns/index.mdx b/src/collections/blog/2021/2021-06-4-announcing-summer-interns/index.mdx
index 93c306066136..747bd2549824 100644
--- a/src/collections/blog/2021/2021-06-4-announcing-summer-interns/index.mdx
+++ b/src/collections/blog/2021/2021-06-4-announcing-summer-interns/index.mdx
@@ -1,93 +1,94 @@
----
-title: "Meet the Summer Interns of 2021"
-date: 2021-06-04 08:00:00 +0000
-author: Interns of Summer 2021
-thumbnail: ./summer-intern.webp
-darkthumbnail: ./summer-intern.webp
-category: "Community"
-tags:
- - Community
-featured: true
-published: true
----
-
-import { Link } from "gatsby";
-
-import Dhruv from "./intern-dhruv-patel.webp";
-import Soham from "./intern-soham-sonawane.webp";
-import Piyush from "./intern-piyush-singariya.webp";
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
-
- Layer5 participates in many
- open source internship programs. We seek out existing contributors who
- actively reflect the culture and principles of Layer5 to participate in these programs. Here are the Summer of 2021's open source interns.
-
-
-Hear about their journeys and follow along this summer as they make waves in the Layer5 community.
-
-
-
- Dhruv Patel
-
-
-
-
- Open source has been intriguing to me ever since I had joined my college's open-source community (DevlupLabs). It was in the middle of the pandemic, though, with my mind trying to find an escape, that I stumbled upon Layer5. Within the first week of joining the Layer5 community, I had a pull request posted, and much to my surprise, found myself demo'ing it in the very next community meeting. In retrospect, it was a minor pull request, making some UI changes for Meshery. The encouragement I received was so welcoming and supportive. After that first week's experience, and so much technology and projects to explore, I was hooked - there was no turning back for me from that point.
-
-
- I started learning more about the projects in Layer5 and its tech stack. From how Meshery Server was using gRPC and protobufs to communicate with each of its service mesh adaptors to defining how SMI Conformance works and the Service Mesh Performance specification to how Meshery UI leverages some awesome libraries like NextJS, BillboardJS, and Redux. It has been through contributing to each of these areas, that I have learned each of these technologies more deeply and it was all possible because of the continuous influx of awesome support from the community, especially Abishek Kumar and I probably won't stop poking him for support anytime soon.
-
-
- As I look forward to a structured internship with Layer5 through Google Summer of Code this summer, I do so knowing I will be collaborating with the large Layer5 community, engineers from other technology companies and spending a lot of time with Soham and Piyush. For my part, I'll be working on a visual topology to help service mesh operators map their deployments, model their application performance, and parse their service proxy logs. I am ready to make an impact, learn more, and help other community members ( and watch as they, too, are initiated into the Layer5 community through ritual of giving an awkward first-timer introduction in our Community Meeting 😛).
-
-
-
-
- Piyush Singariya
-
-
-
-
- It all started with an idea, the idea of doing open source contributions. And with that after scrolling through many open source communities, I found Layer5, jumped up into our Slack workspace, started learning about Meshery. I raised a PR and was immediately made to feel like a rockstar. I began meeting more of the community members, learning more about Meshery and its command line client, `mesheryctl` with each contribution. And you know, its extrenely gratifying to have your pull request merged, and that feeling is amplified by the feedback and attention you receive as a contributor at Layer5.
-
-
- I knew that I wanted to engage even more deeply and learn all that I can from the seasoned engineers at Layer5. And so, I applied for internship. Layer5 takes internships seriously and doesn't accept anyone into internship until you have proven your commitment to their awesome projects.
- And at the time of writing this, it’s been almost three months of contributing bfore being accepted as GSoC student. I have spent most of my time focusing on Layer5’s Meshery project and it’s command line client, `mesheryctl`.
-
-
- And so, we reach the beginning of my GSoC 2021 program, which began on the night of May 17th, 2021 when I learned that I had been selected as a GSoC Participant with the Cloud Native Computing Foundation (CNCF). I am hyped up and excited to go ahead with Layer5 for the upcoming months.
-
-
- My GSoC project is about introducing interesting and important features to Meshery Server and `mesheryctl`. Such as automating Documentation and Interactive playground for Meshery Server’s REST API endpoints, adding commands related to performance testing and enhancing Meshery’s environment health checking, introducing unit testing for `mesheryctl`, and CI/CD and documentation for all the new features.
-
-
- It has been 2 weeks since I have started my GSoC’21 tenure with the Layer5 community, and from the very beginning (I mean before GSoC), I have learned a lot with my code contributions and the Community here. I began with setting up the performance command under mesheryctl and Open API Specification 2.0 for REST API documentation to the project. I am learning a lot of new things, like Unit Testing, Open API Specification, and much more to include.
-
-
-
- Soham Sonawane
-
-
-
- I got to know about Layer5 last year in December when one of my batchmates told me that he was contributing to the community. He asked me if I wanted to join Slack and wanted to contribute to a project. So I looked at the projects on Github and some open issues that I could contribute to. Me being a frontend developer I saw an issue related to removing whitespaces and minor frontend changes. I just made a PR and it was merged then I joined the Slack workspace and attended the Newcomers meeting. I was introduced to a lot of things that I could work on. All of them felt amazing and interesting, all I had to do was “signal” and I could work on any one of them.
-
-
- At first I thought that I should just work on layer5.io or maybe NightHawk, but then I was given an opportunity to work on something that I had never done before. It has been around 4 months that I have been a part of the community and I am actively trying to add to the project attending weekly meetings where everyone shares amazing stuff about what they did.
-
-
- As I said earlier my project is something that I had never worked on before, very interesting to work on, it adds one of the most important and unique features to Meshery. Meshery's MeshMap enables users to visualize their service meshes, look at important statistics. It also enables users to design their own service meshes by either importing their designs from a yaml file or by dragging and dropping service mesh components into a
- canvas, creating edges, grouping components, persisting these designs to see or edit later, realizing these designs by actually deploying them as service meshes and a lot more.
-
-
- My job is to be the God of CytoscapeJS, who knows every nook and cranny of the library that enables us to create the visual topology. It's been a week since I have started my LFX internship and I have been working on visual topology even before that. These months of contributing code have taught me a lot. The first task that was given to me was to explore the
- CytoscapeJS library and demonstrate a proof of concept of animated edges between 2 components. I sat for 3 hours straight right after the community meeting creating the demo and posted a video on our slack. I was never
- appreciated better than on that day. I have never looked back since, each time I am given a feature or issue or any request I try my hardest to realize it in the earliest. I am constantly trying to improve myself and add to the project.
-
-
- \- Dhruv, Piyush, and Soham
+---
+title: "Meet the Summer Interns of 2021"
+date: 2021-06-04 08:00:00 +0000
+author: Interns of Summer 2021
+thumbnail: ./summer-intern.webp
+darkthumbnail: ./summer-intern.webp
+category: "Community"
+tags:
+ - Community
+featured: true
+published: true
+---
+
+
+
+import Dhruv from "./intern-dhruv-patel.webp";
+import Soham from "./intern-soham-sonawane.webp";
+import Piyush from "./intern-piyush-singariya.webp";
+
+
+
+
+
+
+
+ Layer5 participates in many
+ open source internship programs. We seek out existing contributors who
+ actively reflect the culture and principles of Layer5 to participate in these programs. Here are the Summer of 2021's open source interns.
+
+
+
+Hear about their journeys and follow along this summer as they make waves in the Layer5 community.
+
+
+
+ Dhruv Patel
+
+
+
+
+ Open source has been intriguing to me ever since I had joined my college's open-source community (DevlupLabs). It was in the middle of the pandemic, though, with my mind trying to find an escape, that I stumbled upon Layer5. Within the first week of joining the Layer5 community, I had a pull request posted, and much to my surprise, found myself demo'ing it in the very next community meeting. In retrospect, it was a minor pull request, making some UI changes for Meshery. The encouragement I received was so welcoming and supportive. After that first week's experience, and so much technology and projects to explore, I was hooked - there was no turning back for me from that point.
+
+
+ I started learning more about the projects in Layer5 and its tech stack. From how Meshery Server was using gRPC and protobufs to communicate with each of its service mesh adaptors to defining how SMI Conformance works and the Service Mesh Performance specification to how Meshery UI leverages some awesome libraries like NextJS, BillboardJS, and Redux. It has been through contributing to each of these areas, that I have learned each of these technologies more deeply and it was all possible because of the continuous influx of awesome support from the community, especially Abishek Kumar and I probably won't stop poking him for support anytime soon.
+
+
+ As I look forward to a structured internship with Layer5 through Google Summer of Code this summer, I do so knowing I will be collaborating with the large Layer5 community, engineers from other technology companies and spending a lot of time with Soham and Piyush. For my part, I'll be working on a visual topology to help service mesh operators map their deployments, model their application performance, and parse their service proxy logs. I am ready to make an impact, learn more, and help other community members ( and watch as they, too, are initiated into the Layer5 community through ritual of giving an awkward first-timer introduction in our Community Meeting 😛).
+
+
+
+
+ Piyush Singariya
+
+
+
+
+ It all started with an idea, the idea of doing open source contributions. And with that after scrolling through many open source communities, I found Layer5, jumped up into our Slack workspace, started learning about Meshery. I raised a PR and was immediately made to feel like a rockstar. I began meeting more of the community members, learning more about Meshery and its command line client, `mesheryctl` with each contribution. And you know, its extrenely gratifying to have your pull request merged, and that feeling is amplified by the feedback and attention you receive as a contributor at Layer5.
+
+
+ I knew that I wanted to engage even more deeply and learn all that I can from the seasoned engineers at Layer5. And so, I applied for internship. Layer5 takes internships seriously and doesn't accept anyone into internship until you have proven your commitment to their awesome projects.
+ And at the time of writing this, it’s been almost three months of contributing bfore being accepted as GSoC student. I have spent most of my time focusing on Layer5’s Meshery project and it’s command line client, `mesheryctl`.
+
+
+ And so, we reach the beginning of my GSoC 2021 program, which began on the night of May 17th, 2021 when I learned that I had been selected as a GSoC Participant with the Cloud Native Computing Foundation (CNCF). I am hyped up and excited to go ahead with Layer5 for the upcoming months.
+
+
+ My GSoC project is about introducing interesting and important features to Meshery Server and `mesheryctl`. Such as automating Documentation and Interactive playground for Meshery Server’s REST API endpoints, adding commands related to performance testing and enhancing Meshery’s environment health checking, introducing unit testing for `mesheryctl`, and CI/CD and documentation for all the new features.
+
+
+ It has been 2 weeks since I have started my GSoC’21 tenure with the Layer5 community, and from the very beginning (I mean before GSoC), I have learned a lot with my code contributions and the Community here. I began with setting up the performance command under mesheryctl and Open API Specification 2.0 for REST API documentation to the project. I am learning a lot of new things, like Unit Testing, Open API Specification, and much more to include.
+
+
+
+ Soham Sonawane
+
+
+
+ I got to know about Layer5 last year in December when one of my batchmates told me that he was contributing to the community. He asked me if I wanted to join Slack and wanted to contribute to a project. So I looked at the projects on Github and some open issues that I could contribute to. Me being a frontend developer I saw an issue related to removing whitespaces and minor frontend changes. I just made a PR and it was merged then I joined the Slack workspace and attended the Newcomers meeting. I was introduced to a lot of things that I could work on. All of them felt amazing and interesting, all I had to do was “signal” and I could work on any one of them.
+
+
+ At first I thought that I should just work on layer5.io or maybe NightHawk, but then I was given an opportunity to work on something that I had never done before. It has been around 4 months that I have been a part of the community and I am actively trying to add to the project attending weekly meetings where everyone shares amazing stuff about what they did.
+
+
+ As I said earlier my project is something that I had never worked on before, very interesting to work on, it adds one of the most important and unique features to Meshery. Meshery's MeshMap enables users to visualize their service meshes, look at important statistics. It also enables users to design their own service meshes by either importing their designs from a yaml file or by dragging and dropping service mesh components into a
+ canvas, creating edges, grouping components, persisting these designs to see or edit later, realizing these designs by actually deploying them as service meshes and a lot more.
+
+
+ My job is to be the God of CytoscapeJS, who knows every nook and cranny of the library that enables us to create the visual topology. It's been a week since I have started my LFX internship and I have been working on visual topology even before that. These months of contributing code have taught me a lot. The first task that was given to me was to explore the
+ CytoscapeJS library and demonstrate a proof of concept of animated edges between 2 components. I sat for 3 hours straight right after the community meeting creating the demo and posted a video on our slack. I was never
+ appreciated better than on that day. I have never looked back since, each time I am given a feature or issue or any request I try my hardest to realize it in the earliest. I am constantly trying to improve myself and add to the project.
+
+
+ \- Dhruv, Piyush, and Soham
\ No newline at end of file
diff --git a/src/collections/blog/2021/2021-08-24-experience-gsoc-piyush-singariya/index.mdx b/src/collections/blog/2021/2021-08-24-experience-gsoc-piyush-singariya/index.mdx
index c651b3806db2..1373e16f4f37 100644
--- a/src/collections/blog/2021/2021-08-24-experience-gsoc-piyush-singariya/index.mdx
+++ b/src/collections/blog/2021/2021-08-24-experience-gsoc-piyush-singariya/index.mdx
@@ -1,109 +1,109 @@
----
-title: GSoC Experience @ Layer5 - Piyush Singariya
-subtitle: damn, it was good!
-date: 2021-08-25 10:30:05 -0530
-author: Piyush Singariya
-thumbnail: ./gsoc-wide.webp
-darkthumbnail: ./gsoc-wide.webp
-category: Programs
-tags:
- - GSoC
- - Programs
- - Meshery
- - Internship
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-import gsocLogo from "./gsoc.webp";
-
-
-
-
- Hi, I am Piyush Singariya, a short description of me would be “another
- software engineer watching anime”, in the longer version I am a 2021 graduate
- from IIT Roorkee, who loves to watch anime and play video games all day. I
- know both are exactly the same, but it is what it is.
-
-
- It all started around 22 Feb when I jumped into slack, and after 10 whole days
- messing around the project, I started to get a hold of it. I started
- contributing to mesheryctl and I thought to apply for the GSoC 2021.
-
-
Project
-
- My project was to introduce multiple net new features and minor enhancements
- in Meshery and mesheryctl (Meshery’s CLI).
-
-
- Meshery is a multi-service mesh management plane that offers lifecycle,
- configuration, and performance management of service meshes and applications
- running on top of those meshes. Meshery uses the{" "}
- Service Mesh Performance specification to
- describe and capture performance benchmarks and characterize service mesh
- behavior.
-
-
- I integrated many new features in Meshery Some of them are mentioned here.
-
-
mesheryctl
-
-
- Adding a new command to meshery's cli, i.e. mesheryctl for performance
- profiles and result management
-
-
- Introduction of Unit Testing and Integration testing for Cobra commands of
- cli, mesheryctl.
-
-
Reached 28% code-coverage in mesheryctl
-
-
-
- Introducing health-checks for environment checking of pre/post-deployment of
- meshery server
-
-
- Adding a new command to meshery's cli, i.e. mesheryctl for managing
- Webssembly filters
-
-
-
Meshery
-
-
Reworking and consolidation of API endpoint handlers
-
Swagger Spec definition and automatic publishing of documentation
-
-
Others
-
-
- Documentation on writing Unit and Integration Tests and Contributing to
- Meshery Server Documentation
-
-
- CI workflow for Swagger Documentation and running Unit and Integration Tests
- with calculating Code-coverage with CodeCov
-
- During the whole season, as my work was mostly focused on Golang so I can say
- I learned Golang, learned working around HTTP handlers, writing cobra
- commands, setting up golang unit testing for Cobra Commands(damn, it was
- tough), writing environment health-checks, writing GitHub-actions, Open-API
- specification 2.0,
-
-
Summary
-
- A quick summary of this experience would be that I had a really good time with
- Layer5, I learned, I engaged with other folks in the community, and I believe
- the environment here is truly best for any student to spend their time here,
- to learn and engage with each other. The folks here are crazy for helping new
- members get started with Layer5 projects.
-
+ Hi, I am Piyush Singariya, a short description of me would be “another
+ software engineer watching anime”, in the longer version I am a 2021 graduate
+ from IIT Roorkee, who loves to watch anime and play video games all day. I
+ know both are exactly the same, but it is what it is.
+
+
+ It all started around 22 Feb when I jumped into slack, and after 10 whole days
+ messing around the project, I started to get a hold of it. I started
+ contributing to mesheryctl and I thought to apply for the GSoC 2021.
+
+
Project
+
+ My project was to introduce multiple net new features and minor enhancements
+ in Meshery and mesheryctl (Meshery’s CLI).
+
+
+ Meshery is a multi-service mesh management plane that offers lifecycle,
+ configuration, and performance management of service meshes and applications
+ running on top of those meshes. Meshery uses the{" "}
+ Service Mesh Performance specification to
+ describe and capture performance benchmarks and characterize service mesh
+ behavior.
+
+
+ I integrated many new features in Meshery Some of them are mentioned here.
+
+
mesheryctl
+
+
+ Adding a new command to meshery's cli, i.e. mesheryctl for performance
+ profiles and result management
+
+
+ Introduction of Unit Testing and Integration testing for Cobra commands of
+ cli, mesheryctl.
+
+
Reached 28% code-coverage in mesheryctl
+
+
+
+ Introducing health-checks for environment checking of pre/post-deployment of
+ meshery server
+
+
+ Adding a new command to meshery's cli, i.e. mesheryctl for managing
+ Webssembly filters
+
+
+
Meshery
+
+
Reworking and consolidation of API endpoint handlers
+
Swagger Spec definition and automatic publishing of documentation
+
+
Others
+
+
+ Documentation on writing Unit and Integration Tests and Contributing to
+ Meshery Server Documentation
+
+
+ CI workflow for Swagger Documentation and running Unit and Integration Tests
+ with calculating Code-coverage with CodeCov
+
+ During the whole season, as my work was mostly focused on Golang so I can say
+ I learned Golang, learned working around HTTP handlers, writing cobra
+ commands, setting up golang unit testing for Cobra Commands(damn, it was
+ tough), writing environment health-checks, writing GitHub-actions, Open-API
+ specification 2.0,
+
+
Summary
+
+ A quick summary of this experience would be that I had a really good time with
+ Layer5, I learned, I engaged with other folks in the community, and I believe
+ the environment here is truly best for any student to spend their time here,
+ to learn and engage with each other. The folks here are crazy for helping new
+ members get started with Layer5 projects.
+
+
+
diff --git a/src/collections/blog/2021/2021-09-01-announcing-fall-interns/index.mdx b/src/collections/blog/2021/2021-09-01-announcing-fall-interns/index.mdx
index 3eeaadc4289a..a054c0296ca5 100644
--- a/src/collections/blog/2021/2021-09-01-announcing-fall-interns/index.mdx
+++ b/src/collections/blog/2021/2021-09-01-announcing-fall-interns/index.mdx
@@ -1,138 +1,139 @@
----
-title: "Meet the Fall Interns of 2021"
-date: 2021-09-01 08:00:00 +0000
-author: Interns of Fall 2021
-thumbnail: ./fall-interns.webp
-darkthumbnail: ./fall-interns.webp
-category: "Community"
-tags:
- - Community
-featured: true
-published: true
----
-
-import { Link } from "gatsby";
-
-import Nithish from "./nithish-karthik.webp";
-import Ashish from "./ashish-tiwari.webp";
-import Rudraksh from "./rudraksh-pareek.webp";
-import Bariq from "./bariq-nurlis.webp";
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
-
-
- Layer5 participates in many
-
- open source internship programs
- . We seek out existing contributors who actively reflect the culture and
- principles of Layer5 to participate in these programs. Here are the Fall of 2021's
- open source interns.
-
-
-
-Hear about their journeys and follow along this fall as they make waves in the Layer5 community.
-
-
-
- Bariq Nurlis
-
-
-
-
-
- The idea of contributing to an open source has been on the back of my mind since I enrolled in college back in 2019. Like how most people formulate what and how they will do in the uni, I also came from normalcy. In Singapore, students are aiming to get the best mark in every possible lesson in college as our grades hold a very high importance in the culture. Going back and forth between classes, planning a startup with my peers, volunteering in community clubs, I had a spectacular two years in uni.
-
-
-However, during the last summer break, I started asking myself questions. How should I be better? What should I do? When should I do it? As I got more familiar with the Uni and all my messes (like clubs and tech-stacks that I used), I was in my comfort zone. From my experience, once you know that you’re in a comfort zone, that is exactly when you should start taking actions. Then, I found out the concept of open source. I know that I could hone my skills even further in the community, plus I could learn from the very best from all over the world. I took the initiative to join some Discord channels for open source communities and try to contribute to an open source which then somewhat went begrudgingly bad. Frankly, the experience wasn’t as good as I expected. Trying to pinch my way in a Google Summer of Code project, I am overwhelmed by numerous people trying to do the same.
-
-
-I thought open source would be like this all the time and it failed me. But then, I took my second chance and joined Layer5. First two weeks, I tried to familiarize myself with the project and joined in the community calls. I remember sharing my screen the first time in the community call, and it was thrilling, my hands can't stop shaking. I was very excited to share my tiny bit of change in the UI which then welcomed wholeheartedly by the people inside. Overall, I met with a lot of wonderful people that don't mind extending their hands if I am in difficulty. My thoughts on open source were wrong and I realize that it's just a little badness from the overall goodness. Just like Yin Yang. Layer5 has been a supportive community that not only develops your technical side, it nurtures your thinking and reasoning.
-
-
-
-
- Rudraksh Pareek
-
-
-
-
-
-My journey with open source started when I got into college and fell into the company of some geeky open source evangelists. They were the folks from my local open source communities, OSDC and JODC. I learnt there what it means to be a good open source citizen. The fact that I could learn by contributing to a real world project albeit being a student, novice in programming, intrigued me the most and thus I had this goal clear in my mind to make an impact by working on open source software.
-However, it was easier said than done. I started making small contributions to some projects that I came across but couldn't do much past that. Me being a shy kid and the lack of a welcoming community always came into my way. But this all changed when I approached Lee in the CNCF slack for a GSoC internship. I was invited to Layer5. Since day one, I could feel there was something much different about how the community is treated here. Just as I joined, I received a ton of welcome messages and resources to get started. With the course of time and some great advice I moved on from that internship. I decided to become a good contributor first. Though I started with small contributions here too, this time I was able to scale up with time with help and guidance from the community. Whenever I was assigned something, I tried to get my teeth into it as deep as I could before reaching out for help. This helped me learn a lot in a healthy way.
-
-
- There was so much happening around and I wanted to be a part of it all. So I started attending all the meetings and was able to put my finger into many pies. I soon became better at expressing my thoughts and pretty soon, I developed an interest in CI/CD practices. Starting with small workflows, I went on to write GitHub actions for performing SMI conformance and SMP tests in CI pipelines. At the same time, I also found myself working on mesheryctl and the adapters as I came across bugs while working on the actions. Fast forward a few months and I was nominated a Meshery CI maintainer. I couldn't be much happier than this but little did I know there was more coming.
-I learnt about how internships worked at Layer5 during the time I spent and agreed with it in the best sense. Generally, open source projects tend to get more welcoming and open around the months of internship program applications. However, this short span often leads to unjust outcomes.
-
-
- Thus, I believe paying back for what you give to the project is a philosophy in the best faith of everyone in the long term. I kept my patience until I was asked to apply for an internship and I eventually got selected. I finally knew that I had started to make that impact I always wanted to.
-During the course of my internship, I'll be working under the mentorship of Utkarsh Srivastava on improving Layer5 Cloud, the remote provider, and making it securely distributable and usable in "on premise environments". I'll also be collaborating with Ashish Tiwari on integrating a workflow engine with Meshery introducing best practices to be followed by management software.
-Looking forward to learning and growing during this time while continuing to try my best to help others in the community.
-
-
-
-Thank you.
-
-
-
- Nithish Karthik
-
-
-
-
- I knew exactly what I wanted to do ever since my childhood, I wanted to become a programmer. Technology related stuff always intrigued me. But I had to prepare for an entrance examination IITJEE which required enormous dedication and focus to succeed. And so, I had to put my coding dreams on hold till I joined college.
-
-
-
-But after I joined college, I felt a sense of freedom within me, in the sense that I could now pursue my passion wholeheartedly. So, the next question was, "Where do I start ?".
-There were a lot of buzz words going around in my college among my peers like CP, Dev, AI and ML etc. I also noticed that people were forcing themselves to do them even when they had no sense of passion or appreciation towards the field. But for me, I always had more joy in the process of doing something than the outcome I get from it. So, I started exploring various fields to find what I loved the most. And I found that I wanted to do development.
-
-
-
-So, I started working on myself. After I got the fundamentals clear, I wanted to have some practical experience to have an idea of how production grade products are being made. So, I worked on a couple of startups to get an exposure to real world development. And I learned a lot during that period. But then, I felt I needed to switch my gear. The idea of open source has always intrigued me the most but my efforts towards open source contribution has not been a success because,
-
-1. I always got intimidated by the size of codebase
-2. I didn't have people guiding me
-
-Some of my seniors, who had the best interest in me, encouraged me to get into open source, but I did not take it seriously because I felt intimidated by the idea. I instead thought I would look for some open source internships that way I would have someone mentoring me and that would help me in starting my open source journey. I went through many programs but most of them were closed at that time, except, Meshery in LFX. I thought, this is the only choice I have, let's do it, I had nothing to lose. I applied for that program and as a prerequisite, I had to engage with the community. I looked at the community calendar and I saw that there was a newcomer's call that day and I attended it. I have never had such a warm welcome in any other communities.
-
-
-
-
-On that day, I knew that this community is special and I should spend more time with it. I explored the projects and as usual, I felt intimidated, but this time, I had people, wonderful people to help me. I landed my first open source PR, which was a single line style change. But the encouragement and support I got from the community for that was so wonderful . I realised that this community is not just about building best quality products but also about building best quality human beings. It has been a roller coaster ride with Layer5 since then. I got so involved with the process that I had stopped caring about getting that internship.
-
-
-
- The community has really wonderful people who taught me not only about coding, but also about "How to be". I am really grateful that I found this community and I hope that everyone has a chance to experience this.
-I started engaging more in the community projects, especially Meshery UI and always kept coming up with ways to improve it.
-
-
- And fast forward to September 2021, I was told to enroll for the LFX fall term mentorship program and here I am. But, this has never been the goal for me, there is more to me and Layer5 than this internship. I will be engaged with this community as long as I can and will try to give back as much as I can.
-
-
- Thank you
-
-
- Ashish Tiwari
-
-
-
-
-I started my programming career in 2020 when my classmates were bagging internships.I started late because the first two years of my college I never thought that I was a "programming guy" as I always was more of a Physics/Mathematics guy. But in 2020, when the pandemic hit I started programming from "hello world". I thought I was too late to the party and often felt overwhelmed. After 1 year of getting a taste of everything from data structures, web development, databases and everything in between that a CS undergraduate comes across; I thought to call myself a Backend dev. But I still was dissatisfied and finding something interesting when I came across the concept of containerization which looked magic to me. From there it was a roller coaster ride to kubernetes and then understanding service meshes. I immediately was drawn into the entire CNCF ecosystem.
-
-
-After procrastinating for a while, I learnt golang one night, made a side project to feel confident in it and dove back into watching CNCF talks explaining some exciting technology in Golang code.During all this my friend and also my current mentor, Utkarsh helped me through and through. He explained to me what Meshery is and I was immediately drawn in because Meshery is a good vantage point to the entire CNCF ecosystem. Believe me, while working on meshery at one point or another you will run into almost all major projects under CNCF.
-Like for any other beginner, it was all too overwhelming but exciting at the same time. Man it's such a rush when you realize that you don't know so much stuff because then there is an open window for absorbing all that stuff. I started going through docs, blogs and CNCF talks(shit that rhymed). I still binge CNCF talks. There is a plethora of good talks for you, if you are a beginner. I always prefer those over any "youtube tutorials". Anyways, back to my journey.
-
-
-So two months ago, I found an open issue in mesheryctl. I solved the issue/enhancement, showed the code in a community meeting and got the PR merged. This was my first ever open source contribution. From there it just took off. I wrote a new command in mesheryctl then wrote unit tests. All this while trying to get an opportunity to write code for any core component like meshery server or adapters. Then one day I accidentally got into a WASM filter meeting(believe me,joined accidentally), got asked to add one feature and I said - "yes". And this is how it starts for most people. You get out of your comfort zone and say "yes", start learning new stuff, make mistakes, get corrected and the cycle continues. Fast forward two months, I was offered an internship.From what I have learnt as a person who started late is that you only need two things- "Curiosity" to ask questions out of your comfort zone and "Resilience" to absorb answers when they are thrown at you. Layer5 is an amazing community.
-
-
-I guarantee you will not find such a warm and welcoming community so easily. If you come here for internships, you won't be here for long (or anywhere else to be honest). When your goals are solely to gain knowledge, experience while contributing to a niche, new and exciting tech- the opportunities will be waiting for you. I still have a long way to go and so much to learn. My journey with this project is certainly going to be longer than the span of this internship.
-
- \- Nithish, Ashish, Rudraksh and Bariq
-
+---
+title: "Meet the Fall Interns of 2021"
+date: 2021-09-01 08:00:00 +0000
+author: Interns of Fall 2021
+thumbnail: ./fall-interns.webp
+darkthumbnail: ./fall-interns.webp
+category: "Community"
+tags:
+ - Community
+featured: true
+published: true
+---
+
+
+
+import Nithish from "./nithish-karthik.webp";
+import Ashish from "./ashish-tiwari.webp";
+import Rudraksh from "./rudraksh-pareek.webp";
+import Bariq from "./bariq-nurlis.webp";
+
+
+
+
+
+
+
+
+ Layer5 participates in many
+
+ open source internship programs
+
+ . We seek out existing contributors who actively reflect the culture and
+ principles of Layer5 to participate in these programs. Here are the Fall of 2021's
+ open source interns.
+
+
+
+Hear about their journeys and follow along this fall as they make waves in the Layer5 community.
+
+
+
+ Bariq Nurlis
+
+
+
+
+
+ The idea of contributing to an open source has been on the back of my mind since I enrolled in college back in 2019. Like how most people formulate what and how they will do in the uni, I also came from normalcy. In Singapore, students are aiming to get the best mark in every possible lesson in college as our grades hold a very high importance in the culture. Going back and forth between classes, planning a startup with my peers, volunteering in community clubs, I had a spectacular two years in uni.
+
+
+However, during the last summer break, I started asking myself questions. How should I be better? What should I do? When should I do it? As I got more familiar with the Uni and all my messes (like clubs and tech-stacks that I used), I was in my comfort zone. From my experience, once you know that you’re in a comfort zone, that is exactly when you should start taking actions. Then, I found out the concept of open source. I know that I could hone my skills even further in the community, plus I could learn from the very best from all over the world. I took the initiative to join some Discord channels for open source communities and try to contribute to an open source which then somewhat went begrudgingly bad. Frankly, the experience wasn’t as good as I expected. Trying to pinch my way in a Google Summer of Code project, I am overwhelmed by numerous people trying to do the same.
+
+
+I thought open source would be like this all the time and it failed me. But then, I took my second chance and joined Layer5. First two weeks, I tried to familiarize myself with the project and joined in the community calls. I remember sharing my screen the first time in the community call, and it was thrilling, my hands can't stop shaking. I was very excited to share my tiny bit of change in the UI which then welcomed wholeheartedly by the people inside. Overall, I met with a lot of wonderful people that don't mind extending their hands if I am in difficulty. My thoughts on open source were wrong and I realize that it's just a little badness from the overall goodness. Just like Yin Yang. Layer5 has been a supportive community that not only develops your technical side, it nurtures your thinking and reasoning.
+
+
+
+
+ Rudraksh Pareek
+
+
+
+
+
+My journey with open source started when I got into college and fell into the company of some geeky open source evangelists. They were the folks from my local open source communities, OSDC and JODC. I learnt there what it means to be a good open source citizen. The fact that I could learn by contributing to a real world project albeit being a student, novice in programming, intrigued me the most and thus I had this goal clear in my mind to make an impact by working on open source software.
+However, it was easier said than done. I started making small contributions to some projects that I came across but couldn't do much past that. Me being a shy kid and the lack of a welcoming community always came into my way. But this all changed when I approached Lee in the CNCF slack for a GSoC internship. I was invited to Layer5. Since day one, I could feel there was something much different about how the community is treated here. Just as I joined, I received a ton of welcome messages and resources to get started. With the course of time and some great advice I moved on from that internship. I decided to become a good contributor first. Though I started with small contributions here too, this time I was able to scale up with time with help and guidance from the community. Whenever I was assigned something, I tried to get my teeth into it as deep as I could before reaching out for help. This helped me learn a lot in a healthy way.
+
+
+ There was so much happening around and I wanted to be a part of it all. So I started attending all the meetings and was able to put my finger into many pies. I soon became better at expressing my thoughts and pretty soon, I developed an interest in CI/CD practices. Starting with small workflows, I went on to write GitHub actions for performing SMI conformance and SMP tests in CI pipelines. At the same time, I also found myself working on mesheryctl and the adapters as I came across bugs while working on the actions. Fast forward a few months and I was nominated a Meshery CI maintainer. I couldn't be much happier than this but little did I know there was more coming.
+I learnt about how internships worked at Layer5 during the time I spent and agreed with it in the best sense. Generally, open source projects tend to get more welcoming and open around the months of internship program applications. However, this short span often leads to unjust outcomes.
+
+
+ Thus, I believe paying back for what you give to the project is a philosophy in the best faith of everyone in the long term. I kept my patience until I was asked to apply for an internship and I eventually got selected. I finally knew that I had started to make that impact I always wanted to.
+During the course of my internship, I'll be working under the mentorship of Utkarsh Srivastava on improving Layer5 Cloud, the remote provider, and making it securely distributable and usable in "on premise environments". I'll also be collaborating with Ashish Tiwari on integrating a workflow engine with Meshery introducing best practices to be followed by management software.
+Looking forward to learning and growing during this time while continuing to try my best to help others in the community.
+
+
+
+Thank you.
+
+
+
+ Nithish Karthik
+
+
+
+
+ I knew exactly what I wanted to do ever since my childhood, I wanted to become a programmer. Technology related stuff always intrigued me. But I had to prepare for an entrance examination IITJEE which required enormous dedication and focus to succeed. And so, I had to put my coding dreams on hold till I joined college.
+
+
+
+But after I joined college, I felt a sense of freedom within me, in the sense that I could now pursue my passion wholeheartedly. So, the next question was, "Where do I start ?".
+There were a lot of buzz words going around in my college among my peers like CP, Dev, AI and ML etc. I also noticed that people were forcing themselves to do them even when they had no sense of passion or appreciation towards the field. But for me, I always had more joy in the process of doing something than the outcome I get from it. So, I started exploring various fields to find what I loved the most. And I found that I wanted to do development.
+
+
+
+So, I started working on myself. After I got the fundamentals clear, I wanted to have some practical experience to have an idea of how production grade products are being made. So, I worked on a couple of startups to get an exposure to real world development. And I learned a lot during that period. But then, I felt I needed to switch my gear. The idea of open source has always intrigued me the most but my efforts towards open source contribution has not been a success because,
+
+1. I always got intimidated by the size of codebase
+2. I didn't have people guiding me
+
+Some of my seniors, who had the best interest in me, encouraged me to get into open source, but I did not take it seriously because I felt intimidated by the idea. I instead thought I would look for some open source internships that way I would have someone mentoring me and that would help me in starting my open source journey. I went through many programs but most of them were closed at that time, except, Meshery in LFX. I thought, this is the only choice I have, let's do it, I had nothing to lose. I applied for that program and as a prerequisite, I had to engage with the community. I looked at the community calendar and I saw that there was a newcomer's call that day and I attended it. I have never had such a warm welcome in any other communities.
+
+
+
+
+On that day, I knew that this community is special and I should spend more time with it. I explored the projects and as usual, I felt intimidated, but this time, I had people, wonderful people to help me. I landed my first open source PR, which was a single line style change. But the encouragement and support I got from the community for that was so wonderful . I realised that this community is not just about building best quality products but also about building best quality human beings. It has been a roller coaster ride with Layer5 since then. I got so involved with the process that I had stopped caring about getting that internship.
+
+
+
+ The community has really wonderful people who taught me not only about coding, but also about "How to be". I am really grateful that I found this community and I hope that everyone has a chance to experience this.
+I started engaging more in the community projects, especially Meshery UI and always kept coming up with ways to improve it.
+
+
+ And fast forward to September 2021, I was told to enroll for the LFX fall term mentorship program and here I am. But, this has never been the goal for me, there is more to me and Layer5 than this internship. I will be engaged with this community as long as I can and will try to give back as much as I can.
+
+
+ Thank you
+
+
+ Ashish Tiwari
+
+
+
+
+I started my programming career in 2020 when my classmates were bagging internships.I started late because the first two years of my college I never thought that I was a "programming guy" as I always was more of a Physics/Mathematics guy. But in 2020, when the pandemic hit I started programming from "hello world". I thought I was too late to the party and often felt overwhelmed. After 1 year of getting a taste of everything from data structures, web development, databases and everything in between that a CS undergraduate comes across; I thought to call myself a Backend dev. But I still was dissatisfied and finding something interesting when I came across the concept of containerization which looked magic to me. From there it was a roller coaster ride to kubernetes and then understanding service meshes. I immediately was drawn into the entire CNCF ecosystem.
+
+
+After procrastinating for a while, I learnt golang one night, made a side project to feel confident in it and dove back into watching CNCF talks explaining some exciting technology in Golang code.During all this my friend and also my current mentor, Utkarsh helped me through and through. He explained to me what Meshery is and I was immediately drawn in because Meshery is a good vantage point to the entire CNCF ecosystem. Believe me, while working on meshery at one point or another you will run into almost all major projects under CNCF.
+Like for any other beginner, it was all too overwhelming but exciting at the same time. Man it's such a rush when you realize that you don't know so much stuff because then there is an open window for absorbing all that stuff. I started going through docs, blogs and CNCF talks(shit that rhymed). I still binge CNCF talks. There is a plethora of good talks for you, if you are a beginner. I always prefer those over any "youtube tutorials". Anyways, back to my journey.
+
+
+So two months ago, I found an open issue in mesheryctl. I solved the issue/enhancement, showed the code in a community meeting and got the PR merged. This was my first ever open source contribution. From there it just took off. I wrote a new command in mesheryctl then wrote unit tests. All this while trying to get an opportunity to write code for any core component like meshery server or adapters. Then one day I accidentally got into a WASM filter meeting(believe me,joined accidentally), got asked to add one feature and I said - "yes". And this is how it starts for most people. You get out of your comfort zone and say "yes", start learning new stuff, make mistakes, get corrected and the cycle continues. Fast forward two months, I was offered an internship.From what I have learnt as a person who started late is that you only need two things- "Curiosity" to ask questions out of your comfort zone and "Resilience" to absorb answers when they are thrown at you. Layer5 is an amazing community.
+
+
+I guarantee you will not find such a warm and welcoming community so easily. If you come here for internships, you won't be here for long (or anywhere else to be honest). When your goals are solely to gain knowledge, experience while contributing to a niche, new and exciting tech- the opportunities will be waiting for you. I still have a long way to go and so much to learn. My journey with this project is certainly going to be longer than the span of this internship.
+
+ \- Nithish, Ashish, Rudraksh and Bariq
+
diff --git a/src/collections/blog/2021/2021-09-20-service-mesh-specifications-and-why-they-matter/index.mdx b/src/collections/blog/2021/2021-09-20-service-mesh-specifications-and-why-they-matter/index.mdx
index ac39a5a4b275..e800aefcfcb1 100644
--- a/src/collections/blog/2021/2021-09-20-service-mesh-specifications-and-why-they-matter/index.mdx
+++ b/src/collections/blog/2021/2021-09-20-service-mesh-specifications-and-why-they-matter/index.mdx
@@ -1,145 +1,146 @@
----
-title: "Service Mesh Specifications and Why They Matter"
-date: 2021-09-20 10:30:05 -0530
-author: Debopriya Bhattacharjee
-thumbnail: ./Cover-image.webp
-darkthumbnail: ./Cover-image.webp
-category: "Service Mesh"
-tags:
- - Projects
- - Service Mesh Interface
- - Service Mesh Performance
-published: true
-resource: true
-type: Blog
-product: Service Mesh Performance
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-
-import Hamlet from "./Hamlet.webp";
-import Graph from "./Graph1.webp";
-import Bucket from "./Graph2.webp";
-import SMI from "./SMI-demo.webp";
-import SMP from "./SMP.webp";
-import Abstractions from "./abstractions.webp";
-import Journey from "./cloud-native-journey.webp";
-import Flowchart from "./flowchart.webp";
-import { Link } from "gatsby";
-
-
-
-
-
-
- Lee Calcote is an innovator, product and technology leader, active in the community as a Docker Captain, Cloud Native Ambassador and GSoC, GSoD, and Community Bridge Mentor. In this talk, he walked through service mesh specifications and why they matter in your deployment.
- How many service mesh specifications do you know? He went through all of them. So, no worries if you're unfamiliar.
-
-
-
-### Service Mesh Specifications:
-
-
-As the ubiquity of service meshes unfolds and they become a commonplace for any cloud native or edge environment, so does the need for vendor and technology-agnostic interfaces to interact with them. The Service Mesh Interface (SMI), the Service Mesh Performance (SMP), and Multi-Vendor Service Mesh Interoperation (Hamlet) are three open specifications solving the challenge of interoperability, workload and performance management between service meshes.
-
-Learn what makes each of them unique and why they are much needed. See each of these three specifications in action as we use Meshery, the open-source service mesh management plane to demonstrate the value and functionality of each service mesh abstraction, and the adherence of these specifications by Istio, Linkerd, Consul and other popular service meshes.
-
-### Cloud native Journey to service meshes:
-
-
-
-The advent of cloud native was the popularization of containers. Thank you Docker! From there, containers took off like wildfire. Turns out you need an orchestrator to wrangle that sprawl. We saw a number of orchestrators come and we still have a number of orchestrators around.
-
-Service meshes have become a hot topic in the last few years. They still continue to be, rightfully so, a very powerful piece of technology. “A lot of the power is yet to come from my perspective. For my part, I believe that there is a tomorrow in which data plane intelligence really matters. And matters about how people write cloud native applications.”, Lee emphasized. Not everyone quite understands the capabilities of meshes as they are promoted and spoken about today. So come along into the journey of service mesh.
-
-There are a number of service meshes out there. One of the community projects is to track the landscape of all of the meshes there are. There’s a lot to say about each of them, their architecture, and their working. Why are they made? Who are they focused on? What do they do? When did they come about? Why are some of them not here anymore? Why are we still seeing new ones? A lot of things to go through. You might be interested in any number of the details that the landscape tracks.
-
Be Aware, It's Meshy Out There!
-
-### Service Mesh Interface
-
-
-
Its goal and genesis were born inside of Kubernetes.
-
Being a specification that is native to Kubernetes, its focus is on lowest common denominator functionality.
-
The focus on bringing forth APIs that highlight and reinforce the most common use cases that service meshes are being used for currently
-
Leaves space and provides extensibility room for additional APIs to address other service mesh functionality as more people adopt and make use cases well known.
-
There are seven service meshes that claim compatibility with SMI. There's been a community effort, open-source effort to create service mesh conformance tests to assert whether or not a given service mesh is compatible with SMI
-
In order to facilitate those types of tests, you need to have a tool to provision a sample application on those services which will generate load and test whether traffic splitting behaves as expected or works with that service mesh implementation properly.
-
Then you need to be able to collect the results, guarantee the provenance of those results and publish them.
-
As a community, we turned to Meshery as the tool to implement SMI conformance and we have been working with the individual service meshes to validate their conformance.
-
-Meshery
-
-
We work on an open-source project called Meshery.
-
Meshery, the cloud native management plane, is the canonical implementation of the service mesh performance.
-
The management planes can do a number of things to help bridge the divide between other back-end systems and service meshes. They also help performance management, configuration management, making sure you are following best practices in your implementations by taking common patterns and applying them to your environment
-
-Let's take a moment to demo what it looks like to validate conformance in SMI using Meshery.
-
-
-
-
We need to spin up Meshery locally
-
We use mesheryctl as the command line interface to work with Meshery.
-
We can interact with a number of different service mesh. The service mesh we’re going to work with today is an Open service mesh (one of those 7 that is compatible with SMI). Let’s put it to the test.
-
We'll initiate SMI conformance
-
These tests go and do assertions across these different specifications. We’re looking at traffic access, traffic splitting, traffic specification. Meshery then collects these results and will eventually be publishing them in combination with the SMI project.
-
-
-### Service Mesh Performance
-
-
-
Focused on describing and capturing the performance of a service mesh.
-
The overhead of the value is another way of looking at it and characterizing it.
-
Trying to characterize the performance of the infrastructure of a service mesh can be really difficult.
-
Considering the number of variables that you would have to track, how difficult it can be to have repeatable tests, and benchmark your environment, to track your history based on your environment, compare performance between other meshes people need.
-
SMP creates a standard way of capturing the performance of the mesh to help with these issues.
-
It's also the way in which you're configuring your control plan of your service mesh.
-
-
-You might be using a client library to do some service mesh functionality. Maybe you're using those in combination with the service mesh. What costs more? What's more efficient? What's more powerful? Maybe you're using web assembly and filters there.
-These are all open questions that SMP assists in answering in your environment. You’d be surprised by some of the results of some tests that we have done and that the community has done in combination with a couple of universities and graduate students.
-
-Performance Test
-
-Demonstration of the implementation of service mesh Performance:
-
-
-
-
On the terminal, we have a local deployment of Meshery running. You can also deploy on Kubernetes as well as the vendor Kubernetes platforms like AKS, EKS and GCP or you can use a dockerized container to run Meshery. You can also have your Kubernetes on Docker desktop.
-
We have the Open service mesh deployed.
-
The Meshery UI is exposed at 9081 port. This is the UI which is used to instantiate a Load test.
-
Over here you can see we have 3 load generators fortio, wrk2, nighthawk.
-
All of these load generators have their own set of attributes which they record correctly and each of its attributes have their own significance. We begin with fortio.
-
-
-
You can actually download the test results or you can just browse into the Results Tab and see all of the tests which you have run until now.
-
Next, we used nighthawk to generate the load and benchmark the service for the same. Nighthawk is a load generator which is maintained by the Envoy community and is relatively new. It still hasn't got its 1.0 release but right now Nighthawk has sufficient features to compete with different generators which are still in the play. It can generate a gRPC service on its own and it has some more attributes which you can expose using their CLI tools.
-
You can also see that Meshery has the capability to search your environment, see what specifications are being used and what's the load on your Kubernetes.
-
Jump into the results Tab and see how we compare with these results.
-
You can click on the download. You will see that a yaml gets downloaded in which you can browse and see that the start time, load time, the performance latencies, the metrics are being captured.
-
-
-### Hamlet or Multi-vendor Service Mesh Interoperation
-
-
-
Focus on service mesh federation
-
Specifies a set of API standards for enabling service mesh federation
-
Hamlet takes on a client-server architecture in which resources and services of one service mesh are discovered, registered and using a common format, information about them is exchanged between different service mesh.
-
Rules around authentication and authorization rules around which Services get exposed and to whom and who can communicate with them and whether or not they can do it securely. These are things that Hamlet addresses.
-
The specification currently consists of two APIs:
-
-
The Federated Resource Discovery API: API to authenticate and securely distribute resources between federated service meshes.
-
The Federated Service Discovery API: API to discover, reach, authenticate and securely communicate with federated services.
-
-
-
Part of the real power is the ability to overcome what are likely to be separate administrative domains. The intention here is to marry up connect two disparate service mesh deployments, those deployments might be of the same type, they might be of two different types.
-
-
-In addition to SMI, SMP and Hamlet there has been an emergence of service mesh patterns, by which people are running and operating service meshes. There is a service mesh working group under CNCFs network that is helping identify those patterns of which there's a list right now unbeknownst to you. Reach out, join it, help us work through the 60 patterns that are defined right now. 30 of those are going into an O’Reilly book called Service Mesh Patterns.
-
-Something that isn’t always obvious to folks is this piece of value that people get from a service mesh and actually from the specifications that we were just mentioning. It is the fact that teams are decoupled when you’re running a mesh. Developers get to iterate a bit independently of operators, and so do operators get to make changes to implement infrastructure to the way that applications behave independent of developers in the presence of a mesh. Both of these teams are significantly empowered. Everybody gets a piece of power when they deploy a mesh.
-
-
-_**P.S.: If these topics excite come and say "Hi" on our [Slack Channel](http://slack.layer5.io) and one of us will reach out to you!**_
-
-
+---
+title: "Service Mesh Specifications and Why They Matter"
+date: 2021-09-20 10:30:05 -0530
+author: Debopriya Bhattacharjee
+thumbnail: ./Cover-image.webp
+darkthumbnail: ./Cover-image.webp
+category: "Service Mesh"
+tags:
+ - Projects
+ - Service Mesh Interface
+ - Service Mesh Performance
+published: true
+resource: true
+type: Blog
+product: Service Mesh Performance
+---
+
+
+
+
+import Hamlet from "./Hamlet.webp";
+import Graph from "./Graph1.webp";
+import Bucket from "./Graph2.webp";
+import SMI from "./SMI-demo.webp";
+import SMP from "./SMP.webp";
+import Abstractions from "./abstractions.webp";
+import Journey from "./cloud-native-journey.webp";
+import Flowchart from "./flowchart.webp";
+
+
+
+
+
+
+
+ Lee Calcote is an innovator, product and technology leader, active in the community as a Docker Captain, Cloud Native Ambassador and GSoC, GSoD, and Community Bridge Mentor. In this talk, he walked through service mesh specifications and why they matter in your deployment.
+ How many service mesh specifications do you know? He went through all of them. So, no worries if you're unfamiliar.
+
+
+
+### Service Mesh Specifications:
+
+
+As the ubiquity of service meshes unfolds and they become a commonplace for any cloud native or edge environment, so does the need for vendor and technology-agnostic interfaces to interact with them. The Service Mesh Interface (SMI), the Service Mesh Performance (SMP), and Multi-Vendor Service Mesh Interoperation (Hamlet) are three open specifications solving the challenge of interoperability, workload and performance management between service meshes.
+
+Learn what makes each of them unique and why they are much needed. See each of these three specifications in action as we use Meshery, the open-source service mesh management plane to demonstrate the value and functionality of each service mesh abstraction, and the adherence of these specifications by Istio, Linkerd, Consul and other popular service meshes.
+
+### Cloud native Journey to service meshes:
+
+
+
+The advent of cloud native was the popularization of containers. Thank you Docker! From there, containers took off like wildfire. Turns out you need an orchestrator to wrangle that sprawl. We saw a number of orchestrators come and we still have a number of orchestrators around.
+
+Service meshes have become a hot topic in the last few years. They still continue to be, rightfully so, a very powerful piece of technology. “A lot of the power is yet to come from my perspective. For my part, I believe that there is a tomorrow in which data plane intelligence really matters. And matters about how people write cloud native applications.”, Lee emphasized. Not everyone quite understands the capabilities of meshes as they are promoted and spoken about today. So come along into the journey of service mesh.
+
+There are a number of service meshes out there. One of the community projects is to track the landscape of all of the meshes there are. There’s a lot to say about each of them, their architecture, and their working. Why are they made? Who are they focused on? What do they do? When did they come about? Why are some of them not here anymore? Why are we still seeing new ones? A lot of things to go through. You might be interested in any number of the details that the landscape tracks.
+
Be Aware, It's Meshy Out There!
+
+### Service Mesh Interface
+
+
+
Its goal and genesis were born inside of Kubernetes.
+
Being a specification that is native to Kubernetes, its focus is on lowest common denominator functionality.
+
The focus on bringing forth APIs that highlight and reinforce the most common use cases that service meshes are being used for currently
+
Leaves space and provides extensibility room for additional APIs to address other service mesh functionality as more people adopt and make use cases well known.
+
There are seven service meshes that claim compatibility with SMI. There's been a community effort, open-source effort to create service mesh conformance tests to assert whether or not a given service mesh is compatible with SMI
+
In order to facilitate those types of tests, you need to have a tool to provision a sample application on those services which will generate load and test whether traffic splitting behaves as expected or works with that service mesh implementation properly.
+
Then you need to be able to collect the results, guarantee the provenance of those results and publish them.
+
As a community, we turned to Meshery as the tool to implement SMI conformance and we have been working with the individual service meshes to validate their conformance.
+
+Meshery
+
+
We work on an open-source project called Meshery.
+
Meshery, the cloud native management plane, is the canonical implementation of the service mesh performance.
+
The management planes can do a number of things to help bridge the divide between other back-end systems and service meshes. They also help performance management, configuration management, making sure you are following best practices in your implementations by taking common patterns and applying them to your environment
+
+Let's take a moment to demo what it looks like to validate conformance in SMI using Meshery.
+
+
+
+
We need to spin up Meshery locally
+
We use mesheryctl as the command line interface to work with Meshery.
+
We can interact with a number of different service mesh. The service mesh we’re going to work with today is an Open service mesh (one of those 7 that is compatible with SMI). Let’s put it to the test.
+
We'll initiate SMI conformance
+
These tests go and do assertions across these different specifications. We’re looking at traffic access, traffic splitting, traffic specification. Meshery then collects these results and will eventually be publishing them in combination with the SMI project.
+
+
+### Service Mesh Performance
+
+
+
Focused on describing and capturing the performance of a service mesh.
+
The overhead of the value is another way of looking at it and characterizing it.
+
Trying to characterize the performance of the infrastructure of a service mesh can be really difficult.
+
Considering the number of variables that you would have to track, how difficult it can be to have repeatable tests, and benchmark your environment, to track your history based on your environment, compare performance between other meshes people need.
+
SMP creates a standard way of capturing the performance of the mesh to help with these issues.
+
It's also the way in which you're configuring your control plan of your service mesh.
+
+
+You might be using a client library to do some service mesh functionality. Maybe you're using those in combination with the service mesh. What costs more? What's more efficient? What's more powerful? Maybe you're using web assembly and filters there.
+These are all open questions that SMP assists in answering in your environment. You’d be surprised by some of the results of some tests that we have done and that the community has done in combination with a couple of universities and graduate students.
+
+Performance Test
+
+Demonstration of the implementation of service mesh Performance:
+
+
+
+
On the terminal, we have a local deployment of Meshery running. You can also deploy on Kubernetes as well as the vendor Kubernetes platforms like AKS, EKS and GCP or you can use a dockerized container to run Meshery. You can also have your Kubernetes on Docker desktop.
+
We have the Open service mesh deployed.
+
The Meshery UI is exposed at 9081 port. This is the UI which is used to instantiate a Load test.
+
Over here you can see we have 3 load generators fortio, wrk2, nighthawk.
+
All of these load generators have their own set of attributes which they record correctly and each of its attributes have their own significance. We begin with fortio.
+
+
+
You can actually download the test results or you can just browse into the Results Tab and see all of the tests which you have run until now.
+
Next, we used nighthawk to generate the load and benchmark the service for the same. Nighthawk is a load generator which is maintained by the Envoy community and is relatively new. It still hasn't got its 1.0 release but right now Nighthawk has sufficient features to compete with different generators which are still in the play. It can generate a gRPC service on its own and it has some more attributes which you can expose using their CLI tools.
+
You can also see that Meshery has the capability to search your environment, see what specifications are being used and what's the load on your Kubernetes.
+
Jump into the results Tab and see how we compare with these results.
+
You can click on the download. You will see that a yaml gets downloaded in which you can browse and see that the start time, load time, the performance latencies, the metrics are being captured.
+
+
+### Hamlet or Multi-vendor Service Mesh Interoperation
+
+
+
Focus on service mesh federation
+
Specifies a set of API standards for enabling service mesh federation
+
Hamlet takes on a client-server architecture in which resources and services of one service mesh are discovered, registered and using a common format, information about them is exchanged between different service mesh.
+
Rules around authentication and authorization rules around which Services get exposed and to whom and who can communicate with them and whether or not they can do it securely. These are things that Hamlet addresses.
+
+ The specification currently consists of two APIs:
+
+
The Federated Resource Discovery API: API to authenticate and securely distribute resources between federated service meshes.
+
The Federated Service Discovery API: API to discover, reach, authenticate and securely communicate with federated services.
+
+
+
Part of the real power is the ability to overcome what are likely to be separate administrative domains. The intention here is to marry up connect two disparate service mesh deployments, those deployments might be of the same type, they might be of two different types.
+
+
+In addition to SMI, SMP and Hamlet there has been an emergence of service mesh patterns, by which people are running and operating service meshes. There is a service mesh working group under CNCFs network that is helping identify those patterns of which there's a list right now unbeknownst to you. Reach out, join it, help us work through the 60 patterns that are defined right now. 30 of those are going into an O’Reilly book called Service Mesh Patterns.
+
+Something that isn’t always obvious to folks is this piece of value that people get from a service mesh and actually from the specifications that we were just mentioning. It is the fact that teams are decoupled when you’re running a mesh. Developers get to iterate a bit independently of operators, and so do operators get to make changes to implement infrastructure to the way that applications behave independent of developers in the presence of a mesh. Both of these teams are significantly empowered. Everybody gets a piece of power when they deploy a mesh.
+
+
+_**P.S.: If these topics excite 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/2021/2021-10-01-pipelining-service-mesh-specifications/index.mdx b/src/collections/blog/2021/2021-10-01-pipelining-service-mesh-specifications/index.mdx
index 1307e932942c..5107ffe83c99 100644
--- a/src/collections/blog/2021/2021-10-01-pipelining-service-mesh-specifications/index.mdx
+++ b/src/collections/blog/2021/2021-10-01-pipelining-service-mesh-specifications/index.mdx
@@ -1,191 +1,193 @@
----
-title: "Pipelining Service Mesh Specifications"
-subtitle: "Using SMI and SMP specs on your CI/CD pipelines with Meshery's GitHub Actions"
-date: 2021-11-09 10:30:05 -0530
-author: Layer5 Team
-thumbnail: ./service-mesh-specifications.webp
-darkthumbnail: ./service-mesh-specifications.webp
-category: "Service Mesh"
-tags:
- - Service Mesh Interface
- - Service Mesh Performance
- - Meshery
-published: true
-resource: true
-type: Blog
-product: Service Mesh Performance
----
-
-import { Link } from "gatsby";
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-import token from "./download-token.webp";
-import perfdashboard from "./service-mesh-performance-profile-test-results.webp"
-import smidashboard from "./smi-conformance-result.webp";
-import smpLogo from "../../../../assets/images/service-mesh-performance/horizontal/smp-dark-text-side.svg";
-import smiLogo from "../../../../assets/images/service-mesh-icons/service-mesh-interface/horizontal-stackedtext/color/servicemeshinterface-horizontal-stackedtext-color.svg";
-import githubBlack from "../../../../assets/images/socialIcons/github_black.svg";
-
-
-
-
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.
-
-
Service Mesh Performance standardizes service mesh value measurement, characterizing any deployment's performance by capturing the details of infrastructure capacity, service mesh configuration and workload metadata.
-
-
Service Mesh Interface provides a standard interface for service meshes on Kubernetes. These (currently) four specfications offer a common denominator set of interfaces to support most common service mesh use cases and the flexibility to evolve to support new service mesh capabilities over time.
-
-
As a service mesh agnostic tool that provides lifecycle and performance management of a large number of (10+) service meshes, Kubernetes applications, service mesh patterns and WebAssembly filters, Meshery is the ideal tool for the job when it comes to implementing these specifications.
But how do we use these actions? What do they offer? Let’s find out!
-
-
Service Mesh Interface Conformance GitHub Action
-
-
Conformance of SMI specifications is defined as a series of test assertions. These test assertions are categorised by SMI specification (of which, there are currently four specifications) and comprise the complete suite of SMI conformance tests. Conformance requirements will change appropriately as each new version of the SMI spec is released. Refer to Meshery's documentation for details of how Meshery performs SMI conformance.
-
-
-
-
Using Meshery's SMI Conformance GitHub Action
-
-
The Service Mesh Interface Conformance GitHub Action is available in the GitHub Marketplace. You can configure this action to trigger with each of your releases, on every pull request. or any GitHub workflow trigger event.
-
An example of the action configuration which runs on every release is shown below. The action handles setting up a Kubernetes environment, deploying the service mesh (see supported service meshes), running the conformance tests and reporting back the results to the SMI Conformance dashboard in Meshery.
You can download a token from Meshery and add it as a GitHub secret (in the example above, the secret is MESHERY_PROVIDER_TOKEN). After the test is run, you can view the results from the Service Mesh Interface dashboard in Meshery UI.
-
-
-Meshery's Service Mesh Interface Conformance Results
Measuring and managing the performance of a service mesh is key to efficient operation of any service mesh. Meshery is the canonical implementation of the Service Mesh Performance specification. You can choose from multiple load generators and use a highly configurable set of load profiles with variable tunable facets to run a performance test. Meshery packages all these features into an easy-to-use GitHub Action.
-
-
-
-
Using Meshery's Service Mesh Performance GitHub Action
-
-
The Service Mesh Performance GitHub Action is available in the GitHub Marketplace.You can create your own performance profiles to run repeatable tests with Meshery. You can configure this action to trigger with each of your releases, on every pull request. or any GitHub workflow trigger event. A sample configuration of the action is shown below.
See this sample GitHub workflow (action.yml) for more configuration details.
-
-
-
-
The results from the tests are updated on the Performance Management dashboard in Meshery. To learn more about interpreting the test results, check out this guide. You can always checkout the Meshery User Guides to dive deep into these features.
-
-Stay meshy!
-
+---
+title: "Pipelining Service Mesh Specifications"
+subtitle: "Using SMI and SMP specs on your CI/CD pipelines with Meshery's GitHub Actions"
+date: 2021-11-09 10:30:05 -0530
+author: Layer5 Team
+thumbnail: ./service-mesh-specifications.webp
+darkthumbnail: ./service-mesh-specifications.webp
+category: "Service Mesh"
+tags:
+ - Service Mesh Interface
+ - Service Mesh Performance
+ - Meshery
+published: true
+resource: true
+type: Blog
+product: Service Mesh Performance
+---
+
+
+
+
+import token from "./download-token.webp";
+import perfdashboard from "./service-mesh-performance-profile-test-results.webp"
+import smidashboard from "./smi-conformance-result.webp";
+import smpLogo from "../../../../assets/images/service-mesh-performance/horizontal/smp-dark-text-side.svg";
+import smiLogo from "../../../../assets/images/service-mesh-icons/service-mesh-interface/horizontal-stackedtext/color/servicemeshinterface-horizontal-stackedtext-color.svg";
+import githubBlack from "../../../../assets/images/socialIcons/github_black.svg";
+
+
+
+
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.
+
+
Service Mesh Performance standardizes service mesh value measurement, characterizing any deployment's performance by capturing the details of infrastructure capacity, service mesh configuration and workload metadata.
+
+
Service Mesh Interface provides a standard interface for service meshes on Kubernetes. These (currently) four specfications offer a common denominator set of interfaces to support most common service mesh use cases and the flexibility to evolve to support new service mesh capabilities over time.
+
+
As a service mesh agnostic tool that provides lifecycle and performance management of a large number of (10+) service meshes, Kubernetes applications, service mesh patterns and WebAssembly filters, Meshery is the ideal tool for the job when it comes to implementing these specifications.
But how do we use these actions? What do they offer? Let’s find out!
+
+
Service Mesh Interface Conformance GitHub Action
+
+
Conformance of SMI specifications is defined as a series of test assertions. These test assertions are categorised by SMI specification (of which, there are currently four specifications) and comprise the complete suite of SMI conformance tests. Conformance requirements will change appropriately as each new version of the SMI spec is released. Refer to Meshery's documentation for details of how Meshery performs SMI conformance.
+
+
+
+
Using Meshery's SMI Conformance GitHub Action
+
+
The Service Mesh Interface Conformance GitHub Action is available in the GitHub Marketplace. You can configure this action to trigger with each of your releases, on every pull request. or any GitHub workflow trigger event.
+
An example of the action configuration which runs on every release is shown below. The action handles setting up a Kubernetes environment, deploying the service mesh (see supported service meshes), running the conformance tests and reporting back the results to the SMI Conformance dashboard in Meshery.
You can download a token from Meshery and add it as a GitHub secret (in the example above, the secret is MESHERY_PROVIDER_TOKEN). After the test is run, you can view the results from the Service Mesh Interface dashboard in Meshery UI.
+
+
+
+Meshery's Service Mesh Interface Conformance Results
+
Measuring and managing the performance of a service mesh is key to efficient operation of any service mesh. Meshery is the canonical implementation of the Service Mesh Performance specification. You can choose from multiple load generators and use a highly configurable set of load profiles with variable tunable facets to run a performance test. Meshery packages all these features into an easy-to-use GitHub Action.
+
+
+
+
Using Meshery's Service Mesh Performance GitHub Action
+
+
The Service Mesh Performance GitHub Action is available in the GitHub Marketplace.You can create your own performance profiles to run repeatable tests with Meshery. You can configure this action to trigger with each of your releases, on every pull request. or any GitHub workflow trigger event. A sample configuration of the action is shown below.
See this sample GitHub workflow (action.yml) for more configuration details.
+
+
+
+
The results from the tests are updated on the Performance Management dashboard in Meshery. To learn more about interpreting the test results, check out this guide. You can always checkout the Meshery User Guides to dive deep into these features.
+
+Stay meshy!
+
diff --git a/src/collections/blog/2021/2021-10-04-ccoss-meshery-event/index.mdx b/src/collections/blog/2021/2021-10-04-ccoss-meshery-event/index.mdx
index e091d65ce816..2318a813b511 100644
--- a/src/collections/blog/2021/2021-10-04-ccoss-meshery-event/index.mdx
+++ b/src/collections/blog/2021/2021-10-04-ccoss-meshery-event/index.mdx
@@ -1,34 +1,34 @@
----
-title: "Meshery Workshop at CCOSS 2021"
-subtitle: "Announcing the participation of the Meshery project in CCOSS 2021 event"
-date: 2021-10-04 11:10:00 +0000
-author: Rodolfo Martinez Vega
-thumbnail: ./ccoss-open-source.webp
-darkthumbnail: ./ccoss-open-source.webp
-category: Events
-tags:
- - Events
- - Meshery
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import meshery from "./meshery-logo-light-text.webp";
-
-
-
October 04 to 09, 2021
-
-
CCOSS is an Open Source Software Contributor Summit that focuses on promoting and increasing the contributions from people and organizations to Open Source in Latin America. This event will happen online from October 4th to 9th.
-
-
Meshery will be participating as a project in a workshop where attendees will contribute to Documentation, Tests, and more. It’s a good opportunity to learn how to contribute to Open Source supported by the community. To participate you can register here.
-
Speakers:
-
Rodolfo Martinez Vega
-
Alonso López Romo
-
-
-
- We hope to see you at CCOSS Meshery contribution workshop 2021. Be sure to say hello
- in the Layer5 Community!
-
+---
+title: "Meshery Workshop at CCOSS 2021"
+subtitle: "Announcing the participation of the Meshery project in CCOSS 2021 event"
+date: 2021-10-04 11:10:00 +0000
+author: Rodolfo Martinez Vega
+thumbnail: ./ccoss-open-source.webp
+darkthumbnail: ./ccoss-open-source.webp
+category: Events
+tags:
+ - Events
+ - Meshery
+published: true
+---
+
+
+
+import meshery from "./meshery-logo-light-text.webp";
+
+
+
October 04 to 09, 2021
+
+
CCOSS is an Open Source Software Contributor Summit that focuses on promoting and increasing the contributions from people and organizations to Open Source in Latin America. This event will happen online from October 4th to 9th.
+
+
Meshery will be participating as a project in a workshop where attendees will contribute to Documentation, Tests, and more. It’s a good opportunity to learn how to contribute to Open Source supported by the community. To participate you can register here.
+
Speakers:
+
Rodolfo Martinez Vega
+
Alonso López Romo
+
+
+
+ We hope to see you at CCOSS Meshery contribution workshop 2021. Be sure to say hello
+ in the Layer5 Community!
+
\ No newline at end of file
diff --git a/src/collections/blog/2021/2021-10-09-an-introduction-to-meshery/index.mdx b/src/collections/blog/2021/2021-10-09-an-introduction-to-meshery/index.mdx
index 2e1290aef0d2..f5ebd4e8f320 100644
--- a/src/collections/blog/2021/2021-10-09-an-introduction-to-meshery/index.mdx
+++ b/src/collections/blog/2021/2021-10-09-an-introduction-to-meshery/index.mdx
@@ -1,393 +1,395 @@
----
-title: "An Introduction to Meshery (Webinar-on-Demand) "
-date: 2021-10-09 10:30:05 -0530
-author: Debopriya Bhattacharjee
-thumbnail: ./meshery-webinar.webp
-darkthumbnail: ./meshery-webinar.webp
-category: "Meshery"
-tags:
- - Projects
- - Meshery
-published: true
-resource: true
-type: Blog
-product: Meshery
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-
-import MeshManager from "./mesh-manager.webp";
-import MesheryClients from "./meshery-clients.webp";
-import Mesheryfeatures from "./meshery-features.webp";
-import MesheryDeployments from "./meshery-deployment.webp";
-import Nighthawk from "./nighthawk.webp";
-import Patterns from "./patterns.webp";
-import ServiceMeshPatterns from "./service-mesh-patterns.webp";
-import Planes from "./planes.webp";
-import Mesheryoperatoricon from "../../../../assets/images/meshery-operator/meshery-operator.svg";
-import MesheryLogo from "../../../../assets/images/meshery/icon-only/meshery-logo-light.svg";
-import NighthawkIcon from "../../../../assets/images/nighthawk/icon-only/SVG/nighthawk-logo.svg";
-import PatternsLogo from "./patterns-logo.webp";
-import { Link } from "gatsby";
-
-
-
-
-
- Meshery is the open-source, collaborative cloud native manager that can
- configure 230+ Kuberentes infrasturcture operators different service meshes, onboard your applications, manage WebAssembly filters, apply cloud native patterns, validate against best practices, and benchmarks the performance of your cloud native deployments. Let’s learn how to manage cloud native infrastructure with confidence with Meshery.{" "}
-
-
-
-
Network Planes
-
-
- As we unfold what a management plane is, it would serve us well to talk about
- network planes in this regard. Architecturally, a service mesh consists of two
- planes. One of those is the data plane, while the other one is the control
- plane. A service mesh data plane is the collection of intelligent proxies that
- operate in unison under the coordination of the control plane. The control
- plane performs configuration management of these intelligent proxies.
-
-
- A management plane can do many things. Essentially, a management plane helps
- you integrate service meshes into your backend systems. A robust management
- plane allows you to take full advantage of the power of the network while
- integrating your service delivery processes seamlessly. Your management plane
- might federate different types of service meshes, help you instigate chaos
- through controlled experiments, or offer automated traffic splitting in order
- to execute different styles of canarying of your applications. Your management
- plane might offer deep insights into the performance of your applications and
- to the performance of your infrastructure or might deliver a change in
- management framework.
-
-
-
- {" "}
- Meshery
-
-
-
-
- Meshery manages the
- lifecycle of service meshes. Meshery does workload management, helps you
- onboard or offboard your applications onto the mesh. It also lets you do
- performance management.{" "}
- MeshSync,
- a custom controller within{" "}
-
- Meshery operator
-
- , performs discovery of existing service meshes and deep fingerprinting of the
- specific functions that version of your service mesh is capable of performing.
- Through MeshSync, Meshery supports brownfield deployments of your service meshes
- (Meshery discovers your existing service mesh deployment that is already running
- inside your cluster(s) whether those service meshes were deployed by Meshery or
- not){" "}
-
-
- In order to facilitate such a deep level of understanding of each type of
- service mesh, Meshery has
- adapters that are specific to each service mesh (given that each service mesh
- has its own set of features). Consequently, in order to leverage the maximum
- functionality of each service mesh, Meshery has separate, dedicated adapter
- for each of the{" "}
-
- supported service meshes
-
- :{" "}
-
- Meshery also lets you
- integrate your Prometheus and Grafana add-ons so you can import your existing
- Grafana dashboards to Meshery. When you first start Meshery, we also have a
- configuration wizard, which basically walks you through the entire setup to
- get Meshery up and running. By the end of this, it will make sure that you
- have Meshery running on your cluster.
-
-
-
- If you want a more finer configuration, you can configure your environment
- through settings and you can configure service meshes, and you can configure
- the metrics, you can define your performance tests to be reused.
-
-
- For configuration management,{" "}
- Meshery will analyze your
- runtime environment for certain service meshes and tell you if you're doing
- things right or not. What you can do is you can upload your applications
- directly into Meshery, edit them in the Meshery UI itself and actually apply
- these applications or onboard these applications on your service mesh.
-
-
-
- {" "}
- Meshery Operator
-
-
-
-
- Meshery operator
- {" "}
- is a custom controller called MeshSync. MeshSync helps keep Meshery apprised
- of the various changes that are going on to the service meshes and various
- changes that are happening within Kubernetes itself. In this way Meshery
- supports not only greenfield deployments like deploying service meshes itself,
- it also supports connecting to existing service mesh deployments, that is,
- brownfield deployment. So it will discover your existing deployments as well.
-
-
- There's an extensible concept in Meshery called a{" "}
- provider.
- Providers can typically offer a layer of persistence so to the extent that
- users are running performance tests intensely or to the extent that users want
- to have a particular type of directory integrated to bring their own identity
- to Meshery and have a multi-user experience. The other area of extensibility
- is the notion that Meshery has a couple of APIs both – rest API and graphql
- API. It comes with a command-line interface as well as a user interface.{" "}
-
-
-
Layer5 MeshMap
-
- Another capability of Meshery that is going to be released in the upcoming
- version is visually configuring your service mesh using MeshMap. You can add
- filters, applications as well as make other configurations visually here and
- you can export it as patterns to make it reusable quite easily. It
- automatically figures out the sample application we have deployed, then
- generates a visual representation. It provides users the ability to design
- service meshes, service mesh configuration, and the applications that run on
- it.
-
-
-
-
- {" "}
- Patterns
-
-
- {" "}
- A pattern is capable of describing the deployment of any of the meshes that Meshery
- supports as well as the configuration of the mesh. It also notes ongoing behavior
- so if you wanted to run a canary you can describe that in a pattern. So, patterns
- are like a template, they're customizable and ingestible into Meshery itself.
-
-
-
- Meshery will take action based on what you've described in the pattern, things
- like generating or running a performance test, generating load, and then doing
- statistical analysis on that set of results. In the future, if you want to
- deploy a web assembly filter, you can describe that in a pattern as well and
- have Meshery apply it. The patterns are service mesh agnostic, they're
- reusable and the initial set of them is being stored in a public-facing
- repository. There are almost 60 patterns that have been identified.
- Ultimately, it will allow you to ingest these and measure then orchestrate and
- apply them to your infrastructure. You can also use Meshery to visually
- represent them and to visually design.
-
-
-
- {" "}
- Nighthawk
-
-
- There’s a project called Nighthawk that
- helps advance the existing integration of nighthawk and Meshery. Nighthawk is
- a load generator that is an envoy project. It's written in c plus plus and has
- a couple of intriguing capabilities that are the ongoing study within
- Nighthawk. There is an ongoing effort to take advantage of nighthawk’s
- adaptive load controllers, add a couple of those in and expose them through
- Meshery to let people recursively evaluate what is ultimately an optimal
- configuration in your environment and the service mesh.
-
-
-
-
- If you consider that you've got a certain SLO or a certain minimum latency
- requirement that you need to stick to that but you also want to at the same
- time maximize resiliency characteristics of your deployment, that can be a
- difficult thing to figure out particularly if any of your infrastructure
- changes:
-
-
-
if you add another node to your environment, your clusters,
-
if you upgrade your service mesh,
-
if you change the configuration of your service mesh,
-
- if you add another service to your set of workloads that you're running.
-
-
-
- If these factors change, so does the ability to run optimization routines. To
- help you identify the optimal configuration of your mesh but in accordance
- with your own constraints is again the study of{" "}
- Nighthawk.{" "}
-
-
-
- Check out the CNCF On-Demand Webinar:{" "}
- Meshery - The Cloud Native
- Manager to learn more!
-
-
-
-
-
-
+---
+title: "An Introduction to Meshery (Webinar-on-Demand) "
+date: 2021-10-09 10:30:05 -0530
+author: Debopriya Bhattacharjee
+thumbnail: ./meshery-webinar.webp
+darkthumbnail: ./meshery-webinar.webp
+category: "Meshery"
+tags:
+ - Projects
+ - Meshery
+published: true
+resource: true
+type: Blog
+product: Meshery
+---
+
+
+
+
+import MeshManager from "./mesh-manager.webp";
+import MesheryClients from "./meshery-clients.webp";
+import Mesheryfeatures from "./meshery-features.webp";
+import MesheryDeployments from "./meshery-deployment.webp";
+import Nighthawk from "./nighthawk.webp";
+import Patterns from "./patterns.webp";
+import ServiceMeshPatterns from "./service-mesh-patterns.webp";
+import Planes from "./planes.webp";
+import Mesheryoperatoricon from "../../../../assets/images/meshery-operator/meshery-operator.svg";
+import MesheryLogo from "../../../../assets/images/meshery/icon-only/meshery-logo-light.svg";
+import NighthawkIcon from "../../../../assets/images/nighthawk/icon-only/SVG/nighthawk-logo.svg";
+import PatternsLogo from "./patterns-logo.webp";
+
+
+
+
+
+
+ Meshery is the open-source, collaborative cloud native manager that can
+ configure 230+ Kuberentes infrasturcture operators different service meshes, onboard your applications, manage WebAssembly filters, apply cloud native patterns, validate against best practices, and benchmarks the performance of your cloud native deployments. Let’s learn how to manage cloud native infrastructure with confidence with Meshery.{" "}
+
+
+
+
Network Planes
+
+
+ As we unfold what a management plane is, it would serve us well to talk about
+ network planes in this regard. Architecturally, a service mesh consists of two
+ planes. One of those is the data plane, while the other one is the control
+ plane. A service mesh data plane is the collection of intelligent proxies that
+ operate in unison under the coordination of the control plane. The control
+ plane performs configuration management of these intelligent proxies.
+
+
+ A management plane can do many things. Essentially, a management plane helps
+ you integrate service meshes into your backend systems. A robust management
+ plane allows you to take full advantage of the power of the network while
+ integrating your service delivery processes seamlessly. Your management plane
+ might federate different types of service meshes, help you instigate chaos
+ through controlled experiments, or offer automated traffic splitting in order
+ to execute different styles of canarying of your applications. Your management
+ plane might offer deep insights into the performance of your applications and
+ to the performance of your infrastructure or might deliver a change in
+ management framework.
+
+
+
+ {" "}
+ Meshery
+
+
+
+
+ Meshery manages the
+ lifecycle of service meshes. Meshery does workload management, helps you
+ onboard or offboard your applications onto the mesh. It also lets you do
+ performance management.{" "}
+ MeshSync,
+ a custom controller within{" "}
+
+ Meshery operator
+
+ , performs discovery of existing service meshes and deep fingerprinting of the
+ specific functions that version of your service mesh is capable of performing.
+ Through MeshSync, Meshery supports brownfield deployments of your service meshes
+ (Meshery discovers your existing service mesh deployment that is already running
+ inside your cluster(s) whether those service meshes were deployed by Meshery or
+ not){" "}
+
+
+ In order to facilitate such a deep level of understanding of each type of
+ service mesh, Meshery has
+ adapters that are specific to each service mesh (given that each service mesh
+ has its own set of features). Consequently, in order to leverage the maximum
+ functionality of each service mesh, Meshery has separate, dedicated adapter
+ for each of the{" "}
+
+ supported service meshes
+
+ :{" "}
+
+ Meshery also lets you
+ integrate your Prometheus and Grafana add-ons so you can import your existing
+ Grafana dashboards to Meshery. When you first start Meshery, we also have a
+ configuration wizard, which basically walks you through the entire setup to
+ get Meshery up and running. By the end of this, it will make sure that you
+ have Meshery running on your cluster.
+
+
+
+ If you want a more finer configuration, you can configure your environment
+ through settings and you can configure service meshes, and you can configure
+ the metrics, you can define your performance tests to be reused.
+
+
+ For configuration management,{" "}
+ Meshery will analyze your
+ runtime environment for certain service meshes and tell you if you're doing
+ things right or not. What you can do is you can upload your applications
+ directly into Meshery, edit them in the Meshery UI itself and actually apply
+ these applications or onboard these applications on your service mesh.
+
+
+
+ {" "}
+ Meshery Operator
+
+
+
+
+ Meshery operator
+
+ {" "}
+ is a custom controller called MeshSync. MeshSync helps keep Meshery apprised
+ of the various changes that are going on to the service meshes and various
+ changes that are happening within Kubernetes itself. In this way Meshery
+ supports not only greenfield deployments like deploying service meshes itself,
+ it also supports connecting to existing service mesh deployments, that is,
+ brownfield deployment. So it will discover your existing deployments as well.
+
+
+ There's an extensible concept in Meshery called a{" "}
+ provider.
+ Providers can typically offer a layer of persistence so to the extent that
+ users are running performance tests intensely or to the extent that users want
+ to have a particular type of directory integrated to bring their own identity
+ to Meshery and have a multi-user experience. The other area of extensibility
+ is the notion that Meshery has a couple of APIs both – rest API and graphql
+ API. It comes with a command-line interface as well as a user interface.{" "}
+
+
+
Layer5 MeshMap
+
+ Another capability of Meshery that is going to be released in the upcoming
+ version is visually configuring your service mesh using MeshMap. You can add
+ filters, applications as well as make other configurations visually here and
+ you can export it as patterns to make it reusable quite easily. It
+ automatically figures out the sample application we have deployed, then
+ generates a visual representation. It provides users the ability to design
+ service meshes, service mesh configuration, and the applications that run on
+ it.
+
+
+
+
+ {" "}
+ Patterns
+
+
+ {" "}
+ A pattern is capable of describing the deployment of any of the meshes that Meshery
+ supports as well as the configuration of the mesh. It also notes ongoing behavior
+ so if you wanted to run a canary you can describe that in a pattern. So, patterns
+ are like a template, they're customizable and ingestible into Meshery itself.
+
+
+
+ Meshery will take action based on what you've described in the pattern, things
+ like generating or running a performance test, generating load, and then doing
+ statistical analysis on that set of results. In the future, if you want to
+ deploy a web assembly filter, you can describe that in a pattern as well and
+ have Meshery apply it. The patterns are service mesh agnostic, they're
+ reusable and the initial set of them is being stored in a public-facing
+ repository. There are almost 60 patterns that have been identified.
+ Ultimately, it will allow you to ingest these and measure then orchestrate and
+ apply them to your infrastructure. You can also use Meshery to visually
+ represent them and to visually design.
+
+
+
+ {" "}
+ Nighthawk
+
+
+ There’s a project called Nighthawk that
+ helps advance the existing integration of nighthawk and Meshery. Nighthawk is
+ a load generator that is an envoy project. It's written in c plus plus and has
+ a couple of intriguing capabilities that are the ongoing study within
+ Nighthawk. There is an ongoing effort to take advantage of nighthawk’s
+ adaptive load controllers, add a couple of those in and expose them through
+ Meshery to let people recursively evaluate what is ultimately an optimal
+ configuration in your environment and the service mesh.
+
+
+
+
+ If you consider that you've got a certain SLO or a certain minimum latency
+ requirement that you need to stick to that but you also want to at the same
+ time maximize resiliency characteristics of your deployment, that can be a
+ difficult thing to figure out particularly if any of your infrastructure
+ changes:
+
+
+
if you add another node to your environment, your clusters,
+
if you upgrade your service mesh,
+
if you change the configuration of your service mesh,
+
+ if you add another service to your set of workloads that you're running.
+
+
+
+ If these factors change, so does the ability to run optimization routines. To
+ help you identify the optimal configuration of your mesh but in accordance
+ with your own constraints is again the study of{" "}
+ Nighthawk.{" "}
+
+
+
+ Check out the CNCF On-Demand Webinar:{" "}
+ Meshery - The Cloud Native
+ Manager to learn more!
+
+
+
+
+
+
diff --git a/src/collections/blog/2022/2022-01-05-how-to-write-unit-and-integeration-tests-for-mesheryctl/index.mdx b/src/collections/blog/2022/2022-01-05-how-to-write-unit-and-integeration-tests-for-mesheryctl/index.mdx
index 8ca4ea7b4d43..bc4502475cdc 100644
--- a/src/collections/blog/2022/2022-01-05-how-to-write-unit-and-integeration-tests-for-mesheryctl/index.mdx
+++ b/src/collections/blog/2022/2022-01-05-how-to-write-unit-and-integeration-tests-for-mesheryctl/index.mdx
@@ -1,110 +1,109 @@
----
-title: "How to write unit and integration tests for mesheryctl"
-date: 2022-01-05 19:32:05 -0530
-author: Piyush Singariya
-description: Unit and integration tests bolster and roll up into broader end-to-end, functional testing performed across Meshery and the rest of its components.
-thumbnail: ./integration-test.webp
-darkthumbnail: ./integration-test.webp
-category: "Meshery"
-tags:
- - Projects
- - Meshery
- - mesheryctl
-published: true
-resource: true
-type: Blog
-product: Meshery
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-
-import UnitTest from "./unit-test.webp";
-import IntegrationTest from "./integration-test.webp";
-import TreeGraph from "./tree-graph.webp";
-
-
-
-
-
Delivering a high quality user experience is our pinnacle goal in the design of Meshery's CLI: mesheryctl. Delivering a high quality user experience means testing both qualitatively and quantatively. As a concept, quality - whether you're talking about software or anything else - can be directly measured by consistency. A quality user experience is consistent and consistency of mesheryctl is reinforced by its many unit tests.
-
-
-
mesheryctl is written in Golang. In the Meshery project, we use CodeCov to calculate the code coverage across mesheryctl's line of code. And there are plenty of lines of code. Achieving high percentages of code coverage in Meshery's CLI with grows in criticality as we bring more features into mesheryctl as a robust and sophisticated command line client of Meshery. Unit and integration tests bolster and roll up into broader end-to-end, functional testing performed across Meshery and the rest of its components.
-
-
High levels of code coverage makes it easier for each project contributor to be confident that their code changes aren’t breaking any preexisting mesheryctl commands, side-swiping their functionality unknowingly, and consequently, unwittingly lowering the quality of Meshery's overall user experience.
-
Store standard/verified mesheryctl output in a golden file(a text file)
-
Match the stored/expected output with what we grab from the console
-
Cover as many scenarios as possible, test the situations where errors must be thrown
-
This is a standard format, changes can be made accordingly
-
-
-
- Test mesheryctl functions
-
-
This is the standard testing you may have come across in every project
-
You write one test dedicated to one function covering all possible test-cases, matching expected outputs
-
-
-
-
-
Example tree graph
-
This example of a tree graph (from meshery/meshery/pull/4823) shows the impact given changes make on the level of code coverage.
-
-
-
-
Integration Tests
-
-
Integrations tests come into view when you cannot mock something easily and when a given behavior is cross-functional / cross-component. Integration tests put more, but not all of the focus validating system behavior and that the system completes all the necessary actions. Take mesheryctl system start for example. This command deploys Meshery, its adapters, and Kubernetes Operator; it starts Meshery. So, you run the command to start Meshery in a GitHub workflow and after running the mesheryctl subcommand through the tests and make sure that Meshery actually started. And if the workflow successfully runs the test, then boom!, you aced your integration writing test... errr... test writing.
-
-
The integration test writing exam can initially be challenging, but... that’s the fun in it. :) Running tests and making sure a command that is otherwise hard to verify, hard to test, and making it automatic through GH workflows.
-
-
How you can make an impact
-
-
Writing tests and making them work is in itself a tough task to do, so writing one test for a single function counts and makes a big difference over the long term. Don't hesitate. Start writing tests now. A single, new test is worthy of raising a pull request and will get you well on your way to learning much more about Golang, Docker, Kubernetes, and service meshes.
-
-
-
Codecov is used to check code coverage in mesheryctl (login with GitHub to get an in-depth idea of lines-of-code being covered in code coverage).
-
You can check the files on CodeCov’s website to figure out which mesheryctl commands haven’t been covered by existing tests.
-
Guide: Writing tests for mesheryctl. This guide will briefly introduce how tests are supposed to be written for mesheryctl.
-
Contributing to Tests doesn’t always mean writing new tests, It also means improving the effectiveness of already written-ones.
-
Search for Issues marked with area/tests in GitHub - meshery/meshery: Meshery, the cloud native management plane.
-
-
-
The impact that you make with by writing even a single test is quite high. Your tests will be executed and used time-and-time again. I can’t explain in words (I don’t have that good of a vocabulary). Your Tests are going to run in each pull request raised against the Meshery project, in each commit someone pushes to a pull request, in every nightly regression test suite, in every release. Just think: if another contributor incidently introduces a defect or doesn't consider for an edge case, and fails to uphold the intended behavior of the code, your tests are going to catch them redhanded. How cool is that?
-
-
So, what are you waiting for? Jump in and write a few tests today! When you raise your pull request, label it with area/tests and component/mesheryctl and I'll be there to review! Let’s get mesheryctl 100% code coverage badge.
-
+---
+title: "How to write unit and integration tests for mesheryctl"
+date: 2022-01-05 19:32:05 -0530
+author: Piyush Singariya
+description: Unit and integration tests bolster and roll up into broader end-to-end, functional testing performed across Meshery and the rest of its components.
+thumbnail: ./integration-test.webp
+darkthumbnail: ./integration-test.webp
+category: "Meshery"
+tags:
+ - Projects
+ - Meshery
+ - mesheryctl
+published: true
+resource: true
+type: Blog
+product: Meshery
+---
+
+
+
+
+import UnitTest from "./unit-test.webp";
+import IntegrationTest from "./integration-test.webp";
+import TreeGraph from "./tree-graph.webp";
+
+
+
+
+
Delivering a high quality user experience is our pinnacle goal in the design of Meshery's CLI: mesheryctl. Delivering a high quality user experience means testing both qualitatively and quantatively. As a concept, quality - whether you're talking about software or anything else - can be directly measured by consistency. A quality user experience is consistent and consistency of mesheryctl is reinforced by its many unit tests.
+
+
+
mesheryctl is written in Golang. In the Meshery project, we use CodeCov to calculate the code coverage across mesheryctl's line of code. And there are plenty of lines of code. Achieving high percentages of code coverage in Meshery's CLI with grows in criticality as we bring more features into mesheryctl as a robust and sophisticated command line client of Meshery. Unit and integration tests bolster and roll up into broader end-to-end, functional testing performed across Meshery and the rest of its components.
+
+
High levels of code coverage makes it easier for each project contributor to be confident that their code changes aren’t breaking any preexisting mesheryctl commands, side-swiping their functionality unknowingly, and consequently, unwittingly lowering the quality of Meshery's overall user experience.
Store standard/verified mesheryctl output in a golden file(a text file)
+
Match the stored/expected output with what we grab from the console
+
Cover as many scenarios as possible, test the situations where errors must be thrown
+
This is a standard format, changes can be made accordingly
+
+
+
+ Test mesheryctl functions
+
+
This is the standard testing you may have come across in every project
+
You write one test dedicated to one function covering all possible test-cases, matching expected outputs
+
+
+
+
+
Example tree graph
+
This example of a tree graph (from meshery/meshery/pull/4823) shows the impact given changes make on the level of code coverage.
+
+
+
+
Integration Tests
+
+
Integrations tests come into view when you cannot mock something easily and when a given behavior is cross-functional / cross-component. Integration tests put more, but not all of the focus validating system behavior and that the system completes all the necessary actions. Take mesheryctl system start for example. This command deploys Meshery, its adapters, and Kubernetes Operator; it starts Meshery. So, you run the command to start Meshery in a GitHub workflow and after running the mesheryctl subcommand through the tests and make sure that Meshery actually started. And if the workflow successfully runs the test, then boom!, you aced your integration writing test... errr... test writing.
+
+
The integration test writing exam can initially be challenging, but... that’s the fun in it. :) Running tests and making sure a command that is otherwise hard to verify, hard to test, and making it automatic through GH workflows.
+
+
How you can make an impact
+
+
Writing tests and making them work is in itself a tough task to do, so writing one test for a single function counts and makes a big difference over the long term. Don't hesitate. Start writing tests now. A single, new test is worthy of raising a pull request and will get you well on your way to learning much more about Golang, Docker, Kubernetes, and service meshes.
+
+
+
Codecov is used to check code coverage in mesheryctl (login with GitHub to get an in-depth idea of lines-of-code being covered in code coverage).
+
You can check the files on CodeCov’s website to figure out which mesheryctl commands haven’t been covered by existing tests.
+
Guide: Writing tests for mesheryctl. This guide will briefly introduce how tests are supposed to be written for mesheryctl.
+
Contributing to Tests doesn’t always mean writing new tests, It also means improving the effectiveness of already written-ones.
+
Search for Issues marked with area/tests in GitHub - meshery/meshery: Meshery, the cloud native management plane.
+
+
+
The impact that you make with by writing even a single test is quite high. Your tests will be executed and used time-and-time again. I can’t explain in words (I don’t have that good of a vocabulary). Your Tests are going to run in each pull request raised against the Meshery project, in each commit someone pushes to a pull request, in every nightly regression test suite, in every release. Just think: if another contributor incidently introduces a defect or doesn't consider for an edge case, and fails to uphold the intended behavior of the code, your tests are going to catch them redhanded. How cool is that?
+
+
So, what are you waiting for? Jump in and write a few tests today! When you raise your pull request, label it with area/tests and component/mesheryctl and I'll be there to review! Let’s get mesheryctl 100% code coverage badge.
+
\ No newline at end of file
diff --git a/src/collections/blog/2022/2022-01-07-Recap-KubeCon-China-TAG-Network-talk/index.mdx b/src/collections/blog/2022/2022-01-07-Recap-KubeCon-China-TAG-Network-talk/index.mdx
index 968fdfe1541c..322ca50535c1 100644
--- a/src/collections/blog/2022/2022-01-07-Recap-KubeCon-China-TAG-Network-talk/index.mdx
+++ b/src/collections/blog/2022/2022-01-07-Recap-KubeCon-China-TAG-Network-talk/index.mdx
@@ -28,7 +28,7 @@ import { Link } from "gatsby";
-
+
The CNCF Technical Advisory Group for Network Co-Chairs Lee Calcote and Ken Owens gave a presentation entitled Intro and Deep Dive into CNCF TAG Network and CNCF Service Mesh Working Group at KubeCon China 2021.
@@ -91,14 +91,14 @@ The majority of the more detailed activities occur in the CNCF Service Mesh Work
Service Mesh Performance (SMP): SMP tries to make it uniform and succinct the way you characterize the performance of cloud native infrastructure with a focus on service meshes.
-
-
+
+
Owens and Calcote also discuss Service Mesh Patterns and Service Mesh Catalog. These patterns promote the reuse of best practices, are service mesh agnostic, and also help in behavior analysis. A circuit breaker test is a good example. If something goes wrong in your network be it a node failure, router failure, etc., then it helps you identify the point of failure as well as gets your network running quickly.
-
+
@@ -112,12 +112,15 @@ The majority of the more detailed activities occur in the CNCF Service Mesh Work
This brings us to Nighthawk and Meshery. Together they help produce robust, distributed and scalable services. Distributed load testing offers insight into system behaviors that accurately represent real world behaviors of services under load as that load comes from any number of sources.
-
+
-
Calcote and Owens packed a great deal of information in this talk. If you are passionate about Cloud Native Networking and Service Meshes, then this talk is definitely worth your time. Find the recording below. The presentation slides are available here.
+
+
+ Calcote and Owens packed a great deal of information in this talk. If you are passionate about Cloud Native Networking and Service Meshes, then this talk is definitely worth your time. Find the recording below. The presentation slides are available here.
+
-
-
+
+
diff --git a/src/collections/blog/2022/2022-01-14-open-source-journey-gaurav-chadha/index.mdx b/src/collections/blog/2022/2022-01-14-open-source-journey-gaurav-chadha/index.mdx
index 93f7bb14ab52..5c4a9ddb76e1 100644
--- a/src/collections/blog/2022/2022-01-14-open-source-journey-gaurav-chadha/index.mdx
+++ b/src/collections/blog/2022/2022-01-14-open-source-journey-gaurav-chadha/index.mdx
@@ -1,81 +1,81 @@
----
-title: My Open Source Journey @Layer5
-subtitle: From Contributor to SWE Intern
-date: 2022-01-14 10:30:05 -0530
-author: Gaurav Chadha
-thumbnail: ./Gaurav Chadha - Layer5 Intern.webp
-darkthumbnail: ./Gaurav Chadha - Layer5 Intern.webp
-description: "My journey as an Open Source contributor at Layer5. How I started from scratch, got involved in this community
-and gained many new experiences."
-type: Blog
-category: Community
-tags:
- - Open Source
- - Internship
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Profile from "./Intern-profile.webp";
-
-
-
- Hey👋, I am Gaurav Chadha, a student from New Delhi, India with lots of dreams, ambitions, and zeal to learn and grow more each and every day.
-
-
How did it all begin?
-
-My journey in open source started with late-night surfing on LinkedIn.
-I saw a post about the Layer5 organization and open source which drove me to their website and{" "}Slack workspace. And then, 💥 a single-click was all it took to kickstart my journey in Open Source and set in-motion a new chapter in my career development and relationships with new colleagues.
-I would say this was my best ever decision in life till now.
-
-
Getting started in the community
-
-Despite the warm welcome that I receive upon joining Layer5's Slack workspace, I was a bit shy to introduce myself in the{" "}#newcomers channel, but then I saw so many other folks introducing themselves. My inner voice asked, "If they can do it, why can't I?", so I went ahead and introduced myself to the community.
-The best part for newcomers in Layer5 is that not only is each individual warmly welcomed, but that
-Layer5 {" "} MeshMates and Community Managers host a weekly meeting (see the{" "}community calendar) dedicated to the success of newcomers, helping each person find a foothold in the community. The overview provided in each weekly Newcomers meeting gives you the leg up that you need to get started with any of{" "} Layer5's projects and orients you to the how the community works (the{" "} community handbook is an excellent resource in this regard) and who to contact in your areas of interest.
-
-
- I highly recommend all newcomers to engage as much as possible in the community. You will gradually start seeing a change in yourself.
-
-
-
Way to my First Pull Request 🏁
-
-I still remember at that time I was just a beginner with Git, HTML, CSS, and JavaScript and most of the issues on the repository were going over my head.
-So I started with a very beginner-friendly issue about changing a background of a component and who would have thought this changing background issue will eventually change my life in open source.
-Then I made my first ever pull request in Layer5 and that got merged!
-
-
-Try out some good first issues here{""} Layer5 {""} ,Meshery💻
-
-
From 1 Pull Request to 90+ Pull Requests Merged 🚀
-
- After my first pull request got merged I really got pumped up with joy and told myself that I can do more. This journey of learning and pull requests was not at all easy for me, it took almost 9 months of continuous dedication and effort. There are many great folks I met here in the community, who helped me and taught me new interesting concepts.
- A big thanks to all of them, this was not possible without their guidance and support.
-
-
Things I learned at Layer5
-
- There are a variety of things I learned at Layer5 and a lot I'm learning currently. I gained much technical knowledge as well as soft skills in these 9 months. I spend most of my time working on the UI of Meshery and its various projects.
- In terms of technical items I learned React, Docker, Kubernetes, new JavaScript concepts, etc.
-
-
- I would say Layer5 is the best in terms of work ethics, community management, a healthy work environment, and a lot more.
- You can gain real-life working experience on such big projects and guidance related to your career.
-
-
How I landed an internship at Layer5?
-
- I gradually started learning about the project and made myself choose one area to start with and continued to explore further. I kept pushing myself with patience until I feel strong and capable enough to
- take responsibilities and give my best to the community, Then I asked and applied for an internship and eventually, I got selected.
-
-
Now I can make more impact and grow more under the right guidance.😃
-
Apart from coding
-
- Besides coding at Layer5, I made many new friends, great experiences, and memories.
-
-
- At last, I would say, join this amazing community and experience the change in yourself. This will open the doors for opportunities for you. Just be tenacious and push yourself, that's all that I did.
-
-
- Thank you
-
-
-
+---
+title: My Open Source Journey @Layer5
+subtitle: From Contributor to SWE Intern
+date: 2022-01-14 10:30:05 -0530
+author: Gaurav Chadha
+thumbnail: ./Gaurav Chadha - Layer5 Intern.webp
+darkthumbnail: ./Gaurav Chadha - Layer5 Intern.webp
+description: "My journey as an Open Source contributor at Layer5. How I started from scratch, got involved in this community
+and gained many new experiences."
+type: Blog
+category: Community
+tags:
+ - Open Source
+ - Internship
+published: true
+---
+
+
+import Profile from "./Intern-profile.webp";
+
+
+
+ Hey👋, I am Gaurav Chadha, a student from New Delhi, India with lots of dreams, ambitions, and zeal to learn and grow more each and every day.
+
+
How did it all begin?
+
+My journey in open source started with late-night surfing on LinkedIn.
+I saw a post about the Layer5 organization and open source which drove me to their website and{" "}Slack workspace. And then, 💥 a single-click was all it took to kickstart my journey in Open Source and set in-motion a new chapter in my career development and relationships with new colleagues.
+I would say this was my best ever decision in life till now.
+
+
Getting started in the community
+
+Despite the warm welcome that I receive upon joining Layer5's Slack workspace, I was a bit shy to introduce myself in the{" "}#newcomers channel, but then I saw so many other folks introducing themselves. My inner voice asked, "If they can do it, why can't I?", so I went ahead and introduced myself to the community.
+The best part for newcomers in Layer5 is that not only is each individual warmly welcomed, but that
+Layer5 {" "} MeshMates and Community Managers host a weekly meeting (see the{" "}community calendar) dedicated to the success of newcomers, helping each person find a foothold in the community. The overview provided in each weekly Newcomers meeting gives you the leg up that you need to get started with any of{" "} Layer5's projects and orients you to the how the community works (the{" "} community handbook is an excellent resource in this regard) and who to contact in your areas of interest.
+
+
+ I highly recommend all newcomers to engage as much as possible in the community. You will gradually start seeing a change in yourself.
+
+
+
Way to my First Pull Request 🏁
+
+I still remember at that time I was just a beginner with Git, HTML, CSS, and JavaScript and most of the issues on the repository were going over my head.
+So I started with a very beginner-friendly issue about changing a background of a component and who would have thought this changing background issue will eventually change my life in open source.
+Then I made my first ever pull request in Layer5 and that got merged!
+
+
+Try out some good first issues here{""} Layer5 {""} ,Meshery💻
+
+
From 1 Pull Request to 90+ Pull Requests Merged 🚀
+
+ After my first pull request got merged I really got pumped up with joy and told myself that I can do more. This journey of learning and pull requests was not at all easy for me, it took almost 9 months of continuous dedication and effort. There are many great folks I met here in the community, who helped me and taught me new interesting concepts.
+ A big thanks to all of them, this was not possible without their guidance and support.
+
+
Things I learned at Layer5
+
+ There are a variety of things I learned at Layer5 and a lot I'm learning currently. I gained much technical knowledge as well as soft skills in these 9 months. I spend most of my time working on the UI of Meshery and its various projects.
+ In terms of technical items I learned React, Docker, Kubernetes, new JavaScript concepts, etc.
+
+
+ I would say Layer5 is the best in terms of work ethics, community management, a healthy work environment, and a lot more.
+ You can gain real-life working experience on such big projects and guidance related to your career.
+
+
How I landed an internship at Layer5?
+
+ I gradually started learning about the project and made myself choose one area to start with and continued to explore further. I kept pushing myself with patience until I feel strong and capable enough to
+ take responsibilities and give my best to the community, Then I asked and applied for an internship and eventually, I got selected.
+
+
Now I can make more impact and grow more under the right guidance.😃
+
Apart from coding
+
+ Besides coding at Layer5, I made many new friends, great experiences, and memories.
+
+
+ At last, I would say, join this amazing community and experience the change in yourself. This will open the doors for opportunities for you. Just be tenacious and push yourself, that's all that I did.
+
+
+ Thank you
+
+
+
diff --git a/src/collections/blog/2022/2022-01-22-the-story-of-meshery-1000-stars/index.mdx b/src/collections/blog/2022/2022-01-22-the-story-of-meshery-1000-stars/index.mdx
index e7e5391866a7..807c3835ed65 100644
--- a/src/collections/blog/2022/2022-01-22-the-story-of-meshery-1000-stars/index.mdx
+++ b/src/collections/blog/2022/2022-01-22-the-story-of-meshery-1000-stars/index.mdx
@@ -1,159 +1,160 @@
----
-title: "The Story of Meshery's 1,000 Stars"
-subtitle: "A story about growing together as a community and building a project that matters"
-date: 2022-01-26 10:30:05 -0530
-author: Debopriya Bhattacharjee
-thumbnail: ./Meshery-Stars-cover.webp
-darkthumbnail: ./Meshery-Stars-cover.webp
-category: "Announcements"
-description: "Meshery has achieved yet another milestone! Our GitHub repository has surpassed a 1,000 stars."
-tags:
- - Meshery
-type: Blog
-published: true
-featured: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-import BlockquoteAlt from "../../../../reusecore/Blockquote/Blockquote-alt-style";
-import { Link } from "gatsby";
-import Stars from "./stars-forks.webp";
-import Slack from "./meshery-star-notifications.webp";
-
-
-
- Meshery took its first steps into the cloud native world in July of 2019 with the goal to ease the adoption and operation of cloud native infrastructure with a focus on service meshes as ubiquitous a layer within and outside of Kubernetes deployments. Since then, Meshery as a project and Layer5 as an open source community have grown by leaps and bounds. Now, we are bursting with pride in announcing that Meshery has reached yet another milestone: 1,000 stars on the Meshery repository on GitHub.
-
-
-
- As a project, Meshery is comprised of about 30 repositories, and so, in total,
- the project has many more than a thousand stars. The rate by which Meshery is
- accumulating stars only continues to accelerate and is a small moment of pride
- recognized in the community Slack each time a star is added. As we hit the
- 1,000+ stars milestone, let's pause to reflect on the project's incredible
- journey since its inception.
-
-
-
Why was Meshery created?
-
-
- Meshery is an open source, vendor-neutral, extensible management plane that
- enables service mesh users to overcome the challenges of complex virtual
- networking,{" "}
-
{" "}
- empowers them to design and apply patterns containing tried and true best
- practices, and enables developers, operators, and product managers to
- understand and manage their cloud native services with confidence. Meshery is
- the only openly-governed service mesh manager. Given its ability to deeply
- manage Kubernetes, its workloads, and any service mesh, and the highly
- configurable way in which users can load a variety of plugins, the project has
- certainly earned its title as the extensible service mesh manager.
-
-
-
-
- Within just a year of its creation,{" "}
-
- Meshery lands in the CNCF Landscape
-
- .
-
-
-
-
- Not long after, Meshery was{" "}
-
- adopted by the CNCF
- {" "}
- in October 2021. With its natural step into the Cloud Native Computing
- Foundation, the contributor community and Meshery's functionality maintains
- steadfast in their rate of growth and use. With continuous improvements in the
- architecture, user experience and in other features regulated by inclusive
- monitoring, the project is gaining traction very quickly.
-
-
-
Engagement in the community is on the rise!
-
- It isn't just the number of stars that has grown. We've seen a surge of new
- contributors, maintainers, new features, commits, PRs, releases, and so much
- more! How do we assess the impact of Meshery? Here are some statistics on how
- we track our engagement:
-
-
-
-
- Stargazers: 105.4795% annual growth from 584 to 1200
-
-
- Forks: 103.2491% annual growth from 277 to 563
-
-
- Code Commits: 250% annual growth from 3.25k to 11.375k
-
-
In the last 12 months, we had 341 contributors with 291 new.
-
- Number of PR's merged in the last 12 months is 2108. Our count of PR’s
- merged is more than that of 106 CNCF hosted projects.
-
-
-
-
-
- Note: These metrics and reports were obtained from DevStats, a CNCF-created
- tool for analyzing and graphing developer contributions.
-
-
-
-
-
Latest Meshery Features
-
- Meshery v0.6.0 will release soon, jam-packed full of major new features. Final
- release candidate, Meshery v0.6.0-rc-4, available today, so you can take
- advantage of Meshery's new functionality now:
-
-
-
-
Manage Kubernetes Workloads (Applications)
-
Manage WASM filters
-
- Manage{" "}
-
- Service Mesh Patterns
-
-
-
- MeshMap: Visualize
- service mesh deployments
-
-
- Enhanced service mesh discovery in{" "}
-
- Meshery Operator and Meshsync
-
-
-
-
-
- Last, but not least is the announcement of MeshMap's beta release! The waiting
- list is filling up fast, so I recommend{" "}
- signing up for access now!
-
-
-
+---
+title: "The Story of Meshery's 1,000 Stars"
+subtitle: "A story about growing together as a community and building a project that matters"
+date: 2022-01-26 10:30:05 -0530
+author: Debopriya Bhattacharjee
+thumbnail: ./Meshery-Stars-cover.webp
+darkthumbnail: ./Meshery-Stars-cover.webp
+category: "Announcements"
+description: "Meshery has achieved yet another milestone! Our GitHub repository has surpassed a 1,000 stars."
+tags:
+ - Meshery
+type: Blog
+published: true
+featured: true
+---
+
+
+
+
+
+import Stars from "./stars-forks.webp";
+import Slack from "./meshery-star-notifications.webp";
+
+
+
+ Meshery took its first steps into the cloud native world in July of 2019 with the goal to ease the adoption and operation of cloud native infrastructure with a focus on service meshes as ubiquitous a layer within and outside of Kubernetes deployments. Since then, Meshery as a project and Layer5 as an open source community have grown by leaps and bounds. Now, we are bursting with pride in announcing that Meshery has reached yet another milestone: 1,000 stars on the Meshery repository on GitHub.
+
+
+
+ As a project, Meshery is comprised of about 30 repositories, and so, in total,
+ the project has many more than a thousand stars. The rate by which Meshery is
+ accumulating stars only continues to accelerate and is a small moment of pride
+ recognized in the community Slack each time a star is added. As we hit the
+ 1,000+ stars milestone, let's pause to reflect on the project's incredible
+ journey since its inception.
+
+
+
Why was Meshery created?
+
+
+ Meshery is an open source, vendor-neutral, extensible management plane that
+ enables service mesh users to overcome the challenges of complex virtual
+ networking,{" "}
+
{" "}
+ empowers them to design and apply patterns containing tried and true best
+ practices, and enables developers, operators, and product managers to
+ understand and manage their cloud native services with confidence. Meshery is
+ the only openly-governed service mesh manager. Given its ability to deeply
+ manage Kubernetes, its workloads, and any service mesh, and the highly
+ configurable way in which users can load a variety of plugins, the project has
+ certainly earned its title as the extensible service mesh manager.
+
+
+
+
+ Within just a year of its creation,{" "}
+
+ Meshery lands in the CNCF Landscape
+
+ .
+
+
+
+
+ Not long after, Meshery was{" "}
+
+ adopted by the CNCF
+
+ {" "}
+ in October 2021. With its natural step into the Cloud Native Computing
+ Foundation, the contributor community and Meshery's functionality maintains
+ steadfast in their rate of growth and use. With continuous improvements in the
+ architecture, user experience and in other features regulated by inclusive
+ monitoring, the project is gaining traction very quickly.
+
+
+
Engagement in the community is on the rise!
+
+ It isn't just the number of stars that has grown. We've seen a surge of new
+ contributors, maintainers, new features, commits, PRs, releases, and so much
+ more! How do we assess the impact of Meshery? Here are some statistics on how
+ we track our engagement:
+
+
+
+
+ Stargazers: 105.4795% annual growth from 584 to 1200
+
+
+ Forks: 103.2491% annual growth from 277 to 563
+
+
+ Code Commits: 250% annual growth from 3.25k to 11.375k
+
+
In the last 12 months, we had 341 contributors with 291 new.
+
+ Number of PR's merged in the last 12 months is 2108. Our count of PR’s
+ merged is more than that of 106 CNCF hosted projects.
+
+
+
+
+
+ Note: These metrics and reports were obtained from DevStats, a CNCF-created
+ tool for analyzing and graphing developer contributions.
+
+
+
+
+
Latest Meshery Features
+
+ Meshery v0.6.0 will release soon, jam-packed full of major new features. Final
+ release candidate, Meshery v0.6.0-rc-4, available today, so you can take
+ advantage of Meshery's new functionality now:
+
+
+
+
Manage Kubernetes Workloads (Applications)
+
Manage WASM filters
+
+ Manage{" "}
+
+ Service Mesh Patterns
+
+
+
+ MeshMap: Visualize
+ service mesh deployments
+
+
+ Enhanced service mesh discovery in{" "}
+
+ Meshery Operator and Meshsync
+
+
+
+
+
+ Last, but not least is the announcement of MeshMap's beta release! The waiting
+ list is filling up fast, so I recommend{" "}
+ signing up for access now!
+
-Great News!🎉🎉
-OpenForce2022 by CodeFlow is here! And Layer5 is joining forces with other open source organizations to make it an unforgettable experience.
-OpenForce 2022 is a place where contributors can meet mentors from open source organizations and contribute to projects under guidance, network with project maintainers, and “bring the open source culture” with great enthusiasm.
-
-
What Layer5 will do?
-
-During the program, Layer5 as an open source organization will provide OpenForce specific issues which participants can resolve during the contribution period. In addition, there will be a panel of mentors assigned to assist contributors to overcome any challenges they might face.
-Beyond the direct support offered by Layer5 mentors, program participants will have an amazing networking opportunity to connect with the broader set of community members at Layer5. This event will kick-off virtually from March 3rd to March 28th, 2022.
-
-
CodeFlow
-
-The program is organized by CodeFlow, an organization whose main motive is to empower the student community by organizing webinars, hackathons, and open source events, providing them with the best learning environment and helping them gain the principal knowledge about the fast-paced, open source ecosystem. What a great learning opportunity this would prove to be as ‘open source meets its contributor force’ at OpenForce 2022! Come be a part of this amazing initiative.
-
+Great News!🎉🎉
+OpenForce2022 by CodeFlow is here! And Layer5 is joining forces with other open source organizations to make it an unforgettable experience.
+OpenForce 2022 is a place where contributors can meet mentors from open source organizations and contribute to projects under guidance, network with project maintainers, and “bring the open source culture” with great enthusiasm.
+
+
What Layer5 will do?
+
+During the program, Layer5 as an open source organization will provide OpenForce specific issues which participants can resolve during the contribution period. In addition, there will be a panel of mentors assigned to assist contributors to overcome any challenges they might face.
+Beyond the direct support offered by Layer5 mentors, program participants will have an amazing networking opportunity to connect with the broader set of community members at Layer5. This event will kick-off virtually from March 3rd to March 28th, 2022.
+
+
CodeFlow
+
+The program is organized by CodeFlow, an organization whose main motive is to empower the student community by organizing webinars, hackathons, and open source events, providing them with the best learning environment and helping them gain the principal knowledge about the fast-paced, open source ecosystem. What a great learning opportunity this would prove to be as ‘open source meets its contributor force’ at OpenForce 2022! Come be a part of this amazing initiative.
+
+
+Layer5 is an amazing and welcoming community.
+
+
+
+
diff --git a/src/collections/blog/2022/2022-04-01-she-code-africa-contributhon/index.mdx b/src/collections/blog/2022/2022-04-01-she-code-africa-contributhon/index.mdx
index 59b9dc96b0cf..08c9da3bebad 100644
--- a/src/collections/blog/2022/2022-04-01-she-code-africa-contributhon/index.mdx
+++ b/src/collections/blog/2022/2022-04-01-she-code-africa-contributhon/index.mdx
@@ -1,54 +1,54 @@
----
-title: "Layer5 participates in She Code Africa's Contributhon Program 2022"
-date: 2022-04-01 21:00:00 +0000
-author: Shebuel Inyang
-thumbnail: ./layer5-contributhon-banner.webp
-darkthumbnail: ./layer5-contributhon-banner.webp
-category: Community
-tags:
- - Community
- - Events
- - MeshMate
-published: true
----
-
-import { Link } from "gatsby";
-
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
- The Contributhon Program is organized by She Code Africa, a non-profit organization focused on celebrating and empowering young Girls and Women in Technology across Africa. They provide support through diverse offline and online communities, resources, mentorship, and organize amazing programs and initiatives to always keep members or participants engaged.
-
-
-
- The Contributhon Program is a virtual open-source Bootcamp focused on building more women open-source contributors & creating more diversity in the African open source ecosystem. During this Bootcamp, participants work with an open-source organization on a project for the period of 8 weeks with the help of organization mentors.
-
-
-
- At the end of the Bootcamp, participants get rewarded a stipend of $500 upon successful project completion.
-
-
-
- Layer5 is participating as a mentoring organization and will be working directly with the program participants during the Bootcamp to help ensure that the project is completed successfully.
-
-
-
- At Layer5 we use Layer5 Community Forum for discussions in the community, this platform is active and it is easy to miss out on questions answered or important information. For this project, we want to create a leaderboard to show the most active participants based on helpful answers, questions asked, and more.
-
-
-
- Our selected mentors, Ekene Leonard Nwobodo, Yash Kamboj, Etiene James, Raj Gaurav Maurya and Kunal Verma who are trusted, capable, and qualified will guide participants Oyindamola Dawodu and Ednah Akoth throughout the duration of this Bootcamp, help them become a part of the community, teach them how to stay motivated and productive, show them how to solve technical problems, and also give constructive feedback as they keep track of the participants progress
-
-
-
- The She Code Africa hosts their Contributhon as an Africa-wide open source boot camp focused on building more women OSS contributors & creating more diversity in the African open source ecosystem by matching African women in technology with sponsors and mentors from Open Source organizations. During this boot camp, participants work with an open source organisation on a project for 4 weeks with the help of organisation mentors and get rewarded at the end of the boot camp upon successful project completion.
-
-
-
- This program kicks off virtually from April 1, 2022, to May 28, 2022.
-
-
-
+---
+title: "Layer5 participates in She Code Africa's Contributhon Program 2022"
+date: 2022-04-01 21:00:00 +0000
+author: Shebuel Inyang
+thumbnail: ./layer5-contributhon-banner.webp
+darkthumbnail: ./layer5-contributhon-banner.webp
+category: Community
+tags:
+ - Community
+ - Events
+ - MeshMate
+published: true
+---
+
+
+
+
+
+
+
+
+
+ The Contributhon Program is organized by She Code Africa, a non-profit organization focused on celebrating and empowering young Girls and Women in Technology across Africa. They provide support through diverse offline and online communities, resources, mentorship, and organize amazing programs and initiatives to always keep members or participants engaged.
+
+
+
+ The Contributhon Program is a virtual open-source Bootcamp focused on building more women open-source contributors & creating more diversity in the African open source ecosystem. During this Bootcamp, participants work with an open-source organization on a project for the period of 8 weeks with the help of organization mentors.
+
+
+
+ At the end of the Bootcamp, participants get rewarded a stipend of $500 upon successful project completion.
+
+
+
+ Layer5 is participating as a mentoring organization and will be working directly with the program participants during the Bootcamp to help ensure that the project is completed successfully.
+
+
+
+ At Layer5 we use Layer5 Community Forum for discussions in the community, this platform is active and it is easy to miss out on questions answered or important information. For this project, we want to create a leaderboard to show the most active participants based on helpful answers, questions asked, and more.
+
+
+
+ Our selected mentors, Ekene Leonard Nwobodo, Yash Kamboj, Etiene James, Raj Gaurav Maurya and Kunal Verma who are trusted, capable, and qualified will guide participants Oyindamola Dawodu and Ednah Akoth throughout the duration of this Bootcamp, help them become a part of the community, teach them how to stay motivated and productive, show them how to solve technical problems, and also give constructive feedback as they keep track of the participants progress
+
+
+
+ The She Code Africa hosts their Contributhon as an Africa-wide open source boot camp focused on building more women OSS contributors & creating more diversity in the African open source ecosystem by matching African women in technology with sponsors and mentors from Open Source organizations. During this boot camp, participants work with an open source organisation on a project for 4 weeks with the help of organisation mentors and get rewarded at the end of the boot camp upon successful project completion.
+
+
+
+ This program kicks off virtually from April 1, 2022, to May 28, 2022.
+
+
+
diff --git a/src/collections/blog/2022/2022-05-10-dockercon-22-hashicorp-talk/index.mdx b/src/collections/blog/2022/2022-05-10-dockercon-22-hashicorp-talk/index.mdx
index c49344c466e1..49f0f2898641 100644
--- a/src/collections/blog/2022/2022-05-10-dockercon-22-hashicorp-talk/index.mdx
+++ b/src/collections/blog/2022/2022-05-10-dockercon-22-hashicorp-talk/index.mdx
@@ -21,15 +21,15 @@ import { BlogWrapper } from "../../Blog.style.js";
import Blockquote from "../../../../reusecore/Blockquote";
import slidesTAG from "../../../events/2021/kubecon-china-2021/cncf-tag-network-and-service-mesh-working-group-kubecon-china-2021-lee-calcote-ken-owens.pdf";
import { Link } from "gatsby";
-import DDE from './docker-extension-meshery.webp';
-import developer from './developers-need.webp';
-import dashboard from './dashboard.webp';
-import designer from './designer-1.webp';
-import visualizer from './viz-1.webp';
+import DDE from "./docker-extension-meshery.webp";
+import developer from "./developers-need.webp";
+import dashboard from "./dashboard.webp";
+import designer from "./designer-1.webp";
+import visualizer from "./viz-1.webp";
-
+
Lee Calcote and Nic Jackson gave a presentation entitled Extending the Docker Compose Experience to Service Mesh at DockerCon 2022.
@@ -111,13 +111,17 @@ MeshMap is the world's only visual designer for Kubernetes and all cloud native
These Docker Extensions are so powerful that it allows you to do multiple tasks without leaving Docker Desktop.
-
-
+
+
-Lee Calcote and Nic Jackson packed a great deal of information in this talk. Find the recording below. The Meshery Extension is now out! Try now, and Share your Experience
-Apply for MeshMap Beta Program
+
+ Lee Calcote and Nic Jackson packed a great deal of information in this talk. Find the recording below. The Meshery Extension is now out! Try now, and Share your Experience
+
+
+ Apply for MeshMap Beta Program
+
diff --git a/src/collections/blog/2022/2022-05-10-dockercon-22-hpe-talk/index.mdx b/src/collections/blog/2022/2022-05-10-dockercon-22-hpe-talk/index.mdx
index 05363de9f1f2..e78b67f4aabe 100644
--- a/src/collections/blog/2022/2022-05-10-dockercon-22-hpe-talk/index.mdx
+++ b/src/collections/blog/2022/2022-05-10-dockercon-22-hpe-talk/index.mdx
@@ -1,131 +1,125 @@
----
-title: "Extending Docker with Meshery, SPIRE, and Istio"
-date: 2022-05-10 10:30:05 -0530
-author: Gaurav Chadha
-thumbnail: ./dc22-hpe-talk.webp
-darkthumbnail: ./dc22-hpe-talk.webp
-description: "DockerCon 2022 talk with HPE and Meshery Docker Extension Demo"
-category: "Docker"
-tags:
- - Docker
- - Meshery
-published: true
-resource: true
-type: Blog
-technology: Docker
-product: Docker Extension
-featured: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-import { Link } from "gatsby";
-import CloudNative from './cloud-native-management.webp';
-import CloudNativeIdentity from './cloud-native-identity.webp';
-import dde from './dde.webp';
-import designer from './Designer.webp';
-import visualizer from './Visualizer.webp';
-import meshmapInDocker from './meshmap-docker-extension-for-meshery.webp';
-
-
-
-
-
- Lee Calcote and Maximiliano Churichi gave a presentation entitled Extending Docker with Meshery, SPIRE, and Istio at DockerCon 2022.
-
-
-
-
- Lee Calcote is an innovative product and technology leader, passionate about empowering engineers and enabling organizations. As the founder and CEO of Layer5, he is at the forefront of the cloud native movement.
-
-
-
- Maximiliano Churichi is a Software Engineer at Hewlett Packard Enterprise, working in the Security Engineering team, and fully engaged in open source technologies, passionate about service mesh and cloud-native security.
-
-
-
-
- Cloud Native Management
-
-
-
- Lee Calcote introduces Meshery as a Cloud Native Management Plane, stating, "Meshery does Lifecycle and Performance Management of 10 different service meshes more than that it helps with configuration management with Kubernetes and with the Meshery Docker Extension it does same for the Docker Compose application."
-
-
-
-
- "As a Docker Captain, Lee have always been a proponent of Docker, and in particular its enablement of developer workflows", "Now, Docker Extensions bring an integrated experience with ecosystem tooling, like Meshery - a critical tool for developers, who are configuring and managing cloud native applications."
-
-
-
-
- Cloud Native Identity
-
-
- Maximiliano Churichi briefly explains about Cloud Native Identity and HPE's open source Project Mithril, "SPIFFE (Secure Production Identity Framework For Everyone) is a CNCF-incubated project that defines a set of standards for identifying and securing communications between application services. The SPIRE project (another CNCF project), the SPIFFE Runtime Environment, is a production-ready reference implementation of the SPIFFE principles, and additionally it also implements a set of APIs for controlling attestation policies, and coordinate certificate issuance and rotation."
-
-
-
- Maximiliano also tells how HPE's Project Mithril integrates SPIRE and Istio to strengthen service identity in the data plane. Project Mithril leverages the service management capabilities of Istio and the strong identity by attestation principles of SPIFFE and SPIRE to deliver robust and flexible attestation beyond Kubernetes namespaces and service accounts, and provide end-to-end secure attestation of workloads based on zero trust principles regardless of the location of such workloads. The improvements introduced by Project Mithril were already upstreamed into Istio, and are expected to be released in the upcoming Istio 1.14. Starting from this release, Istio users will be able to leverage SPIRE for SPIFFE identities management, and stronger identity attestation mechanisms.
-
-
-
-
-
How "Docker Extension for Meshery" helps to deploy with the click of a button?
-
-
- The new Meshery Docker Extension brings Layer5 MeshMap, the world's only visual designer for Kubernetes and service mesh deployments, to the desktop of millions of developers. Developers and operators alike can visually configure and operate their cloud native infrastructure and applications using MeshMap's low code visual designer.
-
-
-
- Maximiliano Churichi, Software Engineer at HPE says how conveniently Meshery integrates different services into Docker.
-
-
-
Kubernetes and service mesh support for your Docker Compose apps - Import your Docker Compose apps. Configure and deploy them to Kubernetes and any service mesh.
-
-
Visual design of Kubernetes applications - Using MeshMap as a visual topology for designing Docker Compose applications, operating Kubernetes, all Kubernetes operators, workloads, and custom resources.
-
-
Single-click deployment of your infrastructure - Support of 250+ different Kubernetes operators and 60+ cloud services at the fingertips of developers in connection with Docker Desktop’s ability to deliver Kubernetes locally.
-
-
Detection of Kubernetes environments - Scan your kubeconfigs and select your current Kubernetes environment. Switch from one environment to another or manage all clusters concurrently.
-
-
-
-
Maximiliano demonstrates MeshMap
-
-
-
-
-
-
-
-
Designer Mode
- Design a service mesh deployment with application and Envoy filter from scratch. Customize a service mesh deployment with application and Envoy filter from pattern.
-
-
-
-
-
-
-
Visualizer Mode
- Examine a visual topology of Kubernetes cluster and its services. View and search log streams from your pod's containers. Connect an interactive terminal to instances of your containers.
-
-
-
-
-
-
-
-
-
-
-
Lee Calcote and Maximiliano Churichi packed a great deal of information in this talk. Find the recording below. The Meshery Extension is now out! Try now, and Share your Experience
-Apply for MeshMap Beta Program
-
-
-
+---
+title: "Extending Docker with Meshery, SPIRE, and Istio"
+date: 2022-05-10 10:30:05 -0530
+author: Gaurav Chadha
+thumbnail: ./dc22-hpe-talk.webp
+darkthumbnail: ./dc22-hpe-talk.webp
+description: "DockerCon 2022 talk with HPE and Meshery Docker Extension Demo"
+category: "Docker"
+tags:
+ - Docker
+ - Meshery
+published: true
+resource: true
+type: Blog
+technology: Docker
+product: Docker Extension
+featured: true
+---
+
+
+
+
+import CloudNative from "./cloud-native-management.webp";
+import CloudNativeIdentity from "./cloud-native-identity.webp";
+import dde from "./dde.webp";
+import designer from "./Designer.webp";
+import visualizer from "./Visualizer.webp";
+import meshmapInDocker from "./meshmap-docker-extension-for-meshery.webp";
+
+
+
+
+
+ Lee Calcote and Maximiliano Churichi gave a presentation entitled Extending Docker with Meshery, SPIRE, and Istio at DockerCon 2022.
+
+
+
+
+ Lee Calcote is an innovative product and technology leader, passionate about empowering engineers and enabling organizations. As the founder and CEO of Layer5, he is at the forefront of the cloud native movement.
+
+
+
+ Maximiliano Churichi is a Software Engineer at Hewlett Packard Enterprise, working in the Security Engineering team, and fully engaged in open source technologies, passionate about service mesh and cloud-native security.
+
+
+
+
+ Cloud Native Management
+
+
+
+ Lee Calcote introduces Meshery as a Cloud Native Management Plane, stating, "Meshery does Lifecycle and Performance Management of 10 different service meshes more than that it helps with configuration management with Kubernetes and with the Meshery Docker Extension it does same for the Docker Compose application."
+
+
+
+
+ "As a Docker Captain, Lee have always been a proponent of Docker, and in particular its enablement of developer workflows", "Now, Docker Extensions bring an integrated experience with ecosystem tooling, like Meshery - a critical tool for developers, who are configuring and managing cloud native applications."
+
+
+
+
+ Cloud Native Identity
+
+
+ Maximiliano Churichi briefly explains about Cloud Native Identity and HPE's open source Project Mithril, "SPIFFE (Secure Production Identity Framework For Everyone) is a CNCF-incubated project that defines a set of standards for identifying and securing communications between application services. The SPIRE project (another CNCF project), the SPIFFE Runtime Environment, is a production-ready reference implementation of the SPIFFE principles, and additionally it also implements a set of APIs for controlling attestation policies, and coordinate certificate issuance and rotation."
+
+
+
+ Maximiliano also tells how HPE's Project Mithril integrates SPIRE and Istio to strengthen service identity in the data plane. Project Mithril leverages the service management capabilities of Istio and the strong identity by attestation principles of SPIFFE and SPIRE to deliver robust and flexible attestation beyond Kubernetes namespaces and service accounts, and provide end-to-end secure attestation of workloads based on zero trust principles regardless of the location of such workloads. The improvements introduced by Project Mithril were already upstreamed into Istio, and are expected to be released in the upcoming Istio 1.14. Starting from this release, Istio users will be able to leverage SPIRE for SPIFFE identities management, and stronger identity attestation mechanisms.
+
+
+
+
+
How "Docker Extension for Meshery" helps to deploy with the click of a button?
+
+
+ The new Meshery Docker Extension brings Layer5 MeshMap, the world's only visual designer for Kubernetes and service mesh deployments, to the desktop of millions of developers. Developers and operators alike can visually configure and operate their cloud native infrastructure and applications using MeshMap's low code visual designer.
+
+
+
+ Maximiliano Churichi, Software Engineer at HPE says how conveniently Meshery integrates different services into Docker.
+
+
+
Kubernetes and service mesh support for your Docker Compose apps - Import your Docker Compose apps. Configure and deploy them to Kubernetes and any service mesh.
+
+
Visual design of Kubernetes applications - Using MeshMap as a visual topology for designing Docker Compose applications, operating Kubernetes, all Kubernetes operators, workloads, and custom resources.
+
+
Single-click deployment of your infrastructure - Support of 250+ different Kubernetes operators and 60+ cloud services at the fingertips of developers in connection with Docker Desktop’s ability to deliver Kubernetes locally.
+
+
Detection of Kubernetes environments - Scan your kubeconfigs and select your current Kubernetes environment. Switch from one environment to another or manage all clusters concurrently.
+
+
+
+
Maximiliano demonstrates MeshMap
+
+
+
+
+
+
+
+
Designer Mode
+ Design a service mesh deployment with application and Envoy filter from scratch. Customize a service mesh deployment with application and Envoy filter from pattern.
+
+
+
+
+
+
+
Visualizer Mode
+ Examine a visual topology of Kubernetes cluster and its services. View and search log streams from your pod's containers. Connect an interactive terminal to instances of your containers.
+
+
+
+
+
+
+
+
+
+
+
Lee Calcote and Maximiliano Churichi packed a great deal of information in this talk. Find the recording below. The Meshery Extension is now out! Try now, and Share your Experience Apply for MeshMap Beta Program
+
+
\ No newline at end of file
diff --git a/src/collections/blog/2022/2022-05-14-service-meshcon-talk-intel/index.mdx b/src/collections/blog/2022/2022-05-14-service-meshcon-talk-intel/index.mdx
index 08f737b48f4d..9f2185f0b74b 100644
--- a/src/collections/blog/2022/2022-05-14-service-meshcon-talk-intel/index.mdx
+++ b/src/collections/blog/2022/2022-05-14-service-meshcon-talk-intel/index.mdx
@@ -22,18 +22,18 @@ import { BlogWrapper } from "../../Blog.style.js";
import Blockquote from "../../../../reusecore/Blockquote";
import slidesTAG from "../../../events/2021/kubecon-china-2021/cncf-tag-network-and-service-mesh-working-group-kubecon-china-2021-lee-calcote-ken-owens.pdf";
import { Link } from "gatsby";
-import meshmark from './meshmark-dark-text-side.svg';
-import performanceQuestion from './performance-question.webp';
-import smp from './smp.webp';
-import meshmarkSlide from './meshmark.webp';
-import example from './example.webp';
-import formula from './formula.webp';
-import MUE from './mue.webp';
-import MeshMapDemo from './meshmark-score.webp';
+import meshmark from "./meshmark-dark-text-side.svg";
+import performanceQuestion from "./performance-question.webp";
+import smp from "./smp.webp";
+import meshmarkSlide from "./meshmark.webp";
+import example from "./example.webp";
+import formula from "./formula.webp";
+import MUE from "./mue.webp";
+import MeshMapDemo from "./meshmark-score.webp";
-
+
Lee Calcote and Mrittika Ganguli presented MeshMark: Service Mesh value measurement at ServiceMeshCon Europe 2022.
@@ -102,8 +102,8 @@ the value that your infrastructure is providing. So we're really kind of missing
-
-
+
+
@@ -130,11 +130,14 @@ We could also take a look at service intentions of console and examine the effic
-
+
MeshMark in Meshery (an excerpt from ServiceMeshCon EU 2022 demo)
-
Lee Calcote and Mrittika Ganguli covered all the concepts of SMP and MeshMark in this great talk. Learn more about MeshMark on the Service Mesh Performance website.
+
+
+ Lee Calcote and Mrittika Ganguli covered all the concepts of SMP and MeshMark in this great talk. Learn more about MeshMark on the Service Mesh Performance website.
+
diff --git a/src/collections/blog/2022/2022-05-20-meshmate-of-the-year-2021-aditya-chatterjee/index.mdx b/src/collections/blog/2022/2022-05-20-meshmate-of-the-year-2021-aditya-chatterjee/index.mdx
index 4d55b829eb6f..5382cd742000 100644
--- a/src/collections/blog/2022/2022-05-20-meshmate-of-the-year-2021-aditya-chatterjee/index.mdx
+++ b/src/collections/blog/2022/2022-05-20-meshmate-of-the-year-2021-aditya-chatterjee/index.mdx
@@ -1,272 +1,271 @@
----
-title: "MeshMate of the Year 2021: Aditya Chatterjee"
-subtitle: ""
-date: 2022-05-20 09:10:00 +0000
-author: Nikhil Ladha
-thumbnail: ./MeshMate-of-the-Year-2021-Aditya-Chatterjee.webp
-darkthumbnail: ./MeshMate-of-the-Year-2021-Aditya-Chatterjee.webp
-category: Community
-tags:
- - Community
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import MMoY2021 from "./meshmate-of-the-year-2021.svg";
-import Blockquote from "../../../../reusecore/Blockquote";
-import BlockquoteAlt from "../../../../reusecore/Blockquote/Blockquote-alt-style";
-import { Link } from "gatsby";
-import graduateLFX from "./aditya-chatterjee-graduates-lfx-meshery-program.webp";
-import MeshMate from "../../../../assets/images/meshmate/meshmate-stack.svg";
-import MMOYAditya from "./MeshMate-of-the-Year-2021-Aditya-Chatterjee.webp";
-
-
-
-
- Nuturing a diverse, inclusive, and newcomer-friendly community like Layer5's
- is not easy. As a group of hardworking, committed mentors,{" "}
-
- MeshMates
-
- , tirelessly work to help make the Layer5 community the award-winning, open
- source community that it is. Each year, out of the group of MeshMates who
- continuously engage and support community members, a single individual is
- identified as the of MeshMate of the Year.
-
-
-
- As the{" "}
-
- inaugral winner of last year's
- {" "}
- MeshMate of the Year award, I am honored to present the prestigious MeshMate
- of the Year badge to{" "}
-
- Aditya Chatterjee
-
- . Chosen by his peers and for his sheer dedication, Aditya Chatterjee is
- awarded this badge of honor for 2021.{" "}
- Congratulations mate, you have earned it!
-
-
-{" "}
-
-
-
What is a Layer5 MeshMate?
-
-
-
-
- MeshMate
-
- is a distinction that Layer5 awards select members of the community who innately
- align with our culture of helping others, paying it forward, and a commitment to
- knowledge sharing. MeshMates are Layer5 mentors and ambassadors (not employees).
-
-
-
- A Layer5 MeshMate is individual who has consistently demonstrated their
- commitment to helping community members. The MeshMate program pairs
- experienced Layer5 community members with community newcomers to ensure a
- smooth onboarding experience. Helping community members takes all forms from
- ensuring the member has access to resources, is introduced to others,
- understands the vision and goals of projects, can build and contribute to
- projects, can use projects and have their feedback heard.{" "}
-
- MeshMates aid in identifying areas of projects and activities within the community
- to engage within, which working groups to join, and in help community members grow
- in their open source and cloud native knowledge.
-
-
-
- There is a lot going in the Layer5 community. Projects and working groups move
- fast. By connecting one-on-one, MeshMates share tips on how to have the best
- community experience possible, but also build a relationship with the
- community member inevitably leaving a lasting mark as is evident from member
- comments about Aditya.
-
-
-
It's not easy being a MeshMate
-
-
- With thousands of members in the Layer5 community, many come and go. Many take
- and many give. While we hope that each and every individual that joins will
- find a fit in the community and/or on a project, this isn't always the case.
-
- Engaging with and investing in community members can be taxing on mentors in
- terms of both their time and their emotional investment in seeing the newcomer
- plant roots, grow, and blossom.
-
-
-
- One of the goals MeshMates have is that of enabling the newcomer's passion and
- finding their sweetspot in the community and on a project, so that the
- newcomer ultimately achieves their goals - goals that are often similar, but
- different for each person. To help them acheive their goals, each individual
- is engaged 1:1 by their Meshmate, supporting them in becoming a landstanding
- Layer5 community member and contributor. MeshMates understand that many
- mentees start out with the best of intentions, but that not all overcome their
- hurdles in finding an area of the community to call home or aspect of a
- project to own.
-
-
-
-
-
-
-
-
-
MeshMates are a massive force
-
- With all that said, you must have already realized that it is not easy being a
- MeshMate. Only a few get this opportunity by showcasing their abilities and
- commitment to the community. Aditya has always hovered around the horizon of
- MeshMate since the moment he joined the community. In process of confirming
- Aditya as the winner of the MeshMate of the Year award, we looked to the
- community for validation. Little did I realize that meant reaching out to
- nearly a hundred people whom Aditya has mentored or supported in the Layer5
- community. More than a few of them had something to say about their time with
- Aditya:
-
-
-
-
-
-
-
-
- Aditya graduates the LFX Meshery program.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-{" "}
-
-
-
-
-
-
-
-
-{" "}
-
-
-{" "}
-
-
-
-
-
-
-
- In recognition a year's worth of paying it forward, and for the award,{" "}
- Aditya Chatterjee's
- profile identifies him as the MeshMate of the Year award winner. Only two
- people carry this badge today. I can only guess as to who this ribbon may be
- awarded to in 2022. In the year and a half that Aditya has been in the
- community, he has touched the lives of many people, including mine.
-
-
-
-
- The MeshMate badge is a point of pride for individuals participating in the
- program and looked upon with admiration and veneration by many within and
- external to the Layer5 community.
-
-
-
- Wear your MeshMate of the Year badge proudly, Aditya.
-
-
-
+---
+title: "MeshMate of the Year 2021: Aditya Chatterjee"
+subtitle: ""
+date: 2022-05-20 09:10:00 +0000
+author: Nikhil Ladha
+thumbnail: ./MeshMate-of-the-Year-2021-Aditya-Chatterjee.webp
+darkthumbnail: ./MeshMate-of-the-Year-2021-Aditya-Chatterjee.webp
+category: Community
+tags:
+ - Community
+published: true
+---
+
+
+import MMoY2021 from "./meshmate-of-the-year-2021.svg";
+
+
+
+import graduateLFX from "./aditya-chatterjee-graduates-lfx-meshery-program.webp";
+import MeshMate from "../../../../assets/images/meshmate/meshmate-stack.svg";
+import MMOYAditya from "./MeshMate-of-the-Year-2021-Aditya-Chatterjee.webp";
+
+
+
+
+ Nuturing a diverse, inclusive, and newcomer-friendly community like Layer5's
+ is not easy. As a group of hardworking, committed mentors,{" "}
+
+ MeshMates
+
+ , tirelessly work to help make the Layer5 community the award-winning, open
+ source community that it is. Each year, out of the group of MeshMates who
+ continuously engage and support community members, a single individual is
+ identified as the of MeshMate of the Year.
+
+
+
+ As the{" "}
+
+ inaugral winner of last year's
+
+ {" "}MeshMate of the Year award, I am honored to present the prestigious MeshMate
+ of the Year badge to{" "}
+
+ Aditya Chatterjee
+
+ . Chosen by his peers and for his sheer dedication, Aditya Chatterjee is
+ awarded this badge of honor for 2021.{" "}
+ Congratulations mate, you have earned it!
+
+
+{" "}
+
+
+
What is a Layer5 MeshMate?
+
+
+
+
+ MeshMate
+
+ is a distinction that Layer5 awards select members of the community who innately
+ align with our culture of helping others, paying it forward, and a commitment to
+ knowledge sharing. MeshMates are Layer5 mentors and ambassadors (not employees).
+
+
+
+ A Layer5 MeshMate is individual who has consistently demonstrated their
+ commitment to helping community members. The MeshMate program pairs
+ experienced Layer5 community members with community newcomers to ensure a
+ smooth onboarding experience. Helping community members takes all forms from
+ ensuring the member has access to resources, is introduced to others,
+ understands the vision and goals of projects, can build and contribute to
+ projects, can use projects and have their feedback heard.{" "}
+
+ MeshMates aid in identifying areas of projects and activities within the community
+ to engage within, which working groups to join, and in help community members grow
+ in their open source and cloud native knowledge.
+
+
+
+ There is a lot going in the Layer5 community. Projects and working groups move
+ fast. By connecting one-on-one, MeshMates share tips on how to have the best
+ community experience possible, but also build a relationship with the
+ community member inevitably leaving a lasting mark as is evident from member
+ comments about Aditya.
+
+
+
It's not easy being a MeshMate
+
+
+ With thousands of members in the Layer5 community, many come and go. Many take
+ and many give. While we hope that each and every individual that joins will
+ find a fit in the community and/or on a project, this isn't always the case.
+
+ Engaging with and investing in community members can be taxing on mentors in
+ terms of both their time and their emotional investment in seeing the newcomer
+ plant roots, grow, and blossom.
+
+
+
+ One of the goals MeshMates have is that of enabling the newcomer's passion and
+ finding their sweetspot in the community and on a project, so that the
+ newcomer ultimately achieves their goals - goals that are often similar, but
+ different for each person. To help them acheive their goals, each individual
+ is engaged 1:1 by their Meshmate, supporting them in becoming a landstanding
+ Layer5 community member and contributor. MeshMates understand that many
+ mentees start out with the best of intentions, but that not all overcome their
+ hurdles in finding an area of the community to call home or aspect of a
+ project to own.
+
+
+
+
+
+
+
+
+
MeshMates are a massive force
+
+ With all that said, you must have already realized that it is not easy being a
+ MeshMate. Only a few get this opportunity by showcasing their abilities and
+ commitment to the community. Aditya has always hovered around the horizon of
+ MeshMate since the moment he joined the community. In process of confirming
+ Aditya as the winner of the MeshMate of the Year award, we looked to the
+ community for validation. Little did I realize that meant reaching out to
+ nearly a hundred people whom Aditya has mentored or supported in the Layer5
+ community. More than a few of them had something to say about their time with
+ Aditya:
+
+
+
+
+
+
+
+
+ Aditya graduates the LFX Meshery program.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+{" "}
+
+
+
+
+
+
+
+
+{" "}
+
+
+{" "}
+
+
+
+
+
+
+
+ In recognition a year's worth of paying it forward, and for the award,{" "}
+ Aditya Chatterjee's
+ profile identifies him as the MeshMate of the Year award winner. Only two
+ people carry this badge today. I can only guess as to who this ribbon may be
+ awarded to in 2022. In the year and a half that Aditya has been in the
+ community, he has touched the lives of many people, including mine.
+
+
+
+
+ The MeshMate badge is a point of pride for individuals participating in the
+ program and looked upon with admiration and veneration by many within and
+ external to the Layer5 community.
+
+
+
+ Wear your MeshMate of the Year badge proudly, Aditya.
+
+
+
diff --git a/src/collections/blog/2022/2022-05-27-debug-envoy-proxy/index.mdx b/src/collections/blog/2022/2022-05-27-debug-envoy-proxy/index.mdx
index d342bcf97ed4..b1b1a1487926 100644
--- a/src/collections/blog/2022/2022-05-27-debug-envoy-proxy/index.mdx
+++ b/src/collections/blog/2022/2022-05-27-debug-envoy-proxy/index.mdx
@@ -1,190 +1,187 @@
----
-title: "Debug Envoy Proxy"
-subtitle: ""
-description: "An open index for measuring performance of cloud native infrastructure in context of the value provided to your business."
-date: 2022-05-27 09:10:00 +0000
-author: Layer5 Team
-thumbnail: ./debug-envoy-proxy.svg
-darkthumbnail: ./debug-envoy-proxy.svg
-category: Service Mesh
-tags:
- - Envoy
- - Troubleshooting
-published: true
-resource: true
-type: Blog
-redirect_from:
- - /blog/envoy/debug-envoy-proxy/
- - /blog/envoy/debug-envoy-proxy
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import bugEnvoy from "./debug-envoy-proxy.svg";
-import DockerExtensionCTA from "../../../../sections/Docker-Meshery/docker-extension-CTA";
-import Code from "../../../../components/CodeBlock";
-
-
-
- Trying to figure out what's happening with your request traffic? Not sure why your Envoy configuration isn't working? If you're using Istio as your gateway and need to troubleshoot your ingress traffic requests, here are a few tips for debugging Envoy proxy.
-
-
Enable Envoy Debug Logging
-
- By default Envoy system logs are sent to /dev/stderr. This location be overridden using --log-path. Logging to /dev/stderr for system logs and to /dev/stdout for access logs can be useful when running Envoy inside a container. In this way, these two individual logstreams can be separated, and using this approach, logging requires no additional files or directories to be mounted.
-
-
-
- We recommend setting the Envoy proxy’s log level to debug in a pre-production environment. Debug logs can help you identify issues before you graduate the associated configuration to your production environment.
-
-
-
Using envoy CLI
-
- The envoy command has a --log-level flag that can be useful for debugging. By default, it’s set to info. To change it to debug, edit the envoy DaemonSet in the istio-system namespace and replace the --log-level info flag with --log-level debug. Setting the Envoy log level to debug can be particilarly useful for debugging TLS connection failures.
-
-
Using container image
-
- If you’re using the Envoy image, you can set the log level to debug through the ENVOY_LOG_LEVEL environment variable. The log level for Envoy system logs can be set using the -l or --log-level option.
-
-
-The available log levels are:
-
-
-
trace
-
debug
-
info
-
warning/warn
-
error
-
critical
-
off
-
-
-The default is info.
-
-
Setting Envoy logs in the Helm configuration
-
-
- The Consul helm chart uses envoyExtraArgs: to leverage Envoy command line options. One of the helpful options is --component-log-level. This provides granular control over setting log levels for Envoy components. In the example below, the components upstream, http, router and config are set to the debug log level. These four components are vital when debugging issues with requests between your services(sidecar proxies).
-
- You will execute the kubectl command for each component. Make sure to append the correct component at the end of the curl command, i.e. logging? component = debug.
-
-
-
- If curl is not able to be used in your pod, you can alternatively use kubectl port-forward pod-name 19000 to make the Envoy admin accessible. From another terminal window, you can then curl to change the log levels. The output you receive in the terminal will show the modified component log levels.
-
-
-
-
- $ curl -X POST http://localhost:19000/logging? component = debug
-
-
-
Access Envoy logs in Kubernetes
-
-
Accessing Envoy logs via pods can be done with the following command:
The --follow flag provides a real time observation into Envoy logs.
-
-
Setting and Accessing Envoy logs when not using Helm.
-
-
The following command will start an envoy side car proxy, set the log level to debug with -l debug and capture Envoy logs in envoy_logs.txt. The .txt file will need to be created before executing this command.
- With Istio as your gateway, you should first look at VirtualService objects. These can show if the hosts are registered to the gateway correctly.
-
-
-
-
- $ kubectl get virtualservice -o=yaml
-
-
-
-
- However, sometimes, the Envoy inside the gateway container is not properly configured (likely due to a bug). You can dump Envoy configuration to debug this further.
-
-
-
-
- # find istio ingress gateway pod \
- $ kubectl get pods -n istio-system -l app=istio-ingressgateway
-
-
-
-
- Let's use istio-ingressgateway-a93019f9dfw-l39xd as an example pod name.
-
- We hope these steps are useful to you. If you're still having trouble configuring Envoy proxy, open up a new thread on the community discussion forum or subscribe to the Layer5 newletter for tips and tricks.
-
-
+---
+title: "Debug Envoy Proxy"
+subtitle: ""
+description: "An open index for measuring performance of cloud native infrastructure in context of the value provided to your business."
+date: 2022-05-27 09:10:00 +0000
+author: Layer5 Team
+thumbnail: ./debug-envoy-proxy.svg
+darkthumbnail: ./debug-envoy-proxy.svg
+category: Service Mesh
+tags:
+ - Envoy
+ - Troubleshooting
+published: true
+resource: true
+type: Blog
+redirect_from:
+ - /blog/envoy/debug-envoy-proxy/
+ - /blog/envoy/debug-envoy-proxy
+---
+
+import bugEnvoy from "./debug-envoy-proxy.svg";
+
+
+
+
+ Trying to figure out what's happening with your request traffic? Not sure why your Envoy configuration isn't working? If you're using Istio as your gateway and need to troubleshoot your ingress traffic requests, here are a few tips for debugging Envoy proxy.
+
+
Enable Envoy Debug Logging
+
+ By default Envoy system logs are sent to /dev/stderr. This location be overridden using --log-path. Logging to /dev/stderr for system logs and to /dev/stdout for access logs can be useful when running Envoy inside a container. In this way, these two individual logstreams can be separated, and using this approach, logging requires no additional files or directories to be mounted.
+
+
+
+ We recommend setting the Envoy proxy’s log level to debug in a pre-production environment. Debug logs can help you identify issues before you graduate the associated configuration to your production environment.
+
+
+
Using envoy CLI
+
+ The envoy command has a --log-level flag that can be useful for debugging. By default, it’s set to info. To change it to debug, edit the envoy DaemonSet in the istio-system namespace and replace the --log-level info flag with --log-level debug. Setting the Envoy log level to debug can be particilarly useful for debugging TLS connection failures.
+
+
Using container image
+
+ If you’re using the Envoy image, you can set the log level to debug through the ENVOY_LOG_LEVEL environment variable. The log level for Envoy system logs can be set using the -l or --log-level option.
+
+
+The available log levels are:
+
+
+
trace
+
debug
+
info
+
warning/warn
+
error
+
critical
+
off
+
+
+The default is info.
+
+
Setting Envoy logs in the Helm configuration
+
+
+ The Consul helm chart uses envoyExtraArgs: to leverage Envoy command line options. One of the helpful options is --component-log-level. This provides granular control over setting log levels for Envoy components. In the example below, the components upstream, http, router and config are set to the debug log level. These four components are vital when debugging issues with requests between your services(sidecar proxies).
+
+ You will execute the kubectl command for each component. Make sure to append the correct component at the end of the curl command, i.e. logging? component = debug.
+
+
+
+ If curl is not able to be used in your pod, you can alternatively use kubectl port-forward pod-name 19000 to make the Envoy admin accessible. From another terminal window, you can then curl to change the log levels. The output you receive in the terminal will show the modified component log levels.
+
+
+
+
+ $ curl -X POST http://localhost:19000/logging? component = debug
+
+
+
Access Envoy logs in Kubernetes
+
+
Accessing Envoy logs via pods can be done with the following command:
The --follow flag provides a real time observation into Envoy logs.
+
+
Setting and Accessing Envoy logs when not using Helm.
+
+
The following command will start an envoy side car proxy, set the log level to debug with -l debug and capture Envoy logs in envoy_logs.txt. The .txt file will need to be created before executing this command.
+ With Istio as your gateway, you should first look at VirtualService objects. These can show if the hosts are registered to the gateway correctly.
+
+
+
+
+ $ kubectl get virtualservice -o=yaml
+
+
+
+
+ However, sometimes, the Envoy inside the gateway container is not properly configured (likely due to a bug). You can dump Envoy configuration to debug this further.
+
+
+
+
+ # find istio ingress gateway pod \
+ $ kubectl get pods -n istio-system -l app=istio-ingressgateway
+
+
+
+
+ Let's use istio-ingressgateway-a93019f9dfw-l39xd as an example pod name.
+
+ We hope these steps are useful to you. If you're still having trouble configuring Envoy proxy, open up a new thread on the community discussion forum or subscribe to the Layer5 newletter for tips and tricks.
+
+
\ No newline at end of file
diff --git a/src/collections/blog/2022/2022-06-01-perfbytes-podcast/index.mdx b/src/collections/blog/2022/2022-06-01-perfbytes-podcast/index.mdx
index 5a7a11a379e5..99d9f5f4f62e 100644
--- a/src/collections/blog/2022/2022-06-01-perfbytes-podcast/index.mdx
+++ b/src/collections/blog/2022/2022-06-01-perfbytes-podcast/index.mdx
@@ -1,129 +1,126 @@
----
-title: "Perfbytes Podcast"
-subtitle: "Ask Me Anything"
-date: 2022-06-01 09:10:00 +0000
-author: Debopriya Bhattacharjee
-thumbnail: ./perfbytes-layer5.svg
-darkthumbnail: ./perfbytes-layer5.svg
-category: Events
-tags:
- - Events
- - Service Mesh Performance
- - Meshery
-published: true
-resource: true
-type: Blog
-product: Meshery
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-import BlockquoteAlt from "../../../../reusecore/Blockquote/Blockquote-alt-style";
-import { Link } from "gatsby";
-import { PerfbytesPodcast } from "./perfbytesPodcast";
-import ConsulDemo from "./consul-docker-extension-demo.webp"
-
-
-
-
-
Podcast Insights
-
Many questions were asked, answered, and a variety of topics were discussed. The story just gets better. This podcast goes deep into service meshes, load generators, circuit breaker, service mesh patterns in addition to a live demo of Meshery and more. Hosted by Henrik from Perfbytes and joined by Mark, Lee Calcote from Layer5 and Mrittika Ganguli from Intel. Tune in to find out more. Get answers to all community questions as a bonus.
-
-
What is a service mesh?
-
-
Service mesh is one of the solutions that helps you to route traffic within your cluster so as to expose your services outside the cluster. It is a solution to control how different parts of an application share data with one another. Unlike other systems for managing this communication, a service mesh is a dedicated infrastructure layer built right into an app. You have different options like the service type load balancer or using ingress but service mesh makes sense because it will manage a lot of features around your service to service communication.
-
-
-In general, service meshes arose from the concept of proxies such as the NGINX proxy. Then Envoy was introduced by Lyft. Lyft had the architecture, and Google came along and created it. That gave us Istio, which is now part of CNCF.
-
-
-Service meshes, according to Lee, "hit a real sweet spot personally", having been focused on networking for most part of his career.
-He believes that there are a couple of different ways to speak about the genesis of service meshes, with Linkerd being the first to coin the term.
-We had Linkerd v1 written in scala and use jvm and then came Linkerd v2 which is something totally different at this point. It's all different code, different languages and a different service mesh architecture. There's a number of different architectures by which service meshes are deployed. There's a new one that's been softly announced in beta from called Cilium that is helping bring back some of the different architectures of how to run the proxies.
-
-
-
-The way I prefer to think about a surface mesh is that it's all about resiliency.
-If you were to take a three-tiered web or three-tiered app and you think about how you're breaking out those tiers with some amount of
-kind of vertical scaling, you'd probably, end up putting at least a virtual IP address out in front of the whole web tier and then you've got an app tier and a database tier because you've got multiple instances of those things. Maybe there's a load balancer in between. This structure makes it simple to boost your resiliency.
-
-
-
-Henrik goes on to elaborate that in service mesh we can do a lot of things to make sure that the communication is reliable.
-When you design microservice architecture, there is a need of implementing retry logic. So if a service A needs to introduce another service B, then the service mesh will manage the retry logic such that if we reach at one time and the service B is not responding then the service mesh will try to reach out several times. Therefore a service mesh offers a variety of features like this to manage the certificates within the cluster and and circle them in a regular pace. You can also have traffic splitting if you do canary releases. In your service to service communication, there are a plethora of scenarios that the service mesh can handle.
-Henrik recalled that it's normally difficult to obtain a full view of what rules we've applied in the cluster, and when he first saw Meshery, his immediate thought was, "Wow, this is exactly what is missing in the market at the moment."
-
-
-Lets dig deeper into this tool we've been alluding to for a while now: Meshery.
-
-
Meshery
-If you were on a pager and were managing a large service mesh deployment with a number of rules and configurations around how security is enforced and identities are managed, and things like uniform observability and how metrics and logs are collected and enforced, and then the different traffic writing rules and stuff. You might soil myself if you had to go make a change in that sea of yaml. That's in part what we're working towards. There's a capability within Meshery for solving this challenge. As a cloud native management plane, Meshery presides over top of 10 different types of service meshes and it also presides over kubernetes. You can run it outside of kubernetes or inside of kubernetes.
-
-Meshery has a number of components to its architecture. There is Meshery UI. It has a Mesheryctl, which is a CLI component. We have a number of service mesh adapters for each service mesh that Meshery supports.
-
-
-
What is the need for different adapters?
-
-Meshery, as the multi-mesh manager, supports couple of different adapters. Adapters are used by Meshery to manage the numerous service meshes. Different service mesh adapters are written to expose the unique value of each service mesh. Consequently, they are not equally capable just as each service mesh is not equally capable as the other. Some of them work in a similar way. Some of the service meshes have their own differentiated value, which is why there are individual adapters. Some of them work slightly differently depending on whether they're running as a managed service or not.
-
-
-
-We have a plug-in for Meshery it's called MeshMap, it is what you might consider a visual topology. It has a lot of use cases for observing in kind of a read-only mode. There's a second mode to this tool: The Designer Mode. It's a visual configurator of not only the specific settings within any of those service meshes that it supports like a circuit breaker and adjusting the sensor video
-but also end up being a visual designer for your kubernetes deployments. When users drop in, they're able to go over and grab the specific capabilities of any of those service mesh adapters that are loaded for any of the versions of that mesh that they might want to design. The concept here is that they drag and drop these capabilities over and there's a bit of discoverability that's afforded through this ui rather than parsing through yaml, trying to understand what's going on.
-
-
-
-I like to pretend that I know a lot about service meshes, but when it comes to having to keep track of all of them, I don't know what the gateway tls sds config is, and so this type of inline help is quite useful to design your deployments. The deployments may or may not use a mesh; in fact, you can use this to create your Kubernetes configuration and deployment as well. You can even save and recall those designs.
-
-Taking this example of consul, produced by hashicorp, is a little more of an
-intriguing deployment and a simple two-tier deck. We announced the Meshery Docker Extension recently. So if you're using docker desktop, Meshery will be a first class app that's available inside of market and part of what it does as it integrates with docker desktop is it will import docker compose apps convert them to kubernetes manifests or kubernetes apps and they'll let you deploy those formerly docker compose apps onto a mesh which is why I'm talking about a two-tiered service.
-
-
Does MeshMap allow you to load the current configuration that is has been applied in the current cluster?
-
-
-Currently, there are two modes: the one we were looking at before was the designer mode, and the one we'll be looking at now is the visualizer mode, which is probably a little more of an it's not entirely read-only to the extent that you could grab a pod and start an interactive session with the containers in that pod or you could you start a logging session. You could also initiate a performance test against that particular service or that particular endpoint.
-Meshery supports three different types of load generators, which is a nighthawk, fortio and wrk2.
-
-
-
What are the capabilities of these three load generators? When you speak about service mesh testing or performance testing, what is actually the process behind the scene? What should users think about when they're starting a gig and need to configure and optimize the service mesh?
-
-
Lee expounds on that for our benefit.
-It takes weeks to months that you've got to dedicate for performance engineers to go over and like pull together various tools and scripts around them to then get into a spreadsheet or into some database that you then generate results.
-The genesis of Meshery part was to help people comprehend what a service mesh is, when to use one and which one to use? As you go to explain these common questions, the real answer is a totally disappointing, which is, it just depends on what you're asking to do.
-
-People want to measure it in cold hard quantitative metrics but if you're asking to do 100 percent sampling then also consider the distributed tracing implementation you had somewhere else and the fact that you're getting it
-in a uniform way here. Maybe you're likely to consider the overhead that you would have over there. It's frustrating to be trying to explain stuff to folks and get them excited about the tech and and to give them a vague response. Instead we give them a tool that says "Hey look here's a tool that will deploy any of the service meshes that you want to test out."
-
-
-There's a reason why there's ten of them like and actually many more than that.
-There's a lot of overlap between them but different tools for different purposes for different size orgs, so it would be inappropriate to say well you know here's the one. It's rather hey here's a tool that that lets you deploy any number of them quickly, answer your own question about performance, because we can pump out benchmarks of the various service meshes under various configurations, using different types of workloads but which may or may not match your environment and over time those reports are going to get stale and so rather he's a tool to make you empowered.
-
-
-
-
Do you actually generate traffic that will go through the sidecar proxy of the service and then reach out the actual service?
-
-That load is generated on demand or on schedule against one or more endpoints, one or more of your services or something that is not even on your service. You can generate load not only against something running within your infrastructure but something external as well to do statistical analysis based on the configuration that you gave it and so yeah the answer is yes the traffic flows through the sidecar.
-
-
-
If I say I have never scripted or built any scenarios for fortio or nighthawk. Let's say I'm a loadrunner, a neoload, or a k6 user, and I want to accomplish the same thing with them. So what is the journey on those load generator? is it the same thing you have to build a workflow of requests that you want to send in that scenario?
-
-
That leads us to probably talk about one of our other projects which is called Performance which is a specification. It's another one of the projects that we've donated to the CNCF. Service Mesh Performance is the spec while Meshery is an implementation of the spec.
-At a high level, if those other load generators were to adhere to how we standardize and describe the test that you want to run and then hand off that configuration to generate the performance profiles that are created here you're not gonna down download them but the descriptor is important.
-
-This implements a standard for the industry on what is the actual
-service mesh test and then standardize the format so then anyone can use the same format to design their script or whatever they want and then use it to test.
-So when I build a script, and I don't know loadrunner today and I want to use neologo tomorrow, then I don't have to rewrite everything. Great!
-
-
-Missed the podcast? No worries, we got you covered. Check out the recording below :)
-
-
Many questions were asked, answered, and a variety of topics were discussed. The story just gets better. This podcast goes deep into service meshes, load generators, circuit breaker, service mesh patterns in addition to a live demo of Meshery and more. Hosted by Henrik from Perfbytes and joined by Mark, Lee Calcote from Layer5 and Mrittika Ganguli from Intel. Tune in to find out more. Get answers to all community questions as a bonus.
+
+
What is a service mesh?
+
+
Service mesh is one of the solutions that helps you to route traffic within your cluster so as to expose your services outside the cluster. It is a solution to control how different parts of an application share data with one another. Unlike other systems for managing this communication, a service mesh is a dedicated infrastructure layer built right into an app. You have different options like the service type load balancer or using ingress but service mesh makes sense because it will manage a lot of features around your service to service communication.
+
+
+In general, service meshes arose from the concept of proxies such as the NGINX proxy. Then Envoy was introduced by Lyft. Lyft had the architecture, and Google came along and created it. That gave us Istio, which is now part of CNCF.
+
+
+Service meshes, according to Lee, "hit a real sweet spot personally", having been focused on networking for most part of his career.
+He believes that there are a couple of different ways to speak about the genesis of service meshes, with Linkerd being the first to coin the term.
+We had Linkerd v1 written in scala and use jvm and then came Linkerd v2 which is something totally different at this point. It's all different code, different languages and a different service mesh architecture. There's a number of different architectures by which service meshes are deployed. There's a new one that's been softly announced in beta from called Cilium that is helping bring back some of the different architectures of how to run the proxies.
+
+
+
+The way I prefer to think about a surface mesh is that it's all about resiliency.
+If you were to take a three-tiered web or three-tiered app and you think about how you're breaking out those tiers with some amount of
+kind of vertical scaling, you'd probably, end up putting at least a virtual IP address out in front of the whole web tier and then you've got an app tier and a database tier because you've got multiple instances of those things. Maybe there's a load balancer in between. This structure makes it simple to boost your resiliency.
+
+
+
+Henrik goes on to elaborate that in service mesh we can do a lot of things to make sure that the communication is reliable.
+When you design microservice architecture, there is a need of implementing retry logic. So if a service A needs to introduce another service B, then the service mesh will manage the retry logic such that if we reach at one time and the service B is not responding then the service mesh will try to reach out several times. Therefore a service mesh offers a variety of features like this to manage the certificates within the cluster and and circle them in a regular pace. You can also have traffic splitting if you do canary releases. In your service to service communication, there are a plethora of scenarios that the service mesh can handle.
+Henrik recalled that it's normally difficult to obtain a full view of what rules we've applied in the cluster, and when he first saw Meshery, his immediate thought was, "Wow, this is exactly what is missing in the market at the moment."
+
+
+Lets dig deeper into this tool we've been alluding to for a while now: Meshery.
+
+
Meshery
+If you were on a pager and were managing a large service mesh deployment with a number of rules and configurations around how security is enforced and identities are managed, and things like uniform observability and how metrics and logs are collected and enforced, and then the different traffic writing rules and stuff. You might soil myself if you had to go make a change in that sea of yaml. That's in part what we're working towards. There's a capability within Meshery for solving this challenge. As a cloud native management plane, Meshery presides over top of 10 different types of service meshes and it also presides over kubernetes. You can run it outside of kubernetes or inside of kubernetes.
+
+Meshery has a number of components to its architecture. There is Meshery UI. It has a Mesheryctl, which is a CLI component. We have a number of service mesh adapters for each service mesh that Meshery supports.
+
+
+
What is the need for different adapters?
+
+Meshery, as the multi-mesh manager, supports couple of different adapters. Adapters are used by Meshery to manage the numerous service meshes. Different service mesh adapters are written to expose the unique value of each service mesh. Consequently, they are not equally capable just as each service mesh is not equally capable as the other. Some of them work in a similar way. Some of the service meshes have their own differentiated value, which is why there are individual adapters. Some of them work slightly differently depending on whether they're running as a managed service or not.
+
+
+
+We have a plug-in for Meshery it's called MeshMap, it is what you might consider a visual topology. It has a lot of use cases for observing in kind of a read-only mode. There's a second mode to this tool: The Designer Mode. It's a visual configurator of not only the specific settings within any of those service meshes that it supports like a circuit breaker and adjusting the sensor video
+but also end up being a visual designer for your kubernetes deployments. When users drop in, they're able to go over and grab the specific capabilities of any of those service mesh adapters that are loaded for any of the versions of that mesh that they might want to design. The concept here is that they drag and drop these capabilities over and there's a bit of discoverability that's afforded through this ui rather than parsing through yaml, trying to understand what's going on.
+
+
+
+I like to pretend that I know a lot about service meshes, but when it comes to having to keep track of all of them, I don't know what the gateway tls sds config is, and so this type of inline help is quite useful to design your deployments. The deployments may or may not use a mesh; in fact, you can use this to create your Kubernetes configuration and deployment as well. You can even save and recall those designs.
+
+Taking this example of consul, produced by hashicorp, is a little more of an
+intriguing deployment and a simple two-tier deck. We announced the Meshery Docker Extension recently. So if you're using docker desktop, Meshery will be a first class app that's available inside of market and part of what it does as it integrates with docker desktop is it will import docker compose apps convert them to kubernetes manifests or kubernetes apps and they'll let you deploy those formerly docker compose apps onto a mesh which is why I'm talking about a two-tiered service.
+
+
Does MeshMap allow you to load the current configuration that is has been applied in the current cluster?
+
+Currently, there are two modes: the one we were looking at before was the designer mode, and the one we'll be looking at now is the visualizer mode, which is probably a little more of an it's not entirely read-only to the extent that you could grab a pod and start an interactive session with the containers in that pod or you could you start a logging session. You could also initiate a performance test against that particular service or that particular endpoint.
+Meshery supports three different types of load generators, which is a nighthawk, fortio and wrk2.
+
+
+
What are the capabilities of these three load generators? When you speak about service mesh testing or performance testing, what is actually the process behind the scene? What should users think about when they're starting a gig and need to configure and optimize the service mesh?
+
+
Lee expounds on that for our benefit.
+It takes weeks to months that you've got to dedicate for performance engineers to go over and like pull together various tools and scripts around them to then get into a spreadsheet or into some database that you then generate results.
+The genesis of Meshery part was to help people comprehend what a service mesh is, when to use one and which one to use? As you go to explain these common questions, the real answer is a totally disappointing, which is, it just depends on what you're asking to do.
+
+People want to measure it in cold hard quantitative metrics but if you're asking to do 100 percent sampling then also consider the distributed tracing implementation you had somewhere else and the fact that you're getting it
+in a uniform way here. Maybe you're likely to consider the overhead that you would have over there. It's frustrating to be trying to explain stuff to folks and get them excited about the tech and and to give them a vague response. Instead we give them a tool that says "Hey look here's a tool that will deploy any of the service meshes that you want to test out."
+
+
+There's a reason why there's ten of them like and actually many more than that.
+There's a lot of overlap between them but different tools for different purposes for different size orgs, so it would be inappropriate to say well you know here's the one. It's rather hey here's a tool that that lets you deploy any number of them quickly, answer your own question about performance, because we can pump out benchmarks of the various service meshes under various configurations, using different types of workloads but which may or may not match your environment and over time those reports are going to get stale and so rather he's a tool to make you empowered.
+
+
+
+
Do you actually generate traffic that will go through the sidecar proxy of the service and then reach out the actual service?
+
+That load is generated on demand or on schedule against one or more endpoints, one or more of your services or something that is not even on your service. You can generate load not only against something running within your infrastructure but something external as well to do statistical analysis based on the configuration that you gave it and so yeah the answer is yes the traffic flows through the sidecar.
+
+
+
If I say I have never scripted or built any scenarios for fortio or nighthawk. Let's say I'm a loadrunner, a neoload, or a k6 user, and I want to accomplish the same thing with them. So what is the journey on those load generator? is it the same thing you have to build a workflow of requests that you want to send in that scenario?
+
+
That leads us to probably talk about one of our other projects which is called Performance which is a specification. It's another one of the projects that we've donated to the CNCF. Service Mesh Performance is the spec while Meshery is an implementation of the spec. At a high level, if those other load generators were to adhere to how we standardize and describe the test that you want to run and then hand off that configuration to generate the performance profiles that are created here you're not gonna down download them but the descriptor is important.
+This implements a standard for the industry on what is the actual
+service mesh test and then standardize the format so then anyone can use the same format to design their script or whatever they want and then use it to test.
+So when I build a script, and I don't know loadrunner today and I want to use neologo tomorrow, then I don't have to rewrite everything. Great!
+
+
+Missed the podcast? No worries, we got you covered. Check out the recording below :)
+
+
+
+
+
+
+
+
diff --git a/src/collections/blog/2022/2022-06-07-week-open-source-contributions-with-layer5/index.mdx b/src/collections/blog/2022/2022-06-07-week-open-source-contributions-with-layer5/index.mdx
index 50dd4059621e..c971829c2964 100644
--- a/src/collections/blog/2022/2022-06-07-week-open-source-contributions-with-layer5/index.mdx
+++ b/src/collections/blog/2022/2022-06-07-week-open-source-contributions-with-layer5/index.mdx
@@ -12,14 +12,14 @@ tags:
published: true
---
-import { Link } from "gatsby";
-import { BlogWrapper } from "../../Blog.style.js";
-import mentees from './mentees.webp'
+
+
+import mentees from "./mentees.webp"
import meshmate from "../../../../assets/images/meshmate/meshmate-icon.svg"
-
+
To newbies, open source contributions may seem daunting. In much the same way that non-techies develop a reverence for programmers courtesy of the film industry’s portrayal of them as wizards whose brains magically sprout up elaborate mathematical models and whose mouths eloquently spew technological jargon, so do newbies perceive contributors: a bunch of techies who debug in seconds, recite programming language documentation by heart and, well, create pull requests in their sleep (this is a bit exaggerated, but you get the point).
@@ -89,7 +89,7 @@ To newbies, open source contributions may seem daunting. In much the same way th
- Ekene Leonard Nwobodo
+ Ekene Leonard Nwobodo
Etiene James
diff --git a/src/collections/blog/2022/2022-06-08-experience-lfx-pranav-singh/index.mdx b/src/collections/blog/2022/2022-06-08-experience-lfx-pranav-singh/index.mdx
index 5c188d25e8ce..08c95770e658 100644
--- a/src/collections/blog/2022/2022-06-08-experience-lfx-pranav-singh/index.mdx
+++ b/src/collections/blog/2022/2022-06-08-experience-lfx-pranav-singh/index.mdx
@@ -17,8 +17,8 @@ published: true
type: Blog
---
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
+
+
@@ -30,7 +30,7 @@ more excited by the enthusiasm and energy of each community members welcoming me
learned about the project through the demos/updates from fellow contributors. Slowly and gradually, I started contributing too, then delivering updates in the
community calls, and consequently started climbing the contributor ladder.
-When I realised that I would be working on [Layer5 Cloud](https://cloud.layer5.io) and Meshery as an LFX intern at Layer5, then I couldn't control my excitement.
+When I realised that I would be working on [Layer5 Cloud](https://meshery.layer5.io) and Meshery as an LFX intern at Layer5, then I couldn't control my excitement.
That excitement was to ship more impactful features for the Layer5 projects, work and engage more deeply with the engineering team at Layer5 and have an overall
upliftment of my development skills. Throughout my internship I worked on several features. Few on the top of the list are as follows, expanding
[Meshery extension points](https://docs.meshery.io/extensibility), exposing node details of the K8s clusters on which Meshery runs performance tests,
diff --git a/src/collections/blog/2022/2022-06-09-evolution-of-mesheryctl-ref/index.mdx b/src/collections/blog/2022/2022-06-09-evolution-of-mesheryctl-ref/index.mdx
index a0436152f35d..c43c4a0af36e 100644
--- a/src/collections/blog/2022/2022-06-09-evolution-of-mesheryctl-ref/index.mdx
+++ b/src/collections/blog/2022/2022-06-09-evolution-of-mesheryctl-ref/index.mdx
@@ -1,100 +1,102 @@
----
-title: "Evolution of the Meshery CLI Command Reference"
-date: 2022-06-09 01:15:00 -0600
-author: Aadhitya Amarendiran
-description: Autogeneration of Meshery CLI command reference
-thumbnail: ./mesheryctl.webp
-darkthumbnail: ./mesheryctl.webp
-category: "Meshery"
-tags:
- - Projects
- - Meshery
- - mesheryctl
-published: true
-resource: true
-type: Blog
-product: Meshery
-featured: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Blockquote from "../../../../reusecore/Blockquote";
-
-import oldDesign from "./initial-design.webp";
-import newDesign from "./mesheryctl-docs.webp";
-
-
-
-
-
Documentation plays a major role in any project. Even if the project is small or too big, the creator or the team behind the project needs to curate the documentation very well such that it'll be useful for new end users to refer and learn to use the project, troubleshoot the problems occurred and lot more. Thus, we, Layer5 have curated the documentation for Meshery to meet such purposes. Not to mention, mesheryctl, the CLI client of Meshery needs a curated documentation as well. This blog describes about the evolution of mesheryctl command reference page.
-
-
-
Initial Command Reference Design
-
The initial design of mesheryctl command reference page is all made using pure markdown and the functionality is handled using Jekyll, the main framework used for Meshery Docs. This handled great at initial stage but had many limitations, such as:
-
-
Updation of YAML for data is often required
-
Design was obselete at initial stage
-
No separate pages for each command and subcommand
-
- Thus, the idea for redesigning the mesheryctl reference page was desperately needed.
-
To tackle the shortcomings of the previous design, I was tasked to redesign the mesheryctl command reference page entirely. This was a big task at first glance to me, as I was a new contributor back then. Eventually after manipulating the reference section with help of great folks, I was able to pull off the task and the design was updated.
As time passed, we realized that the command reference missed something for a while, though the design has been changed. Then, we thought the idea of automating the generation of docs such that developers don't need to change the code in docs section while working towards mesheryctl. That's where we got to know that Cobra library (the library for CLI apps made using golang) has a feature to make doc pages automatically. So we decided to incorporate that feature into mesheryctl docs page as well! After making several changes and a PR, I was finally able to introduce the feature in the docs site!
-
-```
-var startCmd = &cobra.Command {
- Use: "start",
- Short: "Start Meshery",
- Long: `Start Meshery and each of its service mesh components.`,
- Args: cobra.NoArgs,
- Example: `
-// Start meshery
-mesheryctl system start
-// To create a new context for in-cluster Kubernetes deployments and set the new context as your current-context
-mesheryctl system context create k8s -p kubernetes -s
-// (optional) skip checking for new updates available in Meshery.
-mesheryctl system start --skip-update
-// Reset Meshery's configuration file to default settings.
-mesheryctl system start --reset
-// Silently create Meshery's configuration file with default settings
-mesheryctl system start --yes
-.....
-}
- `,
-```
-
-
Using this information provided above in each golang file, the markdown page is generated using Cobra CLI library and thus reducing the workload on the developer by automating via GitHub Actions.
-
-
This is so far on how the mesheryctl command reference is evolved for now. And I hope that it'll continue to evolve in the field of documentation to serve the users to use Meshery in best way possible.
Documentation plays a major role in any project. Even if the project is small or too big, the creator or the team behind the project needs to curate the documentation very well such that it'll be useful for new end users to refer and learn to use the project, troubleshoot the problems occurred and lot more. Thus, we, Layer5 have curated the documentation for Meshery to meet such purposes. Not to mention, mesheryctl, the CLI client of Meshery needs a curated documentation as well. This blog describes about the evolution of mesheryctl command reference page.
+
+
+
Initial Command Reference Design
+
+The initial design of mesheryctl command reference page is all made using pure markdown and the functionality is handled using Jekyll, the main framework used for Meshery Docs. This handled great at initial stage but had many limitations, such as:
+
+
Updation of YAML for data is often required
+
Design was obselete at initial stage
+
No separate pages for each command and subcommand
+
+ Thus, the idea for redesigning the mesheryctl reference page was desperately needed.
+
+
To tackle the shortcomings of the previous design, I was tasked to redesign the mesheryctl command reference page entirely. This was a big task at first glance to me, as I was a new contributor back then. Eventually after manipulating the reference section with help of great folks, I was able to pull off the task and the design was updated.
As time passed, we realized that the command reference missed something for a while, though the design has been changed. Then, we thought the idea of automating the generation of docs such that developers don't need to change the code in docs section while working towards mesheryctl. That's where we got to know that Cobra library (the library for CLI apps made using golang) has a feature to make doc pages automatically. So we decided to incorporate that feature into mesheryctl docs page as well! After making several changes and a PR, I was finally able to introduce the feature in the docs site!
+
+```
+var startCmd = &cobra.Command {
+ Use: "start",
+ Short: "Start Meshery",
+ Long: `Start Meshery and each of its service mesh components.`,
+ Args: cobra.NoArgs,
+ Example: `
+// Start meshery
+mesheryctl system start
+// To create a new context for in-cluster Kubernetes deployments and set the new context as your current-context
+mesheryctl system context create k8s -p kubernetes -s
+// (optional) skip checking for new updates available in Meshery.
+mesheryctl system start --skip-update
+// Reset Meshery's configuration file to default settings.
+mesheryctl system start --reset
+// Silently create Meshery's configuration file with default settings
+mesheryctl system start --yes
+.....
+}
+ `,
+```
+
+
Using this information provided above in each golang file, the markdown page is generated using Cobra CLI library and thus reducing the workload on the developer by automating via GitHub Actions.
+
+
This is so far on how the mesheryctl command reference is evolved for now. And I hope that it'll continue to evolve in the field of documentation to serve the users to use Meshery in best way possible.
As a contributor, each of us is always striving hard in the ocean to open more and more pull-requests, but being a contributor just doesn't mean only raising PRs, it also means reviewing other PRs, pointing out mistakes, helping others in improving the code-quality/code-reusability/code-readability, helping in finding missing edge-cases that haven't been tackled yet, giving your opinions, writing LGTM, CITY helps nothing but just improving the confidence and engagement of the PR author.
-
So put on your Quality Tester hats because here I'll talk about how to test the PRs with the label component/mesheryctl i.e. pull-requests related to mesheryctl
-
Okay before we start, I'll like to tell you about GitHub CLI, it helps you checkout PRs very easily in your local system.
-
-
The very first step is to review the PR, suggest changes if you think of any, ask queries, help the author to improve the code quality/readability/reusability, ask questions because asking helps you learn asking more better questions next time.
-
-
PR authors either attach a video showcasing expected behavior or add written instructions about their fix under User Acceptance Behavior
-
-
Now it's the time to checkout PR in your local system, we can check out any PR like this
You can check if you're into the same branch as the PR author with
-
git branch
-
-
-
Well, if we're testing a PR related to mesheryctl, we need to build the binary from the same branch. change your directory to mesheryctl folder and run
-
make
-
-
This will create a mesheryctl binary according to your OS in the same directory
-
-
Now it's time to test out this newly built binary according to what's been tackled in the PR and related issues. For e.g. system start has some new functionality, make sure you followed the pull-request/linked-issue instruction for env setup, as sometimes fix/features are tackling an issue with a specific type of environment.
-
-
-
./mesheryctl system start
-
-
the ./ helps us in using the newly built cli-binary present in the current directory which we built in 5th step
-
-
make sure we have a similar experience as mentioned in the Video or the instructions added to the PR. but the wait is it okay to give green flags to the PR? not yet tbh. We as a tester should turn a little evil and think of the relevant situations/environments which might not have been tackled but should be(basically we're trying to break the new feature/fix)
-
After spending a good amount of time testing the new behaviors, old standard behaviors, new test cases, few edge cases. We can provide new insights to the PR author about the behavior in your system, depending on our experience we can ask the PR author to address our new queries, or we can appreciate the work, or give green flags to the PR.
-
-
Wow, that was a ton of work there. well being a Tester is tough but very important before we merge pull requests. Every PR should be marked green with end-to-end testing before merging, we as a project are using GH Workflows to perform standard golang-testing but manual end-to-end testing completely removes margins of error.
As a contributor, each of us is always striving hard in the ocean to open more and more pull-requests, but being a contributor just doesn't mean only raising PRs, it also means reviewing other PRs, pointing out mistakes, helping others in improving the code-quality/code-reusability/code-readability, helping in finding missing edge-cases that haven't been tackled yet, giving your opinions, writing LGTM, CITY helps nothing but just improving the confidence and engagement of the PR author.
+
So put on your Quality Tester hats because here I'll talk about how to test the PRs with the label component/mesheryctl i.e. pull-requests related to mesheryctl
+
Okay before we start, I'll like to tell you about GitHub CLI, it helps you checkout PRs very easily in your local system.
+
+
The very first step is to review the PR, suggest changes if you think of any, ask queries, help the author to improve the code quality/readability/reusability, ask questions because asking helps you learn asking more better questions next time.
+
PR authors either attach a video showcasing expected behavior or add written instructions about their fix under User Acceptance Behavior
+
+
Now it's the time to checkout PR in your local system, we can check out any PR like this
You can check if you're into the same branch as the PR author with
+
git branch
+
+
+
Well, if we're testing a PR related to mesheryctl, we need to build the binary from the same branch. change your directory to mesheryctl folder and run
+
make
+
This will create a mesheryctl binary according to your OS in the same directory
+
+
Now it's time to test out this newly built binary according to what's been tackled in the PR and related issues. For e.g. system start has some new functionality, make sure you followed the pull-request/linked-issue instruction for env setup, as sometimes fix/features are tackling an issue with a specific type of environment.
+
+
./mesheryctl system start
+
the ./ helps us in using the newly built cli-binary present in the current directory which we built in 5th step
+
+
make sure we have a similar experience as mentioned in the Video or the instructions added to the PR. but the wait is it okay to give green flags to the PR? not yet tbh. We as a tester should turn a little evil and think of the relevant situations/environments which might not have been tackled but should be(basically we're trying to break the new feature/fix)
+
After spending a good amount of time testing the new behaviors, old standard behaviors, new test cases, few edge cases. We can provide new insights to the PR author about the behavior in your system, depending on our experience we can ask the PR author to address our new queries, or we can appreciate the work, or give green flags to the PR.
+
+
Wow, that was a ton of work there. well being a Tester is tough but very important before we merge pull requests. Every PR should be marked green with end-to-end testing before merging, we as a project are using GH Workflows to perform standard golang-testing but manual end-to-end testing completely removes margins of error.
+
+
diff --git a/src/collections/blog/2022/2022-07-06-aaditya-gsoc-blogpost/index.mdx b/src/collections/blog/2022/2022-07-06-aaditya-gsoc-blogpost/index.mdx
index ef07d3865cf0..ccc749bac707 100644
--- a/src/collections/blog/2022/2022-07-06-aaditya-gsoc-blogpost/index.mdx
+++ b/src/collections/blog/2022/2022-07-06-aaditya-gsoc-blogpost/index.mdx
@@ -1,55 +1,55 @@
----
-title: "My Journey as a Contributor to GSoC Intern at Layer5"
-subtitle: "Nothing but a magical experience"
-date: 2022-07-06 08:00:00 -0630
-author: Aaditya Narayan Subedy
-thumbnail: ./aaditya-subedy-layer5-intern.webp
-darkthumbnail: ./aaditya-subedy-layer5-intern.webp
-category: Programs
-description: "Aaditya Narayan Subedy's journey from a Contributor at Layer5 to getting an GSoC internship at Layer5"
-tags:
- - Programs
- - GSoC
- - Internship
-type: Blog
-published: true
----
-import { Link } from "gatsby";
-import { BlogWrapper } from "../../Blog.style.js";
-import aadityaFirstPr from "./aaditya-first-pr.webp"
-import aadityaPresenting from "./aaditya-presenting.webp"
-
-
-
-
-### Early Interest in Coding
-I had a strong interest in computers growing up. I used to find it fascinating how computer programs operate because they have such a tremendous impact on their users. This has always motivated me to work in the field of computers.
-
-As I grew up, I was introduced to a broad spectrum of coding languages that enabled us to make the software that we used on the computer. These languages piqued my interest even more. I started exploring and made projects. The more I understood them, the more interesting they got. Slowly I realized that I don’t want to make projects that satisfy just my needs. I want to build something that will be on the internet and will be used by people around the world. With this goal in my mind, I started exploring and hit a gemstone that is open source. I would be working on real-world programming solutions that will be used by people all around the world. This helped me to get started and got me excited about contributing to open source projects.
-
-### First PR at Layer5
-I still remember the first issue I worked on for Layer5 was the auto labeler on a pull request. I spotted a [good first issue](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+org%3Alayer5io+org%3Ameshery+org%3Aservice-mesh-performance+org%3Aservice-mesh-patterns+label%3A%22good+first+issue%22+) tag and expressed interest in working on it despite not knowing what the task was. The issue required knowledge of GitHub Actions, something I was unaware of at the time. After getting the issue assigned, I started researching what GitHub Actions were. I found out that these actions helped automate workflows to build, test, and deploy software. After getting the basics down, I checked if there were any existing GitHub Actions for the auto labeling of the PR. To my surprise, there were a couple of them.
-
-So before actually making a PR, I experimented with the actions extensively in my private repo. I remember making about 20-25 PR in my private repo to get the auto labeler working fine. After verifying that I got the desired results, I made a PR. I also got to discuss my approach in the [Meshery Development Call](https://layer5.io/community/calendar). I was so nervous at that time since that was the first meeting I attended where I had to make people understand what I did and the strategies I used. I was quite thrilled when my code got merged. I was enthralled to see that my code was working and being useful to the community. This motivated me to make more and more contributions.
-
-
-
-### A Journey Never to forget
-
-My Layer5 journey began with this small issue. I gradually started learning more about the projects and made some impactful contributions. I started to engage in the community more prominently. With the help of these contributions, I learned new technologies and techniques. Contributing to the codebase gave me so much exposure to React.js, which would not have been possible if I had done it on my own. I took up issues that used React.js and started solving them, and in no time, I was comfortable with it. I am thankful that I didn’t wait for me to learn more about react and then start contributing. I have always applied this principle, learning more by doing actual stuff rather than sitting there and getting stuck in the tutorial loop.
-
-Another new technology I discovered was Jekyll, a static site generator. I was unfamiliar with this technology as well. I started contributing to issues involving Jekyll and slowly understood the basics and how the language works. I was very happy that I was able to make the [compatibility matrix](https://docs.meshery.io/project/compatibility-matrix), using Jekyll. Even my project for GSoC is written in Jekyll. So, going from not knowing what Jekyll is, to making some big changes, did make me happy.
-
-The community also helped me boost my confidence. The weekly meetings are responsible for this. The way the meetings required me to explain my fixes and give updates regarding the issues I was working on, helped me get vocal and comfortable with talking to various people.
-
-
-
-I am excited to be accepted as a Google Summer of Code Intern for this Summer of 2022. I am looking forward to contributing more and making an impact here. The project assigned to me is to create a dashboard on SMP Website. Results from the [CNCF Cluster labs](https://github.com/layer5io/meshery-smp-action/actions) will be displayed here graphically. I wish to learn more about cloud native technologies and make contributions on the backend too. I also want to state that this will not be the end. I will be engaged with this community as long as I can and will try to give back as much as I can.
-
-### Appreciation for the Community
-
-Finally, I would like to thank the Layer5 Community for always being so supportive whenever I needed it. I took away a very significant lesson from this experience, there is always something to learn, and there is no harm in asking questions if you don't know the answer. It’s kinda hard to find such a welcoming community. There was not a day that I felt completely lost here, and that is what I adore about this community.
-
-Keep Meshing. Thank you.
-
-
+---
+title: "My Journey as a Contributor to GSoC Intern at Layer5"
+subtitle: "Nothing but a magical experience"
+date: 2022-07-06 08:00:00 -0630
+author: Aaditya Narayan Subedy
+thumbnail: ./aaditya-subedy-layer5-intern.webp
+darkthumbnail: ./aaditya-subedy-layer5-intern.webp
+category: Programs
+description: "Aaditya Narayan Subedy's journey from a Contributor at Layer5 to getting an GSoC internship at Layer5"
+tags:
+ - Programs
+ - GSoC
+ - Internship
+type: Blog
+published: true
+---
+
+
+import aadityaFirstPr from "./aaditya-first-pr.webp"
+import aadityaPresenting from "./aaditya-presenting.webp"
+
+
+
+
+### Early Interest in Coding
+I had a strong interest in computers growing up. I used to find it fascinating how computer programs operate because they have such a tremendous impact on their users. This has always motivated me to work in the field of computers.
+
+As I grew up, I was introduced to a broad spectrum of coding languages that enabled us to make the software that we used on the computer. These languages piqued my interest even more. I started exploring and made projects. The more I understood them, the more interesting they got. Slowly I realized that I don’t want to make projects that satisfy just my needs. I want to build something that will be on the internet and will be used by people around the world. With this goal in my mind, I started exploring and hit a gemstone that is open source. I would be working on real-world programming solutions that will be used by people all around the world. This helped me to get started and got me excited about contributing to open source projects.
+
+### First PR at Layer5
+I still remember the first issue I worked on for Layer5 was the auto labeler on a pull request. I spotted a [good first issue](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+org%3Alayer5io+org%3Ameshery+org%3Aservice-mesh-performance+org%3Aservice-mesh-patterns+label%3A%22good+first+issue%22+) tag and expressed interest in working on it despite not knowing what the task was. The issue required knowledge of GitHub Actions, something I was unaware of at the time. After getting the issue assigned, I started researching what GitHub Actions were. I found out that these actions helped automate workflows to build, test, and deploy software. After getting the basics down, I checked if there were any existing GitHub Actions for the auto labeling of the PR. To my surprise, there were a couple of them.
+
+So before actually making a PR, I experimented with the actions extensively in my private repo. I remember making about 20-25 PR in my private repo to get the auto labeler working fine. After verifying that I got the desired results, I made a PR. I also got to discuss my approach in the [Meshery Development Call](https://layer5.io/community/calendar). I was so nervous at that time since that was the first meeting I attended where I had to make people understand what I did and the strategies I used. I was quite thrilled when my code got merged. I was enthralled to see that my code was working and being useful to the community. This motivated me to make more and more contributions.
+
+
+
+### A Journey Never to forget
+
+My Layer5 journey began with this small issue. I gradually started learning more about the projects and made some impactful contributions. I started to engage in the community more prominently. With the help of these contributions, I learned new technologies and techniques. Contributing to the codebase gave me so much exposure to React.js, which would not have been possible if I had done it on my own. I took up issues that used React.js and started solving them, and in no time, I was comfortable with it. I am thankful that I didn’t wait for me to learn more about react and then start contributing. I have always applied this principle, learning more by doing actual stuff rather than sitting there and getting stuck in the tutorial loop.
+
+Another new technology I discovered was Jekyll, a static site generator. I was unfamiliar with this technology as well. I started contributing to issues involving Jekyll and slowly understood the basics and how the language works. I was very happy that I was able to make the [compatibility matrix](https://docs.meshery.io/project/compatibility-matrix), using Jekyll. Even my project for GSoC is written in Jekyll. So, going from not knowing what Jekyll is, to making some big changes, did make me happy.
+
+The community also helped me boost my confidence. The weekly meetings are responsible for this. The way the meetings required me to explain my fixes and give updates regarding the issues I was working on, helped me get vocal and comfortable with talking to various people.
+
+
+
+I am excited to be accepted as a Google Summer of Code Intern for this Summer of 2022. I am looking forward to contributing more and making an impact here. The project assigned to me is to create a dashboard on SMP Website. Results from the [CNCF Cluster labs](https://github.com/layer5io/meshery-smp-action/actions) will be displayed here graphically. I wish to learn more about cloud native technologies and make contributions on the backend too. I also want to state that this will not be the end. I will be engaged with this community as long as I can and will try to give back as much as I can.
+
+### Appreciation for the Community
+
+Finally, I would like to thank the Layer5 Community for always being so supportive whenever I needed it. I took away a very significant lesson from this experience, there is always something to learn, and there is no harm in asking questions if you don't know the answer. It’s kinda hard to find such a welcoming community. There was not a day that I felt completely lost here, and that is what I adore about this community.
+
+Keep Meshing. Thank you.
+
+
diff --git a/src/collections/blog/2022/2022-07-07-deploy-meshery-on-aks/index.mdx b/src/collections/blog/2022/2022-07-07-deploy-meshery-on-aks/index.mdx
index 76aa27dcdb3b..134a103db165 100644
--- a/src/collections/blog/2022/2022-07-07-deploy-meshery-on-aks/index.mdx
+++ b/src/collections/blog/2022/2022-07-07-deploy-meshery-on-aks/index.mdx
@@ -1,76 +1,76 @@
----
-title: "How to deploy Meshery on AKS"
-date: 2022-07-21 08:00:00 -0630
-author: Srinivas Karnati
-category: "Meshery"
-description: "How to deploy Meshery on Azure Kubernetes service(AKS)."
-tags:
- - Meshery
- - Kubernetes
-thumbnail: ./Meshery-on-AKS.webp
-darkthumbnail: ./Meshery-on-AKS.webp
-type: Blog
-published: true
-resource: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import mesheryui from "./mesheryui.webp";
-
-
-
-
-
Meshery's goal is to make the operation of cloud native infrastructure and the service mesh layer of cloud simplified. Originally created by Layer5, Meshery is an open source project with hundreds of contributors world-wide and is actively maintained by engineers from Red Hat, VMware, Intel, Layer5 and others.
-
-
Setup and run Meshery on AKS
-
The following instructions expects you to have an active Azure subscription, and Azure CLI installed on your system.
-
Spin up the AKS Cluster
-
Create the resource group (a logical group where all our resources will be deployed). The following command creates a resource group named MesheryGroup in southindia location.
-
-az group create --name MesheryGroup --location southindia
-
-
-
Create AKS cluster using az aks create. The following command creates aks cluster with a single node.
Meshery should now be running in your AKS cluster and the Meshery UI should be accessible at the specified endpoint you’ve exposed to. Navigate to the meshery service endpoint to log into Meshery.
-
-
-
-
From here, your Meshery deployment on AKS is ready to use. In order to login to Meshery, authenticate with your chosen provider from the list.
-
There are different ways to configure a Meshery on AKS. Join the community and share your deployment’s configuration on the discussion forum today!
-
-
-
+---
+title: "How to deploy Meshery on AKS"
+date: 2022-07-21 08:00:00 -0630
+author: Srinivas Karnati
+category: "Meshery"
+description: "How to deploy Meshery on Azure Kubernetes service(AKS)."
+tags:
+ - Meshery
+ - Kubernetes
+thumbnail: ./Meshery-on-AKS.webp
+darkthumbnail: ./Meshery-on-AKS.webp
+type: Blog
+published: true
+resource: true
+---
+
+
+import mesheryui from "./mesheryui.webp";
+
+
+
+
+
Meshery's goal is to make the operation of cloud native infrastructure and the service mesh layer of cloud simplified. Originally created by Layer5, Meshery is an open source project with hundreds of contributors world-wide and is actively maintained by engineers from Red Hat, VMware, Intel, Layer5 and others.
+
+
Setup and run Meshery on AKS
+
The following instructions expects you to have an active Azure subscription, and Azure CLI installed on your system.
+
Spin up the AKS Cluster
+
Create the resource group (a logical group where all our resources will be deployed). The following command creates a resource group named MesheryGroup in southindia location.
+
+az group create --name MesheryGroup --location southindia
+
+
+
Create AKS cluster using az aks create. The following command creates aks cluster with a single node.
Meshery should now be running in your AKS cluster and the Meshery UI should be accessible at the specified endpoint you’ve exposed to. Navigate to the meshery service endpoint to log into Meshery.
+
+
+
+
From here, your Meshery deployment on AKS is ready to use. In order to login to Meshery, authenticate with your chosen provider from the list.
+
There are different ways to configure a Meshery on AKS. Join the community and share your deployment’s configuration on the discussion forum today!
+
+
+
diff --git a/src/collections/blog/2022/2022-07-28-managing-multiple-clusters-with-meshery/index.mdx b/src/collections/blog/2022/2022-07-28-managing-multiple-clusters-with-meshery/index.mdx
index 3e0fbe7cb9ae..1f45e0146fa6 100644
--- a/src/collections/blog/2022/2022-07-28-managing-multiple-clusters-with-meshery/index.mdx
+++ b/src/collections/blog/2022/2022-07-28-managing-multiple-clusters-with-meshery/index.mdx
@@ -1,110 +1,110 @@
----
-title: Multi-Cluster Kubernetes Management with Meshery
-subtitle: Wrangling your services one cluster at-a-time
-date: 2022-07-28 08:00:00 -0630
-author: Ashish Tiwari
-description: "Manage all of your Kubernetes clusters with the cloud native management plane, Meshery. Learn how Meshery makes connecting, discovering, and configuring multiple clusters a breeze."
-thumbnail: ./multi-cluster-kubernetes-management-with-meshery.webp
-darkthumbnail: ./multi-cluster-kubernetes-management-with-meshery.webp
-category: "Meshery"
-tags:
- - Meshery
- - Multi-cluster
- - Kubernetes
-type: Blog
-featured: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import Switcher from "./context-switcher.webp";
-import Deploy from "./deploy-modal.webp";
-import Cluster2 from "./meshmap-cluster2.webp";
-import Cluster1 from "./meshmap-cluster1.webp";
-import Settings from "./settings.webp";
-import Cluster from "./cluster-mgmt.webp";
-import Flush from "./flush-meshsync.webp";
-import CoreArch from "./meshery-core-architecture.webp";
-import { Link } from "gatsby";
-
-
-
-
-
- From multi-mesh to now multi-cluster, Meshery is
- continuously expanding its capability to give developers, operators, and
- security engineers more control over their infrastructure. In this post,
- we'll take a look behind the scenes at how each component in Meshery's
- architecture plays a role in the management of many Kubernetes clusters.
-
-
-
-## Philosophy behind Meshery's multi-cluster management approach
-
-While designing Meshery for the world of many clouds, and many Kubernetes clusters, much care has been taken to ensure that Meshery is an extensible management platform, ready for handling new types of infrastructure and new use cases rapidly through its plugin model. Under the hood, Meshery Server acts as a delegator of operations by figuring out which Meshery Adapter registered its capability against the given operation. The operation is then sent to that given component (like one of Meshery’s adapters,e.g. Istio adapter) via a gRPC call. When the operation involves a Kubernetes cluster(s), the kubeconfig(s) is sent as a parameter to the RPCs. It is then the job of the handling adapter to respect that and perform the operation across the passed clusters from kubeconfigs as needed. The operations not requiring a kubeconfig are managed through the same RPC, with the only difference being that the handling component would ignore the `kubeconfigs` field altogether making the system work not just for Kubernetes, but for other cloud native use cases. This approach of reusing the same RPC for different types of requests is pretty common and sometimes debatable with the other approach of being strict with the RPCs. This is what makes Meshery completely pluggable and extensible.
-
-## Using multi cluster with Meshery
-
-From a client's perspective, there are two uses of the multi context feature in general. While deploying a MeshMap design or performing any other operation on their cluster(s), selecting any number of Kubernetes contexts will allow them to uniformly and parallely perform the operation across the clusters. And while visualizing the state of their cluster(s), the same context switcher will allow them to filter across the clusters whose view they want to see.
-
-All cluster specific operations are now applied over a number of clusters uniformly. So if you have 10 clusters to manage and 8 of those start with the exact same set of pods, deployments, services, etc then Meshery can help you to apply these operations quickly and easily.
-
-It is as simple as selecting the specific cluster(s) from the Kubernetes context switcher in the navbar, and then applying whatever operation you wanted to, whether that be deploying a sample app, a Prometheus daemonset, or a MeshMap design.
-
-
-
-
-
-Just before applying the operation, you will be prompted with a confirmation modal which will provide the information about which cluster(s) that operation will be performed against. As the User interface improves, this same modal will also convey more useful information about the operation they are going to perform.
-
-
-
-
-
-
-
-### Using MeshMap visualizer
-
-You can switch between views of your cluster in visualizer mode while using MeshMap.
-
-
-
-
-
-
-
-
-### Managing Meshery on multiple clusters
-
-Users can perform cluster related operations from the settings page like adding more clusters, removing data from existing clusters and removing existing clusters.
-
-
-
-Meshery also deploys Meshery operator across the cluster it’s about to manage. This operator manages the lifecycle of a Meshery broker and MeshSync. MeshSync pumps the blood into Meshery’s core, in other words, it is responsible for watching all different types of resources by establishing a watch stream over each of them. MeshSync then pumps that data into the NATS server, of which Meshery server itself is a client. From there, Meshery server gets all the relevant data related to activities in the cluster.
-
-By default, Meshery wants to be as much aware about your infrastructure as possible to provide value so it deploys its operator across each detected cluster. But you can fine tune this configuration by going over each one of them from the table as shown.
-
-
-
-If you disconnect your cluster and do not want to persist the data from that cluster then you can perform a fine-grained deletion by deleting all MeshSync data (which are the Kubernetes objects) for that specific cluster.
-
-
-## Future of multi-cluster
-
-Meshery as an extension point to your infrastructure provides out-of-the-box value by adding components which can be Kubernetes specific, service mesh specific or custom components to add new functionality. We can now add multi-cluster specific components to provide more abstraction. This model can be used along with Meshery’s multi-mesh capabilities to give an overall multi-mesh multi-cluster experience to the user. For instance, your Istio service mesh spanning across multiple clusters can be abstracted and managed by Meshery using custom components such as VirtualGateway and VirtualDestinationRules. In this case, Meshery’s Istio adapter will handle the logic of converting a VirtualGateway into gateways across the clusters. This abstraction provides high value by powering the service mesh to span across the clusters while the Ops team can configure the mesh with minimal effort.
-
-Just like the example above, many such Meshery extension points are in Meshery to add logic into and add useful functionality. And as more of such extension points are added, Meshery will continue to give more and more power to your cloud native infrastructure.
-
-
+---
+title: Multi-Cluster Kubernetes Management with Meshery
+subtitle: Wrangling your services one cluster at-a-time
+date: 2022-07-28 08:00:00 -0630
+author: Ashish Tiwari
+description: "Manage all of your Kubernetes clusters with the cloud native management plane, Meshery. Learn how Meshery makes connecting, discovering, and configuring multiple clusters a breeze."
+thumbnail: ./multi-cluster-kubernetes-management-with-meshery.webp
+darkthumbnail: ./multi-cluster-kubernetes-management-with-meshery.webp
+category: "Meshery"
+tags:
+ - Meshery
+ - Multi-cluster
+ - Kubernetes
+type: Blog
+featured: true
+published: true
+---
+
+
+import Switcher from "./context-switcher.webp";
+import Deploy from "./deploy-modal.webp";
+import Cluster2 from "./meshmap-cluster2.webp";
+import Cluster1 from "./meshmap-cluster1.webp";
+import Settings from "./settings.webp";
+import Cluster from "./cluster-mgmt.webp";
+import Flush from "./flush-meshsync.webp";
+import CoreArch from "./meshery-core-architecture.webp";
+
+
+
+
+
+
+ From multi-mesh to now multi-cluster, Meshery is
+ continuously expanding its capability to give developers, operators, and
+ security engineers more control over their infrastructure. In this post,
+ we'll take a look behind the scenes at how each component in Meshery's
+ architecture plays a role in the management of many Kubernetes clusters.
+
+
+
+## Philosophy behind Meshery's multi-cluster management approach
+
+While designing Meshery for the world of many clouds, and many Kubernetes clusters, much care has been taken to ensure that Meshery is an extensible management platform, ready for handling new types of infrastructure and new use cases rapidly through its plugin model. Under the hood, Meshery Server acts as a delegator of operations by figuring out which Meshery Adapter registered its capability against the given operation. The operation is then sent to that given component (like one of Meshery’s adapters,e.g. Istio adapter) via a gRPC call. When the operation involves a Kubernetes cluster(s), the kubeconfig(s) is sent as a parameter to the RPCs. It is then the job of the handling adapter to respect that and perform the operation across the passed clusters from kubeconfigs as needed. The operations not requiring a kubeconfig are managed through the same RPC, with the only difference being that the handling component would ignore the `kubeconfigs` field altogether making the system work not just for Kubernetes, but for other cloud native use cases. This approach of reusing the same RPC for different types of requests is pretty common and sometimes debatable with the other approach of being strict with the RPCs. This is what makes Meshery completely pluggable and extensible.
+
+## Using multi cluster with Meshery
+
+From a client's perspective, there are two uses of the multi context feature in general. While deploying a MeshMap design or performing any other operation on their cluster(s), selecting any number of Kubernetes contexts will allow them to uniformly and parallely perform the operation across the clusters. And while visualizing the state of their cluster(s), the same context switcher will allow them to filter across the clusters whose view they want to see.
+
+All cluster specific operations are now applied over a number of clusters uniformly. So if you have 10 clusters to manage and 8 of those start with the exact same set of pods, deployments, services, etc then Meshery can help you to apply these operations quickly and easily.
+
+It is as simple as selecting the specific cluster(s) from the Kubernetes context switcher in the navbar, and then applying whatever operation you wanted to, whether that be deploying a sample app, a Prometheus daemonset, or a MeshMap design.
+
+
+
+
+
+Just before applying the operation, you will be prompted with a confirmation modal which will provide the information about which cluster(s) that operation will be performed against. As the User interface improves, this same modal will also convey more useful information about the operation they are going to perform.
+
+
+
+
+
+
+
+### Using MeshMap visualizer
+
+You can switch between views of your cluster in visualizer mode while using MeshMap.
+
+
+
+
+
+
+
+
+### Managing Meshery on multiple clusters
+
+Users can perform cluster related operations from the settings page like adding more clusters, removing data from existing clusters and removing existing clusters.
+
+
+
+Meshery also deploys Meshery operator across the cluster it’s about to manage. This operator manages the lifecycle of a Meshery broker and MeshSync. MeshSync pumps the blood into Meshery’s core, in other words, it is responsible for watching all different types of resources by establishing a watch stream over each of them. MeshSync then pumps that data into the NATS server, of which Meshery server itself is a client. From there, Meshery server gets all the relevant data related to activities in the cluster.
+
+By default, Meshery wants to be as much aware about your infrastructure as possible to provide value so it deploys its operator across each detected cluster. But you can fine tune this configuration by going over each one of them from the table as shown.
+
+
+
+If you disconnect your cluster and do not want to persist the data from that cluster then you can perform a fine-grained deletion by deleting all MeshSync data (which are the Kubernetes objects) for that specific cluster.
+
+
+## Future of multi-cluster
+
+Meshery as an extension point to your infrastructure provides out-of-the-box value by adding components which can be Kubernetes specific, service mesh specific or custom components to add new functionality. We can now add multi-cluster specific components to provide more abstraction. This model can be used along with Meshery’s multi-mesh capabilities to give an overall multi-mesh multi-cluster experience to the user. For instance, your Istio service mesh spanning across multiple clusters can be abstracted and managed by Meshery using custom components such as VirtualGateway and VirtualDestinationRules. In this case, Meshery’s Istio adapter will handle the logic of converting a VirtualGateway into gateways across the clusters. This abstraction provides high value by powering the service mesh to span across the clusters while the Ops team can configure the mesh with minimal effort.
+
+Just like the example above, many such Meshery extension points are in Meshery to add logic into and add useful functionality. And as more of such extension points are added, Meshery will continue to give more and more power to your cloud native infrastructure.
+
+
diff --git a/src/collections/blog/2022/2022-10-19-kubeconna2022/index.mdx b/src/collections/blog/2022/2022-10-19-kubeconna2022/index.mdx
index 2713019e9659..540c6d3de7b6 100644
--- a/src/collections/blog/2022/2022-10-19-kubeconna2022/index.mdx
+++ b/src/collections/blog/2022/2022-10-19-kubeconna2022/index.mdx
@@ -24,7 +24,7 @@ import Button from "../../../../reusecore/Button";
Detroit welcomes the largest open-cloud and container-based developer events and workshops in the world. The event offers tutorials, keynotes, and networking opportunities across five days.
-
+
As a longstanding CNCF member, Layer5 has donated two of its open source projects to the CNCF: Meshery and Service Mesh Performance. We're hosting project office hours where you can learn more about each of the projects, and meet the project maintainers.
@@ -48,7 +48,7 @@ Join us as we host project office hours. Don't be shy with your questions! Proje
Dynamic Management UIs
-
+
@@ -57,7 +57,7 @@ Join us as we host project office hours. Don't be shy with your questions! Proje
October 27, 2022
: Service Mesh Performance is a CNCF-hosted project that has received support from Layer5, Intel, RedHat, and HashiCorp. By utilizing SMP, MeshMark offers a global performance index to compare the effectiveness of your mesh deployment to those in other organizations setups.
-
+
@@ -69,7 +69,7 @@ Join us as we host project office hours. Don't be shy with your questions! Proje
From fundamental Layer 3 connectivity to the newest in service mesh, the third session will cover the big picture of Cloud Native Networking in the CNCF and how to put it all in a context you can utilize.
-
+
@@ -92,8 +92,8 @@ Join us as we host project office hours. Don't be shy with your questions! Proje
Resumé Writing Workshop
- Attendees are encouraged to join this unique DEI event, which will feature a resume writing class, mingling, networking, and refreshments. The event will take place on October 25 from 4:00 PM to 6:00 PM and is sponsored by Visit Detroit. Scholarship recipients and regional groups that support diversity, equality, and inclusion in technology have received special invitations.
+ Attendees are encouraged to join this unique DEI event, which will feature a resume writing className, mingling, networking, and refreshments. The event will take place on October 25 from 4:00 PM to 6:00 PM and is sponsored by Visit Detroit. Scholarship recipients and regional groups that support diversity, equality, and inclusion in technology have received special invitations.
-Be sure to join Layer5 at KubeCon NA 2022 and find us at other events, too. Learn more about each of our open source projects and try one (or all of them) today!
+Be sure to join Layer5 at KubeCon NA 2022 and find us at other events, too. Learn more about each of our open source projects and try one (or all of them) today!
diff --git a/src/collections/blog/2022/2022-12-05-structured-logging-with-klog/index.mdx b/src/collections/blog/2022/2022-12-05-structured-logging-with-klog/index.mdx
index 1dd8c7a6dda7..b88e5786e6f0 100644
--- a/src/collections/blog/2022/2022-12-05-structured-logging-with-klog/index.mdx
+++ b/src/collections/blog/2022/2022-12-05-structured-logging-with-klog/index.mdx
@@ -1,80 +1,76 @@
----
-title: Structured logging in Kubernetes with Klog
-subtitle: Deprecating Klog flags in Kubernetes 1.26
-date: 2022-12-05 15:00:00 -0530
-author: Lee Calcote
-thumbnail: ./kubernetes-logs.webp
-darkthumbnail: ./kubernetes-logs-dark.webp
-description: "Structured logging in Kubernetes 1.26 with Klog"
-type: Blog
-category: Kubernetes
-tags:
- - Kubernetes
- - OpenTelemetry
-featured: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-
-
-
-
As a platform for developers and system administrators to easily deploy and manage applications in a distributed environment, Kubernetes clusters generate logs and lots of them. One of the key components of Kubernetes is its logging and instrumentation capabilities. The upcoming Kubernetes 1.26 release has a handful of noteworthy changes to its system component logger, klog.
-
-## Kubernetes System Log
-
-System component logs record events happening in K8s clusters. More than metrics or traces, logs are the telemetric signal often found to be most useful for debugging. You can configure K8s log verbosity to see more or less detail. Logs can be as coarse-grained as showing errors within a component, or as fine-grained as showing step-by-step traces of events (like HTTP access logs, pod state changes, controller actions, or scheduler decisions).
-
-## Klog
-
-[klog](https://github.com/kubernetes/klog) is a Kubernetes logging library that provides an API for developers and system administrators to instrument their applications for logging and tracing. klog generates log messages for the Kubernetes system components. It provides a comprehensive set of features, including log levels, structured logging and logging context.
-
-Kubernetes 1.23 introduced structured logging (in beta) in `klog`. Structured logging is a uniform structure in log messages allowing for programmatic extraction of information. Structured logs can be stored and processed with less effort and cost. The code which generates a log message determines whether it uses the traditional unstructured `klog` output or structured logging.
-
-As a dependency to structured logging (gated behind `StructuredLogging` feature gate), Kubernetes 1.24 introducted contextual logging (in alpha) in `klog`. Contextual logging builds on top of structured logging. It is primarily about how developers use logging calls: code based on that concept is more flexible and supports additional use cases which will be the topic of a future blog post.
-
-### Klog Deprecations in Kubernetes 1.26
-
-Kubernetes has recently announced that it intends to deprecate certain flags related to Klog in its components. This means that Klog-specific flags, such as `--klog-verbosity`, `--klog-vmodule` and `--klog-stderrthreshold` will no longer be supported. This is due to the fact that Klog has been largely superseded by the more comprehensive OpenTelemetry project, which provides a more complete solution for logging and instrumentation.
-
-The deprecation of Klog-specific flags is a positive step forward for Kubernetes as it moves to OpenTelemetry. This move will ensure that Kubernetes is using the industry-standard logging and instrumentation solution. It will also provide developers and system administrators with a more comprehensive, reliable and consistent experience when instrumenting their applications.
-A goal of this deprecation is one of unblocking development of alternative logging formats. Why does Kubnernetes need another logging format? One reason is performance. Klog performance is much worse than alternatives, for example 7-8x than JSON format:
-
-|logger |time [ns/op]|bytes[B/op]|allocations[alloc/op]|
-|-----------------------|------------|-----------|---------------------|
-|Text Infof |2252 |248 |3 |
-|Text InfoS |2455 |280 |3 |
-|JSON Infof |1406 |19 |1 |
-|JSON InfoS |319 |67 |1 |
-
-Proof of concept implementation of new logging formats were completed to assess the potentional gains of using an alternative format. Results measured on 30s benchmark for passing 2 arguments to format function.
-
-
-
Tip: Logger Performance Comparison
-
-Interestingly, Klog isn't the fastest logger in the West, but Uber's open source project [zap ](https://github.com/uber-go/zap) appears to hold that title instead. The following performance test benchmark is an examle of one of a number of scenarios in which loggers can be performance analyzed.
-
-
-
-
-Output will always be written to stderr, regardless of the output format. Output redirection is expected to be handled by the component which invokes a Kubernetes component. This can be a POSIX shell or a tool like systemd.
-
-The deprecation of Klog-specific flags is part of a larger effort to transition Kubernetes to a more modern and comprehensive logging and instrumentation solution. This will provide Kubernetes users with a more reliable, secure and consistent experience when instrumenting and monitoring their applications.
-
-Kubernetes will continue to provide support for Klog-specific flags for the foreseeable future. However, it is recommended that developers and system administrators begin transitioning their applications to the OpenTelemetry framework. This will ensure that their applications are using the industry-standard solution for logging and instrumentation.
-
-Overall, the deprecation of Klog-specific flags is a positive step forward for Kubernetes. It will ensure that Kubernetes users have access to the most reliable and comprehensive solution for logging and instrumentation. It will also help ensure that Kubernetes is using the industry-standard solution and will provide developers and system administrators with a more reliable and consistent experience when instrumenting their applications.
+---
+title: Structured logging in Kubernetes with Klog
+subtitle: Deprecating Klog flags in Kubernetes 1.26
+date: 2022-12-05 15:00:00 -0530
+author: Lee Calcote
+thumbnail: ./kubernetes-logs.webp
+darkthumbnail: ./kubernetes-logs-dark.webp
+description: "Structured logging in Kubernetes 1.26 with Klog"
+type: Blog
+category: Kubernetes
+tags:
+ - Kubernetes
+ - OpenTelemetry
+featured: false
+published: true
+---
+
+
+
+
As a platform for developers and system administrators to easily deploy and manage applications in a distributed environment, Kubernetes clusters generate logs and lots of them. One of the key components of Kubernetes is its logging and instrumentation capabilities. The upcoming Kubernetes 1.26 release has a handful of noteworthy changes to its system component logger, klog.
+
+## Kubernetes System Log
+
+System component logs record events happening in K8s clusters. More than metrics or traces, logs are the telemetric signal often found to be most useful for debugging. You can configure K8s log verbosity to see more or less detail. Logs can be as coarse-grained as showing errors within a component, or as fine-grained as showing step-by-step traces of events (like HTTP access logs, pod state changes, controller actions, or scheduler decisions).
+
+## Klog
+
+[klog](https://github.com/kubernetes/klog) is a Kubernetes logging library that provides an API for developers and system administrators to instrument their applications for logging and tracing. klog generates log messages for the Kubernetes system components. It provides a comprehensive set of features, including log levels, structured logging and logging context.
+
+Kubernetes 1.23 introduced structured logging (in beta) in `klog`. Structured logging is a uniform structure in log messages allowing for programmatic extraction of information. Structured logs can be stored and processed with less effort and cost. The code which generates a log message determines whether it uses the traditional unstructured `klog` output or structured logging.
+
+As a dependency to structured logging (gated behind `StructuredLogging` feature gate), Kubernetes 1.24 introducted contextual logging (in alpha) in `klog`. Contextual logging builds on top of structured logging. It is primarily about how developers use logging calls: code based on that concept is more flexible and supports additional use cases which will be the topic of a future blog post.
+
+### Klog Deprecations in Kubernetes 1.26
+
+Kubernetes has recently announced that it intends to deprecate certain flags related to Klog in its components. This means that Klog-specific flags, such as `--klog-verbosity`, `--klog-vmodule` and `--klog-stderrthreshold` will no longer be supported. This is due to the fact that Klog has been largely superseded by the more comprehensive OpenTelemetry project, which provides a more complete solution for logging and instrumentation.
+
+The deprecation of Klog-specific flags is a positive step forward for Kubernetes as it moves to OpenTelemetry. This move will ensure that Kubernetes is using the industry-standard logging and instrumentation solution. It will also provide developers and system administrators with a more comprehensive, reliable and consistent experience when instrumenting their applications.
+A goal of this deprecation is one of unblocking development of alternative logging formats. Why does Kubnernetes need another logging format? One reason is performance. Klog performance is much worse than alternatives, for example 7-8x than JSON format:
+
+|logger |time [ns/op]|bytes[B/op]|allocations[alloc/op]|
+|-----------------------|------------|-----------|---------------------|
+|Text Infof |2252 |248 |3 |
+|Text InfoS |2455 |280 |3 |
+|JSON Infof |1406 |19 |1 |
+|JSON InfoS |319 |67 |1 |
+
+Proof of concept implementation of new logging formats were completed to assess the potentional gains of using an alternative format. Results measured on 30s benchmark for passing 2 arguments to format function.
+
+
+
Tip: Logger Performance Comparison
+
+Interestingly, Klog isn't the fastest logger in the West, but Uber's open source project [zap ](https://github.com/uber-go/zap) appears to hold that title instead. The following performance test benchmark is an examle of one of a number of scenarios in which loggers can be performance analyzed.
+
+
+
+Output will always be written to stderr, regardless of the output format. Output redirection is expected to be handled by the component which invokes a Kubernetes component. This can be a POSIX shell or a tool like systemd.
+
+The deprecation of Klog-specific flags is part of a larger effort to transition Kubernetes to a more modern and comprehensive logging and instrumentation solution. This will provide Kubernetes users with a more reliable, secure and consistent experience when instrumenting and monitoring their applications.
+
+Kubernetes will continue to provide support for Klog-specific flags for the foreseeable future. However, it is recommended that developers and system administrators begin transitioning their applications to the OpenTelemetry framework. This will ensure that their applications are using the industry-standard solution for logging and instrumentation.
+
+Overall, the deprecation of Klog-specific flags is a positive step forward for Kubernetes. It will ensure that Kubernetes users have access to the most reliable and comprehensive solution for logging and instrumentation. It will also help ensure that Kubernetes is using the industry-standard solution and will provide developers and system administrators with a more reliable and consistent experience when instrumenting their applications.
\ No newline at end of file
diff --git a/src/collections/blog/2022/2022-12-06-k8s-1.26-release/index.mdx b/src/collections/blog/2022/2022-12-06-k8s-1.26-release/index.mdx
index 2796a6f11011..787c95f21c01 100644
--- a/src/collections/blog/2022/2022-12-06-k8s-1.26-release/index.mdx
+++ b/src/collections/blog/2022/2022-12-06-k8s-1.26-release/index.mdx
@@ -1,135 +1,135 @@
----
-title: Kubernetes 1.26 Highlights, Features, and Deprecations
-subtitle:
-date: 2022-12-06 08:00:00 -0530
-author: Lee Calcote
-thumbnail: ./kubernetes-new.webp
-darkthumbnail: ./kubernetes-new-dark.webp
-description: "Release Notes: What changed in Kubernetes 1.26?"
-type: Blog
-category: Kubernetes
-tags:
- - Kubernetes
-featured: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-
-
-
-As the final Kubernetes release of 2022, Kubernetes 1.26 is an exciting new release of the popular container orchestration platform. It offers a number of new features and improvements that will help platform engineers and DevOps engineers manage their Kubernetes clusters more effectively. Here are some of the highlights of this release.
-
-
-
- As a longstanding CNCF member, Layer5 has donated two of its open source projects to the CNCF: Meshery and Service Mesh Performance. As an end-to-end, open-source, multi-cluster Kuberentes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
-
-
-
-While there are a number of enhancments tracked in this release (38), you need to be aware that there are also a number of features being deprecated (10) in 1.26. In this article, we will focus on some highlighted enhancements, important deprecations, and removals so that you can be confident before upgrading your clusters.
-
-We'll breakdown new K8s features by category, starting with networking.
-
-## Networking in Kubernetes 1.26
-
-### [Service Internal Traffic Policy](https://github.com/kubernetes/enhancements/issues/2086) [Stable]
-
-When requests are made to a Kubernetes service, they are randomly distributed to all available endpoints. The new enhancement enriches the API of a service to use node-local and topology-aware routing for internal traffic. The new internalTrafficPolicy field has two options: Cluster (default) and Local. The Cluster option works like before and tries distributing requests to all available endpoints. On the other hand, the Local option only sends requests to node-local endpoints and drops the request if there is no available instance on the same node. The Local option is useful for sending metrics or logs to an agent running as a DaemonSet.
-
-### [Reserve Service IP Ranges for Dynamic and Static IP Allocation](https://github.com/kubernetes/enhancements/issues/3070) [Stable]
-
-Kubernetes services are assigned a virtual ClusterIP to be reachable inside the cluster. The ClusterIP is either assigned dynamically from a configured Service IP range, or statically set while creating the service resource. There was no possibility of knowing whether another service in the cluster had already used the static ClusterIP before this new stable enhancement. With this change, the IP range is divided into two; this prevents conflicts between services implementing dynamic IP allocation and static IP assignment. The flag --service-cluster-ip-range, with CIDR notation, is part of the Kubernetes API server configuration and is ready to use with the 1.26 release.
-
-### [Support of Mixed Protocols in Services with Type LoadBalancer](https://github.com/kubernetes/enhancements/issues/1435) [Stable]
-
-Kubernetes Services that use the LoadBalancer type have only supported a single Layer 4 protocol until now. With this enhancement going from graduating to stable in v1.26, it is possible to define a mix of protocols in the same service definition. In other words, this enhancement allows a LoadBalancer Service to serve different protocols (e.g. UDP, TCP) under the same port (e.g. 443). For example, serving both UDP and TCP requests for a DNS or SIP server on the same port. For instance, you can expose a DNS server with a single load balancer IP for both TCP and UDP requests, such as the following:
-
-```yaml
-apiVersion: v1
-kind: Service
-metadata:
- name: multi-protocol-dns-server
-spec:
- type: LoadBalancer
- ports:
- - name: dns-udp
- port: 53
- protocol: UDP
- - name: dns-tcp
- port: 53
- protocol: TCP
- selector:
- app: dns-server
-```
-
-## Security in Kubernetes 1.26
-
-### [kubelet Credential Provider](https://github.com/kubernetes/enhancements/issues/2133) [Stable]
-
-The kubelet agent has a built-in credential provider mechanism to retrieve credentials for container image registries. It natively supports Azure, Google Cloud, and AWS container image registries for dynamically retrieving their credentials. The new stable enhancement in v1.26 offers a replacement for the in-tree implementations, and creates an API for extensible plugins in the future.
-
-### [SignedSigning Release Artifacts](https://github.com/kubernetes/enhancements/issues/3031) [Beta]
-
-Every Kubernetes release produces a set of artifacts such as binaries, container images, documentation, and metadata. Since the 1.24 release, the artifacts have been signed as an alpha feature. In the 1.26 release, artifact signing graduates to beta to increase software supply chain security for the Kubernetes release process and mitigate man-in-the-middle attacks.
-
-### [Reduction of Secret-Based Service Account Tokens](https://github.com/kubernetes/enhancements/issues/2799) [Beta]
-
-`BoundServiceAccountTokenVolume` has been GA since version 1.22: Service account tokens for pods are obtained via the TokenRequest API and stored as a projected volume. The new enhancement, in beta, eliminates the need to auto-generate secret-based service account tokens. In addition, Kubernetes will warn about using auto-created secret-based service account tokens, and purge the unused ones.
-
-### [Windows Privileged Containers](https://github.com/kubernetes/enhancements/issues/1981) [Stable] and [Host Networking](https://github.com/kubernetes/enhancements/issues/3503) [Alpha]
-
-Privileged containers are the ones that have similar access and capabilities to the host processes running on the servers. In Linux environments, they are used heavily in Kubernetes for storage, networking, and management. In this release, support for privileged containers for the Windows environment graduates to stable. Management of processes is heavily different from the operating system standpoint in Linux and Windows. Therefore, privileged containers will also work differently in two environments, but they will ensure the same level of security and operational experience.
-
-In addition, there is a new alpha-level enhancement in this release to support host networking for Windows pods. Currently, Windows has all the functionality to make containers use the networking namespace of the nodes. The new alpha enhancement enables this functionality from the Kubernetes side, increasing the parity between Linux and Windows containers.
-
-### [Self-User Attribute and Authentication API](https://github.com/kubernetes/enhancements/issues/33250) [Alpha]
-
-Kubernetes has no resources to identify and manage users as part of its API. Instead, it uses authenticators to get user attributes from tokens, certificates, OIDC providers, or webhooks. The new alpha feature adds a new API endpoint to see what attributes the current users have. The new API is under authentication.k8s.io with the name SelfSubjectReview, and there is a new corresponding command as well: kubectl auth who-am-i. The new feature will reduce the obscurity of complex authentication and help users debug the authentication stack.
-
-## Scheduling in Kubernetes 1.26
-
-### [Non-Graceful Node Shutdown for StatefulSet Pods](https://github.com/kubernetes/enhancements/issues/2268) [Beta]
-
-As a platform Kubernetes is hardened and has been deploy by thousands and thousands of users. Hardening of Kubernetes makes itself resistant to disasters. The kubelet agent that runs on each node in a Kubernetes cluster already uses graceful node shutdown to detect and offboard workloads to other nodes. However, when the shutdown is not detected by the kubelet, the pods of a `StatefulSet` are stuck as `Terminating` and not transferred to a healthy node. The kubelet on the downed node will not delete its pods from Kubernetes API, and the StatefulSet controller will not create new pods with the same name. This happens due to a conflict in the Kubernetes machinery. With this enhancement moving into beta, though, pods will be forcefully deleted along with their volume attachments and new pods will be migrated (created) on healthy nodes.
-
-### [Pod Scheduling Readiness](https://github.com/kubernetes/enhancements/issues/3521) [Alpha]
-
-Currently, pods are considered ready for scheduling as soon as they are created. However, not every pod requires a node, resource allocation, and the start of all its containers immediately after its creation. The new alpha enhancement adds an API to mark pods with their scheduling status: paused and ready. Pods with the .spec.schedulingGates field will be parked in the scheduler and only be assigned to nodes when they are ready to be scheduled.
-
-### [kubectl explain to use OpenAPI v3 for ](https://github.com/kubernetes/enhancements/issues/3515) [Alpha]
-
-Use of OpenAPI v3 means supporting rich type information in `kubectl explan`. Kubernetes has supported OpenAPI v3 as a beta since version 1.24. This richer representation of the fields in the Kubernetes API, means that users can use the `kubectl explain` command to get information that is only detailed in OpenAPI v3, and not the subset defined OpenAPI v2.
-
-## Deprecations and Removals
-
-Consistent to the Kubernetes API lifecycle is deprecations and removals of APIs in each release. It is strongly suggested to check whether you are using the following APIs and flags before there are breaking changes.
-
-
-
- Removal of the `flowcontrol.apiserver.k8s.io/v1beta1` API group for `FlowSchema` and `PriorityLevelConfiguration` requires a migration to the v1beta2 API version.
-
-
- Removal of the `autoscaling/v2beta2` API version for HorizontalPodAutoscaler requires a migration to the autoscaling/v2 API version.
-
-
- Removal of legacy and vendor-specific authentication client-go and kubectl for Azure and Google Cloud requires migration to vendor-neutral authentication plugin mechanisms.
-
-
- Removal of in-tree CSI integration for OpenStack—namely, the `cinder` volume type—requires a migration to use the CSI driver for OpenStack.
-
-
- Some unused options and flags for the kubectl run command are marked as deprecated in the 1.26 release, such as `--grace-period`, `--timeout`, and `--wait`.
-
-
-
-## Last Kubernetes release of 2022
-
-Kubernetes is an ever-evolving platform. For those of you running workloads on Kubernetes taking detailed note of API changes and enhancements is an important activity as you endevour to keep your clusters upgraded with release releases. A more secure, scalable, and flexible Kubernetes is our collective goal. Dign into more details about deprecation, removals, and the latest changes in the 1.26 [release notes](https://relnotes.k8s.io/).
-
-On behalf of the Layer5 community and all of the CNCF projects that its contributors steward, thank you to everyone who participated in this Kubernetes release, and congratulations!
-
-As an end-to-end, open-source, multi-cluster Kuberentes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
-
-
+---
+title: Kubernetes 1.26 Highlights, Features, and Deprecations
+subtitle:
+date: 2022-12-06 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./kubernetes-new.webp
+darkthumbnail: ./kubernetes-new-dark.webp
+description: "Release Notes: What changed in Kubernetes 1.26?"
+type: Blog
+category: Kubernetes
+tags:
+ - Kubernetes
+featured: false
+published: true
+---
+
+
+
+
+
+
+
+As the final Kubernetes release of 2022, Kubernetes 1.26 is an exciting new release of the popular container orchestration platform. It offers a number of new features and improvements that will help platform engineers and DevOps engineers manage their Kubernetes clusters more effectively. Here are some of the highlights of this release.
+
+
+
+ As a longstanding CNCF member, Layer5 has donated two of its open source projects to the CNCF: Meshery and Service Mesh Performance. As an end-to-end, open-source, multi-cluster Kuberentes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
+
+
+
+While there are a number of enhancments tracked in this release (38), you need to be aware that there are also a number of features being deprecated (10) in 1.26. In this article, we will focus on some highlighted enhancements, important deprecations, and removals so that you can be confident before upgrading your clusters.
+
+We'll breakdown new K8s features by category, starting with networking.
+
+## Networking in Kubernetes 1.26
+
+### [Service Internal Traffic Policy](https://github.com/kubernetes/enhancements/issues/2086) [Stable]
+
+When requests are made to a Kubernetes service, they are randomly distributed to all available endpoints. The new enhancement enriches the API of a service to use node-local and topology-aware routing for internal traffic. The new internalTrafficPolicy field has two options: Cluster (default) and Local. The Cluster option works like before and tries distributing requests to all available endpoints. On the other hand, the Local option only sends requests to node-local endpoints and drops the request if there is no available instance on the same node. The Local option is useful for sending metrics or logs to an agent running as a DaemonSet.
+
+### [Reserve Service IP Ranges for Dynamic and Static IP Allocation](https://github.com/kubernetes/enhancements/issues/3070) [Stable]
+
+Kubernetes services are assigned a virtual ClusterIP to be reachable inside the cluster. The ClusterIP is either assigned dynamically from a configured Service IP range, or statically set while creating the service resource. There was no possibility of knowing whether another service in the cluster had already used the static ClusterIP before this new stable enhancement. With this change, the IP range is divided into two; this prevents conflicts between services implementing dynamic IP allocation and static IP assignment. The flag --service-cluster-ip-range, with CIDR notation, is part of the Kubernetes API server configuration and is ready to use with the 1.26 release.
+
+### [Support of Mixed Protocols in Services with Type LoadBalancer](https://github.com/kubernetes/enhancements/issues/1435) [Stable]
+
+Kubernetes Services that use the LoadBalancer type have only supported a single Layer 4 protocol until now. With this enhancement going from graduating to stable in v1.26, it is possible to define a mix of protocols in the same service definition. In other words, this enhancement allows a LoadBalancer Service to serve different protocols (e.g. UDP, TCP) under the same port (e.g. 443). For example, serving both UDP and TCP requests for a DNS or SIP server on the same port. For instance, you can expose a DNS server with a single load balancer IP for both TCP and UDP requests, such as the following:
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+ name: multi-protocol-dns-server
+spec:
+ type: LoadBalancer
+ ports:
+ - name: dns-udp
+ port: 53
+ protocol: UDP
+ - name: dns-tcp
+ port: 53
+ protocol: TCP
+ selector:
+ app: dns-server
+```
+
+## Security in Kubernetes 1.26
+
+### [kubelet Credential Provider](https://github.com/kubernetes/enhancements/issues/2133) [Stable]
+
+The kubelet agent has a built-in credential provider mechanism to retrieve credentials for container image registries. It natively supports Azure, Google Cloud, and AWS container image registries for dynamically retrieving their credentials. The new stable enhancement in v1.26 offers a replacement for the in-tree implementations, and creates an API for extensible plugins in the future.
+
+### [SignedSigning Release Artifacts](https://github.com/kubernetes/enhancements/issues/3031) [Beta]
+
+Every Kubernetes release produces a set of artifacts such as binaries, container images, documentation, and metadata. Since the 1.24 release, the artifacts have been signed as an alpha feature. In the 1.26 release, artifact signing graduates to beta to increase software supply chain security for the Kubernetes release process and mitigate man-in-the-middle attacks.
+
+### [Reduction of Secret-Based Service Account Tokens](https://github.com/kubernetes/enhancements/issues/2799) [Beta]
+
+`BoundServiceAccountTokenVolume` has been GA since version 1.22: Service account tokens for pods are obtained via the TokenRequest API and stored as a projected volume. The new enhancement, in beta, eliminates the need to auto-generate secret-based service account tokens. In addition, Kubernetes will warn about using auto-created secret-based service account tokens, and purge the unused ones.
+
+### [Windows Privileged Containers](https://github.com/kubernetes/enhancements/issues/1981) [Stable] and [Host Networking](https://github.com/kubernetes/enhancements/issues/3503) [Alpha]
+
+Privileged containers are the ones that have similar access and capabilities to the host processes running on the servers. In Linux environments, they are used heavily in Kubernetes for storage, networking, and management. In this release, support for privileged containers for the Windows environment graduates to stable. Management of processes is heavily different from the operating system standpoint in Linux and Windows. Therefore, privileged containers will also work differently in two environments, but they will ensure the same level of security and operational experience.
+
+In addition, there is a new alpha-level enhancement in this release to support host networking for Windows pods. Currently, Windows has all the functionality to make containers use the networking namespace of the nodes. The new alpha enhancement enables this functionality from the Kubernetes side, increasing the parity between Linux and Windows containers.
+
+### [Self-User Attribute and Authentication API](https://github.com/kubernetes/enhancements/issues/33250) [Alpha]
+
+Kubernetes has no resources to identify and manage users as part of its API. Instead, it uses authenticators to get user attributes from tokens, certificates, OIDC providers, or webhooks. The new alpha feature adds a new API endpoint to see what attributes the current users have. The new API is under authentication.k8s.io with the name SelfSubjectReview, and there is a new corresponding command as well: kubectl auth who-am-i. The new feature will reduce the obscurity of complex authentication and help users debug the authentication stack.
+
+## Scheduling in Kubernetes 1.26
+
+### [Non-Graceful Node Shutdown for StatefulSet Pods](https://github.com/kubernetes/enhancements/issues/2268) [Beta]
+
+As a platform Kubernetes is hardened and has been deploy by thousands and thousands of users. Hardening of Kubernetes makes itself resistant to disasters. The kubelet agent that runs on each node in a Kubernetes cluster already uses graceful node shutdown to detect and offboard workloads to other nodes. However, when the shutdown is not detected by the kubelet, the pods of a `StatefulSet` are stuck as `Terminating` and not transferred to a healthy node. The kubelet on the downed node will not delete its pods from Kubernetes API, and the StatefulSet controller will not create new pods with the same name. This happens due to a conflict in the Kubernetes machinery. With this enhancement moving into beta, though, pods will be forcefully deleted along with their volume attachments and new pods will be migrated (created) on healthy nodes.
+
+### [Pod Scheduling Readiness](https://github.com/kubernetes/enhancements/issues/3521) [Alpha]
+
+Currently, pods are considered ready for scheduling as soon as they are created. However, not every pod requires a node, resource allocation, and the start of all its containers immediately after its creation. The new alpha enhancement adds an API to mark pods with their scheduling status: paused and ready. Pods with the .spec.schedulingGates field will be parked in the scheduler and only be assigned to nodes when they are ready to be scheduled.
+
+### [kubectl explain to use OpenAPI v3 for ](https://github.com/kubernetes/enhancements/issues/3515) [Alpha]
+
+Use of OpenAPI v3 means supporting rich type information in `kubectl explan`. Kubernetes has supported OpenAPI v3 as a beta since version 1.24. This richer representation of the fields in the Kubernetes API, means that users can use the `kubectl explain` command to get information that is only detailed in OpenAPI v3, and not the subset defined OpenAPI v2.
+
+## Deprecations and Removals
+
+Consistent to the Kubernetes API lifecycle is deprecations and removals of APIs in each release. It is strongly suggested to check whether you are using the following APIs and flags before there are breaking changes.
+
+
+
+ Removal of the `flowcontrol.apiserver.k8s.io/v1beta1` API group for `FlowSchema` and `PriorityLevelConfiguration` requires a migration to the v1beta2 API version.
+
+
+ Removal of the `autoscaling/v2beta2` API version for HorizontalPodAutoscaler requires a migration to the autoscaling/v2 API version.
+
+
+ Removal of legacy and vendor-specific authentication client-go and kubectl for Azure and Google Cloud requires migration to vendor-neutral authentication plugin mechanisms.
+
+
+ Removal of in-tree CSI integration for OpenStack—namely, the `cinder` volume type—requires a migration to use the CSI driver for OpenStack.
+
+
+ Some unused options and flags for the kubectl run command are marked as deprecated in the 1.26 release, such as `--grace-period`, `--timeout`, and `--wait`.
+
+
+
+## Last Kubernetes release of 2022
+
+Kubernetes is an ever-evolving platform. For those of you running workloads on Kubernetes taking detailed note of API changes and enhancements is an important activity as you endevour to keep your clusters upgraded with release releases. A more secure, scalable, and flexible Kubernetes is our collective goal. Dign into more details about deprecation, removals, and the latest changes in the 1.26 [release notes](https://relnotes.k8s.io/).
+
+On behalf of the Layer5 community and all of the CNCF projects that its contributors steward, thank you to everyone who participated in this Kubernetes release, and congratulations!
+
+As an end-to-end, open-source, multi-cluster Kuberentes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
+
+
diff --git a/src/collections/blog/2023/02-03-validating-admission-controllers/index.mdx b/src/collections/blog/2023/02-03-validating-admission-controllers/index.mdx
index 5d993b460045..75fa0ef52902 100644
--- a/src/collections/blog/2023/02-03-validating-admission-controllers/index.mdx
+++ b/src/collections/blog/2023/02-03-validating-admission-controllers/index.mdx
@@ -1,50 +1,50 @@
----
-title: What are Kubernetes Validating Admission Controllers?
-subtitle: A close cousin to Validating Admission Webhooks
-date: 2023-02-03 08:00:00 -0530
-author: Lee Calcote
-thumbnail: ./kubernetes-new.webp
-darkthumbnail: ./kubernetes-new-dark.webp
-description: "Kubernetes Validating Admission Controllers and Policies use the Common Expression Language (CEL) to offer a declarative, in-process alternative to Validating Admission Webhooks."
-type: Blog
-category: Kubernetes
-tags:
- - Kubernetes
- - Policy-as-Code
-featured: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-
-
-
-Kubernetes is an open-source container orchestration system for automating the deployment, scaling, and management of containerized applications. As part of its functionality, Kubernetes offers a feature called "Admission Controllers" that allow administrators to enforce certain policies on resources being created in the cluster.
-
-In this blog post, we will be discussing a new feature in Kubernetes called "Validating Admission Policies" which is currently in alpha stage. This feature allows administrators to define custom validation rules for resources being created in the cluster and enforce those rules using admission controllers.
-
-## What are Admission Controllers?
-
-Admission controllers are pluggable components in the Kubernetes API server that intercept requests to create, update, or delete resources in the cluster. They allow administrators to enforce certain policies on these requests before they are persisted in the etcd database and acted upon by the Kubernetes control plane.
-
-There are various types of admission controllers available in Kubernetes, such as:
-
-- **NamespaceLifecycle**: This admission controller enforces policies related to namespace creation and deletion.
-- **LimitRanger**: This admission controller enforces resource limits on pods, such as CPU and memory limits.
-- **PodSecurityPolicy**: This admission controller enforces security policies on pods, such as privileged mode, host networking, and volumes.
-
-## Validating Admission Policies
-
-Validating admission policies allow administrators to define custom validation rules for resources being created in the cluster. These rules can be defined using a custom resource definition (CRD) called "ValidatingWebhookConfiguration" and are enforced by the ValidatingAdmissionWebhook admission controller.
-
-For example, an administrator may want to enforce a policy that requires all pods in the cluster to have a specific label. They can define this rule using a ValidatingWebhookConfiguration CRD and configure the ValidatingAdmissionWebhook admission controller to enforce it. Any request to create a pod that does not have the required label will be rejected by the admission controller.
-
-Validating admission policies also allow administrators to use external webhooks to perform the validation. This can be useful when the validation logic is complex or requires access to external resources.
-
-## Conclusion
-
-Validating admission policies is a new feature in Kubernetes that allows administrators to define custom validation rules for resources being created in the cluster. These rules can be enforced using the ValidatingAdmissionWebhook admission controller, and external webhooks can also be used for complex validation logic. This feature can be useful for enforcing policies and ensuring compliance in a Kubernetes cluster.
-
+---
+title: What are Kubernetes Validating Admission Controllers?
+subtitle: A close cousin to Validating Admission Webhooks
+date: 2023-02-03 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./kubernetes-new.webp
+darkthumbnail: ./kubernetes-new-dark.webp
+description: "Kubernetes Validating Admission Controllers and Policies use the Common Expression Language (CEL) to offer a declarative, in-process alternative to Validating Admission Webhooks."
+type: Blog
+category: Kubernetes
+tags:
+ - Kubernetes
+ - Policy-as-Code
+featured: false
+published: true
+---
+
+
+
+
+
+
+
+Kubernetes is an open-source container orchestration system for automating the deployment, scaling, and management of containerized applications. As part of its functionality, Kubernetes offers a feature called "Admission Controllers" that allow administrators to enforce certain policies on resources being created in the cluster.
+
+In this blog post, we will be discussing a new feature in Kubernetes called "Validating Admission Policies" which is currently in alpha stage. This feature allows administrators to define custom validation rules for resources being created in the cluster and enforce those rules using admission controllers.
+
+## What are Admission Controllers?
+
+Admission controllers are pluggable components in the Kubernetes API server that intercept requests to create, update, or delete resources in the cluster. They allow administrators to enforce certain policies on these requests before they are persisted in the etcd database and acted upon by the Kubernetes control plane.
+
+There are various types of admission controllers available in Kubernetes, such as:
+
+- **NamespaceLifecycle**: This admission controller enforces policies related to namespace creation and deletion.
+- **LimitRanger**: This admission controller enforces resource limits on pods, such as CPU and memory limits.
+- **PodSecurityPolicy**: This admission controller enforces security policies on pods, such as privileged mode, host networking, and volumes.
+
+## Validating Admission Policies
+
+Validating admission policies allow administrators to define custom validation rules for resources being created in the cluster. These rules can be defined using a custom resource definition (CRD) called "ValidatingWebhookConfiguration" and are enforced by the ValidatingAdmissionWebhook admission controller.
+
+For example, an administrator may want to enforce a policy that requires all pods in the cluster to have a specific label. They can define this rule using a ValidatingWebhookConfiguration CRD and configure the ValidatingAdmissionWebhook admission controller to enforce it. Any request to create a pod that does not have the required label will be rejected by the admission controller.
+
+Validating admission policies also allow administrators to use external webhooks to perform the validation. This can be useful when the validation logic is complex or requires access to external resources.
+
+## Conclusion
+
+Validating admission policies is a new feature in Kubernetes that allows administrators to define custom validation rules for resources being created in the cluster. These rules can be enforced using the ValidatingAdmissionWebhook admission controller, and external webhooks can also be used for complex validation logic. This feature can be useful for enforcing policies and ensuring compliance in a Kubernetes cluster.
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/04-12-meshery-surpasses-1000-contributors/index.mdx b/src/collections/blog/2023/04-12-meshery-surpasses-1000-contributors/index.mdx
index 4df4de69ecc9..e4f1190e269e 100644
--- a/src/collections/blog/2023/04-12-meshery-surpasses-1000-contributors/index.mdx
+++ b/src/collections/blog/2023/04-12-meshery-surpasses-1000-contributors/index.mdx
@@ -1,53 +1,54 @@
----
-title: Meshery Surpasses 1,000 Contributors
-subtitle: and over 2,000 GitHub stars
-date: 2023-04-12 08:00:00 -0530
-author: Layer5 Team
-thumbnail: ./meshery-contrib-stats.webp
-darkthumbnail: ./meshery-contrib-stats.webp
-description: "Over 1,000 contributors to the Meshery cloud native management project."
-type: Blog
-category: Community
-tags:
- - Meshery
- - Open Source
-featured: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-import MesheryStars from "./2000-github-stars.jpeg";
-import MesheryStats from "./meshery-contrib-stats.webp";
-
-
-
-Meshery, the open source cloud-native manager, has just reached a huge milestone of 1,000 contributors! This is an incredible achievement, and we would like to extend a huge thank you to all of our users and contributors for their support. It is thanks to your dedication and hard work that Meshery as a project and community has grown so quickly. The project has garnered over 2,000 GitHub stars to date and the community has become the #1 most popular Linux Foundation Internship (LFX internship).
-
-
-
-Contributor statistics are tallied across all of the (currently nearly 30) repositories under the [Meshery GitHub organization](https://github.com/meshery). The most popular repository is meshery/meshery, however, there are many supporting components that live in sibling repositories, which receive active contribution. A contributor is an individual who made a review, comment, commit or created PR or issue in Meshery's code base. As of this blog post, over 500 code committers have contributed to Meshery.
-
-
-
-
-
-Meshery is supported by the Layer5 community, which boasts an impressive 4,000 members. The Layer5 community stewards open source projects spanning 5 GitHub organizations and over 70 repositories, two of which are now within the Cloud Native Computing Foundation (CNCF). Meshery is one of Layer5's projects, and is highly extensible, enabling collaborative design and operation of cloud-native infrastructure.
-
-The Meshery platform provides a highly extensible self-service engineering platform, which makes it easy to manage and operate your cloud-native applications. It also enables you to collaborate with others, ensuring that your team can work together seamlessly to design, deploy, and operate cloud-native infrastructure.
-
-The Layer5 community is a warm, welcoming, and supportive community that has won many awards for its open-source contributions. We are proud to be a part of such a great community, and we encourage you to get involved and help us make Meshery even better!
-
-
-
If you haven't already, we invite you to come and see why Meshery is such a popular platform.
- Head over to the Cloud Native Playground and explore all of the amazing features that Meshery has to offer.
-
-
-In conclusion, we would like to thank our amazing community of users and contributors for their dedication and support. It is thanks to you that Meshery has become such a popular and highly-regarded platform, and we look forward to continuing to work with you to make Meshery even better in the future.
-
+---
+title: Meshery Surpasses 1,000 Contributors
+subtitle: and over 2,000 GitHub stars
+date: 2023-04-12 08:00:00 -0530
+author: Layer5 Team
+thumbnail: ./meshery-contrib-stats.webp
+darkthumbnail: ./meshery-contrib-stats.webp
+description: "Over 1,000 contributors to the Meshery cloud native management project."
+type: Blog
+category: Community
+tags:
+ - Meshery
+ - Open Source
+featured: true
+published: true
+---
+
+
+
+
+import MesheryStars from "./2000-github-stars.jpeg";
+import MesheryStats from "./meshery-contrib-stats.webp";
+
+
+
+Meshery, the open source cloud-native manager, has just reached a huge milestone of 1,000 contributors! This is an incredible achievement, and we would like to extend a huge thank you to all of our users and contributors for their support. It is thanks to your dedication and hard work that Meshery as a project and community has grown so quickly. The project has garnered over 2,000 GitHub stars to date and the community has become the #1 most popular Linux Foundation Internship (LFX internship).
+
+
+
+Contributor statistics are tallied across all of the (currently nearly 30) repositories under the [Meshery GitHub organization](https://github.com/meshery). The most popular repository is meshery/meshery, however, there are many supporting components that live in sibling repositories, which receive active contribution. A contributor is an individual who made a review, comment, commit or created PR or issue in Meshery's code base. As of this blog post, over 500 code committers have contributed to Meshery.
+
+
+
+
+
+Meshery is supported by the Layer5 community, which boasts an impressive 4,000 members. The Layer5 community stewards open source projects spanning 5 GitHub organizations and over 70 repositories, two of which are now within the Cloud Native Computing Foundation (CNCF). Meshery is one of Layer5's projects, and is highly extensible, enabling collaborative design and operation of cloud-native infrastructure.
+
+The Meshery platform provides a highly extensible self-service engineering platform, which makes it easy to manage and operate your cloud-native applications. It also enables you to collaborate with others, ensuring that your team can work together seamlessly to design, deploy, and operate cloud-native infrastructure.
+
+The Layer5 community is a warm, welcoming, and supportive community that has won many awards for its open-source contributions. We are proud to be a part of such a great community, and we encourage you to get involved and help us make Meshery even better!
+
+
+
If you haven't already, we invite you to come and see why Meshery is such a popular platform.
+ Head over to the Cloud Native Playground and explore all of the amazing features that Meshery has to offer.
+
+
+
+In conclusion, we would like to thank our amazing community of users and contributors for their dedication and support. It is thanks to you that Meshery has become such a popular and highly-regarded platform, and we look forward to continuing to work with you to make Meshery even better in the future.
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/05-02-layer5-reaches-a-4000-community-member-milestone/index.mdx b/src/collections/blog/2023/05-02-layer5-reaches-a-4000-community-member-milestone/index.mdx
index 5c85c41088de..150a42de98e7 100644
--- a/src/collections/blog/2023/05-02-layer5-reaches-a-4000-community-member-milestone/index.mdx
+++ b/src/collections/blog/2023/05-02-layer5-reaches-a-4000-community-member-milestone/index.mdx
@@ -1,61 +1,56 @@
----
-title: Building amazing open source tools one contributor at-a-time
-subtitle: Layer5 reaches 4,000 community members!
-date: 2023-05-05 08:00:00 -0530
-author: Lee Calcote
-thumbnail: ./4000-layer5-members.webp
-darkthumbnail: ./4000-layer5-members.webp
-description: "Layer5 is an award-winning open community of supportive contributors"
-type: Blog
-category: Community
-tags:
- - Community
- - Open Source
-featured: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-import mesheryMostPopular from "./meshery-most-popular-lfx-internship.webp";
-import Blockquote from "../../../../reusecore/Blockquote";
-import powerOfMeshery from "../../../..//assets/images/playground/gitops-explore-design.webp";
-import CTA_FullWidth from "../../../../components/Call-To-Actions/CTA_FullWidth";
-import CTA_ImageOnly from "../../../../components/Call-To-Actions/CTA_ImageOnly";
-import Playfield from "./layer5-community-playfield.webp";
-import MesheryStats from "./meshery-contrib-stats.webp";
-
-
-
-The Layer5 open source community has reached a milestone that deserves to be celebrated: we're now 4,000 members and growing. Layer5 is an open source community that stewards a number of projects spanning five GitHub organizations and over 80 repositories. Two of the community's projects have even been accepted into the Cloud Native Computing Foundation (CNCF), a testament to the quality of work that the members produce.
-
-
-
-What makes the Layer5 community truly special, however, is not just its impressive technical achievements, but the warmth and welcoming atmosphere that it provides for its members. This is a community that is passionate about collaboration, inclusivity, and supporting each other to reach new heights.
-
-
-Members of the Layer5 community come from all backgrounds and levels of experience, and everyone is encouraged to get involved, share their ideas, and contribute to the projects that they are interested in. The community is always open to new members, and there are plenty of resources available for those who are just starting out or looking to expand their skills.
-
-
-One of the most remarkable things about the Layer5 community is how supportive it is of its members. Whether you are a newcomer or a seasoned veteran, you will find that people are always willing to lend a hand, offer advice, or just provide a friendly ear when you need it.
-
-
-
-
-This culture of support and collaboration has not gone unnoticed by the wider tech community. Layer5's Meshery project, for example, has been recognized as the #1 most popular Linux Foundation Internship (LFX internship). This is a testament to the quality of work that the community produces, but it's also a reflection of the supportive and inclusive environment that it provides for its members.
-
-
-
-
-
- over 1,000 Meshery contributors
-
-
-
-
- As a result of the many, supportive contributors, the Meshery project boasts some impressive statistics with over 1,000 project contributors.
-
-In short, the Layer5 open source community is a warm, welcoming, and award-winning community that is well worth getting involved in. Whether you're looking to expand your skills, work on exciting projects, or just connect with other like-minded individuals, you'll find a home in this community. So why not join us and see for yourself what makes the Layer5 community so special?
-
+---
+title: Building amazing open source tools one contributor at-a-time
+subtitle: Layer5 reaches 4,000 community members!
+date: 2023-05-05 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./4000-layer5-members.webp
+darkthumbnail: ./4000-layer5-members.webp
+description: "Layer5 is an award-winning open community of supportive contributors"
+type: Blog
+category: Community
+tags:
+ - Community
+ - Open Source
+featured: true
+published: true
+---
+
+import mesheryMostPopular from "./meshery-most-popular-lfx-internship.webp";
+import Playfield from "./layer5-community-playfield.webp";
+
+{/*import powerOfMeshery from "../../../../assets/images/playground/gitops-explore-design.webp";
+import MesheryStats from "./meshery-contrib-stats.webp";*/}
+
+
+
+The Layer5 open source community has reached a milestone that deserves to be celebrated: we're now 4,000 members and growing. Layer5 is an open source community that stewards a number of projects spanning five GitHub organizations and over 80 repositories. Two of the community's projects have even been accepted into the Cloud Native Computing Foundation (CNCF), a testament to the quality of work that the members produce.
+
+
+
+What makes the Layer5 community truly special, however, is not just its impressive technical achievements, but the warmth and welcoming atmosphere that it provides for its members. This is a community that is passionate about collaboration, inclusivity, and supporting each other to reach new heights.
+
+
+Members of the Layer5 community come from all backgrounds and levels of experience, and everyone is encouraged to get involved, share their ideas, and contribute to the projects that they are interested in. The community is always open to new members, and there are plenty of resources available for those who are just starting out or looking to expand their skills.
+
+
+One of the most remarkable things about the Layer5 community is how supportive it is of its members. Whether you are a newcomer or a seasoned veteran, you will find that people are always willing to lend a hand, offer advice, or just provide a friendly ear when you need it.
+
+
+
+
+This culture of support and collaboration has not gone unnoticed by the wider tech community. Layer5's Meshery project, for example, has been recognized as the #1 most popular Linux Foundation Internship (LFX internship). This is a testament to the quality of work that the community produces, but it's also a reflection of the supportive and inclusive environment that it provides for its members.
+
+
+
+
+
+ over 1,000 Meshery contributors
+
+
+
+
+ As a result of the many, supportive contributors, the Meshery project boasts some impressive statistics with over 1,000 project contributors.
+
+In short, the Layer5 open source community is a warm, welcoming, and award-winning community that is well worth getting involved in. Whether you're looking to expand your skills, work on exciting projects, or just connect with other like-minded individuals, you'll find a home in this community. So why not join us and see for yourself what makes the Layer5 community so special?
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/change-meshery-release-channels.png b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/change-meshery-release-channels.png
deleted file mode 100644
index 1e7c80c14ae8..000000000000
Binary files a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/change-meshery-release-channels.png and /dev/null differ
diff --git a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/change-meshery-release-channels.webp b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/change-meshery-release-channels.webp
new file mode 100644
index 000000000000..bf16a971cbbe
Binary files /dev/null and b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/change-meshery-release-channels.webp differ
diff --git a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/index.mdx b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/index.mdx
index d15ca7a6a504..de3170cdd545 100644
--- a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/index.mdx
+++ b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/index.mdx
@@ -1,81 +1,87 @@
----
-title: "Changing Meshery Release Channels"
-subtitle: "Change Meshery Release Channels using mesheryctl or using your meshconfig file."
-date: 2023-06-16 10:30:05 -0530
-author: Karan Thakur
-thumbnail: ./change-meshery-release-channels.png
-darkthumbnail: ./change-meshery-release-channels.png
-category: "Meshery"
-description: "Meshery is constantly evolving and improving, with new features and bug fixes being added regularly. To stay up to date with the latest Meshery features and updates, you can switch between different release channels."
-tags:
- - Meshery
- - Open Source
- - mesheryctl
-type: Blog
-resource: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import MesheryVersion from "./meshery-version.png";
-
-
-
-
- Meshery is constantly evolving and improving, with new features and bug fixes being added regularly. To stay up to date with the latest Meshery features and updates, you can switch between different release channels.
-
-
- Artifacts of the builds for Meshery and its components are published under two different release channels, so that improved controls may be provided to both Meshery users and Meshery developers. The two release channels are edge and stable release channels. Relative to stable releases, edge releases occur much more frequently. Edge releases are made with each merge to master, unless that merge to master is for a stable release. Stable releases are made with each
- merge to master when a GitHub release tag is also present in the workflow.
-
-
-
How release channels offer subscription
-
- Release Channels offers a subscription where user can subscribe to a specific release channel and get notified when a new release is available. This is useful for users who want to stay up to date with the latest Meshery features, while also also providing flexibility for users who want to stay on a specific version of Meshery.
- However, this approach can be risky because some updates may introduce bugs or compatibility issues that could break your existing installation. Depending upon your risk aversion and the nature of your deployment environment, having a subscription means that you will automatically receive these updates that you might not be ready incorporate. On the other hand, release channels also offer the ability to pin to a specific release which is a good thing as it allows users to maintain stability and predictability of their environment by preventing unexpected changes from being introduced into their system. However, doing so cancels out any future subscription-based benefits such as receiving security patches or bug fixes that were added after that version was released.
-
-Therefore, it's important for you to weigh the pros and cons of each option before making decisions on how you want to manage your Meshery deployment. It's recommended you and your organizations have a well-defined upgrade strategy based on testing and validation procedures prior to applying new releases in production environments whether via subscriptions or manual upgrades to ensure that system availability is maintained and risks are minimized.
-
-
-
-To subscribe to a specific release channel or version using mesheryctl you can use
-
mesheryctl system channel set [stable|stable-version|edge|edge-version]
-This command will update your local Meshery configuration to use the selected channel for future updates. To set the channel to a specific version, replace Version with the desired version number. Example: mesheryctl system channel set stable or mesheryctl system channel set stable-v0.5.56
-
-
Switching between Release Channels
-
There are two ways to switch between Meshery release channels: using mesheryctl or by editing your meshconfig file. In this blog post, we'll cover both methods.
-
-
What is Meshconfig?
-
- Meshconfig is a configuration file that is used to configure Meshery. It is typically located in the ~/.meshery/config.yaml directory. It contains information about the current release channel, the version of Meshery that is installed, and other configuration options that are specific to your Meshery installation.
- Meshconfig is automatically generated when you run Meshery for the first time. It is also automatically updated when you update Meshery
-
-
-
-
Switching between Meshery release channels using meshconfig file.
-
Open your terminal and confirm that you have mesheryctl installed by running mesheryctl version. If you don't have mesheryctl installed, you can install it by following the instructions in the Meshery documentation.
After making these changes, you can switch between different context by using
mesheryctl system context switch
-
-
-
Switching between Meshery release channels using mesheryctl.
-
mesheryctl is a command-line tool for managing Meshery. You can use it to switch between different release channels. Here's how:
-
-
Run the following command to see the current configuration for Meshery:
-
mesheryctl system context view
-
-
This will show you the currently channels ,stable or edge, along with the version number and other information.
-
Run the following command to switch to a different release channel:
-
mesheryctl system channel switch
-This command will update your meshconfig file to switch release channel and version of context in focus. To switch the channel to a specific version, replace Version with the desired version number.
-
To confirm that the channel has been changed, run the following command again:
mesheryctl system channel view
-
-
Conclusion
-
-
- Switching between Meshery release channels is a simple and straightforward process. You can do it using mesheryctl or by switching between your meshconfig file. Whether you want stable updates or bleeding-edge features, Meshery has a release channel that suits your needs. Just remember to carefully consider your use case and needs before making any changes to ensure that you have the best Meshery experience.
-
-
-
+---
+title: "Changing Meshery Release Channels"
+subtitle: "Change Meshery Release Channels using mesheryctl or using your meshconfig file."
+date: 2023-06-16 10:30:05 -0530
+author: Karan Thakur
+thumbnail: ./change-meshery-release-channels.webp
+darkthumbnail: ./change-meshery-release-channels.webp
+category: "Meshery"
+description: "Meshery is constantly evolving and improving, with new features and bug fixes being added regularly. To stay up to date with the latest Meshery features and updates, you can switch between different release channels."
+tags:
+ - Meshery
+ - Open Source
+ - mesheryctl
+type: Blog
+resource: true
+published: true
+---
+
+
+import MesheryVersion from "./meshery-version.webp";
+
+
+
+
+ Meshery is constantly evolving and improving, with new features and bug fixes being added regularly. To stay up to date with the latest Meshery features and updates, you can switch between different release channels.
+
+
+ Artifacts of the builds for Meshery and its components are published under two different release channels, so that improved controls may be provided to both Meshery users and Meshery developers. The two release channels are edge and stable release channels. Relative to stable releases, edge releases occur much more frequently. Edge releases are made with each merge to master, unless that merge to master is for a stable release. Stable releases are made with each
+ merge to master when a GitHub release tag is also present in the workflow.
+
+
+
How release channels offer subscription
+
+ Release Channels offers a subscription where user can subscribe to a specific release channel and get notified when a new release is available. This is useful for users who want to stay up to date with the latest Meshery features, while also also providing flexibility for users who want to stay on a specific version of Meshery.
+ However, this approach can be risky because some updates may introduce bugs or compatibility issues that could break your existing installation. Depending upon your risk aversion and the nature of your deployment environment, having a subscription means that you will automatically receive these updates that you might not be ready incorporate. On the other hand, release channels also offer the ability to pin to a specific release which is a good thing as it allows users to maintain stability and predictability of their environment by preventing unexpected changes from being introduced into their system. However, doing so cancels out any future subscription-based benefits such as receiving security patches or bug fixes that were added after that version was released.
+
+Therefore, it's important for you to weigh the pros and cons of each option before making decisions on how you want to manage your Meshery deployment. It's recommended you and your organizations have a well-defined upgrade strategy based on testing and validation procedures prior to applying new releases in production environments whether via subscriptions or manual upgrades to ensure that system availability is maintained and risks are minimized.
+
+
+
+To subscribe to a specific release channel or version using mesheryctl you can use
+
mesheryctl system channel set [stable|stable-version|edge|edge-version]
+This command will update your local Meshery configuration to use the selected channel for future updates. To set the channel to a specific version, replace Version with the desired version number. Example: mesheryctl system channel set stable or mesheryctl system channel set stable-v0.5.56
+
+
Switching between Release Channels
+
There are two ways to switch between Meshery release channels: using mesheryctl or by editing your meshconfig file. In this blog post, we'll cover both methods.
+
+
What is Meshconfig?
+
+ Meshconfig is a configuration file that is used to configure Meshery. It is typically located in the ~/.meshery/config.yaml directory. It contains information about the current release channel, the version of Meshery that is installed, and other configuration options that are specific to your Meshery installation.
+ Meshconfig is automatically generated when you run Meshery for the first time. It is also automatically updated when you update Meshery
+
+
+
+
Switching between Meshery release channels using meshconfig file.
+
Open your terminal and confirm that you have mesheryctl installed by running mesheryctl version. If you don't have mesheryctl installed, you can install it by following the instructions in the Meshery documentation.
After making these changes, you can switch between different context by using
mesheryctl system context switch
+
+
+
Switching between Meshery release channels using mesheryctl.
+
mesheryctl is a command-line tool for managing Meshery. You can use it to switch between different release channels. Here's how:
+
+
+
Run the following command to see the current configuration for Meshery:
+
+mesheryctl system context view
+
+
+
This will show you the currently channels ,stable or edge, along with the version number and other information.
+
Run the following command to switch to a different release channel:
+
mesheryctl system channel switch
+This command will update your meshconfig file to switch release channel and version of context in focus. To switch the channel to a specific version, replace Version with the desired version number.
+
To confirm that the channel has been changed, run the following command again:
mesheryctl system channel view
+
+
+
Conclusion
+
+
+ Switching between Meshery release channels is a simple and straightforward process. You can do it using mesheryctl or by switching between your meshconfig file. Whether you want stable updates or bleeding-edge features, Meshery has a release channel that suits your needs. Just remember to carefully consider your use case and needs before making any changes to ensure that you have the best Meshery experience.
+
+
+
diff --git a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/meshery-version.png b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/meshery-version.png
deleted file mode 100644
index 8676b6ea33a7..000000000000
Binary files a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/meshery-version.png and /dev/null differ
diff --git a/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/meshery-version.webp b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/meshery-version.webp
new file mode 100644
index 000000000000..20b0e96a5729
Binary files /dev/null and b/src/collections/blog/2023/05-22-changing-release-channels-in-meshery/meshery-version.webp differ
diff --git a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/MeetTheMeshMate.style.js b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/MeetTheMeshMate.style.js
index 63cd81d62415..8518c78ae4e6 100644
--- a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/MeetTheMeshMate.style.js
+++ b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/MeetTheMeshMate.style.js
@@ -1,5 +1,5 @@
import styled from "styled-components";
-export const MeetTheMeshMate = styled.div`
+const MeetTheMeshMate = styled.div`
div.intro {
word-spacing: 0.5rem;
}
@@ -40,3 +40,5 @@ export const MeetTheMeshMate = styled.div`
font-weight: 600;
}
`;
+
+export default MeetTheMeshMate;
\ No newline at end of file
diff --git a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/index.mdx b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/index.mdx
index 1c84d21bbfe6..1ed0b1077139 100644
--- a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/index.mdx
+++ b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/index.mdx
@@ -1,193 +1,189 @@
----
-title: "Meet the MeshMate: Yash Sharma"
-subtitle: "An interview series with Layer5 MeshMates"
-date: 2023-05-29 10:30:05 -0530
-author: Vivek Vishal
-thumbnail: "./yash-sharma-layer5-meshmate.png"
-darkthumbnail: "./yash-sharma-layer5-meshmate.png"
-category: Community
-tags:
- - Community
- - MeshMate
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import img from "./yash-sharma-layer5-meshmate.png";
-import { MeetTheMeshMate } from "./MeetTheMeshMate.style";
-import { Link } from "gatsby";
-import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
-
-
-
-
Layer5 MeshMates are committed to helping community members be successful contributors. MeshMates aid in identifying areas of projects to engage within, working groups to join, and in helping community members grow in their open source and cloud native knowledge. By connecting one-on-one, MeshMates will share tips on how to have the best community experience possible.
-
-
-
-Vivek:
-
- Yash, thank you for joining me today. Many people inside and outside of the Layer5 Community have seen the effects of your contributions, but may not know the backstory as to who Yash is and how you arrived at your MeshMate role. Indulge us. How did you discover the Layer5 community? What made you stay?
-
-
-
-
-Yash:
-
- "Hey Vivek, thanks for having me! One day, I was scrolling through Twitter and saw someone praising the Layer5 community. I was curious, so I checked it out and joined their Slack channel. As a newbie to open-source, I was unsure about many things, but Shivam ( an amazing contributor ), welcomed me and suggested I should attend the Meshery Dev meet to learn more."
-
-
- "I picked up some issues and started working on them but soon hit a wall. Then one day, Lee Calcote messaged me and said he had me on his intern's list, but noticed I wasn't around the community much. So I reached out to Abhishek and Gaurav for help on how to get more involved. They showed me how to contribute and help others, and then I started attending dev calls, helping others, and making new friends."
-
-
-”After a while, I received a message from Lee and Gaurav saying that I would look good in the MeshMate logo I was surprised. It was one of the best things to happen to me, but also came with a responsibility to help others in the community and guide them on their journey.
-
-
-
-
-Vivek:
-
You’re a MeshMate and have been for some long time now. What does being a MeshMate mean to you? What does it take to be a successful MeshMate?
-
-
-Yash:
-
- "Being a MeshMate is not just an honor, it is also a responsibility towards the community. MeshMates are individuals who are committed to help other members of the community. This includes ensuring that community members have access to resources, are introduced to other members, and understand the vision and goals of the projects.”
-
-
- "I have always loved learning in a community because with a community, we can grow together. Similarly, MeshMates always make sure that their mentees are successful along with the project. It's a great feeling to be a part of a community where everyone is working towards the same goal and supporting each other along the way."
-
-
-
-
- Vivek:
-
- What’s the coolest Meshery demo you have done/seen?
-
-
-
-
-Yash:
-
- "I remember introducing Meshery and MeshMap in my college event. It was an incredibly successful event, and I take great pride in being a part of a community that supports such innovative projects. The response from the attendees was overwhelming, and I am grateful for the hard work and dedication of all the contributors who played a pivotal role in making this project a resounding success. Their collective efforts truly deserve admiration and appreciation."
-
-
-
-
-
-
-
-Vivek:
-
- What is your favorite part of the Layer5 Community? Of being a MeshMate?
-
-
-
-
-
-Yash:
-
- "When I joined Layer5 community I got a welcome message with helping instructions so that I can contribute smoothly and I think this shows how much this community cares about their contributors which I like most about Layer5, everyone here is so welcoming and helping."
-
-
- "Being a MeshMate you get exposure in community which is really good for your growth but this is not best part of being a MeshMate, the best part is the feeling you get after helping someone and being little part of their success."
-
-
-
-
-Vivek:
-
- With the number of people that join the Layer5 community everyday, how do you deal with the continued influx of newcomers?
-
-
-
-
-Yash:
-
- "Layer5 is big community over 4000+ members on slack and everyday so many people join Layer5 community and connecting with newcomers everyday is really not easy it takes time and your little strength too but as I said earliar, being a MeshMate also comes with responsibility which I enjoy most 😎."
-
-
-
-
-
-
-Vivek:
-
- Impressively, you’re also a software engineering intern at Layer5. How did this come to be? What are some personal goals for the next year with respect to the Meshery and the Layer5 community?
-
-
-
-
-Yash:
-
- "Truelly I never joined Layer5 with mindset of internship after I joined Layer5 I saw here people learning new things as they are working on projects, making growth in their personality and improving engineering skills which is what I actually want. Layer5 offers internships all the time and these internships are offered to those who make impact in community and contribute consistently. After 2 months of making impact and contributing consistently I got mail with offer of internship."
-
-
- "Layer5 is growing everyday and many people started using Meshery, MeshMap and other projects for their businesses with this growth my personal goal is to work start helping projects in field of Devops and backend and also I like learning and sharing in public so I’ll also try to spread word of what we do here to appreciate everyone's effort."
-
-
-
-
-Vivek:
-Now, I’ve heard of Community Badges, but what are these? How many are there? More importantly, how do I collect the whole set?! 🙂
-
-
-
-
-Yash:
-
- "Haha the way you are making impact in community soon you’ll get all Vivek, Badges are signs of contributors' efforts in their respective fields given by community. There are different badges for different efforts and I have this which represents MeshMate. I would really like to see you getting so many badges Vivek 😉."
-
-
- "Badges are not also easy to take, this requires your efforts and time towards community and its projects. As I said Layer5 community always wants its contributors' success because with their success it’s layer5's success and badges are one of the ways of recognising contributors' efforts."
-
-
-
-
-Vivek:
-
- Your most often used emoji? Your preference: movie or book? Morning person or night owl? What have you worked on in the past six months that you’re particularly proud of?
-
-
-
-
-Yash:
-
- "😂 some of my favourite questions, I really like using this 🚀 emoji which represents the feeling of keep doing and keep pushing until it's done. I am mostly a night person, as I feel most productive during that time, although I don't recommend it."
-
-
- "I worked on different projects of Layer5 and I am proud for all of them though my favorite part is getting Meshery and MeshMap support default dark mode so that user will get smooth experience of using Meshery or MeshMap "
-
-
-
-
-Vivek:
The cloud native ecosystem moves quickly. Keeping up with all the developments can be challenging. How do you stay up-to-date?
-
-
-
-Yash:
-
- "Yes Cloud native ecosystem is so vast and constantly evolving. I think being part of cloud native community helps me stay up-to-date with its fast moving ecosystem and I’ll also suggest everyone to join community from any platform you like Slack, Twitter or your favorite platform "
-
-
- "As I said Cloud native is so vast so as it’s community too there are so many updated resources available out their on internet by community, which helps me to keep update with Cloud native ecosystem"
-
-
-
-
-Vivek:
What advice do you have for individuals who are hopeful to become Layer5 contributors, interns, or potentially MeshMates?
-
-
-
-Yash:
-
- "Try to come out of your comfort zone. If you are reading this conversation, you are already out of your comfort zone, which is a really good step. Who I am today is because I came out of my comfort zone, which I would also prefer. Lastly, be more helpful towards the community and, most importantly, be consistent. I wish you success."
-
-
-
-
-
-
The open source community at Layer5 is an award winning program and continues to evolve as it grows in number daily. Its projects and activities move at an impressive pace thanks to MeshMates like Yash. Be like Yash. Join the Layer5 Community and say “hi”.
-
-
-
-
+---
+title: "Meet the MeshMate: Yash Sharma"
+subtitle: "An interview series with Layer5 MeshMates"
+date: 2023-05-29 10:30:05 -0530
+author: Vivek Vishal
+thumbnail: "./yash-sharma-layer5-meshmate.webp"
+darkthumbnail: "./yash-sharma-layer5-meshmate.webp"
+category: Community
+tags:
+ - Community
+ - MeshMate
+published: true
+---
+
+import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
+
+
+
+
+
Layer5 MeshMates are committed to helping community members be successful contributors. MeshMates aid in identifying areas of projects to engage within, working groups to join, and in helping community members grow in their open source and cloud native knowledge. By connecting one-on-one, MeshMates will share tips on how to have the best community experience possible.
+
+
+Vivek:
+
+ Yash, thank you for joining me today. Many people inside and outside of the Layer5 Community have seen the effects of your contributions, but may not know the backstory as to who Yash is and how you arrived at your MeshMate role. Indulge us. How did you discover the Layer5 community? What made you stay?
+
+
+
+
+Yash:
+
+ "Hey Vivek, thanks for having me! One day, I was scrolling through Twitter and saw someone praising the Layer5 community. I was curious, so I checked it out and joined their Slack channel. As a newbie to open-source, I was unsure about many things, but Shivam ( an amazing contributor ), welcomed me and suggested I should attend the Meshery Dev meet to learn more."
+
+
+ "I picked up some issues and started working on them but soon hit a wall. Then one day, Lee Calcote messaged me and said he had me on his intern's list, but noticed I wasn't around the community much. So I reached out to Abhishek and Gaurav for help on how to get more involved. They showed me how to contribute and help others, and then I started attending dev calls, helping others, and making new friends."
+
+
+”After a while, I received a message from Lee and Gaurav saying that I would look good in the MeshMate logo I was surprised. It was one of the best things to happen to me, but also came with a responsibility to help others in the community and guide them on their journey.
+
+
+
+
+Vivek:
+
You’re a MeshMate and have been for some long time now. What does being a MeshMate mean to you? What does it take to be a successful MeshMate?
+
+
+
+Yash:
+
+ "Being a MeshMate is not just an honor, it is also a responsibility towards the community. MeshMates are individuals who are committed to help other members of the community. This includes ensuring that community members have access to resources, are introduced to other members, and understand the vision and goals of the projects.”
+
+
+ "I have always loved learning in a community because with a community, we can grow together. Similarly, MeshMates always make sure that their mentees are successful along with the project. It's a great feeling to be a part of a community where everyone is working towards the same goal and supporting each other along the way."
+
+
+
+
+ Vivek:
+
+ What’s the coolest Meshery demo you have done/seen?
+
+
+
+
+Yash:
+
+ "I remember introducing Meshery and MeshMap in my college event. It was an incredibly successful event, and I take great pride in being a part of a community that supports such innovative projects. The response from the attendees was overwhelming, and I am grateful for the hard work and dedication of all the contributors who played a pivotal role in making this project a resounding success. Their collective efforts truly deserve admiration and appreciation."
+
+
+
+
+
+
+
+Vivek:
+
+ What is your favorite part of the Layer5 Community? Of being a MeshMate?
+
+
+
+
+
+Yash:
+
+ "When I joined Layer5 community I got a welcome message with helping instructions so that I can contribute smoothly and I think this shows how much this community cares about their contributors which I like most about Layer5, everyone here is so welcoming and helping."
+
+
+ "Being a MeshMate you get exposure in community which is really good for your growth but this is not best part of being a MeshMate, the best part is the feeling you get after helping someone and being little part of their success."
+
+
+
+
+Vivek:
+
+ With the number of people that join the Layer5 community everyday, how do you deal with the continued influx of newcomers?
+
+
+
+
+Yash:
+
+ "Layer5 is big community over 4000+ members on slack and everyday so many people join Layer5 community and connecting with newcomers everyday is really not easy it takes time and your little strength too but as I said earliar, being a MeshMate also comes with responsibility which I enjoy most 😎."
+
+
+
+
+
+
+Vivek:
+
+ Impressively, you’re also a software engineering intern at Layer5. How did this come to be? What are some personal goals for the next year with respect to the Meshery and the Layer5 community?
+
+
+
+
+Yash:
+
+ "Truelly I never joined Layer5 with mindset of internship after I joined Layer5 I saw here people learning new things as they are working on projects, making growth in their personality and improving engineering skills which is what I actually want. Layer5 offers internships all the time and these internships are offered to those who make impact in community and contribute consistently. After 2 months of making impact and contributing consistently I got mail with offer of internship."
+
+
+ "Layer5 is growing everyday and many people started using Meshery, MeshMap and other projects for their businesses with this growth my personal goal is to work start helping projects in field of Devops and backend and also I like learning and sharing in public so I’ll also try to spread word of what we do here to appreciate everyone's effort."
+
+
+
+
+Vivek:
+
+Now, I’ve heard of Community Badges, but what are these? How many are there? More importantly, how do I collect the whole set?! 🙂
+
+
+
+
+Yash:
+
+ "Haha the way you are making impact in community soon you’ll get all Vivek, Badges are signs of contributors' efforts in their respective fields given by community. There are different badges for different efforts and I have this which represents MeshMate. I would really like to see you getting so many badges Vivek 😉."
+
+
+ "Badges are not also easy to take, this requires your efforts and time towards community and its projects. As I said Layer5 community always wants its contributors' success because with their success it’s layer5's success and badges are one of the ways of recognising contributors' efforts."
+
+
+
+
+Vivek:
+
+ Your most often used emoji? Your preference: movie or book? Morning person or night owl? What have you worked on in the past six months that you’re particularly proud of?
+
+
+
+
+Yash:
+
+ "😂 some of my favourite questions, I really like using this 🚀 emoji which represents the feeling of keep doing and keep pushing until it's done. I am mostly a night person, as I feel most productive during that time, although I don't recommend it."
+
+
+ "I worked on different projects of Layer5 and I am proud for all of them though my favorite part is getting Meshery and MeshMap support default dark mode so that user will get smooth experience of using Meshery or MeshMap "
+
+
+
+
+Vivek:
The cloud native ecosystem moves quickly. Keeping up with all the developments can be challenging. How do you stay up-to-date?
+
+
+
+Yash:
+
+ "Yes Cloud native ecosystem is so vast and constantly evolving. I think being part of cloud native community helps me stay up-to-date with its fast moving ecosystem and I’ll also suggest everyone to join community from any platform you like Slack, Twitter or your favorite platform "
+
+
+ "As I said Cloud native is so vast so as it’s community too there are so many updated resources available out their on internet by community, which helps me to keep update with Cloud native ecosystem"
+
+
+
+
+Vivek:
What advice do you have for individuals who are hopeful to become Layer5 contributors, interns, or potentially MeshMates?
+
+
+
+Yash:
+
+ "Try to come out of your comfort zone. If you are reading this conversation, you are already out of your comfort zone, which is a really good step. Who I am today is because I came out of my comfort zone, which I would also prefer. Lastly, be more helpful towards the community and, most importantly, be consistent. I wish you success."
+
+
+
+
+
+
The open source community at Layer5 is an award winning program and continues to evolve as it grows in number daily. Its projects and activities move at an impressive pace thanks to MeshMates like Yash. Be like Yash. Join the Layer5 Community and say “hi”.
+
+
+
diff --git a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/yash-sharma-layer5-meshmate.png b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/yash-sharma-layer5-meshmate.png
deleted file mode 100644
index d7ca13e511ad..000000000000
Binary files a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/yash-sharma-layer5-meshmate.png and /dev/null differ
diff --git a/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/yash-sharma-layer5-meshmate.webp b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/yash-sharma-layer5-meshmate.webp
new file mode 100644
index 000000000000..652c4ebe307a
Binary files /dev/null and b/src/collections/blog/2023/05-24-meet-the-meshmate-yash-sharma/yash-sharma-layer5-meshmate.webp differ
diff --git a/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/index.mdx b/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/index.mdx
index 30eec90f2613..01d9f457b824 100644
--- a/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/index.mdx
+++ b/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/index.mdx
@@ -1,66 +1,63 @@
----
-title: "Internship Experience with Layer5 - Sudhanshu Dasgupta"
-subtitle: "Unleashing the Journey: From Open-Source Enthusiast to Internship Success"
-date: 2023-06-15 10:30:05 -0530
-author: Sudhanshu Dasgupta
-thumbnail: ./sudhanshu.png
-darkthumbnail: ./sudhanshu.png
-description: "Sharing my internship and open-source experience with this awesome community Layer5"
-category: Community
-type: Blog
-tags:
- - Community
- - Internship
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
-
-
-Hello👋, I'm Sudhanshu Dasgupta, a driven individual from the quaint city of Katni in Madhya Pradesh, India.
-I have an unwavering passion for learning and exploring new horizons in the world of technology and very passionate for open-source. Currently, I am pursuing my
-studies at ITM Gwalior, with a focus on building a successful career in Computer Science and Engineering.
-
-
-
"When and How did it all Start?" ✈️
-
Let's uncover the Origin Story
-
-
-It all began at the start of the year when I made a resolute decision to dive into the world of open-source. Eager to contribute and make a difference, I actively participated in various communities, seeking opportunities to learn and grow.
-Amidst my exploration for exciting projects to contribute to, I stumbled upon Layer5. The moment I delved into their endeavors, I was captivated by the diverse range of tech-stack-driven initiatives they were involved in. Without hesitation, I knew that this was the perfect place for me to start.
-
-Venturing forth, I attended my very first Newcomers meet, a gateway to understanding the vibrant community and its wide array of projects. It was an enriching experience, immersing myself in the ethos of collaboration and knowledge sharing that defined the community's spirit.
-Taking a small yet significant step forward, I eagerly embraced a task assigned to me.
-I understood that even the tiniest actions can pave the way for monumental achievements. But my journey didn't halt there; fueled by my unwavering commitment, continuous skill development, and active engagement with the community, I witnessed remarkable progress.
-And then, within a mere two months, my dedication and contributions were acknowledged, leading to an incredible milestone—I was awarded an internship at Layer5.
-
-
-
- My Experience of Internship with Layer5🚶
-
-
-
- My internship at Layer5 was an extraordinary experience that allowed me to delve deep into the world of open-source and sharpen my skills in a real-world setting.
- Collaborating with talented professionals and working on cutting-edge projects enriched my understanding of various technologies and their practical applications.
-
- During my internship, I actively participated in team discussions, contributed to codebase enhancements, and gained hands-on experience with industry-standard tools and methodologies.
- This internship not only expanded my technical expertise but also provided invaluable insights into the dynamics of a professional work environment and including I was able to improve my communication skills
- as well.
- Overall, my internship at Layer5 was a transformative journey filled with learning, growth, and unforgettable experiences. I look forward to leveraging the skills and knowledge gained during this internship to make a positive impact in the world of technology.
-
-
- Message to other contributors📖
-
-
-
- I remeber myself when I joined the community that I was not aware of many things going in the community but I didn't got off from track, I did take 2 weeks
- to solve a graphql issue but I completed it. Many things are there that you may not know during joining the community but you learn along the journey and
- there is no fear in that. The thing is you can't set back and leave if you are unable to crack something. Learn and come back strong.
- This is community , this is Layer5.
-
-
-
-
+---
+title: "Internship Experience with Layer5 - Sudhanshu Dasgupta"
+subtitle: "Unleashing the Journey: From Open-Source Enthusiast to Internship Success"
+date: 2023-06-15 10:30:05 -0530
+author: Sudhanshu Dasgupta
+thumbnail: ./sudhanshu.webp
+darkthumbnail: ./sudhanshu.webp
+description: "Sharing my internship and open-source experience with this awesome community Layer5"
+category: Community
+type: Blog
+tags:
+ - Community
+ - Internship
+published: true
+---
+
+
+
+
+Hello👋, I'm Sudhanshu Dasgupta, a driven individual from the quaint city of Katni in Madhya Pradesh, India.
+I have an unwavering passion for learning and exploring new horizons in the world of technology and very passionate for open-source. Currently, I am pursuing my
+studies at ITM Gwalior, with a focus on building a successful career in Computer Science and Engineering.
+
+
+
"When and How did it all Start?" ✈️
+
Let's uncover the Origin Story
+
+
+It all began at the start of the year when I made a resolute decision to dive into the world of open-source. Eager to contribute and make a difference, I actively participated in various communities, seeking opportunities to learn and grow.
+Amidst my exploration for exciting projects to contribute to, I stumbled upon Layer5. The moment I delved into their endeavors, I was captivated by the diverse range of tech-stack-driven initiatives they were involved in. Without hesitation, I knew that this was the perfect place for me to start.
+
+Venturing forth, I attended my very first Newcomers meet, a gateway to understanding the vibrant community and its wide array of projects. It was an enriching experience, immersing myself in the ethos of collaboration and knowledge sharing that defined the community's spirit.
+Taking a small yet significant step forward, I eagerly embraced a task assigned to me.
+I understood that even the tiniest actions can pave the way for monumental achievements. But my journey didn't halt there; fueled by my unwavering commitment, continuous skill development, and active engagement with the community, I witnessed remarkable progress.
+And then, within a mere two months, my dedication and contributions were acknowledged, leading to an incredible milestone—I was awarded an internship at Layer5.
+
+
+
+ My Experience of Internship with Layer5🚶
+
+
+
+ My internship at Layer5 was an extraordinary experience that allowed me to delve deep into the world of open-source and sharpen my skills in a real-world setting.
+ Collaborating with talented professionals and working on cutting-edge projects enriched my understanding of various technologies and their practical applications.
+
+ During my internship, I actively participated in team discussions, contributed to codebase enhancements, and gained hands-on experience with industry-standard tools and methodologies.
+ This internship not only expanded my technical expertise but also provided invaluable insights into the dynamics of a professional work environment and including I was able to improve my communication skills
+ as well.
+ Overall, my internship at Layer5 was a transformative journey filled with learning, growth, and unforgettable experiences. I look forward to leveraging the skills and knowledge gained during this internship to make a positive impact in the world of technology.
+
+
+ Message to other contributors📖
+
+
+
+ I remeber myself when I joined the community that I was not aware of many things going in the community but I didn't got off from track, I did take 2 weeks
+ to solve a graphql issue but I completed it. Many things are there that you may not know during joining the community but you learn along the journey and
+ there is no fear in that. The thing is you can't set back and leave if you are unable to crack something. Learn and come back strong.
+ This is community , this is Layer5.
+
+
+
+
diff --git a/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/sudhanshu.png b/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/sudhanshu.png
deleted file mode 100644
index d6535aefcf1f..000000000000
Binary files a/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/sudhanshu.png and /dev/null differ
diff --git a/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/sudhanshu.webp b/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/sudhanshu.webp
new file mode 100644
index 000000000000..16ff9b913de5
Binary files /dev/null and b/src/collections/blog/2023/06-15-internship-experience-blog-sudhanshu-dasgupta/sudhanshu.webp differ
diff --git a/src/collections/blog/2023/06-30-bind-kubernetes-service-account-with-clusterRole/index.mdx b/src/collections/blog/2023/06-30-bind-kubernetes-service-account-with-clusterRole/index.mdx
index c3d49dbfc66f..a415392706e6 100644
--- a/src/collections/blog/2023/06-30-bind-kubernetes-service-account-with-clusterRole/index.mdx
+++ b/src/collections/blog/2023/06-30-bind-kubernetes-service-account-with-clusterRole/index.mdx
@@ -1,99 +1,99 @@
----
-title: "How To Bind Kubernetes Service Account with ClusterRole"
-subtitle: A Comprehensive Guide
-date: 2023-06-30 04:10:00 -0530
-author: Layer5 Team
-thumbnail: ./blog-post.png
-darkthumbnail: ./blog-post.png
-type: Blog
-category: "Meshery"
-tags:
- - Meshery
- - Kubernetes
-featured: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-
-
Kubernetes provides robust RBAC (Role-Based Access Control) capabilities to manage access and authorization within a cluster. This allows you to control and restrict permissions for various resources. In this blog post, we will explore the process of binding a Kubernetes Service Account with a ClusterRole. We will also discuss how Meshery, a service mesh management tool, can be utilized to streamline the lifecycle management of Kubernetes clusters using MeshMap visual diagrams.
-
-
Prerequisites
-
-
Before we delve into the details, ensure that you have the following prerequisites in place:
-
-
-
Access to a running Kubernetes cluster.
-
kubectl, the Kubernetes command-line tool, installed and configured to communicate with your cluster.
-
Meshery, the cloud native manager, installed and set up on your local machine.
-
-
-
Binding a Kubernetes Service Account with ClusterRole:
-
-
To bind a Service Account with a ClusterRole, follow the steps outlined below:
-
-
Step 1: Create a Service Account
-
First, we need to create a Service Account that we will later bind to a ClusterRole. Use the following kubectl command to create a Service Account named my-service-account:
-
-
sh kubectl create serviceaccount my-service-account
-
-
Step 2: Create a ClusterRole
-
Next, let's create a ClusterRole that defines the desired permissions. You can either create a new ClusterRole or use an existing one. For the purpose of this example, we will create a ClusterRole named my-cluster-role that has read-only access to Pods and Services:
Save the above YAML definition to a file named clusterrole.yaml, and create the ClusterRole using the following command:
-
-
bash kubectl apply -f clusterrole.yaml
-
-
Step 3: Bind the Service Account with ClusterRole
-
Finally, we need to bind the Service Account my-service-account with the ClusterRole my-cluster-role. This can be achieved by creating a ClusterRoleBinding. Execute the following command to create the binding:
The above command creates a ClusterRoleBinding named my-cluster-role-binding that associates the Service Account my-service-account with the ClusterRole my-cluster-role.
-
-
Verification:
-
To verify the successful binding, you can use the following command to check the ClusterRoleBinding:
You should see the Service Account and ClusterRole information listed under the Subjects and RoleRef sections, respectively.
-
-
Using Meshery and MeshMap for Kubernetes Cluster Lifecycle Management:
-
Meshery is a powerful service mesh management tool that simplifies the management and operation of service meshes, including Kubernetes clusters. MeshMap, a visual diagram feature of Meshery, provides a graphical representation of the service mesh components and their interactions.
-
-
To utilize Meshery and MeshMap for Kubernetes cluster lifecycle management, follow these steps:
-
-
Step 1: Install Meshery
-
Refer to the official Meshery documentation to install Meshery on your local machine or within your Kubernetes cluster.
-
-
Step 2: Connect to Your Kubernetes Cluster
-
Once Meshery is installed, connect it to your Kubernetes cluster by configuring the necessary authentication and connection details.
-
-
Step 3: Access MeshMap
-
After successfully connecting Meshery to your Kubernetes cluster, you can access MeshMap from the Meshery user interface. MeshMap visually represents the deployed service mesh, including service endpoints, traffic flows, and workload distribution.
-
Step 4: Visualize the Kubernetes Cluster with MeshMap
-
Once you have accessed Meshery and connected it to your Kubernetes cluster, follow these steps to visualize the cluster using MeshMap:
-
-
-
From the Meshery user interface, navigate to the MeshMap section.
-
Select your connected Kubernetes cluster from the dropdown menu.
-
Click on the "Generate Map" button to generate a visual representation of the service mesh components and their interactions within the cluster.
-
Explore the generated MeshMap to gain insights into your Kubernetes cluster's architecture, traffic patterns, and workload distribution.
-
-
-
Conclusion
-
In this blog post, we have learned how to bind a Kubernetes Service Account with a ClusterRole to control access and authorization within a cluster. We have also explored how Meshery and its MeshMap feature can be used for visualizing the service mesh components and their interactions within a Kubernetes cluster. By following these steps, you can effectively manage and monitor your Kubernetes cluster's lifecycle using RBAC and visualization tools.
-
+---
+title: "How To Bind Kubernetes Service Account with ClusterRole"
+subtitle: A Comprehensive Guide
+date: 2023-06-30 04:10:00 -0530
+author: Layer5 Team
+thumbnail: ./blog-post.png
+darkthumbnail: ./blog-post.png
+type: Blog
+category: "Meshery"
+tags:
+ - Meshery
+ - Kubernetes
+featured: true
+published: true
+---
+
+
+
+
+
Kubernetes provides robust RBAC (Role-Based Access Control) capabilities to manage access and authorization within a cluster. This allows you to control and restrict permissions for various resources. In this blog post, we will explore the process of binding a Kubernetes Service Account with a ClusterRole. We will also discuss how Meshery, a service mesh management tool, can be utilized to streamline the lifecycle management of Kubernetes clusters using MeshMap visual diagrams.
+
+
Prerequisites
+
+
Before we delve into the details, ensure that you have the following prerequisites in place:
+
+
+
Access to a running Kubernetes cluster.
+
kubectl, the Kubernetes command-line tool, installed and configured to communicate with your cluster.
+
Meshery, the cloud native manager, installed and set up on your local machine.
+
+
+
Binding a Kubernetes Service Account with ClusterRole:
+
+
To bind a Service Account with a ClusterRole, follow the steps outlined below:
+
+
Step 1: Create a Service Account
+
First, we need to create a Service Account that we will later bind to a ClusterRole. Use the following kubectl command to create a Service Account named my-service-account:
+
+
sh kubectl create serviceaccount my-service-account
+
+
Step 2: Create a ClusterRole
+
Next, let's create a ClusterRole that defines the desired permissions. You can either create a new ClusterRole or use an existing one. For the purpose of this example, we will create a ClusterRole named my-cluster-role that has read-only access to Pods and Services:
Save the above YAML definition to a file named clusterrole.yaml, and create the ClusterRole using the following command:
+
+
bash kubectl apply -f clusterrole.yaml
+
+
Step 3: Bind the Service Account with ClusterRole
+
Finally, we need to bind the Service Account my-service-account with the ClusterRole my-cluster-role. This can be achieved by creating a ClusterRoleBinding. Execute the following command to create the binding:
The above command creates a ClusterRoleBinding named my-cluster-role-binding that associates the Service Account my-service-account with the ClusterRole my-cluster-role.
+
+
Verification:
+
To verify the successful binding, you can use the following command to check the ClusterRoleBinding:
You should see the Service Account and ClusterRole information listed under the Subjects and RoleRef sections, respectively.
+
+
Using Meshery and MeshMap for Kubernetes Cluster Lifecycle Management:
+
Meshery is a powerful service mesh management tool that simplifies the management and operation of service meshes, including Kubernetes clusters. MeshMap, a visual diagram feature of Meshery, provides a graphical representation of the service mesh components and their interactions.
+
+
To utilize Meshery and MeshMap for Kubernetes cluster lifecycle management, follow these steps:
+
+
Step 1: Install Meshery
+
Refer to the official Meshery documentation to install Meshery on your local machine or within your Kubernetes cluster.
+
+
Step 2: Connect to Your Kubernetes Cluster
+
Once Meshery is installed, connect it to your Kubernetes cluster by configuring the necessary authentication and connection details.
+
+
Step 3: Access MeshMap
+
After successfully connecting Meshery to your Kubernetes cluster, you can access MeshMap from the Meshery user interface. MeshMap visually represents the deployed service mesh, including service endpoints, traffic flows, and workload distribution.
+
Step 4: Visualize the Kubernetes Cluster with MeshMap
+
Once you have accessed Meshery and connected it to your Kubernetes cluster, follow these steps to visualize the cluster using MeshMap:
+
+
+
From the Meshery user interface, navigate to the MeshMap section.
+
Select your connected Kubernetes cluster from the dropdown menu.
+
Click on the "Generate Map" button to generate a visual representation of the service mesh components and their interactions within the cluster.
+
Explore the generated MeshMap to gain insights into your Kubernetes cluster's architecture, traffic patterns, and workload distribution.
+
+
+
Conclusion
+
In this blog post, we have learned how to bind a Kubernetes Service Account with a ClusterRole to control access and authorization within a cluster. We have also explored how Meshery and its MeshMap feature can be used for visualizing the service mesh components and their interactions within a Kubernetes cluster. By following these steps, you can effectively manage and monitor your Kubernetes cluster's lifecycle using RBAC and visualization tools.
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/index.mdx b/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/index.mdx
index 12a2c35d36ed..44bfa99f1528 100644
--- a/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/index.mdx
+++ b/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/index.mdx
@@ -1,34 +1,29 @@
----
-title: Layer5 💚's Open Source
-subtitle: HashiCorp Relicensing and Layer5's Partnership
-date: 2023-08-11 08:00:00 -0530
-author: Lee Calcote
-thumbnail: ./layer5-open-source.png
-darkthumbnail: ./layer5-open-source.png
-description: "HashiCorp Relicensing and Layer5's Partnership"
-type: Blog
-category: Announcements
-tags:
- - Open Source
-featured: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-import Blockquote from "../../../../reusecore/Blockquote";
-
-
-
-Yesterday, [HashiCorp announced a change in their source code license](https://www.globenewswire.com/news-release/2023/08/10/2723189/0/en/HashiCorp-adopts-the-Business-Source-License-for-future-releases-of-its-products.html) from Mozilla Public License v2.0 (MPL 2.0) to the Business Source License (BSL, or BUSL) v1.1, effective in all future releases of HashiCorp’s core products, including Terraform, Vault, Consul, Boundary, Nomad, Waypoint, Packer, and Vagrant. HashiCorp APIs, SDKs, and with almost all other libraries remaining MPLv2.
-
-[HashiCorp and Layer5 partnered](/company/news/layer5-hashicorp-launch-service-mesh-partnership) early at the start of Layer5 and continues to be a technology partner. Layer5's projects and products are unaffected by HashiCorp relicensing their software yesterday. Layer5 stands with the open source community and with source-available HashiCorp.
-
-
-Layer5's sprawling [portfolio of projects](/projects) [are open source](/blog/community/meshery-surpasses-1000-contributors), pervasively using the Apache 2.0 license. Layer5 is a [community-first organization](/company/about).
-
-Under an open core model, we look forward to continuing to serve our customers with open source and our amazing, fast-growing [community](/community) at the center of our focus.
-
-
-
+---
+title: Layer5 💚's Open Source
+subtitle: HashiCorp Relicensing and Layer5's Partnership
+date: 2023-08-11 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./layer5-open-source.webp
+darkthumbnail: ./layer5-open-source.webp
+description: "HashiCorp Relicensing and Layer5's Partnership"
+type: Blog
+category: Announcements
+tags:
+ - Open Source
+featured: false
+published: true
+---
+
+
+
+Yesterday, [HashiCorp announced a change in their source code license](https://www.globenewswire.com/news-release/2023/08/10/2723189/0/en/HashiCorp-adopts-the-Business-Source-License-for-future-releases-of-its-products.html) from Mozilla Public License v2.0 (MPL 2.0) to the Business Source License (BSL, or BUSL) v1.1, effective in all future releases of HashiCorp’s core products, including Terraform, Vault, Consul, Boundary, Nomad, Waypoint, Packer, and Vagrant. HashiCorp APIs, SDKs, and with almost all other libraries remaining MPLv2.
+
+[HashiCorp and Layer5 partnered](/company/news/layer5-hashicorp-launch-service-mesh-partnership) early at the start of Layer5 and continues to be a technology partner. Layer5's projects and products are unaffected by HashiCorp relicensing their software yesterday. Layer5 stands with the open source community and with source-available HashiCorp.
+
+
+Layer5's sprawling [portfolio of projects](/projects) [are open source](/blog/community/meshery-surpasses-1000-contributors), pervasively using the Apache 2.0 license. Layer5 is a [community-first organization](/company/about).
+
+Under an open core model, we look forward to continuing to serve our customers with open source and our amazing, fast-growing [community](/community) at the center of our focus.
+
+
+
diff --git a/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/layer5-open-source.png b/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/layer5-open-source.png
deleted file mode 100644
index 23b9c8845d2d..000000000000
Binary files a/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/layer5-open-source.png and /dev/null differ
diff --git a/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/layer5-open-source.webp b/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/layer5-open-source.webp
new file mode 100644
index 000000000000..f1b122ce7d85
Binary files /dev/null and b/src/collections/blog/2023/08-11-layer5-hashicorp-open-source/layer5-open-source.webp differ
diff --git a/src/collections/blog/2023/08-21-layer5-badge-program/badges-modal.png b/src/collections/blog/2023/08-21-layer5-badge-program/badges-modal.png
deleted file mode 100644
index 10cdb8654e11..000000000000
Binary files a/src/collections/blog/2023/08-21-layer5-badge-program/badges-modal.png and /dev/null differ
diff --git a/src/collections/blog/2023/08-21-layer5-badge-program/badges-modal.webp b/src/collections/blog/2023/08-21-layer5-badge-program/badges-modal.webp
new file mode 100644
index 000000000000..6352aa5e6625
Binary files /dev/null and b/src/collections/blog/2023/08-21-layer5-badge-program/badges-modal.webp differ
diff --git a/src/collections/blog/2023/08-21-layer5-badge-program/index.mdx b/src/collections/blog/2023/08-21-layer5-badge-program/index.mdx
index f783a2532dc6..46d6f7adc155 100644
--- a/src/collections/blog/2023/08-21-layer5-badge-program/index.mdx
+++ b/src/collections/blog/2023/08-21-layer5-badge-program/index.mdx
@@ -1,216 +1,212 @@
----
-title: Layer5 Recognition Program
-subtitle: Showcasing Your Achievements as a User and a Contributor
-date: 2023-08-21 08:00:00 -0530
-author: Layer5 Team
-thumbnail: ./recognition-banner.webp
-darkthumbnail: ./recognition-banner.webp
-description: "Showcasing Your Achievements as a User and a Contributor"
-type: Blog
-category: Community
-tags:
- - Community
-featured: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-import Blockquote from "../../../../reusecore/Blockquote";
-import { Blog } from "./blog.style";
-import BadgesGH from "./badges-modal.png"
-import RecognitionProgram from "./recognition-program.png"
-import Playfield from "./layer5-community-playfield.webp"
-import RecognitionBanner from "./recognition-banner.webp"
-
-
-
-
-
-
-
-
-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! 🎉🎈
-
-Our users and contributors have always been celebrated at Layer5. Each participation milestone you achieve and every uplifting community interaction contributes to our shared mission of empowering engineers.
-
-Every aspect of what we do revolves around our users and contributors. We are thrilled to unveil our latest initiative that celebrates and rewards our invaluable users and contributors – Layer5 Badges!
-
-### What Are Layer5 Badges?
-
-These badges are a representation of your participation and milestones that you achieve together and in solidarity with the Layer5 community. Badges are how users demonstrate their prowess with the projects and how contributors identify their ownership, dedication, aand skills. There are several badges each representing a specific user achievement or contributor skill.
-
-Layer5 Badges are a tangible way for us to recognize and honor the exceptional efforts put forth by our contributors and the milestones achieved by our users. These badges are a symbol of your dedication, commitment, and passion for making a positive impact within the Layer5 community and projects. They serve as a testament to the hours spent using, coding, testing, documenting, and collaborating.
-
-Layer5 Badges are more than just virtual tokens; they represent the values we hold dear – openness, collaboration, and continuous improvement. Each badge is a unique recognition of the different roles and responsibilities you take on, reflecting your growth as a contributor and your journey within the Layer5 ecosystem.
-
-
-
-### Why Are Badges Important?
-
-Contributors are the lifeblood of open-source projects, and Layer5 is no exception. Your contributions, large or small, shape the evolution of our projects, drive innovation, and foster a culture of shared learning. Layer5 Badges aims to acknowledge the diverse ways in which you contribute, ensuring that your dedication does not go unnoticed.
-
-Whether you're a power user, an experienced developer, a meticulous documenter, an outreach champion, or a supportive community member, there's a badge that reflects your unique contributions. These badges are our way of saying "thank you" for making Layer5 what it is – a thriving ecosystem of knowledge exchange and collaborative development.
-
- - **Recognition**: Badges provide tangible recognition for your hard work and commitment. They showcase your achievements and highlight the areas where you've made a positive impact.
- - **Motivation**: Striving to earn badges can serve as a powerful motivator for every contributor. As you earn badges, you'll gain a sense of accomplishment, pushing you to set new goals and bring forth new ideas for the betterment of the Layer5 community.
- - **Community Building**: Badges help foster a sense of belonging among contributors. They encourage collaboration, healthy competition, and the sharing of knowledge and experience. We recognize such individuals as [MeshMates](/community/meshmates).
- - **Resume Boost**: Your Layer5 badges can help you stand out in your resume, LinkedIn profile, and other professional platforms. They serve as concrete evidence of your expertise and your dedication to open source hence helping your personal growth.
- - **Social Media Showcase**: These badges can be shared on several social media platforms! Let your friends, family, colleagues, and your bosses know about your contributions, your journey, and your passion for cloud-native technology.
-
-### How Can I Earn Badges?
-Earning Layer5 badges is both rewarding and straightforward. Each badge is tied to specific activities. For users, badges for activities such as using our projects, talking about the projects, sharing your successes and what you like about them. For contributors, badges include activities such as submitting code, assisting with documentation, participating in community events, and more. As you accumulate contributions in various areas, you'll begin to unlock badges that showcase your multifaceted involvement.
-
-These badges will be prominently displayed on your Layer5 community profile, visually representing your journey as a contributor. Not only does this serve as a source of personal pride, but it also helps others in the community recognize your expertise and dedication.
-
-
Project Badges are assigned by the admin to the user when a user contributes to a particular project. Achievement Badges are the badges that are assigned automatically when a user completes a task like sharing a design, creating a design for the first time, etc.
-
-
-
-Earning Layer5 Badges is both exciting and achievable. As you continue to contribute to our projects, your accomplishments will be recognized with badges that reflect your dedication and expertise. Here are some ways you can earn Layer5 Badges:
-
-### How can I Share My Badge On My Profile
-
-
To share your badges on other social profiles, utilize the provided embedded code and direct share functionality. Access your badges from the Layer5 Cloud profile badges section, and then use it to post your achievements on social media platforms seamlessly. This enables you to showcase your Layer5 contributions and milestones to a wider audience.
-
-
Layer5 Badges
-
-
Achievement Badges
-
-
- Design Pioneer
This badge is awarded upon creating your first design.
-
-
- Bring a Buddy
This badge is awarded to the users who invite someone to Layer5 cloud.
-
-
-
- Sharing is Caring
This badge is awarded upon first-time sharing one of your designs.
-
-
-
- Shipped
This badge is awarded upon the success of your first design deployment.
-
-
-
- Need for Speed
This badge is awarded upon successful execution of your first performance test.
-
-
-
- Hip Hacker
This badge is awarded the first time that you establish an interactive terminal session with a Kubernetes Pod.
-
-
- Log Streamer
This badge is awarded the first time that you stream logs from a Kubernetes Pod.
-
-
-
- GitOps with Friends
This badge is awarded the first time a collaborator saves changes to one of your designs.
-
-
-
-
Project Badges
-
-
-
-
- UI/UX
This badge is awarded to the community members who create or improve designs for visual aspects or user flow for any of the websites, flyers, promotions, Meshery UI, and so on in recognition and appreciation of their efforts.
-
-
-
- MeshMap
This badge is awarded to the community members who make consistent and impactful contributions to the MeshMap project in recognition and appreciation of their efforts. Community members who earn this badge occasionally become a project maintainer.
-
-
-
- Service Mesh Performance
This badge is awarded to the community members who make consistent and impactful contributions to the Service Mesh Performance project. Community members who earn this badge occasionally become a project maintainer.
-
-
-
- Community
This badge is awarded to the community members who repeatedly engage in welcoming, encouraging, and supporting other Layer5 community members. Community members who earn this badge occasionally graduate to undertake the Community Manager role.
-
-
-
- Writer's Program
awarded to the community members who make two or more published writings whether in an article, blog post, project documentation, or other form in recognition and appreciation of their efforts.
-
-
-
- Meshery
This badge is awarded to the community members who make consistent and impactful contributions to the Meshery project. Community members who earn this badge occasionally become a project maintainer.
-
-
-
- Patterns
This badge is awarded to the community members who make consistent and impactful contributions to the Service Mesh Patterns project in recognition and appreciation of their efforts.
-
-
-
- Landscape
This badge is awarded to the community members who make consistent and impactful contributions to the layer5.io website.
-
-
-
- Nighthawk
This badge is awarded to the community members who make consistent and impactful contributions to the NightHawk project in recognition and appreciation of their efforts. Community members who earn this badge occasionally become a project maintainer.
-
-
-
- Meshery Catalog
This badge is awarded to the community members who make consistent and impactful contributions to the Meshery Catalog of Meshery project in recognition and appreciation of their efforts.
-
-
-
- Meshery Operator
This badge awarded is awarded to the community members who make consistent and impactful contributions to Meshery Operator of the Meshery project in recognition and appreciation of their efforts.
-
-
-
- Docker Extension
This badge is awarded to the community members who make consistent and impactful contributions to the Docker Extension of meshery project in recognition and appreciation of their efforts.
-
-
- Meshery Docs
This badge is awarded to the community members who make consistent and impactful contributions to the Meshery Docs in recognition and appreciation of their efforts.
-
-
-
-
Certification Badges
-
-
-
-
- MeshMaster
This badge is awarded to individuals who have demonstrated a clear and holistic understanding of cloud-native infrastructure management.
-
-
-
- Coming Soon
Additional certifications are coming soon!
-
-
-
-
Earn your first badge today
-
-Are you ready to start earning badges? Join the [Layer5](http://layer5.io/) community platform and start making your contributions! By earning badges, you don't just highlight your accomplishments - you contribute to the growth and success of Layer5. Let's celebrate your milestones, your dedication, and your passion for open source together. By obtaining a Layer5 Badge, you have the opportunity to inspire others on their journey and shine.
-
-
-
-### FAQ's
-
-**Is there a limit to the number of badges that I can earn?**
-There is no set limit to the number of badges you can earn within the Layer5 Recognition Program. Your achievements and contributions determine the badges you receive, showcasing your dedication and skills within the community.
-
-**How do I share my badges on other social profiles?**
-To share your badges on other social profiles, utilize the provided embedded code and direct share functionality. Access your badges from the Layer5 Cloud profile badges section, and then use it to post your achievements on social media platforms seamlessly. This enables you to showcase your Layer5 contributions and milestones to a wider audience.
-
-**How many badges are there?**
-With three sets of badges, each with their own echelons you'll be collecting new badges for a while. Will you make it onto the badge leaderboard? New badges are being developed, so keep your eyes peeled for their emergence... or help us design a new one!
-
-**Will there be other categories in the future?**
-Yes, we aim to expand badge categories to recognize a broader range of achievements and contributions, fostering a more inclusive and diverse community.
-
-**Should I add these to my résumé?**
-Yes, incorporating Layer5 recognition badges into your résumé showcases your technical proficiency, commitment, and collaborative spirit, adding credibility to your open-source contributions and skills.
-
-**Can I design a badge?**
-Yes, Layer5 encourages collaboration and welcomes your ideas to enhance the badge design process and community engagement.
-
-### What's Next?
-We are excited to roll out Layer5 Badges as part of our ongoing commitment to fostering a vibrant, collaborative, and inclusive community. With these badges, we hope to inspire more individuals to join us in our mission of advancing the networking industry through open-source projects and initiatives.
-
-Thank you for being an essential part of Layer5. Your contributions continue to shape the future of open-source networking, and Layer5 badges are just one small way we can show our gratitude for your dedication.
-
-Send us screenshots or links of your new badges adorning your profiles. We will select our favorites and share them with the open-source community at large. Here's to celebrating your journey and achievements with Layer5 badges! 🌟🚀
-
-
-
-
+---
+title: Layer5 Recognition Program
+subtitle: Showcasing Your Achievements as a User and a Contributor
+date: 2023-08-21 08:00:00 -0530
+author: Layer5 Team
+thumbnail: ./recognition-banner.webp
+darkthumbnail: ./recognition-banner.webp
+description: "Showcasing Your Achievements as a User and a Contributor"
+type: Blog
+category: Community
+tags:
+ - Community
+featured: false
+published: true
+---
+
+import { Blog } from "./blog.style";
+import BadgesGH from "./badges-modal.webp"
+import RecognitionProgram from "./recognition-program.webp"
+import Playfield from "./layer5-community-playfield.webp"
+import RecognitionBanner from "./recognition-banner.webp"
+
+
+
+
+
+
+
+
+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! 🎉🎈
+
+Our users and contributors have always been celebrated at Layer5. Each participation milestone you achieve and every uplifting community interaction contributes to our shared mission of empowering engineers.
+
+Every aspect of what we do revolves around our users and contributors. We are thrilled to unveil our latest initiative that celebrates and rewards our invaluable users and contributors – Layer5 Badges!
+
+### What Are Layer5 Badges?
+
+These badges are a representation of your participation and milestones that you achieve together and in solidarity with the Layer5 community. Badges are how users demonstrate their prowess with the projects and how contributors identify their ownership, dedication, aand skills. There are several badges each representing a specific user achievement or contributor skill.
+
+Layer5 Badges are a tangible way for us to recognize and honor the exceptional efforts put forth by our contributors and the milestones achieved by our users. These badges are a symbol of your dedication, commitment, and passion for making a positive impact within the Layer5 community and projects. They serve as a testament to the hours spent using, coding, testing, documenting, and collaborating.
+
+Layer5 Badges are more than just virtual tokens; they represent the values we hold dear – openness, collaboration, and continuous improvement. Each badge is a unique recognition of the different roles and responsibilities you take on, reflecting your growth as a contributor and your journey within the Layer5 ecosystem.
+
+
+
+### Why Are Badges Important?
+
+Contributors are the lifeblood of open-source projects, and Layer5 is no exception. Your contributions, large or small, shape the evolution of our projects, drive innovation, and foster a culture of shared learning. Layer5 Badges aims to acknowledge the diverse ways in which you contribute, ensuring that your dedication does not go unnoticed.
+
+Whether you're a power user, an experienced developer, a meticulous documenter, an outreach champion, or a supportive community member, there's a badge that reflects your unique contributions. These badges are our way of saying "thank you" for making Layer5 what it is – a thriving ecosystem of knowledge exchange and collaborative development.
+
+ - **Recognition**: Badges provide tangible recognition for your hard work and commitment. They showcase your achievements and highlight the areas where you've made a positive impact.
+ - **Motivation**: Striving to earn badges can serve as a powerful motivator for every contributor. As you earn badges, you'll gain a sense of accomplishment, pushing you to set new goals and bring forth new ideas for the betterment of the Layer5 community.
+ - **Community Building**: Badges help foster a sense of belonging among contributors. They encourage collaboration, healthy competition, and the sharing of knowledge and experience. We recognize such individuals as [MeshMates](/community/meshmates).
+ - **Resume Boost**: Your Layer5 badges can help you stand out in your resume, LinkedIn profile, and other professional platforms. They serve as concrete evidence of your expertise and your dedication to open source hence helping your personal growth.
+ - **Social Media Showcase**: These badges can be shared on several social media platforms! Let your friends, family, colleagues, and your bosses know about your contributions, your journey, and your passion for cloud-native technology.
+
+### How Can I Earn Badges?
+Earning Layer5 badges is both rewarding and straightforward. Each badge is tied to specific activities. For users, badges for activities such as using our projects, talking about the projects, sharing your successes and what you like about them. For contributors, badges include activities such as submitting code, assisting with documentation, participating in community events, and more. As you accumulate contributions in various areas, you'll begin to unlock badges that showcase your multifaceted involvement.
+
+These badges will be prominently displayed on your Layer5 community profile, visually representing your journey as a contributor. Not only does this serve as a source of personal pride, but it also helps others in the community recognize your expertise and dedication.
+
+
Project Badges are assigned by the admin to the user when a user contributes to a particular project. Achievement Badges are the badges that are assigned automatically when a user completes a task like sharing a design, creating a design for the first time, etc.
+
+
+
+Earning Layer5 Badges is both exciting and achievable. As you continue to contribute to our projects, your accomplishments will be recognized with badges that reflect your dedication and expertise. Here are some ways you can earn Layer5 Badges:
+
+### How can I Share My Badge On My Profile
+
+
To share your badges on other social profiles, utilize the provided embedded code and direct share functionality. Access your badges from the Layer5 Cloud profile badges section, and then use it to post your achievements on social media platforms seamlessly. This enables you to showcase your Layer5 contributions and milestones to a wider audience.
+
+
Layer5 Badges
+
+
Achievement Badges
+
+
+ Design Pioneer
This badge is awarded upon creating your first design.
+
+
+ Bring a Buddy
This badge is awarded to the users who invite someone to Layer5 cloud.
+
+
+
+ Sharing is Caring
This badge is awarded upon first-time sharing one of your designs.
+
+
+
+ Shipped
This badge is awarded upon the success of your first design deployment.
+
+
+
+ Need for Speed
This badge is awarded upon successful execution of your first performance test.
+
+
+
+ Hip Hacker
This badge is awarded the first time that you establish an interactive terminal session with a Kubernetes Pod.
+
+
+ Log Streamer
This badge is awarded the first time that you stream logs from a Kubernetes Pod.
+
+
+
+ GitOps with Friends
This badge is awarded the first time a collaborator saves changes to one of your designs.
+
+
+
+
Project Badges
+
+
+
+
+ UI/UX
This badge is awarded to the community members who create or improve designs for visual aspects or user flow for any of the websites, flyers, promotions, Meshery UI, and so on in recognition and appreciation of their efforts.
+
+
+
+ MeshMap
This badge is awarded to the community members who make consistent and impactful contributions to the MeshMap project in recognition and appreciation of their efforts. Community members who earn this badge occasionally become a project maintainer.
+
+
+
+ Service Mesh Performance
This badge is awarded to the community members who make consistent and impactful contributions to the Service Mesh Performance project. Community members who earn this badge occasionally become a project maintainer.
+
+
+
+ Community
This badge is awarded to the community members who repeatedly engage in welcoming, encouraging, and supporting other Layer5 community members. Community members who earn this badge occasionally graduate to undertake the Community Manager role.
+
+
+
+ Writer's Program
awarded to the community members who make two or more published writings whether in an article, blog post, project documentation, or other form in recognition and appreciation of their efforts.
+
+
+
+ Meshery
This badge is awarded to the community members who make consistent and impactful contributions to the Meshery project. Community members who earn this badge occasionally become a project maintainer.
+
+
+
+ Patterns
This badge is awarded to the community members who make consistent and impactful contributions to the Service Mesh Patterns project in recognition and appreciation of their efforts.
+
+
+
+ Landscape
This badge is awarded to the community members who make consistent and impactful contributions to the layer5.io website.
+
+
+
+ Nighthawk
This badge is awarded to the community members who make consistent and impactful contributions to the NightHawk project in recognition and appreciation of their efforts. Community members who earn this badge occasionally become a project maintainer.
+
+
+
+ Meshery Catalog
This badge is awarded to the community members who make consistent and impactful contributions to the Meshery Catalog of Meshery project in recognition and appreciation of their efforts.
+
+
+
+ Meshery Operator
This badge awarded is awarded to the community members who make consistent and impactful contributions to Meshery Operator of the Meshery project in recognition and appreciation of their efforts.
+
+
+
+ Docker Extension
This badge is awarded to the community members who make consistent and impactful contributions to the Docker Extension of meshery project in recognition and appreciation of their efforts.
+
+
+ Meshery Docs
This badge is awarded to the community members who make consistent and impactful contributions to the Meshery Docs in recognition and appreciation of their efforts.
+
+
+
+
Certification Badges
+
+
+
+
+ MeshMaster
This badge is awarded to individuals who have demonstrated a clear and holistic understanding of cloud-native infrastructure management.
+
+
+
+ Coming Soon
Additional certifications are coming soon!
+
+
+
+
Earn your first badge today
+
+Are you ready to start earning badges? Join the [Layer5](http://layer5.io/) community platform and start making your contributions! By earning badges, you don't just highlight your accomplishments - you contribute to the growth and success of Layer5. Let's celebrate your milestones, your dedication, and your passion for open source together. By obtaining a Layer5 Badge, you have the opportunity to inspire others on their journey and shine.
+
+
+
+### FAQ's
+
+**Is there a limit to the number of badges that I can earn?**
+There is no set limit to the number of badges you can earn within the Layer5 Recognition Program. Your achievements and contributions determine the badges you receive, showcasing your dedication and skills within the community.
+
+**How do I share my badges on other social profiles?**
+To share your badges on other social profiles, utilize the provided embedded code and direct share functionality. Access your badges from the Layer5 Cloud profile badges section, and then use it to post your achievements on social media platforms seamlessly. This enables you to showcase your Layer5 contributions and milestones to a wider audience.
+
+**How many badges are there?**
+With three sets of badges, each with their own echelons you'll be collecting new badges for a while. Will you make it onto the badge leaderboard? New badges are being developed, so keep your eyes peeled for their emergence... or help us design a new one!
+
+**Will there be other categories in the future?**
+Yes, we aim to expand badge categories to recognize a broader range of achievements and contributions, fostering a more inclusive and diverse community.
+
+**Should I add these to my résumé?**
+Yes, incorporating Layer5 recognition badges into your résumé showcases your technical proficiency, commitment, and collaborative spirit, adding credibility to your open-source contributions and skills.
+
+**Can I design a badge?**
+Yes, Layer5 encourages collaboration and welcomes your ideas to enhance the badge design process and community engagement.
+
+### What's Next?
+We are excited to roll out Layer5 Badges as part of our ongoing commitment to fostering a vibrant, collaborative, and inclusive community. With these badges, we hope to inspire more individuals to join us in our mission of advancing the networking industry through open-source projects and initiatives.
+
+Thank you for being an essential part of Layer5. Your contributions continue to shape the future of open-source networking, and Layer5 badges are just one small way we can show our gratitude for your dedication.
+
+Send us screenshots or links of your new badges adorning your profiles. We will select our favorites and share them with the open-source community at large. Here's to celebrating your journey and achievements with Layer5 badges! 🌟🚀
+
+
+
+
diff --git a/src/collections/blog/2023/08-21-layer5-badge-program/recognition-banner.webp b/src/collections/blog/2023/08-21-layer5-badge-program/recognition-banner.webp
index 35b392f12de1..c1f78270a54d 100644
Binary files a/src/collections/blog/2023/08-21-layer5-badge-program/recognition-banner.webp and b/src/collections/blog/2023/08-21-layer5-badge-program/recognition-banner.webp differ
diff --git a/src/collections/blog/2023/08-21-layer5-badge-program/recognition-program.png b/src/collections/blog/2023/08-21-layer5-badge-program/recognition-program.png
deleted file mode 100644
index be9a9f333a10..000000000000
Binary files a/src/collections/blog/2023/08-21-layer5-badge-program/recognition-program.png and /dev/null differ
diff --git a/src/collections/blog/2023/08-21-layer5-badge-program/recognition-program.webp b/src/collections/blog/2023/08-21-layer5-badge-program/recognition-program.webp
new file mode 100644
index 000000000000..1204972207d8
Binary files /dev/null and b/src/collections/blog/2023/08-21-layer5-badge-program/recognition-program.webp differ
diff --git a/src/collections/blog/2023/08-23-importance-of-github-stars/index.mdx b/src/collections/blog/2023/08-23-importance-of-github-stars/index.mdx
index d723acbac873..45246060e2ab 100644
--- a/src/collections/blog/2023/08-23-importance-of-github-stars/index.mdx
+++ b/src/collections/blog/2023/08-23-importance-of-github-stars/index.mdx
@@ -1,104 +1,102 @@
----
-title: On the Importance of GitHub Stars
-subtitle: Why GitHub Stars matter to open source projects, their contributors, and their users
-date: 2023-08-24 12:30:05 -0530
-author: Victoria Nduka
-thumbnail: ./hero-image.svg
-darkthumbnail: ./hero-image.svg
-category: Community
-description: "Why GitHub Stars matter to open source projects, their contributors, and their users."
-tags:
- - Community
- - Open Source
- - Meshery
-type: Blog
-resource: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-
-import Before from "./before.png";
-import After from "./after.png";
-import Five from "./five-image.png";
-
-
-
-You've probably seen tweets or LinkedIn posts celebrating the number of stars a project receives on GitHub. Maybe someone has even asked you to star their repository. If you've ever wondered how much of an impact your star could make on their project, you're in the right place. Let's explore what GitHub Stars are and explore the significant role they play in boosting a project.
-
-### What are GitHub Stars?
-
-GitHub stars are like virtual thumbs-up or bookmarks that you can give to projects you like on the GitHub platform. They're a way to show that you find a project interesting, useful, or valuable. When you star a project, when you star a project, it's represented at the [stargazers](https://github.com/meshery/meshery/stargazers) section of the repository.
-
-Stars are one of the key metrics that GitHub uses to track and identify trending projects on its platform. When a repository gains a significant number of stars within a relatively short period, it can be an indicator that the project is gaining popularity, and consequently, qualifies as a "trending project".
-
-Here's how GitHub uses stars to track trending projects:
-
-1. **Star Activity** -
-GitHub monitors the rate at which repositories are being starred. Projects that receive a sudden surge of stars are likely to catch the attention of GitHub's algorithms.
-1. **Time Interval** -
-GitHub takes into account the time frame within which stars are accumulated. Projects that gain stars rapidly in a short span of time are considered for trending status.
-1. **Relative Comparison** -
-Trending repositories are often determined based on a comparison with their usual star activity. If a repository's star activity significantly exceeds its typical rate, it might be flagged as trending.
-1. **Consistency** -
-While rapid stars are important, consistent activity also matters. Projects that sustain their increased star activity over time are more likely to be recognized as trending.
-
-Once a repository meets these criteria, it might be highlighted on GitHub's Trending page or other curated sections of the platform. This visibility can attract even more attention and stars, creating a feedback loop that amplifies the project's popularity.
-
-### Effect of Stars on a Project
-Starring a project on GitHub does not directly impact the project’s functionality, but it can have several positive effects which include:
-
-- **Visibility** -
-Starring a project increases its visibility. Projects with more stars tend to appear higher in search results, making it easier for others to discover and contribute to the project
-- **Community Engagement** -
-A higher number of stars can attract more contributors, users, and potential collaborators. It indicates that the project has generated interest and resonates with others.
-- **Motivation** -
-For project maintainers and contributors, seeing their project receive stars can be motivating. It shows that their work is appreciated and valued by the community.
-- **Recognition** - Starring a project is a way for users to acknowledge and recognize the effort put into it. It’s a form of social validation.
-- **Contributor Potential** - Potential contributors might use the number of stars a project has as a signal of the project’s importance and popularity. A well-started project might attract developers looking for projects to contribute to.
-- **Feedback and Support** - Starring can also serve as a lightweight way for users to express their support for the project or to keep track of projects they find interesting even if they don’t actively contribute.
-
-Overall, starring a project helps create a positive cycle where visibility leads to engagement, engagement leads to contributions, and contributions lead to a stronger project.
-
-### How to Star a Repository
-Starring a repository is a simple two-step process.
-- **Step 1:** On [GitHub](https://github.com/meshery/meshery), navigate to the main page of the repository.
-- **Step 2:** At the top-right corner of the page, click Star.
-
-
-
-
-
Before adding a star
-
-
-
-
-
This is what a project will look like after you have starred it:
-
-
-
-
-
After adding a star
-
-
-
-
-
-## Five Needs Your Stars
-
-Now that you understand how much impact stars can make, take a moment to help [Five on his Cloud Native journey](https://layer5.io/five/vol1/mascot-five-adventure-github-stars.pdf). Five is our intergalactic Cloud Native Hero on a journey to the Meshery planet. Five’s rocketship runs on stars and he needs all the stars he can get. The community is doing its best to provide fuel, but that's not enough. Our friend Five needs more stars to get him through this journey.
-
-You can help Five by giving a star to the [Meshery](https://github.com/meshery/meshery)!
-
-
-
-
-
- 🌟 Star the Meshery repository 🌟
-
-
-
-
-
-
-
+---
+title: On the Importance of GitHub Stars
+subtitle: Why GitHub Stars matter to open source projects, their contributors, and their users
+date: 2023-08-24 12:30:05 -0530
+author: Victoria Nduka
+thumbnail: ./hero-image.svg
+darkthumbnail: ./hero-image.svg
+category: Community
+description: "Why GitHub Stars matter to open source projects, their contributors, and their users."
+tags:
+ - Community
+ - Open Source
+ - Meshery
+type: Blog
+resource: false
+published: true
+---
+
+import Before from "./before.png";
+import After from "./after.png";
+import Five from "./five-image.png";
+
+
+
+You've probably seen tweets or LinkedIn posts celebrating the number of stars a project receives on GitHub. Maybe someone has even asked you to star their repository. If you've ever wondered how much of an impact your star could make on their project, you're in the right place. Let's explore what GitHub Stars are and explore the significant role they play in boosting a project.
+
+### What are GitHub Stars?
+
+GitHub stars are like virtual thumbs-up or bookmarks that you can give to projects you like on the GitHub platform. They're a way to show that you find a project interesting, useful, or valuable. When you star a project, when you star a project, it's represented at the [stargazers](https://github.com/meshery/meshery/stargazers) section of the repository.
+
+Stars are one of the key metrics that GitHub uses to track and identify trending projects on its platform. When a repository gains a significant number of stars within a relatively short period, it can be an indicator that the project is gaining popularity, and consequently, qualifies as a "trending project".
+
+Here's how GitHub uses stars to track trending projects:
+
+1. **Star Activity** -
+GitHub monitors the rate at which repositories are being starred. Projects that receive a sudden surge of stars are likely to catch the attention of GitHub's algorithms.
+1. **Time Interval** -
+GitHub takes into account the time frame within which stars are accumulated. Projects that gain stars rapidly in a short span of time are considered for trending status.
+1. **Relative Comparison** -
+Trending repositories are often determined based on a comparison with their usual star activity. If a repository's star activity significantly exceeds its typical rate, it might be flagged as trending.
+1. **Consistency** -
+While rapid stars are important, consistent activity also matters. Projects that sustain their increased star activity over time are more likely to be recognized as trending.
+
+Once a repository meets these criteria, it might be highlighted on GitHub's Trending page or other curated sections of the platform. This visibility can attract even more attention and stars, creating a feedback loop that amplifies the project's popularity.
+
+### Effect of Stars on a Project
+Starring a project on GitHub does not directly impact the project’s functionality, but it can have several positive effects which include:
+
+- **Visibility** -
+Starring a project increases its visibility. Projects with more stars tend to appear higher in search results, making it easier for others to discover and contribute to the project
+- **Community Engagement** -
+A higher number of stars can attract more contributors, users, and potential collaborators. It indicates that the project has generated interest and resonates with others.
+- **Motivation** -
+For project maintainers and contributors, seeing their project receive stars can be motivating. It shows that their work is appreciated and valued by the community.
+- **Recognition** - Starring a project is a way for users to acknowledge and recognize the effort put into it. It’s a form of social validation.
+- **Contributor Potential** - Potential contributors might use the number of stars a project has as a signal of the project’s importance and popularity. A well-started project might attract developers looking for projects to contribute to.
+- **Feedback and Support** - Starring can also serve as a lightweight way for users to express their support for the project or to keep track of projects they find interesting even if they don’t actively contribute.
+
+Overall, starring a project helps create a positive cycle where visibility leads to engagement, engagement leads to contributions, and contributions lead to a stronger project.
+
+### How to Star a Repository
+Starring a repository is a simple two-step process.
+- **Step 1:** On [GitHub](https://github.com/meshery/meshery), navigate to the main page of the repository.
+- **Step 2:** At the top-right corner of the page, click Star.
+
+
+
+
+
Before adding a star
+
+
+
+
+
This is what a project will look like after you have starred it:
+
+
+
+
+
After adding a star
+
+
+
+
+
+## Five Needs Your Stars
+
+Now that you understand how much impact stars can make, take a moment to help [Five on his Cloud Native journey](https://layer5.io/five/vol1/mascot-five-adventure-github-stars.pdf). Five is our intergalactic Cloud Native Hero on a journey to the Meshery planet. Five’s rocketship runs on stars and he needs all the stars he can get. The community is doing its best to provide fuel, but that's not enough. Our friend Five needs more stars to get him through this journey.
+
+You can help Five by giving a star to the [Meshery](https://github.com/meshery/meshery)!
+
+
+
+
+
+ 🌟 Star the Meshery repository 🌟
+
+
+
+
+
+
+
diff --git a/src/collections/blog/2023/12-13-k8s-1.29-release/index.mdx b/src/collections/blog/2023/12-13-k8s-1.29-release/index.mdx
index 9258146b0d18..83c488312a83 100644
--- a/src/collections/blog/2023/12-13-k8s-1.29-release/index.mdx
+++ b/src/collections/blog/2023/12-13-k8s-1.29-release/index.mdx
@@ -1,130 +1,130 @@
----
-title: Kubernetes 1.29 Highlights, Features, and Deprecations
-subtitle:
-date: 2023-12-13 08:00:00 -0530
-author: Lee Calcote
-thumbnail: ./kubernetes-new.webp
-darkthumbnail: ./kubernetes-new-dark.webp
-description: "Release Notes: What changed in Kubernetes 1.29?"
-type: Blog
-category: Kubernetes
-tags:
- - Kubernetes
-featured: false
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import Button from "../../../../reusecore/Button";
-
-
-
-As the final Kubernetes release of 2023, Kubernetes 1.29 is a new release of the popular container orchestration platform. It offers a number of new features and improvements that will help platform engineers and DevOps engineers manage their Kubernetes clusters more effectively. Here are some of the highlights of this release.
-
-
-
- As a longstanding CNCF member, Layer5 has donated two of its open source projects to the CNCF: Meshery and Cloud Native Performance. As an end-to-end, open-source, multi-cluster Kubernetes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
-
-
-
-While there are a number of enhancements tracked in this release (72), you need to be aware that a number of these are code freezes or deprecations in 1.29. In this article, we will focus on some highlighted enhancements, and important deprecations, so that you can be confident before upgrading your clusters.
-
-Let's breakdown new K8s features between networking and security categories.
-
-## Networking in Kubernetes 1.29
-
-### [Gateway API reaches 1.0](https://gateway-api.sigs.k8s.io) [Stable]
-
-The Gateway API has reached v1.0 in between Kubernetes 1.28 and 1.29. The Gateway API is the eventual successor to the Ingress API and significantly augments the Service API. The Kubernetes Service API is one of the oldest and most used APIs in Kubernetes. The Service API, in fact, was present in the very first public commit of Kubernetes in 2014, and almost everyone who deploys workloads in Kubernetes ends up using Services. Nearly ten years later in 2024, While Service API offers a kitchen sink full of functionality, it’s nearly ten year old design is limiting what can be done in Kubernetes networking.
-
-The Gateway API takes a fresh approach in offering expressive, extensible, and role-oriented interfaces. Gateway API is expressive and extensible in that it offers core support for advanced traffic management (like traffic weighting, header-based matching) that is only possible through customizations in Ingress API. Gateway API is role-oriented in that it defines three main roles: infrastructure provider, cluster operator, and application developer, who need to work together to use and configure Kubernetes service networking.
-
-
-### [Sidecar Containers](https://github.com/kubernetes/enhancements/issues/753) [Beta]
-
-The new sidecar feature enables restartable init containers and is available in alpha in Kubernetes 1.28. The concept of a “sidecar” has been part of Kubernetes since nearly the very beginning. Sidecar containers have become a common Kubernetes deployment pattern and are often used for network proxies or as part of a logging system. Until now, sidecars were a concept that Kubernetes users applied without native support. The lack of native support has caused some usage friction, which this enhancement aims to resolve.
-
-The new feature adds a new restartPolicy field to init containers that is available when the SidecarContainers feature gate is enabled. The field is optional and, if set, the only valid value is Always. Setting this field changes the behavior of init containers as follows: The container restarts if it exits. Any subsequent init container starts immediately after the startupProbe has successfully completed instead of waiting for the restartable init container to exit. The resource usage calculation changes for the pod as restartable init container resources are now added to the sum of the resource requests by the main containers. Pod termination continues to only depend on the main containers. An init container with a restartPolicy of Always (named a sidecar) won’t prevent the pod from terminating after the main containers exit.
-
-Beginning in Kubernetes 1.29, if your Pod includes one or more sidecar containers (init containers with an Always restart policy), the kubelet will delay sending the TERM signal to these sidecar containers until the last main container has fully terminated. The sidecar containers will be terminated in the reverse order they are defined in the Pod spec. This ensures that sidecar containers continue serving the other containers in the Pod until they are no longer needed.
-
-The behavior of this beta capability in 1.29 is that sidecar containers that have a `PreStop` hook will be notified when the Pod has begun terminating by executing the `PreStop` hook. Once the last primary container terminates, the last started sidecar container is notified by sending a `SIGTERM` signal. The next sidecar (in reverse order) is notified by sending a `SIGTERM` signal after the previous sidecar container terminates. This continues until all sidecar containers have terminated, or the Pod’s termination grace period expires. In the latter case, all remaining containers are notified by a `SIGTERM`, followed by a fixed grace period of 2 seconds and finally terminated. The Pod will be terminated after that.
-
-Note that slow termination of a main container will also delay the termination of the sidecar containers. If the grace period expires before the termination process is complete, the Pod may enter emergency termination. In this case, all remaining containers in the Pod will be terminated simultaneously with a short grace period.
-
-Similarly, if the Pod has a `preStop` hook that exceeds the termination grace period, emergency termination may occur. In general, if you have used `preStop` hooks to control the termination order without sidecar containers, you can now remove them and allow the kubelet to manage sidecar termination automatically.
-
-### [Transition SPDY to WebSockets](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4006-transition-spdy-to-websockets) [Alpha]
-
-This change aims to deprecate SPDY in favor of WebSockets for Kubernetes API server communications. WebSockets provide a more modern and scalable protocol that can improve the overall reliability and maintainability of Kubernetes communications. This can enhance security by making sure that the communication protocols used by Kubernetes are robust and well-supported.
-
-These general enhancements contribute to a more secure and efficient Kubernetes environment. By improving Kubernetes’ underlying reliability, performance, and operational control, the above features lay the groundwork for a more secure infrastructure platform capable of hosting sensitive and critical workloads.
-
-## Security in Kubernetes 1.29
-
-### [Ensure Secret Pulled Images](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2535-ensure-secret-pulled-images) [Alpha]
-
-Container images often contain sensitive components, making the security of image pull operations critical. The new alpha feature makes sure that images are always pulled using Kubernetes secrets of the Pod using them. This is important when Kubelet pulls an image for one Pod and another Pod is pointing to the same image. Up until now, the second Pod’s image request did not need authentication since it still used the first one’s credentials. This could lead to unauthorized access. By securing the image pull process, this enhancement prevents attackers from intercepting or tampering with container images, which is vital for maintaining the integrity of workloads.
-
-### [SignedSigning Release Artifacts](https://github.com/kubernetes/enhancements/issues/3031) [Beta]
-
-Every Kubernetes release produces a set of artifacts such as binaries, container images, documentation, and metadata. Since the 1.24 release, the artifacts have been signed as an alpha feature. In the 1.26 release, artifact signing graduates to beta to increase software supply chain security for the Kubernetes release process and mitigate man-in-the-middle attacks.
-
-### [Reduction of Secret-Based Service Account Tokens](https://github.com/kubernetes/enhancements/issues/2799) [Beta]
-
-`BoundServiceAccountTokenVolume` has been GA since version 1.22: Service account tokens for pods are obtained via the TokenRequest API and stored as a projected volume. The new enhancement, in beta, eliminates the need to auto-generate secret-based service account tokens. In addition, Kubernetes will warn about using auto-created secret-based service account tokens, and purge the unused ones.
-
-### [Reduction of Secret-Based Service Account Tokens](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2799-reduction-of-secret-based-service-account-token) [Beta]
-
-In addition to “Bound Service Account Token Improvements” enhancement and narrowing the scope of service account tokens, this improvement seeks to reduce the reliance on long-lived secret-based service account tokens. By limiting the use of these tokens, the potential attack surface is significantly diminished.
-
-This move aligns with the broader industry trend of short-lived, just-in-time credentials that minimize the chances of token leakage leading to unauthorized access.
-
-### [Structured Authentication Configuration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3221-structured-authorization-configuration) [Alpha]
-
-Similar to the authorization counterpart, Kubernetes 1.29 provides another alpha feature for structured configuration for authentication mechanisms. This enhancement offers users a more maintainable and secure approach to managing authentication, allowing administrators to implement complex authentication schemes more efficiently and with less room for error.
-
-With the new enhancement, it is now possible to configure multiple OIDC providers, clients, and validation rules:
-
-```yaml
-apiVersion: apiserver.config.k8s.io/v1alpha1
-kind: AuthenticationConfiguration
-jwt:
-- issuer:
- claimValidationRules:
- ...
- - expression: 'claims.exp - claims.nbf <= 86400'
- message: total token lifetime must not exceed 24 hours
- claimMappings:
- username:
- expression: 'claims.username + ":external-user"'
- groups:
- expression: 'claims.roles.split(",")'
- …
- userValidationRules:
- - expression: "!user.username.startsWith('system:')"
- message: username cannot used reserved system: prefix
- - expression: "user.groups.all(group, !group.startsWith('system:'))"
- message: groups cannot used reserved system: prefix
-```
-
-## Last Kubernetes release of 2023
-
-Kubernetes is an ever-evolving platform. For those of you running workloads on Kubernetes taking detailed note of API changes and enhancements is an important activity as you endeavour to keep your clusters upgraded with release releases. A more secure, scalable, and flexible Kubernetes is our collective goal. Dign into more details about deprecation, removals, and the latest changes in the 1.29 [release notes](https://relnotes.k8s.io/).
-
-On behalf of the Layer5 community and all of the CNCF projects that its contributors steward, thank you to everyone who participated in this Kubernetes release, and congratulations!
-
-As an end-to-end, open-source, multi-cluster Kuberentes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
-
-## What's ahead for Kubernetes in 2024?
-
-### AI/MLOps
-
-Generative AI came into the world with a big splash this year and helmsman, Kubernetes, is here helping navigate the AI waters. While some people suggest that the CNCF and Kubernetes ecosystem is in catch up mode in context of GenAI, they perhaps, forget that OpenAI is running a 7,500 node Kubernetes cluster in the development and hosting of GPT-3, CLIP, DALL·E, and research on other models. Where I think that Kubernetes and the CNCF can improve is in embracing and enabling AI/ML as a forerunner of our workload use cases. The CNCF has a massive developer ecosystem that will that can be enabled with MLOps and new model training projects like Kubeflow with its Kartib and KFServing sub-projects.
-
-### Looking past YAML
-
-DZone’s annual trend report on Kubernetes in the Enterprise has 55% of respondents identifying "Maintaining YAML files” as one of the more significant, ongoing pain-points in their experience with Kubernetes. In 2024, I’m looking forward to CNCF projects like Meshery addressing this pain-point with [a visual designer for Kubernetes](/cloud-native-management/meshmap) resource and workflow configuration. The inability for some developers to either be capable of or have time to comprehend the intricacies of their virtualized applications by staring at endless lines of YAML is poised to significantly improve in 2024.
-
+---
+title: Kubernetes 1.29 Highlights, Features, and Deprecations
+subtitle:
+date: 2023-12-13 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./kubernetes-new.webp
+darkthumbnail: ./kubernetes-new-dark.webp
+description: "Release Notes: What changed in Kubernetes 1.29?"
+type: Blog
+category: Kubernetes
+tags:
+ - Kubernetes
+featured: false
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import Button from "../../../../reusecore/Button";
+
+
+
+As the final Kubernetes release of 2023, Kubernetes 1.29 is a new release of the popular container orchestration platform. It offers a number of new features and improvements that will help platform engineers and DevOps engineers manage their Kubernetes clusters more effectively. Here are some of the highlights of this release.
+
+
+
+ As a longstanding CNCF member, Layer5 has donated two of its open source projects to the CNCF: Meshery and Cloud Native Performance. As an end-to-end, open-source, multi-cluster Kubernetes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
+
+
+
+While there are a number of enhancements tracked in this release (72), you need to be aware that a number of these are code freezes or deprecations in 1.29. In this article, we will focus on some highlighted enhancements, and important deprecations, so that you can be confident before upgrading your clusters.
+
+Let's breakdown new K8s features between networking and security categories.
+
+## Networking in Kubernetes 1.29
+
+### [Gateway API reaches 1.0](https://gateway-api.sigs.k8s.io) [Stable]
+
+The Gateway API has reached v1.0 in between Kubernetes 1.28 and 1.29. The Gateway API is the eventual successor to the Ingress API and significantly augments the Service API. The Kubernetes Service API is one of the oldest and most used APIs in Kubernetes. The Service API, in fact, was present in the very first public commit of Kubernetes in 2014, and almost everyone who deploys workloads in Kubernetes ends up using Services. Nearly ten years later in 2024, While Service API offers a kitchen sink full of functionality, it’s nearly ten year old design is limiting what can be done in Kubernetes networking.
+
+The Gateway API takes a fresh approach in offering expressive, extensible, and role-oriented interfaces. Gateway API is expressive and extensible in that it offers core support for advanced traffic management (like traffic weighting, header-based matching) that is only possible through customizations in Ingress API. Gateway API is role-oriented in that it defines three main roles: infrastructure provider, cluster operator, and application developer, who need to work together to use and configure Kubernetes service networking.
+
+
+### [Sidecar Containers](https://github.com/kubernetes/enhancements/issues/753) [Beta]
+
+The new sidecar feature enables restartable init containers and is available in alpha in Kubernetes 1.28. The concept of a “sidecar” has been part of Kubernetes since nearly the very beginning. Sidecar containers have become a common Kubernetes deployment pattern and are often used for network proxies or as part of a logging system. Until now, sidecars were a concept that Kubernetes users applied without native support. The lack of native support has caused some usage friction, which this enhancement aims to resolve.
+
+The new feature adds a new restartPolicy field to init containers that is available when the SidecarContainers feature gate is enabled. The field is optional and, if set, the only valid value is Always. Setting this field changes the behavior of init containers as follows: The container restarts if it exits. Any subsequent init container starts immediately after the startupProbe has successfully completed instead of waiting for the restartable init container to exit. The resource usage calculation changes for the pod as restartable init container resources are now added to the sum of the resource requests by the main containers. Pod termination continues to only depend on the main containers. An init container with a restartPolicy of Always (named a sidecar) won’t prevent the pod from terminating after the main containers exit.
+
+Beginning in Kubernetes 1.29, if your Pod includes one or more sidecar containers (init containers with an Always restart policy), the kubelet will delay sending the TERM signal to these sidecar containers until the last main container has fully terminated. The sidecar containers will be terminated in the reverse order they are defined in the Pod spec. This ensures that sidecar containers continue serving the other containers in the Pod until they are no longer needed.
+
+The behavior of this beta capability in 1.29 is that sidecar containers that have a `PreStop` hook will be notified when the Pod has begun terminating by executing the `PreStop` hook. Once the last primary container terminates, the last started sidecar container is notified by sending a `SIGTERM` signal. The next sidecar (in reverse order) is notified by sending a `SIGTERM` signal after the previous sidecar container terminates. This continues until all sidecar containers have terminated, or the Pod’s termination grace period expires. In the latter case, all remaining containers are notified by a `SIGTERM`, followed by a fixed grace period of 2 seconds and finally terminated. The Pod will be terminated after that.
+
+Note that slow termination of a main container will also delay the termination of the sidecar containers. If the grace period expires before the termination process is complete, the Pod may enter emergency termination. In this case, all remaining containers in the Pod will be terminated simultaneously with a short grace period.
+
+Similarly, if the Pod has a `preStop` hook that exceeds the termination grace period, emergency termination may occur. In general, if you have used `preStop` hooks to control the termination order without sidecar containers, you can now remove them and allow the kubelet to manage sidecar termination automatically.
+
+### [Transition SPDY to WebSockets](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4006-transition-spdy-to-websockets) [Alpha]
+
+This change aims to deprecate SPDY in favor of WebSockets for Kubernetes API server communications. WebSockets provide a more modern and scalable protocol that can improve the overall reliability and maintainability of Kubernetes communications. This can enhance security by making sure that the communication protocols used by Kubernetes are robust and well-supported.
+
+These general enhancements contribute to a more secure and efficient Kubernetes environment. By improving Kubernetes’ underlying reliability, performance, and operational control, the above features lay the groundwork for a more secure infrastructure platform capable of hosting sensitive and critical workloads.
+
+## Security in Kubernetes 1.29
+
+### [Ensure Secret Pulled Images](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2535-ensure-secret-pulled-images) [Alpha]
+
+Container images often contain sensitive components, making the security of image pull operations critical. The new alpha feature makes sure that images are always pulled using Kubernetes secrets of the Pod using them. This is important when Kubelet pulls an image for one Pod and another Pod is pointing to the same image. Up until now, the second Pod’s image request did not need authentication since it still used the first one’s credentials. This could lead to unauthorized access. By securing the image pull process, this enhancement prevents attackers from intercepting or tampering with container images, which is vital for maintaining the integrity of workloads.
+
+### [SignedSigning Release Artifacts](https://github.com/kubernetes/enhancements/issues/3031) [Beta]
+
+Every Kubernetes release produces a set of artifacts such as binaries, container images, documentation, and metadata. Since the 1.24 release, the artifacts have been signed as an alpha feature. In the 1.26 release, artifact signing graduates to beta to increase software supply chain security for the Kubernetes release process and mitigate man-in-the-middle attacks.
+
+### [Reduction of Secret-Based Service Account Tokens](https://github.com/kubernetes/enhancements/issues/2799) [Beta]
+
+`BoundServiceAccountTokenVolume` has been GA since version 1.22: Service account tokens for pods are obtained via the TokenRequest API and stored as a projected volume. The new enhancement, in beta, eliminates the need to auto-generate secret-based service account tokens. In addition, Kubernetes will warn about using auto-created secret-based service account tokens, and purge the unused ones.
+
+### [Reduction of Secret-Based Service Account Tokens](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2799-reduction-of-secret-based-service-account-token) [Beta]
+
+In addition to “Bound Service Account Token Improvements” enhancement and narrowing the scope of service account tokens, this improvement seeks to reduce the reliance on long-lived secret-based service account tokens. By limiting the use of these tokens, the potential attack surface is significantly diminished.
+
+This move aligns with the broader industry trend of short-lived, just-in-time credentials that minimize the chances of token leakage leading to unauthorized access.
+
+### [Structured Authentication Configuration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3221-structured-authorization-configuration) [Alpha]
+
+Similar to the authorization counterpart, Kubernetes 1.29 provides another alpha feature for structured configuration for authentication mechanisms. This enhancement offers users a more maintainable and secure approach to managing authentication, allowing administrators to implement complex authentication schemes more efficiently and with less room for error.
+
+With the new enhancement, it is now possible to configure multiple OIDC providers, clients, and validation rules:
+
+```yaml
+apiVersion: apiserver.config.k8s.io/v1alpha1
+kind: AuthenticationConfiguration
+jwt:
+- issuer:
+ claimValidationRules:
+ ...
+ - expression: 'claims.exp - claims.nbf <= 86400'
+ message: total token lifetime must not exceed 24 hours
+ claimMappings:
+ username:
+ expression: 'claims.username + ":external-user"'
+ groups:
+ expression: 'claims.roles.split(",")'
+ …
+ userValidationRules:
+ - expression: "!user.username.startsWith('system:')"
+ message: username cannot used reserved system: prefix
+ - expression: "user.groups.all(group, !group.startsWith('system:'))"
+ message: groups cannot used reserved system: prefix
+```
+
+## Last Kubernetes release of 2023
+
+Kubernetes is an ever-evolving platform. For those of you running workloads on Kubernetes taking detailed note of API changes and enhancements is an important activity as you endeavour to keep your clusters upgraded with release releases. A more secure, scalable, and flexible Kubernetes is our collective goal. Dign into more details about deprecation, removals, and the latest changes in the 1.29 [release notes](https://relnotes.k8s.io/).
+
+On behalf of the Layer5 community and all of the CNCF projects that its contributors steward, thank you to everyone who participated in this Kubernetes release, and congratulations!
+
+As an end-to-end, open-source, multi-cluster Kuberentes management platform, Meshery makes Day 2 Kubernetes cluster management a breeze. Run Meshery to explore the behavorial changes of this Kubernetes release and what they really mean to you.
+
+## What's ahead for Kubernetes in 2024?
+
+### AI/MLOps
+
+Generative AI came into the world with a big splash this year and helmsman, Kubernetes, is here helping navigate the AI waters. While some people suggest that the CNCF and Kubernetes ecosystem is in catch up mode in context of GenAI, they perhaps, forget that OpenAI is running a 7,500 node Kubernetes cluster in the development and hosting of GPT-3, CLIP, DALL·E, and research on other models. Where I think that Kubernetes and the CNCF can improve is in embracing and enabling AI/ML as a forerunner of our workload use cases. The CNCF has a massive developer ecosystem that will that can be enabled with MLOps and new model training projects like Kubeflow with its Kartib and KFServing sub-projects.
+
+### Looking past YAML
+
+DZone’s annual trend report on Kubernetes in the Enterprise has 55% of respondents identifying "Maintaining YAML files” as one of the more significant, ongoing pain-points in their experience with Kubernetes. In 2024, I’m looking forward to CNCF projects like Meshery addressing this pain-point with [a visual designer for Kubernetes](/cloud-native-management/meshmap) resource and workflow configuration. The inability for some developers to either be capable of or have time to comprehend the intricacies of their virtualized applications by staring at endless lines of YAML is poised to significantly improve in 2024.
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/2023-05-12-k8s-nodeports/index.mdx b/src/collections/blog/2023/2023-05-12-k8s-nodeports/index.mdx
new file mode 100644
index 000000000000..fa4ec58baa5f
--- /dev/null
+++ b/src/collections/blog/2023/2023-05-12-k8s-nodeports/index.mdx
@@ -0,0 +1,75 @@
+---
+title: Kubernetes NodePorts - Static and Dynamic Assignments
+subtitle: Avoiding Port Collisions
+date: 2023-05-12 08:00:00 -0530
+author: Lee Calcote
+thumbnail: ./k8s-nodeports.webp
+darkthumbnail: ./k8s-nodeports.webp
+description: "Avoiding Port Collisions with Kubernetes NodePorts Static and Dynamic Assignments"
+type: Blog
+category: Kubernetes
+tags:
+ - Kubernetes
+ - Networking
+featured: false
+published: true
+---
+
+
+
+Kubernetes provides a Service to offer a unified traffic endpoint for the Pods. While it offers a VIP to the clients for access and Kubernetes ensures traffic balancing for the accessing back-end Pods, it has a limitation of routing traffic from outside the cluster. The Kubernetes Service setting of "NodePort" was created to overcome this issue.
+
+By setting up a mapping to a specific port of all nodes in the cluster, a NodePort Service redirects traffic from the outside to the inside of the cluster. When a NodePort Service is created, Kubernetes control plane allocates its corresponding ports in two ways. The first is dynamic, where Kubernetes control plane automatically assigns an unused port at the creation time. The second is static, which assigns a port within the nodeport port range configuration. It is crucial to assign a unique nodePort across the entire cluster while manually assigning nodePort, or it will result in an error if a service of type NodePort already uses that port.
+
+Sometimes, there is a need to run a NodePort Service on well-known ports so that other components and users inside or outside the cluster can use them. In such cases, users need to reserve the required ports before using them. Kubernetes 1.27 introduced a new feature gate "ServiceNodePortStaticSubrange" that allows users to use a different port allocation strategy for type NodePort Services. Enabling this feature gate will divide the port range for NodePort Services based on a formula that uses nodeport size and determines the size of the static port range.
+
+Here are a few examples of different port ranges and their band offset values:
+
+
+| Range properties | Values |
+| --- | --- |
+| service-node-port-range | 30000-32767 |
+| Band Offset | 86 |
+| Static band start | 30000 |
+| Static band end | 30085 |
+| Dynamic band start | 30086 |
+| Dynamic band end | 32767 |
+
+
+
+
+
+| Range properties | Values |
+| --- | --- |
+| service-node-port-range | 30000-30015 |
+| Band Offset | 16 |
+| Static band start | 30000 |
+| Static band end | 30015 |
+| Dynamic band start | N/A |
+| Dynamic band end | N/A |
+
+
+
+NodePort Services can be useful in many scenarios. For example, consider a user that needs to expose a Minio object storage service on Kubernetes to clients running outside the Kubernetes cluster. The agreed port is 30009, and the user needs to create a Service as follows:
+
+```
+apiVersion: v1
+kind: Service
+metadata:
+ name: minio
+spec:
+ ports:
+ - name: api
+ nodePort: 30009
+ port: 9000
+ protocol: TCP
+ targetPort: 9000
+ selector:
+ app: minio
+ type: NodePort
+```
+If the port required for the Minio Service is not reserved and another NodePort (or possibly LoadBalancer) Service is created and dynamically allocated before or concurrently with the Minio Service, the TCP port 30009 might be allocated to that other Service. In this case, creation of the Minio Service will fail due to a node port collision.
+
+In conclusion, using the NodePort Service will help Kubernetes users by allowing traffic to be routed from outside to inside the cluster, providing a unified traffic endpoint for the Pods. By enabling the ServiceNodePortStaticSubrange feature gate, users can adopt a different port allocation strategy, reducing the risk of collisions while using a different range of ports.
+
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/2023-05-12-k8s-nodeports/k8s-nodeports.webp b/src/collections/blog/2023/2023-05-12-k8s-nodeports/k8s-nodeports.webp
new file mode 100644
index 000000000000..01d1c3874307
Binary files /dev/null and b/src/collections/blog/2023/2023-05-12-k8s-nodeports/k8s-nodeports.webp differ
diff --git a/src/collections/blog/2023/2023-09-05-unlocking-the-power-of-webassembly-in-service-mesh-management/intel-colorMode.svg b/src/collections/blog/2023/2023-09-05-unlocking-the-power-of-webassembly-in-service-mesh-management/intel-colorMode.svg
new file mode 100644
index 000000000000..bca5f01992ae
--- /dev/null
+++ b/src/collections/blog/2023/2023-09-05-unlocking-the-power-of-webassembly-in-service-mesh-management/intel-colorMode.svg
@@ -0,0 +1,22 @@
+
\ No newline at end of file
diff --git a/src/collections/blog/2023/2023-09-05-unlocking-the-power-of-webassembly-in-service-mesh-management/intel_white.svg b/src/collections/blog/2023/2023-09-05-unlocking-the-power-of-webassembly-in-service-mesh-management/intel_white.svg
new file mode 100644
index 000000000000..d6a81ebf3b8f
--- /dev/null
+++ b/src/collections/blog/2023/2023-09-05-unlocking-the-power-of-webassembly-in-service-mesh-management/intel_white.svg
@@ -0,0 +1,26 @@
+
\ No newline at end of file
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
index e8d96eddfc20..f3bab4b222b1 100644
--- 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
@@ -1,60 +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!**_
-
-
+---
+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
+---
+
+
+
+
+
+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
index 19dc42b45414..594b802a646c 100644
--- 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
@@ -1,155 +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.
-
+---
+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-24-open-container-image-meshery/index.mdx b/src/collections/blog/2024/02-24-open-container-image-meshery/index.mdx
index f1ebe479f5ed..c6bb34298ea5 100644
--- 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
@@ -1,92 +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.
-
-
-
-
+---
+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/03-10-demystifying-open-source/index.mdx b/src/collections/blog/2024/03-10-demystifying-open-source/index.mdx
index 26c2dd2550be..b4d5e7c4f825 100644
--- a/src/collections/blog/2024/03-10-demystifying-open-source/index.mdx
+++ b/src/collections/blog/2024/03-10-demystifying-open-source/index.mdx
@@ -1,103 +1,106 @@
----
-title: Demystifying Open Source
-subtitle: A Personal Journey and Insights into Getting Started
-date: 2024-03-10 08:00:00 -0530
-author: Sandra Ashipala
-thumbnail: ./banner.png
-darkthumbnail: ./banner.png
-description: "Demystifying Open Source"
-type: Blog
-category: Open Source
-tags:
- - Open Source
-featured: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import FIVE from './meshery-skateboard.png';
-import MESHERY from './meshery-issues.png';
-import STAR from './star-meshery.png';
-import STACK from './tech-stack.png';
-import GITHUB from './github-issues.png';
-import SEARCH from './search-layer5.png';
-
-
-
-
-Picture this: You're honing your tech skills in silos (⌒_⌒;) and building projects for your GitHub and resume to impress the ever-inquisitive technical hiring manager who seeks the unique aspects in projects provided by potential candidates. Along your learning journey, you've encountered mentions of open source here and there, but never delved deeply into its realm. Additionally, you find yourself uncertain about where to begin. Does this sound familiar? Not long ago, I found myself in precisely this situation.
-
-However, with the right community and a sprinkle of courage (and chipping away at my own imposter syndrome), I found my footing and embarked on an exhilarating journey of growth and contribution.
-
-In this blog post, I'll not only share my personal experiences and insights but also provide guidance based on my initial experience for those eager to dip their toes into the vast world of open-source contributions. So, grab a cup of your favourite beverage (latte macchiato☕ or bubble tea 🧋 for me), settle in, and let's embark on an adventure filled with learning, growth, and community.
-
-
-### Getting Started: Choosing a project to contribute toes
-
-
- Are you feeling overwhelmed (⋟﹏⋞) by the multitude of open-source projects available? Don't fret; here are some tips to guide you in finding a project that aligns with your interests for your contributions (⌒‿⌒) :
-
-
-
Search GitHub for "good-first-issues": GitHub is a treasure chest of open-source projects, and many of them tag beginner-friendly issues with labels like "good-first-issue" or "help-wanted." Simply head to GitHub, use the search bar to look for these labels, and you'll find a list of tasks waiting for eager contributors like yourself.
-
Explore Projects Related to Your Tech Stack: Leverage your expertise by searching GitHub for projects using keywords related to your tech stack. Utilizing the sort functionality you can filter through projects by Most stars, Recently updated, Best match etc. Whether it's i.e Python, C, or React.js, there's a project out there waiting for your unique skill set.
-
-
-
-
Websites with a list of open source projects: Websites like Good First Issue curate easy pickings from popular open-source projects, making it easier than ever to find your first contribution opportunity. Browse through their listings, pick a project that piques your interest, and dive in!
-
-
Another valuable approach involved searching LinkedIn for profiles of individuals possessing similar skills or expertise to mine. By examining the projects they were involved in and conducting further research. This method provided insights into relevant projects and served as a catalyst in discovering the Meshery project, which I will delve into further later on.
-
-
-
-### What skills do I need to get started?
-
-
The short answer? Whatever you bring to the table! Open source thrives on diversity, and contributions come in a variety of ways based on the contributors skill sets and their level. If you're eager to learn and collaborate, you're already halfway there. Start by exploring the repository, familiarise yourself with the tools used to build it, and don't hesitate to ask for guidance along the way.
-
-
-
-
For example, Layer5 is host to a vast variety of projects built and designed using different technologies and skill sets from people located all over the world (yay version control ┌(˘⌣˘)ʃ ), keep in mind that contribution goes beyond code. Whether you're a UX/UI designer, a technical writer, an SEO specialist, or a passionate blogger, there's a place for you in the community. Explore the repositories, find where your skills align, and dive in.
-
-### My Open Source Journey: From Curiosity to Contribution
-
-
- Let me rewind to the genesis of it all — during a Women Who Code Berlin webinar in April 2023, where a fellow attendee posed a question that the invited speaker graciously answered in detail during the Q&A session. As the speaker delved into the advantages of contributing to open-source projects, she highlighted the EddieHub Open Source community as an inclusive and welcoming environment. And Eddie, the founder, standing out as one of the most enthusiastic and supportive open-source leaders (a big shout out to Ellie King! ), igniting my interest.
-
-
-
Intrigued, I delved into the community (even before the webinar ended), joined their Discord, and found the BioDrop (formerly LinkFree) project, a shining example of a community-driven project, characterized by its meticulous organization and comprehensive documentation. I was pleasantly surprised by Eddie's active involvement and encouragement to get started no matter the level of contribution (yes I read the conversation history -- "reading the room").
-
As my understanding of the open-source community deepened and my proficiency in Python programming and understanding of DevOps grew, I felt compelled to explore opportunities where my newly acquired skills could be put to meaningful use and provide avenues for continuous improvement. This pursuit ultimately led me to encounter Meshery, nestled within the CNCF ecosystem.
-
With Meshery, I didn't just find another open source project; I found a community, a platform for learning and growth, and the perfect avenue for channelling my newfound skills and passions into meaningful contributions. And so, my journey with Meshery under the Layer5 organization began, marking the dawn of an exciting chapter in my open-source journey.
-
-### How to Get Started with Meshery - Making your first contributions:
-
Before we dive deeper, allow me to introduce Meshery. It serves as an open-source, cloud-native management platform, providing multi-cluster Kubernetes management functionalities. Notably, Meshery has been acknowledged as the 10th fastest-growing project out of over 200+ Cloud Native Computing Foundation (CNCF) projects. It seamlessly integrates with all CNCF projects, alongside existing tools and Kubernetes clusters, enabling users to optimize their preferred monitoring, CI/CD, and security solutions with ease.
-
Now that you've been introduced to Meshery, you might be wondering how you can get involved. Here are some steps to kickstart your journey with Meshery:
-
-
Explore the website: Start by visiting the Meshery website to gain a better understanding of its features and capabilities. You'll find comprehensive documentation, tutorials, and resources to help you get started.
-
Join the community: Connect with fellow Meshery enthusiasts by joining the community forums, mailing lists, and social media channels. Engage in discussions in the #meshery Slack channel, ask clarifying questions, and share your experiences with the community.
-
Contribute to the repository: Regardless of your experience level, there are numerous opportunities to make valuable contributions to the repository. Begin by familiarizing yourself with the CONTRIBUTING.md guidelines. Don't hesitate to ask questions for clarification and seek assistance from the community when needed (the discussion forum is a good place to do this too).
-Start small by identifying issues labeled "good-first-issues" or bugs marked as "beginner-friendly," and tailor your involvement within the project to align with your interests. As you explore the project and associated resources, and notice areas for improvement such as grammar adjustments, refining code segments, fixing a logo/banner or enhancing installation steps based on your initial experience, don't hesitate to raise an issue. Remember, every contribution, no matter how minor, has the potential to make a meaningful impact.
-
-
-
-
-
Attend events: Keep an eye out for development meetings that happen online every week. These meets are a great way to learn from community members, network with like-minded individuals, and stay updated on the latest developments with projects in Layer5. If you're new to the community the Layer5 Newcomers' meet (as of now happens every Thursday - sync the community calendar to get a reminder in your local time) is a great place to get your first introductions to the community, meet other folks and get introduced to the community/projects flow!
-
-
-
-
-
The steps described above were simply how I approached my first few weeks in the community. Initially, I spent the first few days quietly observing conversations in Slack, akin to "reading the room," to understand the community's communication style, how to start engaging in the conversations and determine if it was a place where I could engage and thrive (if you haven't guessed by now - it is and beyond).
-
-
-💡In Layer5, I discovered more than just a collection of projects; it's a supportive network of like-minded individuals with a shared mission to innovate and empower. The Layer5 community fosters an environment where contribution isn't merely encouraged; it's celebrated. If you find the Meshery project interesting, consider starring 🌟 the repository to show your support!
-
-
-
-
-### Reflections on Personal and Professional Growth
-
My journey into open source has been nothing short of transformative. From honing technical skills to cultivating soft skills like communication and collaboration, every contribution has been a stepping stone toward personal and professional growth. But the real challenge? It was transitioning from solitary learning and development to learning/building in public. Being part of welcoming and supportive open-source communities has been instrumental in overcoming that hurdle and taking those crucial first steps into learning and building in public and ultimately contributing to my growth as an engineer/developer.
-
In a healthy open-source community, you're not just a contributor; you're part of something bigger. You collaborate with like-minded individuals, tackle real-world problems, and make a tangible impact on projects that transcend individual efforts. We get to forge new meaningful connections and share knowledge. So, whether you're just starting out or looking to expand your horizons, remember this: the journey is yours to chart, so just get started. “jiāyóu” 加油 !!
-
+---
+title: Demystifying Open Source
+subtitle: A Personal Journey and Insights into Getting Started
+date: 2024-03-10 08:00:00 -0530
+author: Sandra Ashipala
+thumbnail: ./banner.png
+darkthumbnail: ./banner.png
+description: "Demystifying Open Source"
+type: Blog
+category: Open Source
+tags:
+ - Open Source
+featured: true
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import FIVE from "./meshery-skateboard.png";
+import MESHERY from "./meshery-issues.png";
+import STAR from "./star-meshery.png";
+import STACK from "./tech-stack.png";
+import GITHUB from "./github-issues.png";
+import SEARCH from "./search-layer5.png";
+
+
+
+
+Picture this: You're honing your tech skills in silos (⌒_⌒;) and building projects for your GitHub and resume to impress the ever-inquisitive technical hiring manager who seeks the unique aspects in projects provided by potential candidates. Along your learning journey, you've encountered mentions of open source here and there, but never delved deeply into its realm. Additionally, you find yourself uncertain about where to begin. Does this sound familiar? Not long ago, I found myself in precisely this situation.
+
+However, with the right community and a sprinkle of courage (and chipping away at my own imposter syndrome), I found my footing and embarked on an exhilarating journey of growth and contribution.
+
+In this blog post, I'll not only share my personal experiences and insights but also provide guidance based on my initial experience for those eager to dip their toes into the vast world of open-source contributions. So, grab a cup of your favourite beverage (latte macchiato☕ or bubble tea 🧋 for me), settle in, and let's embark on an adventure filled with learning, growth, and community.
+
+
+### Getting Started: Choosing a project to contribute toes
+
+
+ Are you feeling overwhelmed (⋟﹏⋞) by the multitude of open-source projects available? Don't fret; here are some tips to guide you in finding a project that aligns with your interests for your contributions (⌒‿⌒) :
+
+
+
Search GitHub for "good-first-issues": GitHub is a treasure chest of open-source projects, and many of them tag beginner-friendly issues with labels like "good-first-issue" or "help-wanted." Simply head to GitHub, use the search bar to look for these labels, and you'll find a list of tasks waiting for eager contributors like yourself.
+
Explore Projects Related to Your Tech Stack: Leverage your expertise by searching GitHub for projects using keywords related to your tech stack. Utilizing the sort functionality you can filter through projects by Most stars, Recently updated, Best match etc. Whether it's i.e Python, C, or React.js, there's a project out there waiting for your unique skill set.
+
+
+
+
Websites with a list of open source projects: Websites like Good First Issue curate easy pickings from popular open-source projects, making it easier than ever to find your first contribution opportunity. Browse through their listings, pick a project that piques your interest, and dive in!
+
+
Another valuable approach involved searching LinkedIn for profiles of individuals possessing similar skills or expertise to mine. By examining the projects they were involved in and conducting further research. This method provided insights into relevant projects and served as a catalyst in discovering the Meshery project, which I will delve into further later on.
+
+
+
+### What skills do I need to get started?
+
+
The short answer? Whatever you bring to the table! Open source thrives on diversity, and contributions come in a variety of ways based on the contributors skill sets and their level. If you're eager to learn and collaborate, you're already halfway there. Start by exploring the repository, familiarise yourself with the tools used to build it, and don't hesitate to ask for guidance along the way.
+
+
+
+
For example, Layer5 is host to a vast variety of projects built and designed using different technologies and skill sets from people located all over the world (yay version control ┌(˘⌣˘)ʃ ), keep in mind that contribution goes beyond code. Whether you're a UX/UI designer, a technical writer, an SEO specialist, or a passionate blogger, there's a place for you in the community. Explore the repositories, find where your skills align, and dive in.
+
+### My Open Source Journey: From Curiosity to Contribution
+
+
+ Let me rewind to the genesis of it all — during a Women Who Code Berlin webinar in April 2023, where a fellow attendee posed a question that the invited speaker graciously answered in detail during the Q&A session. As the speaker delved into the advantages of contributing to open-source projects, she highlighted the EddieHub Open Source community as an inclusive and welcoming environment. And Eddie, the founder, standing out as one of the most enthusiastic and supportive open-source leaders (a big shout out to Ellie King!), igniting my interest.
+
+
+
Intrigued, I delved into the community (even before the webinar ended), joined their Discord, and found the BioDrop (formerly LinkFree) project, a shining example of a community-driven project, characterized by its meticulous organization and comprehensive documentation. I was pleasantly surprised by Eddie's active involvement and encouragement to get started no matter the level of contribution (yes I read the conversation history -- "reading the room").
+
As my understanding of the open-source community deepened and my proficiency in Python programming and understanding of DevOps grew, I felt compelled to explore opportunities where my newly acquired skills could be put to meaningful use and provide avenues for continuous improvement. This pursuit ultimately led me to encounter Meshery, nestled within the CNCF ecosystem.
+
With Meshery, I didn't just find another open source project; I found a community, a platform for learning and growth, and the perfect avenue for channelling my newfound skills and passions into meaningful contributions. And so, my journey with Meshery under the Layer5 organization began, marking the dawn of an exciting chapter in my open-source journey.
+
+### How to Get Started with Meshery - Making your first contributions:
+
Before we dive deeper, allow me to introduce Meshery. It serves as an open-source, cloud-native management platform, providing multi-cluster Kubernetes management functionalities. Notably, Meshery has been acknowledged as the 10th fastest-growing project out of over 200+ Cloud Native Computing Foundation (CNCF) projects. It seamlessly integrates with all CNCF projects , alongside existing tools and Kubernetes clusters, enabling users to optimize their preferred monitoring, CI/CD, and security solutions with ease.
+
Now that you've been introduced to Meshery, you might be wondering how you can get involved. Here are some steps to kickstart your journey with Meshery:
+
+
+ Explore the website: Start by visiting the Meshery website to gain a better understanding of its features and capabilities. You'll find comprehensive documentation, tutorials, and resources to help you get started.
+
+
+ Join the community: Connect with fellow Meshery enthusiasts by joining the community forums, mailing lists, and social media channels. Engage in discussions in the #meshery Slack channel, ask clarifying questions, and share your experiences with the community.
+
+
+ Contribute to the repository: Regardless of your experience level, there are numerous opportunities to make valuable contributions to the repository. Begin by familiarizing yourself with the CONTRIBUTING.md guidelines. Don't hesitate to ask questions for clarification and seek assistance from the community when needed (the discussion forum is a good place to do this too).
+ Start small by identifying issues labeled "good-first-issues" or bugs marked as "beginner-friendly," and tailor your involvement within the project to align with your interests. As you explore the project and associated resources, and notice areas for improvement such as grammar adjustments, refining code segments, fixing a logo/banner or enhancing installation steps based on your initial experience, don't hesitate to raise an issue. Remember, every contribution, no matter how minor, has the potential to make a meaningful impact.
+
+
+
Attend events: Keep an eye out for development meetings that happen online every week. These meets are a great way to learn from community members, network with like-minded individuals, and stay updated on the latest developments with projects in Layer5. If you're new to the community the Layer5 Newcomers' meet (as of now happens every Thursday - sync the community calendar to get a reminder in your local time) is a great place to get your first introductions to the community, meet other folks and get introduced to the community/projects flow!
+
+
+
+
+
The steps described above were simply how I approached my first few weeks in the community. Initially, I spent the first few days quietly observing conversations in Slack, akin to "reading the room," to understand the community's communication style, how to start engaging in the conversations and determine if it was a place where I could engage and thrive (if you haven't guessed by now - it is and beyond).
+
+
+💡In Layer5, I discovered more than just a collection of projects; it's a supportive network of like-minded individuals with a shared mission to innovate and empower. The Layer5 community fosters an environment where contribution isn't merely encouraged; it's celebrated. If you find the Meshery project interesting, consider starring 🌟 the repository to show your support!
+
+
+
+
+### Reflections on Personal and Professional Growth
+
My journey into open source has been nothing short of transformative. From honing technical skills to cultivating soft skills like communication and collaboration, every contribution has been a stepping stone toward personal and professional growth. But the real challenge? It was transitioning from solitary learning and development to learning/building in public. Being part of welcoming and supportive open-source communities has been instrumental in overcoming that hurdle and taking those crucial first steps into learning and building in public and ultimately contributing to my growth as an engineer/developer.
+
In a healthy open-source community, you're not just a contributor; you're part of something bigger. You collaborate with like-minded individuals, tackle real-world problems, and make a tangible impact on projects that transcend individual efforts. We get to forge new meaningful connections and share knowledge. So, whether you're just starting out or looking to expand your horizons, remember this: the journey is yours to chart, so just get started. “jiāyóu” 加油 !!
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.
@@ -31,17 +31,17 @@ In Meshery, two key concepts play a pivotal role in managing infrastructure and
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.
+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 standardized packages that bundle components and characterize their relationships. Components are often representative of infrastructure, but can, in fact, represent anything (see semantically meaningful vs non-semantically meaingful components). Models uniformly wrap each component with a layer of metadata therein standardizing all entities (infrasturcture or otherwise) under a common interface much in the same way that the Industrial Revolution offered consistency of parts and interchangability of machinery, Meshery Components become fundamental building blocks. Components are like standard Lego bricks, window pieces, wheels that all snap together - or don't - depending upon way in which they relate to one another.
+
Meshery Models are standardized packages that bundle components and characterize their relationships. Components are often representative of infrastructure, but can, in fact, represent anything (see semantically meaningful vs non-semantically meaingful components). Models uniformly wrap each component with a layer of metadata therein standardizing all entities (infrasturcture or otherwise) under a common interface much in the same way that the Industrial Revolution offered consistency of parts and interchangability of machinery, Meshery Components become fundamental building blocks. Components are like standard Lego bricks, window pieces, wheels that all snap together - or don't - depending upon way in which they relate to one another.
As versioned and portable pacakges, Models provide a structured, reusable, and extensible way to represent infrastructure components and their relationships, going beyond just code. This enables a more flexible and adaptable approach to modeling complex systems. are powerful Relationships and policies. contain 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.
+
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.
Streamline your Docker Compose workflow and gain powerful visualization and lifecycle management for your multi-container applications with the Docker Meshery Extension. This extension seamlessly integrates Meshery, a service management platform, with Docker, allowing you to effortlessly import, deploy, visualize, and manage your Docker Compose applications.
-
-
-
-
Effortless Import: Docker Compose as Meshery Design
-
-
Get started quickly by importing your existing Docker Compose applications directly into Meshery. The extension streamlines the process, eliminating the need for manual configuration. Simply navigate to Meshery and leverage the intuitive UI to import your Compose file. Meshery intelligently parses the file, recognizing your application's components and dependencies.
-
-
Import your existing designs and existing infrastructure configurations into Meshery. The platform supports a variety of application definition formats, and you can import designs using either the Meshery CLI or the Meshery UI.
-Before you can use the Meshery CLI to import a Docker Compose app, you must first install it. You can install Meshery CLI by following the instructions.
-
-
-Step 2: Import the Design Manifest
-
-Once you have created your Design Definition file, you can use the Meshery CLI to import your Docker Compose app into Meshery. To do this, run the following command:
-
-```shell
-mesheryctl pattern import -f [file/url] -s [source-type]
-```
-
-This command enable users to import their existing designs from sources as
-
-- Helm Charts
-- Kubernetes Manifests
-- Docker Compose
-
-**Example :**
-
-```shell
-mesheryctl pattern import -f docker-compose.yaml -s "Docker Compose"
-```
-
-
-
-### Seamless Deployment to Kubernetes
-
-
With your application imported, take advantage of Meshery's robust deployment capabilities. Deploy your multi-container application to a Kubernetes cluster with a single click. Meshery handles the intricacies of the deployment process, ensuring your application runs smoothly within your Kubernetes environment.
-
-### Visualize Your Application with MeshMap
-
-Gain valuable insights into your application's health and performance with MeshMap, Meshery's interactive service graph. MeshMap provides a clear visual representation of your application's architecture, allowing you to easily identify dependencies and potential bottlenecks.
-
-### Interactive Management with MeshMap
-
-[MeshMap](/cloud-native-management/meshmap) empowers you to manage your application directly within the visualized service graph. The web-based interactive terminal integrated with MeshMap grants you the ability to execute commands on individual containers or services within your application. This eliminates the need to switch between different tools or terminals, streamlining troubleshooting and management tasks.
-
-## Seamless Integration with Docker: A Powerful Partnership
-
-
-
-
The Docker Meshery Extension fosters a powerful collaboration between Layer5 and Docker. Leveraging the familiarity and widespread adoption of Docker Compose, the extension empowers you to harness the advanced management and visualization capabilities of Meshery. This translates to a more efficient and streamlined workflow for managing your multi-container applications.
-
-Get Started Today
-
-
Experience the power and ease of the Docker Meshery Extension. Download the extension from Docker Hub and start streamlining your multi-container application development and management today.
-
-
+---
+title: Simplify Multi-container Application Management with the Docker Meshery Extension
+subtitle: Multi-Cluster Kubernetes Deployments of Docker Compose Apps
+date: 2024-04-25
+author: Layer5 Team
+thumbnail: ../../../../assets/images/dockercompose-logo/dockercompose-logo.webp
+darkthumbnail: ../../../../assets/images/dockercompose-logo/dockercompose-logo.webp
+description: "Simplify Multi-container Application Management with the Docker Meshery Extension"
+type: Blog
+category: Docker
+tags:
+ - Meshery
+ - Docker
+featured: false
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import Button from "../../../../reusecore/Button";
+import DockerLogo from "../../../../assets/images/partners/docker.svg";
+import dockercompose_logo from "../../../../assets/images/dockercompose-logo/dockercompose-logo.webp";
+
+
+
+Experience the power and ease of the Docker Meshery Extension. Download the extension from Docker Hub and start streamlining your multi-container application development and management today.
+
+
+
Streamline your Docker Compose workflow and gain powerful visualization and lifecycle management for your multi-container applications with the Docker Meshery Extension. This extension seamlessly integrates Meshery, a service management platform, with Docker, allowing you to effortlessly import, deploy, visualize, and manage your Docker Compose applications.
+
+
+
+
Effortless Import: Docker Compose as Meshery Design
+
+
Get started quickly by importing your existing Docker Compose applications directly into Meshery. The extension streamlines the process, eliminating the need for manual configuration. Simply navigate to Meshery and leverage the intuitive UI to import your Compose file. Meshery intelligently parses the file, recognizing your application's components and dependencies.
+
+
Import your existing designs and existing infrastructure configurations into Meshery. The platform supports a variety of application definition formats, and you can import designs using either the Meshery CLI or the Meshery UI.
+Before you can use the Meshery CLI to import a Docker Compose app, you must first install it. You can install Meshery CLI by following the instructions.
+
+
+Step 2: Import the Design Manifest
+
+Once you have created your Design Definition file, you can use the Meshery CLI to import your Docker Compose app into Meshery. To do this, run the following command:
+
+```shell
+mesheryctl pattern import -f [file/url] -s [source-type]
+```
+
+This command enable users to import their existing designs from sources as
+
+- Helm Charts
+- Kubernetes Manifests
+- Docker Compose
+
+**Example :**
+
+```shell
+mesheryctl pattern import -f docker-compose.yaml -s "Docker Compose"
+```
+
+
+
+### Seamless Deployment to Kubernetes
+
+
With your application imported, take advantage of Meshery's robust deployment capabilities. Deploy your multi-container application to a Kubernetes cluster with a single click. Meshery handles the intricacies of the deployment process, ensuring your application runs smoothly within your Kubernetes environment.
+
+### Visualize Your Application with MeshMap
+
+Gain valuable insights into your application's health and performance with MeshMap, Meshery's interactive service graph. MeshMap provides a clear visual representation of your application's architecture, allowing you to easily identify dependencies and potential bottlenecks.
+
+### Interactive Management with MeshMap
+
+[MeshMap](/cloud-native-management/meshmap) empowers you to manage your application directly within the visualized service graph. The web-based interactive terminal integrated with MeshMap grants you the ability to execute commands on individual containers or services within your application. This eliminates the need to switch between different tools or terminals, streamlining troubleshooting and management tasks.
+
+## Seamless Integration with Docker: A Powerful Partnership
+
+
+
+
The Docker Meshery Extension fosters a powerful collaboration between Layer5 and Docker. Leveraging the familiarity and widespread adoption of Docker Compose, the extension empowers you to harness the advanced management and visualization capabilities of Meshery. This translates to a more efficient and streamlined workflow for managing your multi-container applications.
+
+Get Started Today
+
+
Experience the power and ease of the Docker Meshery Extension. Download the extension from Docker Hub and start streamlining your multi-container application development and management today.
+
+
diff --git a/src/collections/blog/2024/06-21-meshery-5000-star-milestone/index.mdx b/src/collections/blog/2024/06-21-meshery-5000-star-milestone/index.mdx
index c79de33d2127..7f0658af05b1 100644
--- a/src/collections/blog/2024/06-21-meshery-5000-star-milestone/index.mdx
+++ b/src/collections/blog/2024/06-21-meshery-5000-star-milestone/index.mdx
@@ -1,153 +1,153 @@
----
-title: Meshery's 5,000 Star Milestone
-subtitle: Meshery soars past 5,000 stars on GitHub!
-date: 2024-06-20 08:00:00 -0530
-author: Sandra Ashipala
-thumbnail: ./banner.jpeg
-darkthumbnail: ./banner.jpeg
-description: "Celebrating Meshery's 5,000 GitHub Star Milestone"
-type: Blog
-category: Announcements
-tags:
- - Announcements
- - Meshery
- - Layer5
-featured: true
-published: true
----
-
-import { BlogWrapper } from "../../Blog.style.js";
-import { Link } from "gatsby";
-import STAR from './star-meshery.png';
-import STATS from './meshery-stats.png';
-import LFX from './lfx-mentorship.png';
-import GRAPH from './star-history.png';
-import Blockquote from "../../../../reusecore/Blockquote";
-import BlockquoteAlt from "../../../../reusecore/Blockquote/Blockquote-alt-style";
-
-
-
-## A Journey of Growth and Community
-
-
- Achieving key milestones in open source reflects the combined efforts of passionate individuals and forward-thinking development. Today, we are thrilled to announce that Meshery, a leading project under the Layer5 umbrella, has reached a significant milestone: 5,000 stars 🌟 on GitHub! This achievement is more than just a number; it represents the collective efforts of our vibrant community, the dedication of our contributors, and the transformative journey that Meshery has embarked upon.
-
-
-
- Let's take a moment to reflect on this journey, celebrate the people behind it, and look forward to the exciting future ahead.
-
-
-## The Genesis of Meshery
-
-
- Meshery was born out of a simple yet ambitious idea: to create an open source, cloud native management platform that simplifies and enhances the experience of managing Kubernetes environments. The vision was to build a tool that integrates seamlessly with all CNCF projects, providing users with unparalleled control over their multi-cluster Kubernetes deployments.
-
-
-
- From its inception, Meshery was designed with the user in mind. It aimed to provide a robust and intuitive interface for managing service meshes, enabling users to optimize their monitoring, CI/CD, and security solutions effortlessly. With a focus on user experience and community-driven development, Meshery quickly gained traction within the open-source community.
-
-
-## Who is Meshery For?
-
-
- Meshery is for everyone passionate about cloud-native technologies. Whether you're a DevOps engineer looking to streamline your Kubernetes management, a developer seeking to optimize your CI/CD pipelines, or a cloud enthusiast eager to explore the intricacies of service meshes, Meshery offers something valuable for you.
-
-
-
-Our diverse community includes individuals from all walks of life—seasoned professionals, enthusiastic beginners, and everyone in between. This diversity is our strength, fostering a rich environment where ideas flourish, and innovation thrives.
-
-
-## Celebrating the Community
-
-
- Reaching 5,000 stars on GitHub is a testament to the incredible contributions from our community. Each star, each pull request, and each issue raised has played a part in shaping Meshery into the powerful tool it is today.
-
-
-#### A Heartfelt Thank You
-
-
- To our contributors, thank you for your unwavering dedication. Your code contributions, documentation improvements, bug reports, and feature requests have been instrumental in Meshery's growth.
-
-
-
-
-
- We extend our deepest gratitude to each of you.
-
-
-#### Acknowledging the CNCF
-
-
- We are also proud to share that Meshery is the 10th fastest-growing project within the Cloud Native Computing Foundation (CNCF) by contributor count, among over 200 projects. This recognition is a significant milestone and a validation of our vision and efforts. Meshery has been proposed for incubation within CNCF, marking another exciting chapter in our journey.
-
-
-
-
-## Meshery: Leading in Open Source
-
-
-Meshery has garnered significant attention within the open-source community and stands out as a cornerstone program under the Linux Foundation. Its popularity stems from its ability to simplify and enhance cloud-native management, integrating seamlessly with CNCF projects for optimized Kubernetes environment management.
-
-
-#### Why Meshery Stands Out
-
-
-
Integration and Compatibility: Meshery's seamless integration with CNCF projects ensures comprehensive management capabilities across multi-cluster Kubernetes deployments, enhancing operational efficiency and scalability.
-
Community-Driven Innovation: Embracing community-driven development, Meshery empowers a global network of contributors to collaborate on enhancing functionality, reliability, and user experience, fostering continuous innovation.
-
Educational Leadership: Meshery's educational initiatives, including workshops and webinars, cultivate industry best practices and empower users to maximize their cloud-native potential, contributing to a skilled workforce.
-
Prestigious Position: As the most popular Linux Foundation program, Meshery's leadership within CNCF and its widespread adoption underscore its pivotal role in advancing cloud-native technologies and standards.
-
-
-
-
-## The Road Ahead: Inviting New Contributors
-
-
As we celebrate this milestone, we also recognize that this is just the beginning. The journey ahead is filled with opportunities for growth, learning, and innovation. We invite you—yes, you!—to join us in this exciting adventure.
-
-#### How to Get Started
-
-
-
Explore the Website: Visit the Meshery website to understand its features and capabilities. The comprehensive documentation, tutorials, and resources are great starting points.
-
Join the Community: Engage with fellow Meshery enthusiasts on our community forums, mailing lists, and social media channels. Join the conversations in the #meshery Slack channel, ask questions, and share your experiences.
-
Contribute to the Repository: There are numerous opportunities to contribute, regardless of your experience level. Start by familiarizing yourself with the CONTRIBUTING.md guidelines. Look for issues labeled "good-first-issue" or "beginner-friendly," and start small.
-
Attend Events: Participate in our online development meetings, and don't miss the Layer5 Newcomers' meet. Sync the community calendar to get reminders for these events.
-
-
-#### Reflections on the Journey
-
-
- For many, contributing to Meshery has been more than a technical endeavor; it has been a personal and professional growth journey.
-
-{" "}
-
-{" "}
-
- Each contribution, big or small, has been a stepping stone, enhancing technical prowess and fostering essential soft skills like communication and collaboration.
-
-
-
-
-## The Journey Has Just Begun
-
-
As we look back on our achievements, we are filled with gratitude and excitement for the future.
-
-
With new features, enhancements, and community engagements on the horizon, there are endless opportunities to make a meaningful impact. We invite you to be a part of this journey. Join us in shaping the future of cloud-native management with Meshery. Together, we can achieve great things.
-
-
Thank you for your support, and happy contributing!
-
-
+---
+title: Meshery's 5,000 Star Milestone
+subtitle: Meshery soars past 5,000 stars on GitHub!
+date: 2024-06-20 08:00:00 -0530
+author: Sandra Ashipala
+thumbnail: ./banner.jpeg
+darkthumbnail: ./banner.jpeg
+description: "Celebrating Meshery's 5,000 GitHub Star Milestone"
+type: Blog
+category: Announcements
+tags:
+ - Announcements
+ - Meshery
+ - Layer5
+featured: true
+published: true
+---
+
+import { BlogWrapper } from "../../Blog.style.js";
+import { Link } from "gatsby";
+import STAR from "./star-meshery.png";
+import STATS from "./meshery-stats.png";
+import LFX from "./lfx-mentorship.png";
+import GRAPH from "./star-history.png";
+import Blockquote from "../../../../reusecore/Blockquote";
+import BlockquoteAlt from "../../../../reusecore/Blockquote/Blockquote-alt-style";
+
+
+
+## A Journey of Growth and Community
+
+
+ Achieving key milestones in open source reflects the combined efforts of passionate individuals and forward-thinking development. Today, we are thrilled to announce that Meshery, a leading project under the Layer5 umbrella, has reached a significant milestone: 5,000 stars 🌟 on GitHub! This achievement is more than just a number; it represents the collective efforts of our vibrant community, the dedication of our contributors, and the transformative journey that Meshery has embarked upon.
+
+
+
+ Let's take a moment to reflect on this journey, celebrate the people behind it, and look forward to the exciting future ahead.
+
+
+## The Genesis of Meshery
+
+
+ Meshery was born out of a simple yet ambitious idea: to create an open source, cloud native management platform that simplifies and enhances the experience of managing Kubernetes environments. The vision was to build a tool that integrates seamlessly with all CNCF projects, providing users with unparalleled control over their multi-cluster Kubernetes deployments.
+
+
+
+ From its inception, Meshery was designed with the user in mind. It aimed to provide a robust and intuitive interface for managing service meshes, enabling users to optimize their monitoring, CI/CD, and security solutions effortlessly. With a focus on user experience and community-driven development, Meshery quickly gained traction within the open-source community.
+
+
+## Who is Meshery For?
+
+
+ Meshery is for everyone passionate about cloud-native technologies. Whether you're a DevOps engineer looking to streamline your Kubernetes management, a developer seeking to optimize your CI/CD pipelines, or a cloud enthusiast eager to explore the intricacies of service meshes, Meshery offers something valuable for you.
+
+
+
+Our diverse community includes individuals from all walks of life—seasoned professionals, enthusiastic beginners, and everyone in between. This diversity is our strength, fostering a rich environment where ideas flourish, and innovation thrives.
+
+
+## Celebrating the Community
+
+
+ Reaching 5,000 stars on GitHub is a testament to the incredible contributions from our community. Each star, each pull request, and each issue raised has played a part in shaping Meshery into the powerful tool it is today.
+
+
+#### A Heartfelt Thank You
+
+
+ To our contributors, thank you for your unwavering dedication. Your code contributions, documentation improvements, bug reports, and feature requests have been instrumental in Meshery's growth.
+
+
+
+
+
+ We extend our deepest gratitude to each of you.
+
+
+#### Acknowledging the CNCF
+
+
+ We are also proud to share that Meshery is the 10th fastest-growing project within the Cloud Native Computing Foundation (CNCF) by contributor count, among over 200 projects. This recognition is a significant milestone and a validation of our vision and efforts. Meshery has been proposed for incubation within CNCF, marking another exciting chapter in our journey.
+
+
+
+
+## Meshery: Leading in Open Source
+
+
+Meshery has garnered significant attention within the open-source community and stands out as a cornerstone program under the Linux Foundation. Its popularity stems from its ability to simplify and enhance cloud-native management, integrating seamlessly with CNCF projects for optimized Kubernetes environment management.
+
+
+#### Why Meshery Stands Out
+
+
+
Integration and Compatibility: Meshery's seamless integration with CNCF projects ensures comprehensive management capabilities across multi-cluster Kubernetes deployments, enhancing operational efficiency and scalability.
+
Community-Driven Innovation: Embracing community-driven development, Meshery empowers a global network of contributors to collaborate on enhancing functionality, reliability, and user experience, fostering continuous innovation.
+
Educational Leadership: Meshery's educational initiatives, including workshops and webinars, cultivate industry best practices and empower users to maximize their cloud-native potential, contributing to a skilled workforce.
+
Prestigious Position: As the most popular Linux Foundation program, Meshery's leadership within CNCF and its widespread adoption underscore its pivotal role in advancing cloud-native technologies and standards.
+
+
+
+
+## The Road Ahead: Inviting New Contributors
+
+
As we celebrate this milestone, we also recognize that this is just the beginning. The journey ahead is filled with opportunities for growth, learning, and innovation. We invite you—yes, you!—to join us in this exciting adventure.
+
+#### How to Get Started
+
+
+
Explore the Website: Visit the Meshery website to understand its features and capabilities. The comprehensive documentation, tutorials, and resources are great starting points.
+
Join the Community: Engage with fellow Meshery enthusiasts on our community forums, mailing lists, and social media channels. Join the conversations in the #meshery Slack channel, ask questions, and share your experiences.
+
Contribute to the Repository: There are numerous opportunities to contribute, regardless of your experience level. Start by familiarizing yourself with the CONTRIBUTING.md guidelines. Look for issues labeled "good-first-issue" or "beginner-friendly," and start small.
+
Attend Events: Participate in our online development meetings, and don't miss the Layer5 Newcomers' meet. Sync the community calendar to get reminders for these events.
+
+
+#### Reflections on the Journey
+
+
+ For many, contributing to Meshery has been more than a technical endeavor; it has been a personal and professional growth journey.
+
+{" "}
+
+{" "}
+
+ Each contribution, big or small, has been a stepping stone, enhancing technical prowess and fostering essential soft skills like communication and collaboration.
+
+
+
+
+## The Journey Has Just Begun
+
+
As we look back on our achievements, we are filled with gratitude and excitement for the future.
+
+
With new features, enhancements, and community engagements on the horizon, there are endless opportunities to make a meaningful impact. We invite you to be a part of this journey. Join us in shaping the future of cloud-native management with Meshery. Together, we can achieve great things.
+
+
Thank you for your support, and happy contributing!
Continuing in our Meet the Maintainer series, we have Xin Huang. Xin is a maintainer of the Cloud Native Performance project. In this interview, we get to know Xin a little better and learn about his journey as an open source project maintainer and with Layer5 community.
-
+
Layer5 Team:
Xin, thank you for joining me today. Many people inside and outside of the Layer5 Community have seen the effects of your contributions, but may not know the backstory as to who Xin is and how you arrived at your maintainer role. Indulge us. How did you discover the Layer5 community? What made you stay?
-
+
Xin:
- I’m working around Service Mesh Acceleration in Intel, and noticed the Service Mesh Performance project. So I attended the community meeting, the community is very active and welcoming and they hope for feedback and contribution from me. It’s the main reason that made me stay here and contribute continuously.
+ "I’m working around Service Mesh Acceleration in Intel, and noticed the Service Mesh Performance project. So I attended the community meeting, the community is very active and welcoming and they hope for feedback and contribution from me. It’s the main reason that made me stay here and contribute continuously."
-
+
Layer5 Team:
Have you worked with any other open source project? How does Layer5 community compare?
-
+
Xin:
-
Yes, I’ve worked with some open source projects. Layer5 community knows how to cultivate and fulfill the sprint of open source. If you are a newcomer to open source, you can get a big leg up from the Layer5 community.
+
“Yes, I’ve worked with some open source projects. Layer5 community knows how to cultivate and fulfill the sprint of open source. If you are a newcomer to open source, you can get a big leg up from the Layer5 community."
-
+
Layer5 Team:
What is so fascinating about service meshes? Why are you focused on this technology specifically?
-
+
Xin:
- First, I’m working on Service Mesh Acceleration at Intel. Second, service mesh is a hot area this year, more and more people or enterprises are trying service mesh in their production.
+ “First, I’m working on Service Mesh Acceleration at Intel. Second, service mesh is a hot area this year, more and more people or enterprises are trying service mesh in their production."
-
Service Mesh is the bridge between developers and infrastructure, how fascinating it is to build such a thing that benefits everyone.
+
“Service Mesh is the bridge between developers and infrastructure, how fascinating it is to build such a thing that benefits everyone.“
-
+
Layer5 Team:
Layer5 projects has a number of active, open source projects. You’ve been consistently contributing to a few of them. Which one(s) are you currently focusing on?
-
+
Xin:
- I’m focusing on the SMP project, because it’s related to my working scope. I also use Meshery to manage our service mesh environment and show our effort on Service Mesh acceleration. Every project has its specific goal, I can’t tell which one is the best.
+ “I’m focusing on the SMP project, because it’s related to my working scope. I also use Meshery to manage our service mesh environment and show our effort on Service Mesh acceleration. Every project has its specific goal, I can’t tell which one is the best."
-
+
Layer5 Team:
What is your favorite Meshery CLI command?
-
+
Xin:
- Having worked on and been a user of Meshery's performance characterization features, I'm biased. I like the `mesheryctl perf` command the most.
+ "Having worked on and been a user of Meshery's performance characterization features, I'm biased. I like the `mesheryctl perf` command the most."
-
+
Layer5 Team:
Where do you see Service Mesh Performance, Nighthawk, and Meshery heading?
-
+
Xin:
- Meshery has a great dream to manage all the popular service mesh projects. It's a great idea for infrastructure & platform managers who are confused with so many different projects to try and understand their differences.
+ “Meshery has a great dream to manage all the popular service mesh projects. It's a great idea for infrastructure & platform managers who are confused with so many different projects to try and understand their differences."
-
+
Layer5 Team:
What is your hot tip for working with Service Mesh Performance, Nighthawk, or Meshery that others may not know?
-
+
Xin:
- We have a distributed performance characterization feature upcoming in Meshery in which Nighthawk will be externalized. Meshery manages the lifecycle of Nighthawk, using Nighthawk as one of its load generators to run performance benchmarks. As Nighthawk supports an adaptive load control as a feature, Meshery can leverage this to build a custom load controller to run performance benchmarks.
+ "We have a distributed performance characterization feature upcoming in Meshery in which Nighthawk will be externalized. Meshery manages the lifecycle of Nighthawk, using Nighthawk as one of its load generators to run performance benchmarks. As Nighthawk supports an adaptive load control as a feature, Meshery can leverage this to build a custom load controller to run performance benchmarks."
+
-
By default, the adaptive load controller in Nighthawk runs benchmarks with different RPS values and based on the latency, it adjusts the RPS value. But, with its custom plugin ability, we can bring in our own inputs as well as metrics to measure.
+
"By default, the adaptive load controller in Nighthawk runs benchmarks with different RPS values and based on the latency, it adjusts the RPS value. But, with its custom plugin ability, we can bring in our own inputs as well as metrics to measure."
-
With the metrics from these tests, Meshery should also adjust the resiliency characteristics of the mesh automatically so as to improve these metrics and in turn improve performance. Meshery allows users to generate traffic load tests using Nighthawk. The tests are controlled and provisioned using meshery-nighthawk, a Meshery component supporting multiple load generators. This is a very powerful feature that is coming up in Meshery.
-
+
+ "With the metrics from these tests, Meshery should also adjust the resiliency characteristics of the mesh automatically so as to improve these metrics and in turn improve performance. Meshery allows users to generate traffic load tests using Nighthawk. The tests are controlled and provisioned using meshery-nighthawk, a Meshery component supporting multiple load generators. This is a very powerful feature that is coming up in Meshery."
+
-
-Layer5 Team:
Do you have any advice for individuals hopeful to become Layer5 contributors or potentially maintainers?
-
+
+Layer5 Team:
Do you have any advice for individuals hopeful to become Layer5 contributors or potentially maintainers?
+
-
+
Xin:
-
Yes! I think that being a maintainer requires a combination of technical expertise, community engagement, and leadership skills. Start by being a consistent contributor yourself. Demonstrate your commitment by making regular and valuable contributions to the projects. You'll need to build a strong understanding of the technologies and the codebase. In order to demonstrate your technical leadership, you'll need to show initiative, take ownership of tasks, and often do the menial work that other contributors may not want to do.
+
"Yes! I think that being a maintainer requires a combination of technical expertise, community engagement, and leadership skills. Start by being a consistent contributor yourself. Demonstrate your commitment by making regular and valuable contributions to the projects. You'll need to build a strong understanding of the technologies and the codebase. In order to demonstrate your technical leadership, you'll need to show initiative, take ownership of tasks, and often do the menial work that other contributors may not want to do."
-
One aspect of being a maintainer is actively participating in the Layer5 community, helping newcomers, and engaging in helping advance project discussions. Guiding and supporting other contributors is an expecation of a maintainer, so it's important to have a good understanding of the project and the technologies involved.
+
"One aspect of being a maintainer is actively participating in the Layer5 community, helping newcomers, and engaging in helping advance project discussions. Guiding and supporting other contributors is an expecation of a maintainer, so it's important to have a good understanding of the project and the technologies involved."
-
Finally, I wholeheartedly suggest that you are not afraid to ask questions. The Layer5 community is welcoming and supportive. The existing maintainers are individuals who have given their time and demonstrated their dedication to the betterment of the projects. They are a valuable resource for you to learn from, too, so when you engage with them, be respectful of their time - be sure to have done your homework before asking questions.
+
Finally, I wholeheartedly suggest that you are not afraid to ask questions. The Layer5 community is welcoming and supportive. The existing maintainers are individuals who have given their time and demonstrated their dedication to the betterment of the projects. They are a valuable resource for you to learn from, too, so when you engage with them, be respectful of their time - be sure to have done your homework before asking questions."
-
-Layer5 Team:
In other words, whether your contribution is big or small, it sounds like aiming for high-quality contributions that add value to the projects is key.
+
+Layer5 Team:
In other words, whether your contribution is big or small, it sounds like aiming for high-quality contributions that add value to the projects is key.
+
-
+
Xin:
-
Yes, that's right. It's important to remember that the Layer5 community is a diverse group of individuals with different backgrounds, experiences, and perspectives. Remember to have fun and enjoy the process of learning, contributing, and collaborating with the community.
+
"Yes, that's right. It's important to remember that the Layer5 community is a diverse group of individuals with different backgrounds, experiences, and perspectives. Remember to have fun and enjoy the process of learning, contributing, and collaborating with the community."
-
The Meshery project moves at an impressive pace thanks to maintainers like Xin. Be like Xin. Join the Layer5 Slack and say “hi".
+
The Meshery project moves at an impressive pace thanks to maintainers like Xin. Be like Xin. Join the Layer5 Slack and say “hi".
\ No newline at end of file
diff --git a/src/collections/blog/2024/09-08-meet-the-maintainer-hussaina-begum/post.mdx b/src/collections/blog/2024/09-08-meet-the-maintainer-hussaina-begum/post.mdx
index a7ac5543a4d2..1266643f156e 100644
--- a/src/collections/blog/2024/09-08-meet-the-maintainer-hussaina-begum/post.mdx
+++ b/src/collections/blog/2024/09-08-meet-the-maintainer-hussaina-begum/post.mdx
@@ -23,7 +23,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Continuing in our Meet the Maintainer series, we have{" "}
Hussaina Begum, Staff Engineer at VMware. Hussaina
@@ -34,7 +34,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
Hussaina, thank you for joining me today. Many people inside and outside of
@@ -45,7 +45,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
I wanted to contribute to open source for a long time and finally made up
@@ -60,7 +60,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
You’re a Meshery Maintainer and have been for some long time now. What does
@@ -68,7 +68,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
Lots of learning. Though I started out small in Meshery with a
@@ -77,7 +77,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
Layer5 projects has a number of active, open
@@ -87,7 +87,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
I have contributed to mesheryctl, meshkit and meshery.io projects so far,
@@ -95,46 +95,46 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
What’s the coolest Meshery demo you have done/seen?
-
+
Hussaina:
The Meshery Playground is an awesome system and a something of a hidden gem in cloud native ecosystem. I also remember the `mesheryctl perf` CLI demo I have done on the Meshery office hours from one of the Kubecon events and am proud of this. Kudos to all the contributors of `mesheryctl` command development and refactors.
-
+
Vivek:
What do you anticipate will be Meshery’s biggest announcement this year?
-
+
Hussaina:
Meshery project moving to Incubating status! 🙂
-
+
Vivek:
What is your favorite Meshery CLI command?
-
+
Hussaina:
mesheryctl system start
-
+
Vivek:
What is your hot tip for working with Meshery that others may not know?
-
+
Hussaina:
Use Slack effectively and leverage discuss forum, talk to MeshMates and
@@ -142,7 +142,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
What are some personal goals for the next year with respect to the Meshery
@@ -150,7 +150,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
Work on the long pending `system config` CLI improvements and contribute to
@@ -158,7 +158,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
Interesting. Do expand on that: What do you think Meshery could offer in
@@ -166,12 +166,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
Labs designed in a way that they work with local resources.
-
+
Vivek:
Your most often used emoji? Your preference: movie or book? Morning person
@@ -180,7 +180,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
eyes emoji. My preference is a book compared to a movie. I am a Night Owl
@@ -191,7 +191,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
The cloud native ecosystem moves quickly. Keeping up with all the
@@ -199,7 +199,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
I like listening to kubernetes podcasts and I follow the internal slack
@@ -211,7 +211,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
Do you have any advice for individuals hopeful to become Layer5 contributors
@@ -219,7 +219,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hussaina:
Show up and attend the meetings which align with your expertise and areas
@@ -229,7 +229,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
The Meshery project moves at an impressive pace thanks to maintainers like
diff --git a/src/collections/blog/2024/09-27-meet-the-maintainer-aisuko-li/post.mdx b/src/collections/blog/2024/09-27-meet-the-maintainer-aisuko-li/post.mdx
index 1d07776600b4..6489c1b7acdb 100644
--- a/src/collections/blog/2024/09-27-meet-the-maintainer-aisuko-li/post.mdx
+++ b/src/collections/blog/2024/09-27-meet-the-maintainer-aisuko-li/post.mdx
@@ -23,7 +23,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Continuing in our Meet the Maintainer series, we have{" "}
Aisuko Li. Aisuko is a
@@ -35,7 +35,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Aisuko, thank you for joining me today. Many people inside and outside of
@@ -46,7 +46,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aisuko:
Thanks for having me here. Actually, Aisuko is my code name. My real name is Bowen Li. I love both of
@@ -63,7 +63,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
You’ve been consistently contributing to a large number of Layer5 projects
@@ -73,7 +73,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aisuko:
Actually, the Meshery project in 2021-2022 has changed a lot. More skilled and
@@ -88,14 +88,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Have you worked with any other open source projects? How does Layer5 compare?
-
+
Aisuko:
I was active in the Rancher community and the Helm charts project, where I owned
@@ -112,12 +112,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Fascinating. Why did you pick service meshes specifically, though?
-
+
Aisuko:
I have worked with many middle- and small-sized companies that wanted to migrate
@@ -129,7 +129,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Haha. Leading on from that, what should Meshery dream about next? What can we hope
@@ -137,7 +137,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aisuko:
I once talked to Lee, the founder of Layer5. Due to time zone differences, we don’t
@@ -153,14 +153,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Interesting. Do expand on that. What do you think Meshery could offer, in addition to what it already does?
-
+
Aisuko:
I believe we can offer a CNCF-standard performance tool for all service mesh
@@ -170,12 +170,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
What are today's challenges when working with service meshes?
-
+
Aisuko:
Even though service mesh has many features, it's still not always stable in production.
@@ -187,14 +187,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
That’s good to hear. What do you think we should look forward to with respect to service mesh development?
-
+
Aisuko:
I’ve worked with service mesh applications like Linkerd2, Istio, and OSM in development environments. OSM is my preference because it’s modular and has a simpler architecture compared to others.
@@ -205,7 +205,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Ah, while I have you here, let me get more reading recommendations lined up.
@@ -215,7 +215,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aisuko:
People are always interested in new technology, but we are limited by time. I believe
@@ -228,14 +228,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
What does being a Meshery maintainer mean to you? How has being a maintainer impacted your full-time role?
-
+
Aisuko:
It’s an honor to be a maintainer of the Meshery community. The membership
@@ -245,7 +245,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Anita:
Do you have any advice for individuals hoping to become Layer5 contributors
@@ -253,7 +253,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aisuko:
The Layer5 and Meshery communities are always welcoming to everyone.
@@ -266,7 +266,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
The Meshery project moves at an impressive pace thanks to maintainers like
diff --git a/src/collections/blog/2024/10-22-meet-the-maintainer-aadhitya-amarendiran/post.mdx b/src/collections/blog/2024/10-22-meet-the-maintainer-aadhitya-amarendiran/post.mdx
index 4c1d851741be..c8e2972c72f5 100644
--- a/src/collections/blog/2024/10-22-meet-the-maintainer-aadhitya-amarendiran/post.mdx
+++ b/src/collections/blog/2024/10-22-meet-the-maintainer-aadhitya-amarendiran/post.mdx
@@ -23,7 +23,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Continuing in our Meet the Maintainer series, we have{" "}
Aadhitya Amarendiran. Aadhitya
@@ -34,21 +34,21 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Vivek:
Aadhitya, thank you for joining me today. Many people inside and outside of the Layer5 Community have seen the effects of your contributions, but may not know the backstory as to who Aadhitya is and how you arrived at your maintainer role. Indulge us. How did you discover the Layer5 community? What made you stay?
-
+
Aadhitya:
It was around the year 2020 when I was a sophomore and explored many things in the field of open source. I got to know about Meshery via the LFX program and tried applying for it, though I was a newcomer at that time. Later, I learned more about Layer5, started attending the community call, and met the community. The community members helped me a lot wherever I got stuck as a newcomer, which made me learn new things and involve myself in the project, which later helped me grow. Oh, of course, great learning sessions from Lee during development and community calls.
-
+
Vivek:
You’re a Meshery Maintainer and have been for some long time now. What does
@@ -56,26 +56,26 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aadhitya:
Three things come into my mind: Learning lots of new things, Challenging yourself to your limits and being a helpful navigator for contributors. During my time as a newcomer, I started out with a simple readme fix PR in the Meshery project, which I thought would cause less impact. But the maintainers accepted my PR though it’s a very small one. That instilled a feeling in me that I should give back to the community by helping newcomers and contributors whenever they are stuck in work.
-
+
Vivek:
Have you worked with any other open source project? How does Layer5 compare?
-
+
Aadhitya:
Not a lot, but I worked on quite a few open source projects. Layer5 is one of the best places to start if you are new to open source. By being involved in the community, you will feel and understand the spirit of open source.
-
+
Vivek:
Layer5 projects have a number of active, open
@@ -84,62 +84,62 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aadhitya:
I currently work on Meshery, as it piqued my interest during my initial days. I also work on the Meshery-SMP GitHub action project as well.
-
+
Vivek:
What’s the coolest Meshery demo you have done/seen?
-
+
Aadhitya:
I’ve seen a lot of demos but the coolest one for me is the Meshery Docker extension where you can start and use Meshery right from DockerHub!
-
+
Vivek:
What is your favorite Meshery CLI Command?
-
+
Aadhitya:
Oof! That’s a tricky one. But my favorite one is definitely mesheryctl perf
-
+
Vivek:
What is your hot tip for working with Meshery that others may not know?
-
+
Aadhitya:
If you’re starting out with Meshery, make sure to use the Meshery Playground if you want to get hands-on for the first time without the need to deploy Meshery in your system. After you get the basics right, install Meshery and log in to your deployed instance. You’ll see that your designs, performance test results and configurations remain intact in your instance as if they are present exactly the same in the Playground. There’s no need to start from scratch. Just continue where you left off!
-
+
Vivek:
Where do you see opportunities for contributors to get involved within Meshery and Layer5 community?
-
+
Aadhitya:
Considering the fact that Meshery is now a part of CNCF (especially the fact that we are aiming for the Incubation status as well!), I feel that Meshery has a wide range of scope for contributors to be involved in. Whether you’re an expert or a newbie, Meshery has lots of subdomains to contribute. Documentation, Frontend, Backend, Adapters… the list goes on.
-
+
Vivek:
Your most often used emoji? Your preference: movie or book? Morning person
@@ -148,14 +148,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aadhitya:
Most used emoji: 😎. I’m a morning person usually and sleep early, but sometimes I’m a night owl when it comes to intense work. I’d prefer movies compared to books as for some they clearly adapt from books. I’ve worked on refactoring the mesheryctl pattern command to mesheryctl design without losing the core features present. This took me a bit of time as I had to balance my current work as well which caused a bit of inactivity. But I managed to complete it, and I’m proud of doing such great work!
-
+
Vivek:
Do you have any advice for individuals hopeful to become Layer5 contributors
@@ -163,28 +163,28 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Aadhitya:
Make your presence stand out from the crowd even if you are a beginner, and learn as much as you can. Seek MeshMates and maintainers if you get stuck in something. Ask questions during meets or in Slack, and get feedback on your PRs, doesn’t matter if it’s big or small. Incorporate feedback and improvise. Remember, communication is the key, and be active!
-
+
Vivek:
In other words, whether your contribution is big or small, it sounds like aiming for high-quality contributions that add value to the projects is key.
-
+
Aadhitya:
Yes, you got it right! Even the smallest contribution which creates a good impact in a project becomes a great factor in Open source. All that matters is perseverance, challenging yourself to limits and learning. Do these things right and you’ll find yourself growing in the community.
-
+
The Meshery project moves at an impressive pace thanks to maintainers like
diff --git a/src/collections/blog/2024/11-01-meet-the-maintainer-yash-sharma/post.mdx b/src/collections/blog/2024/11-01-meet-the-maintainer-yash-sharma/post.mdx
index 78d3c60418e8..5495a17349a9 100644
--- a/src/collections/blog/2024/11-01-meet-the-maintainer-yash-sharma/post.mdx
+++ b/src/collections/blog/2024/11-01-meet-the-maintainer-yash-sharma/post.mdx
@@ -23,7 +23,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Continuing in our Meet the Maintainer series, we have{" "}
Yash Sharma. Yash is a
@@ -33,7 +33,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
Yash, thank you for joining me today. Many people inside and outside of the
@@ -44,7 +44,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Yash:
Thanks for having me, Hargun, I got into open source about two years ago,
@@ -63,14 +63,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
You’re a Meshery maintainer and have been for some long time now. What does being a Meshery maintainer mean to you?
-
+
Yash:
Honestly, being a maintainer is about taking responsibility for a big part
@@ -82,14 +82,14 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
Have you worked with any other open source project? How does Layer5 compare?
-
+
Yash:
I’ve contributed to other open source projects, but I didn’t really get a
@@ -102,7 +102,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
Layer5 projects have a number of active, open
@@ -111,7 +111,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Yash:
Absolutely, Layer5 has a number of active open source projects, and I’ve
@@ -120,12 +120,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
What’s the coolest Meshery demo you have done/seen?
-
+
Yash:
Haha good one, this year I got a chance to represent Meshery at KubeCon
@@ -135,12 +135,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
What is your favorite feature in Meshery UI?
-
+
Yash:
Meshery is an extensible platform and I like this feature of it, it gives Meshery a whole new powerful capability to interact with various
@@ -149,12 +149,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
What is your hot tip for working with Meshery that others may not know?
-
+
Yash:
I definitely encourage you to join the meetings. They’re a great way to
@@ -165,7 +165,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
Where do you see opportunities for contributors to get involved within
@@ -173,7 +173,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Yash:
Meshery is growing very fast, it is the 9th fastest growing project under
@@ -193,7 +193,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
Your most often used emoji? Your preference: movie or book? Morning person
@@ -202,7 +202,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Yash:
I’d definitely recommend reading 'Six Easy Pieces' by Richard Feynman. It’s
@@ -210,7 +210,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
Do you have any advice for individuals hopeful to become Layer5 contributors
@@ -218,7 +218,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Yash:
Good question, I’d say think about the long-term. People are more likely to
@@ -230,7 +230,7 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Hargun:
In other words, whether your contribution is big or small, it sounds like
@@ -238,12 +238,12 @@ import ForkLift from "../../../../assets/images/app/hero/forklift.svg";
-
+
Yash:
You summarized it perfectly, yes I agree with you Hargun.
-
+
The Meshery project moves at an impressive pace thanks to maintainers like
diff --git a/src/collections/blog/2024/11-10-kubecon-na-2024/post.mdx b/src/collections/blog/2024/11-10-kubecon-na-2024/post.mdx
index 69dda7e6fe3b..4c36e6748750 100644
--- a/src/collections/blog/2024/11-10-kubecon-na-2024/post.mdx
+++ b/src/collections/blog/2024/11-10-kubecon-na-2024/post.mdx
@@ -43,7 +43,7 @@ Human-Computer Interaction Principles in Meshery:
-
+
Date: November 12, 2024
Time: 3:04pm - 3:09pm MST
@@ -58,7 +58,7 @@ Human-Computer Interaction Principles in Meshery:
“It’s the network!” is the cry of every engineer. With the increased prevalence of microservices and distributed systems, it’s true - networking as a discipline has never been more critical in the well-architected design and efficient operation of modern infrastructure. Join this talk for an intro to the TAG, its charter and a deeper discussion of current cloud native networking topics being advanced in this TAG.
-
+
Date: November 14, 2024
Time: 11:55am - 12:30pm MST
@@ -76,7 +76,7 @@ Join the Meshery maintainers and community in improving the leading cloud native
Why Contribute to Meshery? - Gain experience with cloud native technologies, including essentially every CNCF project and open source development practices. As is the 10th fastest growing CNCF project, Meshery has a vibrant community. Work alongside passionate maintainers and contributors. No Prior Experience Needed: We welcome contributions from all levels of experience. Join us at Meshery Contribfest and be part of the growing community shaping the future of collaborative cloud native management.
-
+
Date: November 14, 2024
Time: 4:30pm - 6:00pm MST
diff --git a/src/collections/blog/Blog.style.js b/src/collections/blog/Blog.style.js
index 0a47ce5a84d0..7b9536cf0171 100644
--- a/src/collections/blog/Blog.style.js
+++ b/src/collections/blog/Blog.style.js
@@ -1,5 +1,5 @@
import styled from "styled-components";
-export const BlogWrapper = styled.div`
+const BlogWrapper = styled.div`
color: #000;
.sub-heading {
color: gray;
@@ -444,3 +444,5 @@ code {
}
`;
+
+export default BlogWrapper;
\ No newline at end of file
diff --git a/src/collections/blog/MeetTheMeshMate.style.js b/src/collections/blog/MeetTheMeshMate.style.js
new file mode 100644
index 000000000000..8518c78ae4e6
--- /dev/null
+++ b/src/collections/blog/MeetTheMeshMate.style.js
@@ -0,0 +1,44 @@
+import styled from "styled-components";
+const MeetTheMeshMate = styled.div`
+ div.intro {
+ word-spacing: 0.5rem;
+ }
+ div.interviewer {
+ margin-top: 1rem;
+ text-align: left;
+ span {
+ font-weight: 600;
+ font-style: normal;
+ }
+ }
+ div.interviewee {
+ display: flex;
+ flex-direction: column;
+ justify-content: flex-start;
+ font-style: italic;
+ text-align: left;
+ border-left: 2px solid ${(props) => props.theme.primaryLightColor};
+ padding-left: 2rem;
+ span {
+ font-weight: 600;
+ font-style: normal;
+ }
+ }
+ div.note {
+ margin: 1rem;
+ padding: 2rem;
+ display: flex;
+ border: 1px solid ${(props) => props.theme.primaryLightColor};
+ img {
+ margin-right: 3rem;
+ }
+ }
+ .centered-text {
+ padding-top: 2rem;
+ padding-bottom: 2rem;
+ font-size: 1.2rem;
+ font-weight: 600;
+ }
+`;
+
+export default MeetTheMeshMate;
\ No newline at end of file
diff --git a/src/collections/blog/blog-template/index.mdx b/src/collections/blog/blog-template/index.mdx
index 08b93523f229..6a8102509cde 100644
--- a/src/collections/blog/blog-template/index.mdx
+++ b/src/collections/blog/blog-template/index.mdx
@@ -1,50 +1,50 @@
----
-title: "Lorem Ipsum"
-subtitle: "Lorem Ipsum"
-date: 2020-06-23 10:30:05 -0530
-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: true
-published: false
----
-
-import { BlogWrapper } from "../Blog.style.js";
-import Blockquote from "../../../reusecore/Blockquote";
-import image from "../../../assets/images/layer5/layer5-only/svg/layer5-light-no-trim.svg";
-
-
-
-
-## 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
-
-_**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!**_
-
-
+---
+title: "Lorem Ipsum"
+subtitle: "Lorem Ipsum"
+date: 2020-06-23 10:30:05 -0530
+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: true
+published: false
+---
+
+import { BlogWrapper } from "../Blog.style.js";
+import Blockquote from "../../../reusecore/Blockquote";
+import image from "../../../assets/images/layer5/layer5-only/svg/layer5-light-no-trim.svg";
+
+
+
+
+## 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
+
+_**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/careers/Career.style.js b/src/collections/careers/Career.style.js
index 423cd62f5b7a..4a9e0545bcce 100644
--- a/src/collections/careers/Career.style.js
+++ b/src/collections/careers/Career.style.js
@@ -1,7 +1,7 @@
import styled from "styled-components";
import List_Icon from "../../assets/images/careers/list-icon.svg";
-export const CareerWrapper = styled.div`
+const CareerWrapper = styled.div`
.body-sections {
position: relative;
p {
@@ -69,3 +69,5 @@ export const CareerWrapper = styled.div`
}
}
`;
+
+export default CareerWrapper;
\ No newline at end of file
diff --git a/src/collections/careers/digital-marketing-internship/index.mdx b/src/collections/careers/digital-marketing-internship/index.mdx
index f2cfb8b6e098..68da797db6b1 100644
--- a/src/collections/careers/digital-marketing-internship/index.mdx
+++ b/src/collections/careers/digital-marketing-internship/index.mdx
@@ -10,12 +10,10 @@ thumbnail: ./digital-marketing.svg
abstract: "Learn and exercise modern marketing strategies and automation as a Layer5 Digital Marketing Intern."
published: true
---
-
import { CareerWrapper } from "../Career.style.js";
import PositionApply from "../how-to-apply.js";
import { Col } from "../../../reusecore/Layout";
-
About Layer5
@@ -40,7 +38,8 @@ import { Col } from "../../../reusecore/Layout";
In this position, you will collaborate with our core team in each stage of marketing campaigns. Your work will include developing,
growing, and expanding our marketing channels through social media outreach, blogging, event planning, and speaker engagement.
- Internships are continuously available. This is a dynamic position and a great opportunity for an entry level marketing person to build their skills and their career. The Digital Marketing Intern will work closely with the open source community and broad set of Layer5 academic and technology partners.
+ Internships are continuously available. This is a dynamic position and a great opportunity for an entry level marketing person to build their skills and their career. The Digital Marketing Intern will work closely with the open source community and broad set of Layer5 academic and technology partners.
+
The ideal candidate has excellent English composition and grammar skills. He/she is analytical, great with numbers and is driven to succeed with little supervision. You are someone who works well in a team and takes pride in helping a company succeed and grow and are willing to put in the work needed to become a valued member of an evolving marketing team.
diff --git a/src/collections/events/2020/addo/index.mdx b/src/collections/events/2020/addo/index.mdx
index 9d7f14c7ea1e..71005d3c6e89 100644
--- a/src/collections/events/2020/addo/index.mdx
+++ b/src/collections/events/2020/addo/index.mdx
@@ -1,11 +1,11 @@
----
-title: "2020 All Day DevOps"
-description: "Register for All Day DevOps and all its greatness!"
-date: 2020-11-12
-thumbnail: ./all-day-devops.webp
-darkthumbnail: ./all-day-devops.webp
-eurl: https://www.alldaydevops.com/addo-speakers/lee-calcote
-type: Event
-published: true
-
----
+---
+title: "2020 All Day DevOps"
+description: "Register for All Day DevOps and all its greatness!"
+date: 2020-11-12
+thumbnail: ./all-day-devops.webp
+darkthumbnail: ./all-day-devops.webp
+eurl: https://www.alldaydevops.com/addo-speakers/lee-calcote
+type: Event
+published: true
+
+---
diff --git a/src/collections/events/2020/advanced-istio/index.mdx b/src/collections/events/2020/advanced-istio/index.mdx
index 4c389b53c9c8..ff7615e54d20 100644
--- a/src/collections/events/2020/advanced-istio/index.mdx
+++ b/src/collections/events/2020/advanced-istio/index.mdx
@@ -1,55 +1,55 @@
----
-title: "Advanced Istio"
-description: "Discover advanced concepts in service mesh technology with Lee Calcote's comprehensive online course on Istio. Gain hands-on experience over three hours, exploring telemetry management, advanced traffic scenarios, canary deployments, and securing communication."
-author: "Lee Calcote"
-date: 2020-12-09
-thumbnail: ./istio.webp
-darkthumbnail: ./istio.webp
-eurl: https://www.oreilly.com/live-training/courses/advanced-istio/0636920471639/
-type: Workshop
-mesh: Istio
-resource: true
-published: true
-speakers: ["Lee Calcote", "Abishek Kumar"]
----
-Organizations that have adopted containers and are running a handful (or more) of microservices often find tools to provide observability, control, and security lacking. Service meshes—the third phase in the microservices journey—have quickly entered the cloud native landscape, filling unmet service-level needs and providing a substrate of secure connectivity, uniform visibility, and granular control over service requests. Operating at layer 5, service meshes offer great value.
-
-Lee Calcote walks you through advanced service mesh concepts and each and every aspect of the open source service mesh Istio. Over three hours, you’ll gain hands-on experience with this popular tool as you learn how to deploy Istio alongside microservices running in Kubernetes.
-
-### What you'll learn-and how you can apply it
-
-#### By the end of this live online course, you’ll understand:
-
-- Istio's methods for managing telemetry, monitoring, and reporting
-- Advanced traffic management scenarios
-- Approaches to canary deployments and securing communication with Istio
-
-#### And you’ll be able to:
-
-- Configure and operate Istio in context of an example workloads and their common use cases
-- Manage traffic through load balancing and resilient communications
-- Enforce policies and rate limiting
-- Be confident in the third step of your cloud native journey with ongoing management of your service mesh
-
-### This training course is for you because...
-
-- You’re an operator who wants uniform observability irrespective of the different languages and libraries that run your services.
-- You’re a developer who wants to affect application behavior without code changes.
-- You want to become a cloud native architect or level up as one.
-
-#### Prerequisites
-
-- A working knowledge of Istio and Kubernetes
-- Familiarity with Docker Desktop, Minikube, or kind
-- A computer with Docker and Meshery installed locally
-- Access to local or remote Kubernetes cluster of any size, with cluster admin privileges (Either of these two local single-node clusters will work: Docker Desktop or Minikube.)
-
-#### Recommended preparation
-
-- Take Introduction to Istio (live online training course with Lee Calcote)
-- If you need to brush up on Kubernetes, take Introduction to Kubernetes (live online training course with Sébastien Goasguen) or read Kubernetes Cookbook (book) or Kubernetes: Up and Running (book)
-
-#### Recommended follow-up
-
-- Read The Enterprise Path to Service Mesh Architectures (report)
-- Read Istio: Up and Running (early release book)
+---
+title: "Advanced Istio"
+description: "Discover advanced concepts in service mesh technology with Lee Calcote's comprehensive online course on Istio. Gain hands-on experience over three hours, exploring telemetry management, advanced traffic scenarios, canary deployments, and securing communication."
+author: "Lee Calcote"
+date: 2020-12-09
+thumbnail: ./istio.webp
+darkthumbnail: ./istio.webp
+eurl: https://www.oreilly.com/live-training/courses/advanced-istio/0636920471639/
+type: Workshop
+mesh: Istio
+resource: true
+published: true
+speakers: ["Lee Calcote", "Abishek Kumar"]
+---
+Organizations that have adopted containers and are running a handful (or more) of microservices often find tools to provide observability, control, and security lacking. Service meshes—the third phase in the microservices journey—have quickly entered the cloud native landscape, filling unmet service-level needs and providing a substrate of secure connectivity, uniform visibility, and granular control over service requests. Operating at layer 5, service meshes offer great value.
+
+Lee Calcote walks you through advanced service mesh concepts and each and every aspect of the open source service mesh Istio. Over three hours, you’ll gain hands-on experience with this popular tool as you learn how to deploy Istio alongside microservices running in Kubernetes.
+
+### What you'll learn-and how you can apply it
+
+#### By the end of this live online course, you’ll understand:
+
+- Istio's methods for managing telemetry, monitoring, and reporting
+- Advanced traffic management scenarios
+- Approaches to canary deployments and securing communication with Istio
+
+#### And you’ll be able to:
+
+- Configure and operate Istio in context of an example workloads and their common use cases
+- Manage traffic through load balancing and resilient communications
+- Enforce policies and rate limiting
+- Be confident in the third step of your cloud native journey with ongoing management of your service mesh
+
+### This training course is for you because...
+
+- You’re an operator who wants uniform observability irrespective of the different languages and libraries that run your services.
+- You’re a developer who wants to affect application behavior without code changes.
+- You want to become a cloud native architect or level up as one.
+
+#### Prerequisites
+
+- A working knowledge of Istio and Kubernetes
+- Familiarity with Docker Desktop, Minikube, or kind
+- A computer with Docker and Meshery installed locally
+- Access to local or remote Kubernetes cluster of any size, with cluster admin privileges (Either of these two local single-node clusters will work: Docker Desktop or Minikube.)
+
+#### Recommended preparation
+
+- Take Introduction to Istio (live online training course with Lee Calcote)
+- If you need to brush up on Kubernetes, take Introduction to Kubernetes (live online training course with Sébastien Goasguen) or read Kubernetes Cookbook (book) or Kubernetes: Up and Running (book)
+
+#### Recommended follow-up
+
+- Read The Enterprise Path to Service Mesh Architectures (report)
+- Read Istio: Up and Running (early release book)
diff --git a/src/collections/events/2020/ccoss2020/index.mdx b/src/collections/events/2020/ccoss2020/index.mdx
index 53db1bb1f91f..1f19a9d65d63 100644
--- a/src/collections/events/2020/ccoss2020/index.mdx
+++ b/src/collections/events/2020/ccoss2020/index.mdx
@@ -1,12 +1,12 @@
----
-title: "CCOSS 2020"
-description: "Meshery is a tool that allows you to deploy, configure, measure, operate, and modify multiple service meshes (Istio, Linkerd, etc.). In this workshop, you will learn what a service mesh is and how Meshery can help you assess the landscape of service meshes available in the market."
-date: 2020-10-19
-thumbnail: ./ccoss-logo.svg
-darkthumbnail: ./ccoss-logo.svg
-eurl: https://ccoss.org/sessions/w-meshery/
-type: Workshop
-product: Meshery
-resource: true
-published: true
----
+---
+title: "CCOSS 2020"
+description: "Meshery is a tool that allows you to deploy, configure, measure, operate, and modify multiple service meshes (Istio, Linkerd, etc.). In this workshop, you will learn what a service mesh is and how Meshery can help you assess the landscape of service meshes available in the market."
+date: 2020-10-19
+thumbnail: ./ccoss-logo.svg
+darkthumbnail: ./ccoss-logo.svg
+eurl: https://ccoss.org/sessions/w-meshery/
+type: Workshop
+product: Meshery
+resource: true
+published: true
+---
diff --git a/src/collections/events/2020/cnfc-day/index.mdx b/src/collections/events/2020/cnfc-day/index.mdx
index 6e6e758edf29..d4e8a619a6da 100644
--- a/src/collections/events/2020/cnfc-day/index.mdx
+++ b/src/collections/events/2020/cnfc-day/index.mdx
@@ -1,10 +1,10 @@
----
-title: "Virtual Cloud Native Ambassador Day"
-description: "Explore the latest in cloud-native technology as CNCF Ambassadors present Virtual Cloud Native Ambassador Day. "
-date: 2020-10-14
-thumbnail: ./cnfc.webp
-darkthumbnail: ./cnfc.webp
-eurl: https://community.cncf.io/events/details/cncf-cncf-ambassadors-presents-virtual-cloud-native-ambassador-day/
-type: Event
-published: true
----
+---
+title: "Virtual Cloud Native Ambassador Day"
+description: "Explore the latest in cloud-native technology as CNCF Ambassadors present Virtual Cloud Native Ambassador Day. "
+date: 2020-10-14
+thumbnail: ./cnfc.webp
+darkthumbnail: ./cnfc.webp
+eurl: https://community.cncf.io/events/details/cncf-cncf-ambassadors-presents-virtual-cloud-native-ambassador-day/
+type: Event
+published: true
+---
diff --git a/src/collections/events/2020/dockercon-live/index.mdx b/src/collections/events/2020/dockercon-live/index.mdx
index 19238474c4ec..425472897cd8 100644
--- a/src/collections/events/2020/dockercon-live/index.mdx
+++ b/src/collections/events/2020/dockercon-live/index.mdx
@@ -1,21 +1,22 @@
----
-title: "DockerCon LIVE"
-description: "Streamline multi-tenancy effortlessly! Join our talk to discover how Docker Desktop, Kubernetes, and Meshery simplify deploying a service mesh."
-talk-title: "Service Meshing with Docker Desktop and WebAssembly"
-thumbnail: ./dockerCon2020.webp
-darkthumbnail: ./dockerCon2020.webp
-date: 2020-05-28
-eurl: https://docker.events.cube365.net/docker/dockercon/content/Videos/63TCCNpzDC7Xxnm8b
-type: Event
-product: Meshery
-technology: Docker
-resource: true
-event-category: talk
-speakers: ["Lee Calcote", "Kanishkar J"]
-attribute:
- [{ name: "Docker Austin", url: https://www.meetup.com/Docker-Austin }]
-published: true
----
-Too lazy to implement multi-tenancy? Don't have time to implement per user rate limiting in your application's endpoints? In this talk, we will examine how to let application infrastructure concerns melt off your Dockerized workloads and have your infrastructure implement multi-tenancy on your behalf.
-
+---
+title: "DockerCon LIVE"
+description: "Streamline multi-tenancy effortlessly! Join our talk to discover how Docker Desktop, Kubernetes, and Meshery simplify deploying a service mesh."
+talk-title: "Service Meshing with Docker Desktop and WebAssembly"
+thumbnail: ./dockerCon2020.webp
+darkthumbnail: ./dockerCon2020.webp
+date: 2020-05-28
+eurl: https://docker.events.cube365.net/docker/dockercon/content/Videos/63TCCNpzDC7Xxnm8b
+type: Event
+product: Meshery
+technology: Docker
+resource: true
+event-category: talk
+speakers: ["Lee Calcote", "Kanishkar J"]
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+published: true
+---
+Too lazy to implement multi-tenancy? Don't have time to implement per user rate limiting in your application's endpoints? In this talk, we will examine how to let application infrastructure concerns melt off your Dockerized workloads and have your infrastructure implement multi-tenancy on your behalf.
+
Learn how to use Docker Desktop and Kubernetes as your development platforms of choice in combination with Meshery, the cloud native management plane, to easily deploy a service mesh. Using Consul and Envoy's latest capabilities, see how WASM can be used to move user authentication and authorization from your application to the infrastructure.
\ No newline at end of file
diff --git a/src/collections/events/2020/establishing-an-open-source-program-office/index.mdx b/src/collections/events/2020/establishing-an-open-source-program-office/index.mdx
index 5b2ffd826e14..ccc2231c1860 100644
--- a/src/collections/events/2020/establishing-an-open-source-program-office/index.mdx
+++ b/src/collections/events/2020/establishing-an-open-source-program-office/index.mdx
@@ -1,21 +1,16 @@
----
-title: "Establishing an Open Source Program Office"
-description: "Meetup for Docker Austin by establishing an Open Source Program Office"
-thumbnail: ./establishing-open-source.webp
-darkthumbnail: ./establishing-open-source.webp
-date: 2020-05-21
-eurl: https://www.meetup.com/Cloud-Native-Austin/events/267785133/
-type: Meetups
-attribute: [
- {
- name: "Docker Austin",
- url: https://www.meetup.com/Docker-Austin
- },
- {
- name: "Cloud Native Austin",
- url: https://www.meetup.com/Cloud-Native-Austin
- }
-]
-published: true
-speakers: ["Lee Calcote"]
----
+---
+title: "Establishing an Open Source Program Office"
+description: "Meetup for Docker Austin by establishing an Open Source Program Office"
+thumbnail: ./establishing-open-source.webp
+darkthumbnail: ./establishing-open-source.webp
+date: 2020-05-21
+eurl: https://www.meetup.com/Cloud-Native-Austin/events/267785133/
+type: Meetups
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+ - name: "Cloud Native Austin"
+ url: https://www.meetup.com/Cloud-Native-Austin
+published: true
+speakers: ["Lee Calcote"]
+---
diff --git a/src/collections/events/2020/hands-on-workshop-introduction-to-istio/index.mdx b/src/collections/events/2020/hands-on-workshop-introduction-to-istio/index.mdx
index 93dd2dafcd02..7d60a90e2d9a 100644
--- a/src/collections/events/2020/hands-on-workshop-introduction-to-istio/index.mdx
+++ b/src/collections/events/2020/hands-on-workshop-introduction-to-istio/index.mdx
@@ -1,20 +1,15 @@
----
-title: "Hands-on Workshop: Introduction to Istio"
-description: "Unlock the power of Istio with our hands-on workshop"
-thumbnail: ./istio.webp
-darkthumbnail: ./istio.webp
-date: 2020-01-16
-eurl: https://www.meetup.com/Cloud-Native-Austin/events/267271852/
-type: Meetups
-attribute: [
- {
- name: "Docker Austin",
- url: https://www.meetup.com/Docker-Austin
- },
- {
- name: "Cloud Native Austin",
- url: https://www.meetup.com/Cloud-Native-Austin
- }
-]
-published: true
----
+---
+title: "Hands-on Workshop: Introduction to Istio"
+description: "Unlock the power of Istio with our hands-on workshop"
+thumbnail: ./istio.webp
+darkthumbnail: ./istio.webp
+date: 2020-01-16
+eurl: https://www.meetup.com/Cloud-Native-Austin/events/267271852/
+type: Meetups
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+ - name: "Cloud Native Austin"
+ url: https://www.meetup.com/Cloud-Native-Austin
+published: true
+---
diff --git a/src/collections/events/2020/innotech/index.mdx b/src/collections/events/2020/innotech/index.mdx
index 96f6f9aa1df0..c9b52a41ffe3 100644
--- a/src/collections/events/2020/innotech/index.mdx
+++ b/src/collections/events/2020/innotech/index.mdx
@@ -1,11 +1,11 @@
----
-title: "InnoTech Dallas"
-description: "View more about this event at InnoTech Dallas"
-date: 2020-04-14
-thumbnail: ./innotech.webp
-darkthumbnail: ./innotech.webp
-eurl: https://innotechdallas2020.sched.com/event/aN7E/a-management-plane-for-service-meshes
-type: Event
-published: true
-
----
+---
+title: "InnoTech Dallas"
+description: "View more about this event at InnoTech Dallas"
+date: 2020-04-14
+thumbnail: ./innotech.webp
+darkthumbnail: ./innotech.webp
+eurl: https://innotechdallas2020.sched.com/event/aN7E/a-management-plane-for-service-meshes
+type: Event
+published: true
+
+---
diff --git a/src/collections/events/2020/introduction-to-istio/index.mdx b/src/collections/events/2020/introduction-to-istio/index.mdx
index 49439ea75225..6681b43a41b1 100644
--- a/src/collections/events/2020/introduction-to-istio/index.mdx
+++ b/src/collections/events/2020/introduction-to-istio/index.mdx
@@ -1,60 +1,60 @@
----
-title: "Introduction to Istio"
-description: "Master advanced service mesh concepts with Lee Calcote in our hands-on workshop, Introduction to Istio."
-author: "Lee Calcote"
-date: 2020-12-10
-thumbnail: ./istio-intro.webp
-darkthumbnail: ./istio-intro.webp
-eurl: https://www.oreilly.com/live-training/courses/introduction-to-istio/0636920422716/
-type: Workshop
-resource: true
-mesh: Istio
-technology: Kubernetes
-published: true
-register: false
-upcoming: false
-speakers: ["Lee Calcote", "Abishek Kumar"]
----
-Organizations that have adopted containers and are running a handful (or more) of microservices often find tools to provide observability, control, and security lacking. Service meshes—the third phase in the microservices journey—have quickly entered the cloud native landscape, filling unmet service-level needs and providing a substrate of secure connectivity, uniform visibility, and granular control over service requests. Operating at layer 5, service meshes offer great value.
-
-Lee Calcote walks you through advanced service mesh concepts and each and every aspect of the open source service mesh Istio. Over three hours, you’ll gain hands-on experience with this popular tool as you learn how to deploy Istio alongside microservices running in Kubernetes.
-
-### What you'll learn-and how you can apply it
-
-#### By the end of this live online course, you’ll understand:
-
-- How to manage traffic through load balancing and resilient communications
-- How to enforce policies and rate limiting
-- Istio's methods for managing telemetry, monitoring, and reporting
-- Approaches to canary deployments and securing communication with Istio
-
-### And you’ll be able to:
-
-- Configure and operate Istio in context of an example workloads and their common use cases
-- Take the third step in your cloud native journey with an initial deployment of a service mesh
-
-### This training course is for you because...
-
-- You’re an operator who wants uniform observability irrespective of the different languages and libraries that run your services.
-- You’re a developer who wants to affect application behavior without code changes.
-- You want to become a cloud native architect or level up as one.
-
-#### Prerequisites
-
-- Working knowledge of Docker, Kubernetes, and kubectl.
-
-#### A locally running instance of:
-
-- Docker (Docker Desktop for Mac or Windows, or Docker for Linux)
-- Kubernetes (using Docker Desktop or Minikube for Mac, Windows, or Linux)
-- [Meshery](/cloud-native-management/meshery) (Mac, Windows or Linux)
-
-#### Recommended preparation:
-
-- Take Introduction to Kubernetes (live online training course with Sébastien Goasguen)
-- If you need help installing Kubernetes, read “Installing Kubernetes Locally Using Minikube” (short section in “Chapter 3: Deploying a Kubernetes Cluster” in Kubernetes: Up and Running)
-
-#### Recommended follow-up:
-
-- Read [The Enterprise Path to Service Mesh Architectures](/learn/service-mesh-books/the-enterprise-path-to-service-mesh-architectures) (report)
-- Read [Istio: Up and Running](/learn/service-mesh-books/istio-up-and-running)
+---
+title: "Introduction to Istio"
+description: "Master advanced service mesh concepts with Lee Calcote in our hands-on workshop, Introduction to Istio."
+author: "Lee Calcote"
+date: 2020-12-10
+thumbnail: ./istio-intro.webp
+darkthumbnail: ./istio-intro.webp
+eurl: https://www.oreilly.com/live-training/courses/introduction-to-istio/0636920422716/
+type: Workshop
+resource: true
+mesh: Istio
+technology: Kubernetes
+published: true
+register: false
+upcoming: false
+speakers: ["Lee Calcote", "Abishek Kumar"]
+---
+Organizations that have adopted containers and are running a handful (or more) of microservices often find tools to provide observability, control, and security lacking. Service meshes—the third phase in the microservices journey—have quickly entered the cloud native landscape, filling unmet service-level needs and providing a substrate of secure connectivity, uniform visibility, and granular control over service requests. Operating at layer 5, service meshes offer great value.
+
+Lee Calcote walks you through advanced service mesh concepts and each and every aspect of the open source service mesh Istio. Over three hours, you’ll gain hands-on experience with this popular tool as you learn how to deploy Istio alongside microservices running in Kubernetes.
+
+### What you'll learn-and how you can apply it
+
+#### By the end of this live online course, you’ll understand:
+
+- How to manage traffic through load balancing and resilient communications
+- How to enforce policies and rate limiting
+- Istio's methods for managing telemetry, monitoring, and reporting
+- Approaches to canary deployments and securing communication with Istio
+
+### And you’ll be able to:
+
+- Configure and operate Istio in context of an example workloads and their common use cases
+- Take the third step in your cloud native journey with an initial deployment of a service mesh
+
+### This training course is for you because...
+
+- You’re an operator who wants uniform observability irrespective of the different languages and libraries that run your services.
+- You’re a developer who wants to affect application behavior without code changes.
+- You want to become a cloud native architect or level up as one.
+
+#### Prerequisites
+
+- Working knowledge of Docker, Kubernetes, and kubectl.
+
+#### A locally running instance of:
+
+- Docker (Docker Desktop for Mac or Windows, or Docker for Linux)
+- Kubernetes (using Docker Desktop or Minikube for Mac, Windows, or Linux)
+- [Meshery](/cloud-native-management/meshery) (Mac, Windows or Linux)
+
+#### Recommended preparation:
+
+- Take Introduction to Kubernetes (live online training course with Sébastien Goasguen)
+- If you need help installing Kubernetes, read “Installing Kubernetes Locally Using Minikube” (short section in “Chapter 3: Deploying a Kubernetes Cluster” in Kubernetes: Up and Running)
+
+#### Recommended follow-up:
+
+- Read [The Enterprise Path to Service Mesh Architectures](/learn/service-mesh-books/the-enterprise-path-to-service-mesh-architectures) (report)
+- Read [Istio: Up and Running](/learn/service-mesh-books/istio-up-and-running)
diff --git a/src/collections/events/2020/introduction-to-network-service-mesh/index.mdx b/src/collections/events/2020/introduction-to-network-service-mesh/index.mdx
index 25bf196440cd..d4ffceff1ab6 100644
--- a/src/collections/events/2020/introduction-to-network-service-mesh/index.mdx
+++ b/src/collections/events/2020/introduction-to-network-service-mesh/index.mdx
@@ -1,22 +1,17 @@
----
-title: "Introduction to Network Service Mesh"
-description: "Introduce yourself with Network Service Mesh, speakers - Lee Calcote"
-thumbnail: ./network-service.webp
-darkthumbnail: ./network-service.webp
-date: 2020-02-20
-eurl: https://www.meetup.com/Cloud-Native-Austin/events/267272035/
-type: Meetups
-attribute: [
- {
- name: "Docker Austin",
- url: https://www.meetup.com/Docker-Austin
- },
- {
- name: "Cloud Native Austin",
- url: https://www.meetup.com/Cloud-Native-Austin
- }
-]
-published: true
-speakers: ["Lee Calcote"]
-
----
+---
+title: "Introduction to Network Service Mesh"
+description: "Introduce yourself with Network Service Mesh, speakers - Lee Calcote"
+thumbnail: ./network-service.webp
+darkthumbnail: ./network-service.webp
+date: 2020-02-20
+eurl: https://www.meetup.com/Cloud-Native-Austin/events/267272035/
+type: Meetups
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+ - name: "Cloud Native Austin"
+ url: https://www.meetup.com/Cloud-Native-Austin
+published: true
+speakers: ["Lee Calcote"]
+
+---
diff --git a/src/collections/events/2020/istiocon2020/index.mdx b/src/collections/events/2020/istiocon2020/index.mdx
index 5e75c916d4a3..36b3e6015a2a 100644
--- a/src/collections/events/2020/istiocon2020/index.mdx
+++ b/src/collections/events/2020/istiocon2020/index.mdx
@@ -1,49 +1,49 @@
----
-title: "IstioCon 2021"
-description: "Kickstart your service mesh journey with Layer5's renowned workshop featuring Meshery, the service mesh manager. Learn the ins and outs of Istio, the popular service mesh, in this hands-on training. "
-date: 2021-02-22
-thumbnail: ./istiocon-logo.svg
-darkthumbnail: ./istiocon-logo.svg
-eurl: https://events.istio.io/istiocon-2021/workshops/using-istio/
-type: Event
-published: true
-upcoming: false
-technology: WebAssembly
-mesh: Istio
-resource: true
-speakers: ["Lee Calcote", "Abishek Kumar"]
-redirect_from:
- - /community/events/istiocon-2020
----
-Join Layer5 at the inaugural Istio conference on Monday, Feb. 22nd to Friday, Feb. 26th. IstioCon is a 100% virtual event that is designed to connect community members across the globe with Istio and the Istio ecosystem.
-
-Layer5 will kickoff the event with our renowned service mesh workshop, featuring Meshery, the service mesh manager. Attend our workshop to help you get started with managing your own service mesh!
-
-
Using Istio
-
-
-As the third phase in your microservices journey, service meshes provide a substrate of secure connectivity, uniform visibility and granular control over service requests. Service meshes have quickly entered the cloud native landscape filling unmet service-level needs. Organizations that have adopted containers and who are running a handful or more of microservices find tools to provide observability, control and security lacking. Operating at layer 5, service meshes promise much value. This live training walks you through a series of hands-on labs, introducing you to each and every aspect of the popular service mesh - Istio. During this workshop you will gain hands-on experience as we walk through deploying Istio alongside microservices running in Kubernetes.
-
-You will learn to:
-
-
-
Configure and operate Istio in context of an example workloads and their common use cases
-
Manage traffic through load balancing and resilient communications
-
Enforce policies and rate limiting
-
Be confident with ongoing management of Istio
-
Understand WebAssembly filters for Envoy and deploy a custom filter
-
-
-
+---
+title: "IstioCon 2021"
+description: "Kickstart your service mesh journey with Layer5's renowned workshop featuring Meshery, the service mesh manager. Learn the ins and outs of Istio, the popular service mesh, in this hands-on training. "
+date: 2021-02-22
+thumbnail: ./istiocon-logo.svg
+darkthumbnail: ./istiocon-logo.svg
+eurl: https://events.istio.io/istiocon-2021/workshops/using-istio/
+type: Event
+published: true
+upcoming: false
+technology: WebAssembly
+mesh: Istio
+resource: true
+speakers: ["Lee Calcote", "Abishek Kumar"]
+redirect_from:
+ - /community/events/istiocon-2020
+---
+Join Layer5 at the inaugural Istio conference on Monday, Feb. 22nd to Friday, Feb. 26th. IstioCon is a 100% virtual event that is designed to connect community members across the globe with Istio and the Istio ecosystem.
+
+Layer5 will kickoff the event with our renowned service mesh workshop, featuring Meshery, the service mesh manager. Attend our workshop to help you get started with managing your own service mesh!
+
+
Using Istio
+
+
+As the third phase in your microservices journey, service meshes provide a substrate of secure connectivity, uniform visibility and granular control over service requests. Service meshes have quickly entered the cloud native landscape filling unmet service-level needs. Organizations that have adopted containers and who are running a handful or more of microservices find tools to provide observability, control and security lacking. Operating at layer 5, service meshes promise much value. This live training walks you through a series of hands-on labs, introducing you to each and every aspect of the popular service mesh - Istio. During this workshop you will gain hands-on experience as we walk through deploying Istio alongside microservices running in Kubernetes.
+
+You will learn to:
+
+
+
Configure and operate Istio in context of an example workloads and their common use cases
+
Manage traffic through load balancing and resilient communications
+
Enforce policies and rate limiting
+
Be confident with ongoing management of Istio
+
Understand WebAssembly filters for Envoy and deploy a custom filter
\ No newline at end of file
diff --git a/src/collections/events/2020/kubecon-NA-2020/index.mdx b/src/collections/events/2020/kubecon-NA-2020/index.mdx
index bae51ee50ea1..016ba77e6587 100644
--- a/src/collections/events/2020/kubecon-NA-2020/index.mdx
+++ b/src/collections/events/2020/kubecon-NA-2020/index.mdx
@@ -1,11 +1,11 @@
----
-title: "Kubecon NA 2020"
-description: "View more about this event at KubeCon + CloudNativeCon North America 2020 Virtual"
-date: 2020-11-17
-thumbnail: ./kubeconNA2020.webp
-darkthumbnail: ./kubeconNA2020.webp
-eurl: https://kccncna20.sched.com/event/ekEz/service-mesh-specifications-and-why-they-matter-in-your-deployment-lee-calcote-naveen-kumar-layer5
-type: Event
-published: true
-upcoming: false
----
+---
+title: "Kubecon NA 2020"
+description: "View more about this event at KubeCon + CloudNativeCon North America 2020 Virtual"
+date: 2020-11-17
+thumbnail: ./kubeconNA2020.webp
+darkthumbnail: ./kubeconNA2020.webp
+eurl: https://kccncna20.sched.com/event/ekEz/service-mesh-specifications-and-why-they-matter-in-your-deployment-lee-calcote-naveen-kumar-layer5
+type: Event
+published: true
+upcoming: false
+---
diff --git a/src/collections/events/2020/kubecon-eu-2020/index.mdx b/src/collections/events/2020/kubecon-eu-2020/index.mdx
index 06af25f4547c..35f33ddf4f8e 100644
--- a/src/collections/events/2020/kubecon-eu-2020/index.mdx
+++ b/src/collections/events/2020/kubecon-eu-2020/index.mdx
@@ -1,11 +1,11 @@
----
-title: "KubeCon EU 2020"
-description: "View more about this event at KubeCon + CloudNativeCon Europe 2020"
-date: 2020-04-02
-thumbnail: ./kubecon-europe-2020.webp
-darkthumbnail: ./kubecon-europe-2020.webp
-eurl: https://kccnceu20.sched.com/event/Zetg/discreetly-studying-the-effects-of-individual-traffic-control-functions-lee-calcote-layer5?iframe=no&w=100%&sidebar=yes&bg=no
-type: Event
-published: true
-upcoming: false
----
+---
+title: "KubeCon EU 2020"
+description: "View more about this event at KubeCon + CloudNativeCon Europe 2020"
+date: 2020-04-02
+thumbnail: ./kubecon-europe-2020.webp
+darkthumbnail: ./kubecon-europe-2020.webp
+eurl: https://kccnceu20.sched.com/event/Zetg/discreetly-studying-the-effects-of-individual-traffic-control-functions-lee-calcote-layer5?iframe=no&w=100%&sidebar=yes&bg=no
+type: Event
+published: true
+upcoming: false
+---
diff --git a/src/collections/events/2020/meshery-the-multi-mesh/index.mdx b/src/collections/events/2020/meshery-the-multi-mesh/index.mdx
index eb5a53d9abab..dbd4993e677b 100644
--- a/src/collections/events/2020/meshery-the-multi-mesh/index.mdx
+++ b/src/collections/events/2020/meshery-the-multi-mesh/index.mdx
@@ -1,16 +1,13 @@
----
-title: "Meshery - The Multi-Mesh Manager | KUDO - Kubernetes Operators the Easy Way"
-description: "Get insight on Meshery the Multi-Mesh Manager and KUDO the Kubernetes Operators the Easy Way"
-thumbnail: ./meshery.webp
-darkthumbnail: ./meshery.webp
-date: 2020-04-16
-eurl: https://www.meetup.com/Cloud-Native-Austin/events/267784090/
-type: Meetups
-attribute: [
- {
- name: "Cloud Native Austin",
- url: https://www.meetup.com/Cloud-Native-Austin
- }
-]
-published: true
----
+---
+title: "Meshery - The Multi-Mesh Manager | KUDO - Kubernetes Operators the Easy Way"
+description: "Get insight on Meshery the Multi-Mesh Manager and KUDO the Kubernetes Operators the Easy Way"
+thumbnail: ./meshery.webp
+darkthumbnail: ./meshery.webp
+date: 2020-04-16
+eurl: https://www.meetup.com/Cloud-Native-Austin/events/267784090/
+type: Meetups
+attribute:
+ - name: "Cloud Native Austin"
+ url: https://www.meetup.com/Cloud-Native-Austin
+published: true
+---
diff --git a/src/collections/events/2020/meshery-the-service-mesh-management-plane/index.mdx b/src/collections/events/2020/meshery-the-service-mesh-management-plane/index.mdx
index ad0df242322e..05bcb1aad6ca 100644
--- a/src/collections/events/2020/meshery-the-service-mesh-management-plane/index.mdx
+++ b/src/collections/events/2020/meshery-the-service-mesh-management-plane/index.mdx
@@ -1,16 +1,13 @@
----
-title: "Meshery - the cloud native management plane | KUDO - Kubernetes Operators the Ea"
-description: "Get insight on Meshery the cloud native management plane and KUDO the Kubernetes Operators the Ea"
-thumbnail: ./meshery-logo.webp
-darkthumbnail: ./meshery-logo.webp
-date: 2020-04-16
-eurl: https://www.meetup.com/Docker-Austin/events/270084395/
-type: Meetups
-attribute: [
- {
- name: "Docker Austin",
- url: https://www.meetup.com/Docker-Austin
- }
-]
-published: true
----
+---
+title: "Meshery - the cloud native management plane | KUDO - Kubernetes Operators the Ea"
+description: "Get insight on Meshery the cloud native management plane and KUDO the Kubernetes Operators the Ea"
+thumbnail: ./meshery-logo.webp
+darkthumbnail: ./meshery-logo.webp
+date: 2020-04-16
+eurl: https://www.meetup.com/Docker-Austin/events/270084395/
+type: Meetups
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+published: true
+---
diff --git a/src/collections/events/2020/oio/index.mdx b/src/collections/events/2020/oio/index.mdx
index e20df0a5f305..76a87704d5cd 100644
--- a/src/collections/events/2020/oio/index.mdx
+++ b/src/collections/events/2020/oio/index.mdx
@@ -1,11 +1,11 @@
----
-title: "O'Reilly Infrastructure & Ops"
-description: "Transforming our in-person events to online, O'Reilly Infrastructure and Ops"
-date: 2020-06-15
-thumbnail: ./infra-ops.webp
-darkthumbnail: ./infra-ops.webp
-eurl: https://conferences.oreilly.com/infrastructure-ops/io-ca/public/schedule/speaker/226795
-type: Workshop
-resource: true
-published: true
----
+---
+title: "O'Reilly Infrastructure & Ops"
+description: "Transforming our in-person events to online, O'Reilly Infrastructure and Ops"
+date: 2020-06-15
+thumbnail: ./infra-ops.webp
+darkthumbnail: ./infra-ops.webp
+eurl: https://conferences.oreilly.com/infrastructure-ops/io-ca/public/schedule/speaker/226795
+type: Workshop
+resource: true
+published: true
+---
diff --git a/src/collections/events/2020/ois2020/index.mdx b/src/collections/events/2020/ois2020/index.mdx
index c924f16b4726..8a474bbbb152 100644
--- a/src/collections/events/2020/ois2020/index.mdx
+++ b/src/collections/events/2020/ois2020/index.mdx
@@ -1,11 +1,11 @@
----
-title: "Open Infrastructure Summit 2020"
-description: "Collaborate directly with the people building and running open source infrastructure using Linux, OpenStack, Kubernetes and 30+ other technologies."
-date: 2020-10-21
-thumbnail: ./ois2020.webp
-darkthumbnail: ./ois2020.webp
-eurl: https://summit.openinfra.dev/
-type: Event
-published: true
-
----
+---
+title: "Open Infrastructure Summit 2020"
+description: "Collaborate directly with the people building and running open source infrastructure using Linux, OpenStack, Kubernetes and 30+ other technologies."
+date: 2020-10-21
+thumbnail: ./ois2020.webp
+darkthumbnail: ./ois2020.webp
+eurl: https://summit.openinfra.dev/
+type: Event
+published: true
+
+---
diff --git a/src/collections/events/2020/oscon2020/index.mdx b/src/collections/events/2020/oscon2020/index.mdx
index d3cad1056e45..1f6bee6468a6 100644
--- a/src/collections/events/2020/oscon2020/index.mdx
+++ b/src/collections/events/2020/oscon2020/index.mdx
@@ -1,11 +1,11 @@
----
-title: "O'Reilly OSCON 2020"
-description: "Conferences - O'Reilly Media"
-date: 2020-07-13
-thumbnail: ./oscon.webp
-darkthumbnail: ./oscon.webp
-eurl: https://www.oreilly.com/conferences/
-type: Workshop
-resource: true
-published: true
----
+---
+title: "O'Reilly OSCON 2020"
+description: "Conferences - O'Reilly Media"
+date: 2020-07-13
+thumbnail: ./oscon.webp
+darkthumbnail: ./oscon.webp
+eurl: https://www.oreilly.com/conferences/
+type: Workshop
+resource: true
+published: true
+---
diff --git a/src/collections/events/2020/securing-the-mesh/index.mdx b/src/collections/events/2020/securing-the-mesh/index.mdx
index 167082538b1f..5277815de3cf 100644
--- a/src/collections/events/2020/securing-the-mesh/index.mdx
+++ b/src/collections/events/2020/securing-the-mesh/index.mdx
@@ -1,20 +1,15 @@
----
-title: "Securing the Mesh"
-description: "Learn how to Secure your Mesh"
-thumbnail: ./securing-mesh.webp
-darkthumbnail: ./securing-mesh.webp
-date: 2020-06-16
-eurl: https://www.meetup.com/Cloud-Native-Austin/events/267785376/
-type: Meetups
-attribute: [
- {
- name: "Docker Austin",
- url: https://www.meetup.com/Docker-Austin
- },
- {
- name: "Cloud Native Austin",
- url: https://www.meetup.com/Cloud-Native-Austin
- }
-]
-published: true
----
+---
+title: "Securing the Mesh"
+description: "Learn how to Secure your Mesh"
+thumbnail: ./securing-mesh.webp
+darkthumbnail: ./securing-mesh.webp
+date: 2020-06-16
+eurl: https://www.meetup.com/Cloud-Native-Austin/events/267785376/
+type: Meetups
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+ - name: "Cloud Native Austin"
+ url: https://www.meetup.com/Cloud-Native-Austin
+published: true
+---
diff --git a/src/collections/events/2020/service-meshes-but-at-what-cost/index.mdx b/src/collections/events/2020/service-meshes-but-at-what-cost/index.mdx
index f5fa199dbf07..599b5ba05cc0 100644
--- a/src/collections/events/2020/service-meshes-but-at-what-cost/index.mdx
+++ b/src/collections/events/2020/service-meshes-but-at-what-cost/index.mdx
@@ -1,20 +1,15 @@
----
-title: "Service Meshes, but at What Cost?"
-description: "Get insight on Service Mesh at Cloud Native Austin"
-thumbnail: ./service-mesh.webp
-darkthumbnail: ./service-mesh.webp
-date: 2020-09-17
-eurl: https://www.meetup.com/Cloud-Native-Austin/events/267784462/
-type: Meetups
-attribute: [
- {
- name: "Docker Austin",
- url: https://www.meetup.com/Docker-Austin
- },
- {
- name: "Cloud Native Austin",
- url: https://www.meetup.com/Cloud-Native-Austin
- }
-]
-published: true
----
+---
+title: "Service Meshes, but at What Cost?"
+description: "Get insight on Service Mesh at Cloud Native Austin"
+thumbnail: ./service-mesh.webp
+darkthumbnail: ./service-mesh.webp
+date: 2020-09-17
+eurl: https://www.meetup.com/Cloud-Native-Austin/events/267784462/
+type: Meetups
+attribute:
+ - name: "Docker Austin"
+ url: https://www.meetup.com/Docker-Austin
+ - name: "Cloud Native Austin"
+ url: https://www.meetup.com/Cloud-Native-Austin
+published: true
+---
diff --git a/src/collections/events/2020/servicemeshcon-NA-2020/index.mdx b/src/collections/events/2020/servicemeshcon-NA-2020/index.mdx
index 86b62d060a10..6dc18c362fa3 100644
--- a/src/collections/events/2020/servicemeshcon-NA-2020/index.mdx
+++ b/src/collections/events/2020/servicemeshcon-NA-2020/index.mdx
@@ -1,11 +1,11 @@
----
-title: "ServiceMeshCon NA 2020"
-description: "Vendor-neutral conference on service mesh technologies: getting started with and adopting a mesh, lessons learned from production deployments & technical sessions from maintainers."
-date: 2020-11-17
-thumbnail: ./servicemeshcon.webp
-darkthumbnail: ./servicemeshcon.webp
-eurl: https://events.linuxfoundation.org/servicemeshcon-north-america/
-type: Event
-published: true
-upcoming: false
----
+---
+title: "ServiceMeshCon NA 2020"
+description: "Vendor-neutral conference on service mesh technologies: getting started with and adopting a mesh, lessons learned from production deployments & technical sessions from maintainers."
+date: 2020-11-17
+thumbnail: ./servicemeshcon.webp
+darkthumbnail: ./servicemeshcon.webp
+eurl: https://events.linuxfoundation.org/servicemeshcon-north-america/
+type: Event
+published: true
+upcoming: false
+---
diff --git a/src/collections/events/2021/ccoss-meshery-workshop/index.mdx b/src/collections/events/2021/ccoss-meshery-workshop/index.mdx
index bd2fabde3cd5..44c7fb6f4852 100644
--- a/src/collections/events/2021/ccoss-meshery-workshop/index.mdx
+++ b/src/collections/events/2021/ccoss-meshery-workshop/index.mdx
@@ -1,14 +1,14 @@
----
-title: "CCOSS Meshery Workshop 2021"
-description: "Explore the world of service meshes with our workshop, where we provide an introduction to Meshery and delve into the essentials of Service Mesh technology with CCOSS Meshery Workshop."
-date: 2021-10-04
-thumbnail: ./ccoss.jpeg
-darkthumbnail: ./ccoss.jpeg
-eurl: https://ccoss.org/sessions/2021/taller-contribucion-meshery/
-type: Workshop
-product: Meshery
-resource: true
-published: true
-speakers: ["Alonso Lopez","Rodolfo Martinez Vega"]
----
-
In this workshop an introduction to Meshery and what a Service Mesh is will be addressed. Then the entire flow will be shown to contribute to various Meshery repositories such as CI workflows, e2e Testing with Cypress, Documentation, Translations, among others.
+---
+title: "CCOSS Meshery Workshop 2021"
+description: "Explore the world of service meshes with our workshop, where we provide an introduction to Meshery and delve into the essentials of Service Mesh technology with CCOSS Meshery Workshop."
+date: 2021-10-04
+thumbnail: ./ccoss.jpeg
+darkthumbnail: ./ccoss.jpeg
+eurl: https://ccoss.org/sessions/2021/taller-contribucion-meshery/
+type: Workshop
+product: Meshery
+resource: true
+published: true
+speakers: ["Alonso Lopez","Rodolfo Martinez Vega"]
+---
+
In this workshop an introduction to Meshery and what a Service Mesh is will be addressed. Then the entire flow will be shown to contribute to various Meshery repositories such as CI workflows, e2e Testing with Cypress, Documentation, Translations, among others.
diff --git a/src/collections/events/2021/kubecon-china-2021/cncf-tag-network-and-service-mesh-working-group-kubecon-china-2021-lee-calcote-ken-owens_compressed.pdf b/src/collections/events/2021/kubecon-china-2021/cncf-tag-network-and-service-mesh-working-group-kubecon-china-2021-lee-calcote-ken-owens_compressed.pdf
new file mode 100644
index 000000000000..ddccfd5c84fb
Binary files /dev/null and b/src/collections/events/2021/kubecon-china-2021/cncf-tag-network-and-service-mesh-working-group-kubecon-china-2021-lee-calcote-ken-owens_compressed.pdf differ
diff --git a/src/collections/events/2021/kubecon-china-2021/index.mdx b/src/collections/events/2021/kubecon-china-2021/index.mdx
index e52e171d7121..b125ad30d8be 100644
--- a/src/collections/events/2021/kubecon-china-2021/index.mdx
+++ b/src/collections/events/2021/kubecon-china-2021/index.mdx
@@ -1,183 +1,183 @@
----
-title: "KubeCon China 2021"
-description: "Learn about different service meshes, their functionalities, and how Meshery, an open-source multi-service mesh management plane, facilitates benchmarking and configuration scenarios. "
-date: 2021-12-09
-thumbnail: ./kubeconchina2021.webp
-darkthumbnail: ./kubeconchina2021.webp
-eurl: https://www.lfasiallc.com/kubecon-cloudnativecon-open-source-summit-china/
-type: Event
-Talk Description: CNCF TAG Network and Service Mesh Working Group
-Talk Link: https://kccncosschn21.sched.com/event/pcYk/cncf-tag-jie-zhang-re-jie-yuan-cncf-tag-network-and-service-mesh-working-group-lee-calcote-layer5-ed-warnicke-cisco-ken-owens-fiserv?iframe=no
-published: true
-featured: true
-upcoming: false
-product: Meshery
-resource: true
-# Deck: N/A
-# Video: N/A
----
-import {Link} from "gatsby";
-import slidesTAG from "./cncf-tag-network-and-service-mesh-working-group-kubecon-china-2021-lee-calcote-ken-owens.pdf";
-import slidesAdopt from "./solving-the-service-mesh-adopters-dilemma-anita-ihuman-kubecon-china-2021.pdf";
-
-
-
- Which service mesh should I use and how do I get started? What are the
- different service meshes, and how do they contrast? Learn about the
- functionality of different service meshes and visually manipulate mesh
- configuration.{" "}
-
-
-
- This talk introduces Meshery, an open source, multi-service mesh management
- plane that provisions (ten and counting) different service meshes, their
- sample applications and how it benchmarks the performance of service mesh
- deployments. Meshery facilitates benchmarking various configuration scenarios
- of any service mesh, comparison of performance of services (applications) on
- and off the mesh and across different meshes. It vets mesh and service
- configurations against deployment best practices. Some of the service mesh
- projects use Meshery as their performance benchmark tool for each release.
-
- With the increasing prevalence of microservice-based distributed systems, this
- is true: the network, as a discipline, has never been so critical in the
- efficient operation of cloud-native deployments. Network primitives including
- load balancing, observability, authentication, authorization, policies, rate
- limiting, QoS, mesh networks, traditional infrastructure bridging, and so on
- are now being developed and invested by the entire industry, and are the focus
- of the Service Mesh Working Group withing the CNCF TAG Network.{" "}
-
-
- Listen to our introduction and get an in-depth understanding of the service
- mesh projects being managed within the working group.
-
-
-
Lee Calcote
-
Ed Warnicke
-
Ken Owens
-
-
-- Presentation Slides
-
-
Meshery Project Office Hours
-
-
Join the Meshery Project Office Hours at KubeCon China 2021 to learn more about the CNCF's latest service mesh project and its maintainers.
-
Come and discover why Meshery is the easiest way to get started with 10+ service meshes!
-
-Speakers:
-
-
Aisuko Lee
-
Lee Calcote
-
Navendu Pottekkat
-
All Meshery project maintainers
-
-
-
-
-
Service Mesh Performance Project Office Hours
-
-
Join the Service Mesh Performance Project Office Hours at KubeCon China 2021 and get introduced to the new standard of cloud native performance characterisation and to its open source maintainers.
-
Learn what Service Mesh Performance is and how Meshery's implementation uses it to measure the performance of any service mesh available.
随着基于微服务的分布式系统越来越流行，网络作为一门学科，在云原生的高效部署和运行中变得越来越重要已然成为了不可动摇的事实。包括负载均衡，可观察性，鉴权，授权，策略，限速，QoS，Mesh网络，传统基础设施桥接等，正在被整个行业大力发展和投资，这些也是CNCF TAG Network的Service Mesh Working Group的重点。
+ Which service mesh should I use and how do I get started? What are the
+ different service meshes, and how do they contrast? Learn about the
+ functionality of different service meshes and visually manipulate mesh
+ configuration.{" "}
+
+
+
+ This talk introduces Meshery, an open source, multi-service mesh management
+ plane that provisions (ten and counting) different service meshes, their
+ sample applications and how it benchmarks the performance of service mesh
+ deployments. Meshery facilitates benchmarking various configuration scenarios
+ of any service mesh, comparison of performance of services (applications) on
+ and off the mesh and across different meshes. It vets mesh and service
+ configurations against deployment best practices. Some of the service mesh
+ projects use Meshery as their performance benchmark tool for each release.
+
+ With the increasing prevalence of microservice-based distributed systems, this
+ is true: the network, as a discipline, has never been so critical in the
+ efficient operation of cloud-native deployments. Network primitives including
+ load balancing, observability, authentication, authorization, policies, rate
+ limiting, QoS, mesh networks, traditional infrastructure bridging, and so on
+ are now being developed and invested by the entire industry, and are the focus
+ of the Service Mesh Working Group withing the CNCF TAG Network.{" "}
+
+
+ Listen to our introduction and get an in-depth understanding of the service
+ mesh projects being managed within the working group.
+
+
+
Lee Calcote
+
Ed Warnicke
+
Ken Owens
+
+
+- Presentation Slides
+
+
Meshery Project Office Hours
+
+
Join the Meshery Project Office Hours at KubeCon China 2021 to learn more about the CNCF's latest service mesh project and its maintainers.
+
Come and discover why Meshery is the easiest way to get started with 10+ service meshes!
+
+Speakers:
+
+
Aisuko Lee
+
Lee Calcote
+
Navendu Pottekkat
+
All Meshery project maintainers
+
+
+
+
+
Service Mesh Performance Project Office Hours
+
+
Join the Service Mesh Performance Project Office Hours at KubeCon China 2021 and get introduced to the new standard of cloud native performance characterisation and to its open source maintainers.
+
Learn what Service Mesh Performance is and how Meshery's implementation uses it to measure the performance of any service mesh available.
随着基于微服务的分布式系统越来越流行，网络作为一门学科，在云原生的高效部署和运行中变得越来越重要已然成为了不可动摇的事实。包括负载均衡，可观察性，鉴权，授权，策略，限速，QoS，Mesh网络，传统基础设施桥接等，正在被整个行业大力发展和投资，这些也是CNCF TAG Network的Service Mesh Working Group的重点。
欢迎大家加入到KubeCon 2021 中国站 Service Mesh Performance Project Office Hours，来了解云原生性能表征的新标准的资讯，以及与项目维护者进行在线互动。
+
欢迎大家来了解什么是服务网格性能以及Meshery如何实现衡量任何可用服务网格的性能。
+
+
+Speakers:
+
+
Sunku Ranganath
+
Lee Calcote
+
Otto Van der Schaaf
+
Nic Jackson
+
Xin Huang
+
Mrittika Ganguli
+
All SMP project maintainers
+
+
diff --git a/src/collections/events/2021/kubecon-china-2021/solving-the-service-mesh-adopters-dilemma-anita-ihuman-kubecon-china-2021_compressed.pdf b/src/collections/events/2021/kubecon-china-2021/solving-the-service-mesh-adopters-dilemma-anita-ihuman-kubecon-china-2021_compressed.pdf
new file mode 100644
index 000000000000..8ba2aedded3e
Binary files /dev/null and b/src/collections/events/2021/kubecon-china-2021/solving-the-service-mesh-adopters-dilemma-anita-ihuman-kubecon-china-2021_compressed.pdf differ
diff --git a/src/collections/events/2021/kubecon2021-na-smp/layer5- solving-the-service-mesh-adopters-dilemma_compressed.pdf b/src/collections/events/2021/kubecon2021-na-smp/layer5- solving-the-service-mesh-adopters-dilemma_compressed.pdf
new file mode 100644
index 000000000000..fc95a78aec73
Binary files /dev/null and b/src/collections/events/2021/kubecon2021-na-smp/layer5- solving-the-service-mesh-adopters-dilemma_compressed.pdf differ
diff --git a/src/collections/events/2022/devconf-2022-measure-smp/index.mdx b/src/collections/events/2022/devconf-2022-measure-smp/index.mdx
index e91d507d7905..8e9526373f09 100644
--- a/src/collections/events/2022/devconf-2022-measure-smp/index.mdx
+++ b/src/collections/events/2022/devconf-2022-measure-smp/index.mdx
@@ -1,114 +1,114 @@
----
-title: "DEVCONF 2022"
-description: "Join Layer5 at DevConf.cz 2022 for insightful talks on CNCF projects Meshery and Service Mesh Performance. Dive into 'Measuring Service Mesh Performance 101' to explore the intricacies of benchmarking service meshes and workload performance."
-date: 2022-01-29
-thumbnail: ./devConf22.webp
-darkthumbnail: ./devConf22.webp
-eurl: https://sched.co/siKF
-type: Event
-event-category: talk
-published: true
-featured: true
-product: Meshery
-resource: true
-upcoming: false
-# Deck: N/A
-# Video: N/A
----
-
-import { Link } from "gatsby";
-
-
- Join Layer5 at DevConf.cz 2022 as
- we share on our CNCF projects Meshery and Service Mesh Performance. Bring
- your questions. We have answers. Engage with us in our talks!
-
-
-Benchmarking a service mesh and your workload’s performance is no simple task. Questions arise like:
-
-
-
Which load generator should you use and what signals should you measure?
-
How long should I run a test?
-
How has the performance of service meshes evolved over time?
-
Should I run tests from outside or within my cluster?
-
How does the configuration of my service mesh affect performance?
-
-
-
-This talk answers these questions by empowering attendees with at-hand tooling for continual evaluation of their service mesh environment and a reflection of how service mesh deployment models affect performance.
-
-
-
-Speakers:
-
-
-
-Engineers adopting microservice architectures are quickly faced with distributed systems challenges and in need of implementing rate limiting, circuit breaking, timeouts, retries, and implementing metrics, logging and tracing into each service is no simple task. Enter the service mesh.
-
-
-
-
Let’s talk about:
-
-
-
-What is a service mesh? Why do you need one?
-What types of service meshes are available? How do they contrast?
-
-Learn how Meshery, a CNCF Project, multi-service mesh management plane implements the service mesh specifications, Service Mesh Performance (SMP) and Service Mesh Interface (SMI), to empower users to manage more than 10 service meshes simultaneously.
-
-Understand how Meshery uses a catalog of Cloud Native Patterns to provide templates for best practice configurations and how you can design new patterns with the visual topology designer, Kanvas
-
-
-
-
Benefits to the ecosystem:
-
-
- Attendees will be empowered with the ability to quickly deploy different
- service meshes in which they may learn how service meshes function and how
- each differs from the next, so that they may select the best-fit-for-purpose
- service mesh for their workloads and their environment. It will be very
- helpful for experienced service mesh operators seeking to learn best practices
- through service mesh design patterns.
-
-
-Speakers:
-
-
-
- Aditya Krishna Sharma
-
-
- Nithish Karthik
-
-
+---
+title: "DEVCONF 2022"
+description: "Join Layer5 at DevConf.cz 2022 for insightful talks on CNCF projects Meshery and Service Mesh Performance. Dive into 'Measuring Service Mesh Performance 101' to explore the intricacies of benchmarking service meshes and workload performance."
+date: 2022-01-29
+thumbnail: ./devConf22.webp
+darkthumbnail: ./devConf22.webp
+eurl: https://sched.co/siKF
+type: Event
+event-category: talk
+published: true
+featured: true
+product: Meshery
+resource: true
+upcoming: false
+# Deck: N/A
+# Video: N/A
+---
+
+
+
+
+ Join Layer5 at DevConf.cz 2022 as
+ we share on our CNCF projects Meshery and Service Mesh Performance. Bring
+ your questions. We have answers. Engage with us in our talks!
+
+
+Benchmarking a service mesh and your workload’s performance is no simple task. Questions arise like:
+
+
+
Which load generator should you use and what signals should you measure?
+
How long should I run a test?
+
How has the performance of service meshes evolved over time?
+
Should I run tests from outside or within my cluster?
+
How does the configuration of my service mesh affect performance?
+
+
+
+This talk answers these questions by empowering attendees with at-hand tooling for continual evaluation of their service mesh environment and a reflection of how service mesh deployment models affect performance.
+
+
+
+Speakers:
+
+
+
+Engineers adopting microservice architectures are quickly faced with distributed systems challenges and in need of implementing rate limiting, circuit breaking, timeouts, retries, and implementing metrics, logging and tracing into each service is no simple task. Enter the service mesh.
+
+
+
+
Let’s talk about:
+
+
+
+What is a service mesh? Why do you need one?
+What types of service meshes are available? How do they contrast?
+
+Learn how Meshery, a CNCF Project, multi-service mesh management plane implements the service mesh specifications, Service Mesh Performance (SMP) and Service Mesh Interface (SMI), to empower users to manage more than 10 service meshes simultaneously.
+
+Understand how Meshery uses a catalog of Cloud Native Patterns to provide templates for best practice configurations and how you can design new patterns with the visual topology designer, Kanvas
+
+
+
+
Benefits to the ecosystem:
+
+
+ Attendees will be empowered with the ability to quickly deploy different
+ service meshes in which they may learn how service meshes function and how
+ each differs from the next, so that they may select the best-fit-for-purpose
+ service mesh for their workloads and their environment. It will be very
+ helpful for experienced service mesh operators seeking to learn best practices
+ through service mesh design patterns.
+
+
+Speakers:
+
+
+
+ Aditya Krishna Sharma
+
+
+ Nithish Karthik
+
+
diff --git a/src/collections/events/2022/devops-and-docker-live/index.mdx b/src/collections/events/2022/devops-and-docker-live/index.mdx
index 2c0e71c330fc..f90ee5de8347 100644
--- a/src/collections/events/2022/devops-and-docker-live/index.mdx
+++ b/src/collections/events/2022/devops-and-docker-live/index.mdx
@@ -1,23 +1,23 @@
----
-title: "DevOps and Docker Live Show"
-description: "Join Bret Fisher, Lee Calcote from Layer5, and Nic Jackson from HashiCorp on the DevOps and Docker Live Show. Witness the Meshery Docker Extension in action as it transforms Docker Desktop into a robust cloud-native infrastructure development environment."
-thumbnail: ./docker-and-meshery-live-show.webp
-darkthumbnail: ./docker-and-meshery-live-show.webp
-date: 2022-09-22
-eurl: https://www.youtube.com/watch?v=FkwD2icthXM
-type: Event
-product: Meshery
-technology: Docker
-resource: true
-speakers: ["Lee Calcote", "Nic Jackson", "Bret Fisher"]
-published: true
-upcoming: false
----
-
-import { Link } from "gatsby" ;
-
-Join host Bret Fisher and guests Lee Calcote from Layer5 and Nic Jackson from HashiCorp at DevOps and Docker Live Show to see the Meshery Docker Extension in-action! Design and deploy your Docker Compose and Kubernetes apps on Docker Desktop or any remote cluster.
-
-The Meshery extension transforms Docker Desktop into powerful cloud native infrastructure development environment in a box with Kubernetes and service mesh. Learn how to discover and model your cloud native deployments with Kanvas. Kanvas enables GitOps integrated, visual composition of your cloud native infrastructure.
-
-Can’t wait to get your hands on Docker Desktop for Meshery in the meantime? Sign up and learn all about the Meshery Docker Extension to make the most out of it.
+---
+title: "DevOps and Docker Live Show"
+description: "Join Bret Fisher, Lee Calcote from Layer5, and Nic Jackson from HashiCorp on the DevOps and Docker Live Show. Witness the Meshery Docker Extension in action as it transforms Docker Desktop into a robust cloud-native infrastructure development environment."
+thumbnail: ./docker-and-meshery-live-show.webp
+darkthumbnail: ./docker-and-meshery-live-show.webp
+date: 2022-09-22
+eurl: https://www.youtube.com/watch?v=FkwD2icthXM
+type: Event
+product: Meshery
+technology: Docker
+resource: true
+speakers: ["Lee Calcote", "Nic Jackson", "Bret Fisher"]
+published: true
+upcoming: false
+---
+
+
+
+Join host Bret Fisher and guests Lee Calcote from Layer5 and Nic Jackson from HashiCorp at DevOps and Docker Live Show to see the Meshery Docker Extension in-action! Design and deploy your Docker Compose and Kubernetes apps on Docker Desktop or any remote cluster.
+
+The Meshery extension transforms Docker Desktop into powerful cloud native infrastructure development environment in a box with Kubernetes and service mesh. Learn how to discover and model your cloud native deployments with Kanvas. Kanvas enables GitOps integrated, visual composition of your cloud native infrastructure.
+
+Can’t wait to get your hands on Docker Desktop for Meshery in the meantime? Sign up and learn all about the Meshery Docker Extension to make the most out of it.
diff --git a/src/collections/events/2022/docker-community-meetup-2022-hacktoberfest/index.mdx b/src/collections/events/2022/docker-community-meetup-2022-hacktoberfest/index.mdx
index dbd7592353f7..06f9afbafa78 100644
--- a/src/collections/events/2022/docker-community-meetup-2022-hacktoberfest/index.mdx
+++ b/src/collections/events/2022/docker-community-meetup-2022-hacktoberfest/index.mdx
@@ -1,51 +1,51 @@
----
-title: "Hacktoberfest 2022: Docker Extensions Show-n-Tell"
-description: "Join Layer5 in person at the Docker Community Meetup in Bengaluru as we unveil the Meshery Docker Extension and demonstrate how it revolutionizes the management of cloud-native applications. Explore the Meshery Docker Extension with a deep dive into its basic concepts, architecture, and components"
-date: 2022-10-22
-thumbnail: ./dockerBengaluru.webp
-darkthumbnail: ./dockerBengaluru.webp
-eurl: https://www.meetup.com/docker-bangalore/events/288597531/
-type: Meetups
-event-category: talk
-published: true
-featured: true
-product: Meshery Extensions
-resource: true
-upcoming: false
-# Deck: N/A
-# Video: N/A
----
-
-import { Link } from "gatsby";
-
-
- Join Layer5 in-person at Docker Community Meetup - Bengaluru as
- we share on the Meshery Docker Extension and how you can manage your cloud native applications using it.
-
-
-
-
Take the Blinders off with Meshery Docker Extension
-
-
-
-Managing cloud native infrastructure becomes a nightmare with hundreds of distributed systems. Vectors like performance, and metrics are game changers but not precisely interpreted. Meshery Docker Extension is here to empower engineers so they can extract more value from their infrastructure.
-
-
What will you learn?
-
-
An introduction to basic concepts, architecture diagrams, and general ideas about the functioning of different components of Meshery Docker Extension
-
Performance Management and Metrics Intro, how to run performance tests, interpret the results, and metrics from Grafana and Prometheus.
-
An introduction to service meshes, the concept of meshery adapters, provisioning of service meshes, sample applications and SMI conformance tests.
Introduction to Kanvas, the visual topology for your cloud native infrastructure.
-
Hacktoberfest participation for newcomers in the community, how to get started, open issues and how to engage in the community.
-
-
-Speakers:
-
-
-
- Pranav Singh
-
-
-
-
+---
+title: "Hacktoberfest 2022: Docker Extensions Show-n-Tell"
+description: "Join Layer5 in person at the Docker Community Meetup in Bengaluru as we unveil the Meshery Docker Extension and demonstrate how it revolutionizes the management of cloud-native applications. Explore the Meshery Docker Extension with a deep dive into its basic concepts, architecture, and components"
+date: 2022-10-22
+thumbnail: ./dockerBengaluru.webp
+darkthumbnail: ./dockerBengaluru.webp
+eurl: https://www.meetup.com/docker-bangalore/events/288597531/
+type: Meetups
+event-category: talk
+published: true
+featured: true
+product: Meshery Extensions
+resource: true
+upcoming: false
+# Deck: N/A
+# Video: N/A
+---
+
+
+
+
+ Join Layer5 in-person at Docker Community Meetup - Bengaluru as
+ we share on the Meshery Docker Extension and how you can manage your cloud native applications using it.
+
+
+
+
Take the Blinders off with Meshery Docker Extension
+
+
+
+Managing cloud native infrastructure becomes a nightmare with hundreds of distributed systems. Vectors like performance, and metrics are game changers but not precisely interpreted. Meshery Docker Extension is here to empower engineers so they can extract more value from their infrastructure.
+
+
What will you learn?
+
+
An introduction to basic concepts, architecture diagrams, and general ideas about the functioning of different components of Meshery Docker Extension
+
Performance Management and Metrics Intro, how to run performance tests, interpret the results, and metrics from Grafana and Prometheus.
+
An introduction to service meshes, the concept of meshery adapters, provisioning of service meshes, sample applications and SMI conformance tests.
Introduction to Kanvas, the visual topology for your cloud native infrastructure.
+
Hacktoberfest participation for newcomers in the community, how to get started, open issues and how to engage in the community.
+
+
+Speakers:
+
+
+
+ Pranav Singh
+
+
+
+
diff --git a/src/collections/events/2022/docker-developer-community-meetup-2022/index.mdx b/src/collections/events/2022/docker-developer-community-meetup-2022/index.mdx
index 8fdfb1e63e5b..e2f999c0078b 100644
--- a/src/collections/events/2022/docker-developer-community-meetup-2022/index.mdx
+++ b/src/collections/events/2022/docker-developer-community-meetup-2022/index.mdx
@@ -1,54 +1,53 @@
----
-title: "Composing Cloud Native Infrastructure with Docker Desktop and Meshery"
-description: "Unlock the potential of your microservices development with the Meshery Docker Extension. Join speakers Aditya Krishna Sharma and Karthik Ravishankar as they showcase the extension's ability to import Docker Compose apps, seamlessly convert them to Kubernetes applications, and deploy them on any service mesh."
-date: 2022-06-11
-thumbnail: ./dockerBengaluru.webp
-darkthumbnail: ./dockerBengaluru.webp
-eurl: https://www.meetup.com/Docker-Bangalore/events/285342797/
-type: Meetups
-event-category: talk
-published: true
-featured: true
-product: Meshery Extensions
-resource: true
-upcoming: false
-# Deck: N/A
-# Video: N/A
----
-
-import { Link } from "gatsby";
-
-
- Join Layer5 in-person at Docker Developer Community Meetup - Bengaluru as
- we share on the Meshery Docker Extension and how you can manage your cloud native applications using it.
-
-
-
-
Composing Cloud Native Infrastructure with Docker Desktop and Meshery
-
-
-
-
-The Meshery Docker Extension’s ability to import Docker Compose apps, convert them to Kubernetes applications, and deploy them on any visually and collaboratively is a powerful enabler for microservices developers, who need to develop, test, and deploy their modern applications in the context of and compatibility with any Kubernetes cluster. Along with this, the extension can help you to:
-
-
-
Get Kubernetes support for your Docker Compose apps: Import your Docker Compose apps. Configure and deploy them to Kubernetes and any infrastructure with a Kubernetes Operator.
-
Help you with single-click deployment of your infrastructure - Support of 250+ different cloud native infrastructure projects (including all the CNCF projects) at the fingertips of developers in connection with Docker Desktop’s ability to deliver Kubernetes locally.: Supports 10 different service meshes to the fingertips of developers in connection with Docker Desktop’s ability to deliver Kubernetes locally.
-
Detection of Kubernetes environments: Scan your kubeconfigs and select your current Kubernetes environment. Switch from one environment to another.
-
-
-This talk can help the attendees to improve upon their K8s or Docker deployments as well as help them in managing different service meshes simultaneously. I have a pretty basic knowledge of cloud native stuff having worked with Kubernetes, Docker, Helm, and using some of the service meshes, trying them out for different stuff or applications. I have been using Docker Desktop for the past year and a half. I’m also a maintainer of Meshery and have contributed to several other open source projects.
-
-
-
-Speakers:
-
-
-
- Aditya Krishna Sharma
-
-
Karthik Ravishankar
-
-
-
-
+---
+title: "Composing Cloud Native Infrastructure with Docker Desktop and Meshery"
+description: "Unlock the potential of your microservices development with the Meshery Docker Extension. Join speakers Aditya Krishna Sharma and Karthik Ravishankar as they showcase the extension's ability to import Docker Compose apps, seamlessly convert them to Kubernetes applications, and deploy them on any service mesh."
+date: 2022-06-11
+thumbnail: ./dockerBengaluru.webp
+darkthumbnail: ./dockerBengaluru.webp
+eurl: https://www.meetup.com/Docker-Bangalore/events/285342797/
+type: Meetups
+event-category: talk
+published: true
+featured: true
+product: Meshery Extensions
+resource: true
+upcoming: false
+# Deck: N/A
+# Video: N/A
+---
+
+
+
+
+ Join Layer5 in-person at Docker Developer Community Meetup - Bengaluru as
+ we share on the Meshery Docker Extension and how you can manage your cloud native applications using it.
+
+
+
+
Composing Cloud Native Infrastructure with Docker Desktop and Meshery
+
+
+
+
+The Meshery Docker Extension’s ability to import Docker Compose apps, convert them to Kubernetes applications, and deploy them on any visually and collaboratively is a powerful enabler for microservices developers, who need to develop, test, and deploy their modern applications in the context of and compatibility with any Kubernetes cluster. Along with this, the extension can help you to:
+
+
+
Get Kubernetes support for your Docker Compose apps: Import your Docker Compose apps. Configure and deploy them to Kubernetes and any infrastructure with a Kubernetes Operator.
+
Help you with single-click deployment of your infrastructure - Support of 250+ different cloud native infrastructure projects (including all the CNCF projects) at the fingertips of developers in connection with Docker Desktop’s ability to deliver Kubernetes locally.: Supports 10 different service meshes to the fingertips of developers in connection with Docker Desktop’s ability to deliver Kubernetes locally.
+
Detection of Kubernetes environments: Scan your kubeconfigs and select your current Kubernetes environment. Switch from one environment to another.
+
+
+This talk can help the attendees to improve upon their K8s or Docker deployments as well as help them in managing different service meshes simultaneously. I have a pretty basic knowledge of cloud native stuff having worked with Kubernetes, Docker, Helm, and using some of the service meshes, trying them out for different stuff or applications. I have been using Docker Desktop for the past year and a half. I’m also a maintainer of Meshery and have contributed to several other open source projects.
+
+
+
+Speakers:
+
+
+
+ Aditya Krishna Sharma
+
+
Karthik Ravishankar
+
+
+
diff --git a/src/collections/events/2022/dockercon-2022/lighting-talk-in-a-dedicated-community-room.mdx b/src/collections/events/2022/dockercon-2022/lighting-talk-in-a-dedicated-community-room.mdx
index ec89f7e35efe..423b1a25454b 100644
--- a/src/collections/events/2022/dockercon-2022/lighting-talk-in-a-dedicated-community-room.mdx
+++ b/src/collections/events/2022/dockercon-2022/lighting-talk-in-a-dedicated-community-room.mdx
@@ -1,27 +1,27 @@
----
-title: "DockerCon 2022: Lighting Talk in a dedicated community room"
-description: "Discover how HPE Security Engineering achieves workload identity and attestation across all service meshes with the Meshery Docker Extension. Leveraging this extension, HPE tests the performance of their SPIFFE and SPIRE-based identity solution on their service mesh of choice."
-thumbnail: ./HPE.webp
-darkthumbnail: ./HPE.webp
-date: 2022-05-10
-eurl: https://docker.events.cube365.net/dockercon/2022
-type: Event
-product: Meshery
-technology: Docker
-resource: true
-speakers: ["Lee Calcote", "Maximiliano Churichi"]
-published: true
-upcoming: false
----
-
-import { Link } from "gatsby" ;
-
-With a goal to bring workload identity and attestation to all service meshes, HPE Security Engineering uses the Docker Desktop Extension for Meshery to deploy their service mesh of choice and test the performance of their SPIFFE and SPIRE-based identity solution.
-
-The Meshery extension transforms Docker Desktop into powerful load generation utility, conveniently enables HPE engineers with the ability to deploy and configure any service mesh with a click of the button and invoke and control load-based performance tests from their desktop.
-
-Can’t wait to get your hands on Docker Desktop for Meshery in the meantime? Sign up for our beta program to get early access!
-
-
-Read the recap blog post and find out more about Docker Extension for Meshery.
+---
+title: "DockerCon 2022: Lighting Talk in a dedicated community room"
+description: "Discover how HPE Security Engineering achieves workload identity and attestation across all service meshes with the Meshery Docker Extension. Leveraging this extension, HPE tests the performance of their SPIFFE and SPIRE-based identity solution on their service mesh of choice."
+thumbnail: ./HPE.webp
+darkthumbnail: ./HPE.webp
+date: 2022-05-10
+eurl: https://docker.events.cube365.net/dockercon/2022
+type: Event
+product: Meshery
+technology: Docker
+resource: true
+speakers: ["Lee Calcote", "Maximiliano Churichi"]
+published: true
+upcoming: false
+---
+
+
+
+With a goal to bring workload identity and attestation to all service meshes, HPE Security Engineering uses the Docker Desktop Extension for Meshery to deploy their service mesh of choice and test the performance of their SPIFFE and SPIRE-based identity solution.
+
+The Meshery extension transforms Docker Desktop into powerful load generation utility, conveniently enables HPE engineers with the ability to deploy and configure any service mesh with a click of the button and invoke and control load-based performance tests from their desktop.
+
+Can’t wait to get your hands on Docker Desktop for Meshery in the meantime? Sign up for our beta program to get early access!
+
+
\ No newline at end of file
diff --git a/src/collections/events/2022/dockercon-2022/lightning-talk-on-the-main-stage.mdx b/src/collections/events/2022/dockercon-2022/lightning-talk-on-the-main-stage.mdx
index fcdb30079a89..80928e74597e 100644
--- a/src/collections/events/2022/dockercon-2022/lightning-talk-on-the-main-stage.mdx
+++ b/src/collections/events/2022/dockercon-2022/lightning-talk-on-the-main-stage.mdx
@@ -1,28 +1,28 @@
----
-title: "DockerCon 2022: Lighting Talk on the main stage"
-description: "Explore the unique functionalities of HashiCorp’s Consul service mesh with Meshery. Using the visual designer, Kanvas, Meshery empowers developers to fully understand Consul's differentiated capabilities, enabling visual configuration and deployment of Consul-based deployments and workloads."
-thumbnail: ./Hashicorp.webp
-darkthumbnail: ./Hashicorp.webp
-date: 2022-05-10
-eurl: https://docker.events.cube365.net/dockercon/2022
-type: Event
-product: Meshery
-technology: Docker
-resource: true
-speakers: ["Lee Calcote", "Nic Jackson"]
-published: true
-upcoming: false
-featured: true
----
-
-import { Link } from "gatsby" ;
-
-HashiCorp’s Consul service mesh offers unique functionality offered to its users. Using its visual designer, Kanvas, Meshery facilitates the developers full understanding of Consul’s differientiated capabilities, allowing developer’s to visually configure and deploy Consul-based deployments and their workloads.
-
-The Meshery extension’s ability to import Docker Compose apps, convert them to Kubernetes applications, and deploy them on Consult service meshes is a powerful enabler for microservices developers, who need to dev, test, and deploy their modern applications in context of and compatibility with Consul service mesh.
-
-Can’t wait to get your hands on Docker Desktop for Meshery in the meantime? Sign up for our beta program to get early access!
-
-
-Read the recap blog post and find out more about Docker Extension for Meshery.
+---
+title: "DockerCon 2022: Lighting Talk on the main stage"
+description: "Explore the unique functionalities of HashiCorp’s Consul service mesh with Meshery. Using the visual designer, Kanvas, Meshery empowers developers to fully understand Consul's differentiated capabilities, enabling visual configuration and deployment of Consul-based deployments and workloads."
+thumbnail: ./Hashicorp.webp
+darkthumbnail: ./Hashicorp.webp
+date: 2022-05-10
+eurl: https://docker.events.cube365.net/dockercon/2022
+type: Event
+product: Meshery
+technology: Docker
+resource: true
+speakers: ["Lee Calcote", "Nic Jackson"]
+published: true
+upcoming: false
+featured: true
+---
+
+
+
+HashiCorp’s Consul service mesh offers unique functionality offered to its users. Using its visual designer, Kanvas, Meshery facilitates the developers full understanding of Consul’s differientiated capabilities, allowing developer’s to visually configure and deploy Consul-based deployments and their workloads.
+
+The Meshery extension’s ability to import Docker Compose apps, convert them to Kubernetes applications, and deploy them on Consult service meshes is a powerful enabler for microservices developers, who need to dev, test, and deploy their modern applications in context of and compatibility with Consul service mesh.
+
+Can’t wait to get your hands on Docker Desktop for Meshery in the meantime? Sign up for our beta program to get early access!
+
+
\ No newline at end of file
diff --git a/src/collections/events/2022/kubecon-eu-2022/index.mdx b/src/collections/events/2022/kubecon-eu-2022/index.mdx
index 1cb84e98766e..b78520eb1039 100644
--- a/src/collections/events/2022/kubecon-eu-2022/index.mdx
+++ b/src/collections/events/2022/kubecon-eu-2022/index.mdx
@@ -1,21 +1,21 @@
----
-title: "KubeCon + CloudNativeCon EU Virtual 2022"
-description: "Dive deep into the world of microservice-based distributed systems with 'CNCF TAG Network and Service Mesh Working Group"
-date: 2022-05-16
-thumbnail: ./kubecon-eu-2022.jpeg
-darkthumbnail: ./kubecon-eu-2022.jpeg
-eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
-type: Event
-published: true
-upcoming: false
-feature: true
-speakers: ["Ken Owens", "Lee Calcote", "Ed Warnicke"]
-
----
-
-Join Layer5 at KubeCon + CloudNativeCon EU Virtual 2022. Engage with us in our talks and booth!
-
-
CNCF Tag Network and Service mesh Working Group Deep Dive
-
-With the increasing prevalence of microservice-based distributed systems, this is true: the network, as a discipline, has never been so critical in the efficient operation of cloud-native deployments. Network primitives including load balancing, observability, authentication, authorization, policies, rate limiting, QoS, mesh networks, traditional infrastructure bridging, and so on are now being developed and invested by the entire industry, and are the focus of the Service Mesh Working Group withing the CNCF TAG Network. Listen to our introduction and get an in-depth understanding of the service mesh projects being managed within the working group.
-
+---
+title: "KubeCon + CloudNativeCon EU Virtual 2022"
+description: "Dive deep into the world of microservice-based distributed systems with 'CNCF TAG Network and Service Mesh Working Group"
+date: 2022-05-16
+thumbnail: ./kubecon-eu-2022.jpeg
+darkthumbnail: ./kubecon-eu-2022.jpeg
+eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
+type: Event
+published: true
+upcoming: false
+feature: true
+speakers: ["Ken Owens", "Lee Calcote", "Ed Warnicke"]
+
+---
+
+Join Layer5 at KubeCon + CloudNativeCon EU Virtual 2022. Engage with us in our talks and booth!
+
+
CNCF Tag Network and Service mesh Working Group Deep Dive
+
+With the increasing prevalence of microservice-based distributed systems, this is true: the network, as a discipline, has never been so critical in the efficient operation of cloud-native deployments. Network primitives including load balancing, observability, authentication, authorization, policies, rate limiting, QoS, mesh networks, traditional infrastructure bridging, and so on are now being developed and invested by the entire industry, and are the focus of the Service Mesh Working Group withing the CNCF TAG Network. Listen to our introduction and get an in-depth understanding of the service mesh projects being managed within the working group.
+
diff --git a/src/collections/events/2022/kubecon-na-2022/index.mdx b/src/collections/events/2022/kubecon-na-2022/index.mdx
index 5f2082a8a57c..9acc02f381e2 100644
--- a/src/collections/events/2022/kubecon-na-2022/index.mdx
+++ b/src/collections/events/2022/kubecon-na-2022/index.mdx
@@ -51,7 +51,7 @@ Join Laye
Join CNCF Technical Advisory Group co-chair and Layer5's founder, Lee Calcote as he discusses the many projects of TAG Network and its working groups. NATs, Network Service Mesh, BFE, Contour, Kuma, Service Mesh Interface, Chaos Mesh, Open Service Mesh, Emissary, k8gb, Service Mesh Performance, Submariner, Cilium, Meshery, Fab Edge, Istio, Nighthawk, Aeraki, and FabEdge are just a few of the many terms used to describe cloud native networking. Learn more by comparing service meshes.
-
+
Date: October 27, 2022
Time: 4:30 - 5:05 pm ET
diff --git a/src/collections/events/2022/ossna-2022/index.mdx b/src/collections/events/2022/ossna-2022/index.mdx
index 30d3893dc967..2b192d9c0fc5 100644
--- a/src/collections/events/2022/ossna-2022/index.mdx
+++ b/src/collections/events/2022/ossna-2022/index.mdx
@@ -1,26 +1,26 @@
----
-title: 'Open Source Summit North America 2022'
-description: 'Explore open source with MeshMates, a mentorship program by Layer5. Designed to help new contributors, especially students, MeshMates offer personalized, one-on-one guidance, making open source participation accessible and enjoyable.'
-date: 2022-06-24
-thumbnail: ./oss-na-2022.webp
-darkthumbnail: ./oss-na-2022.webp
-eurl: https://events.linuxfoundation.org/open-source-summit-north-america/
-type: Event
-published: true
-upcoming: false
-feature: true
-speakers: ['Shivay Lamba']
----
-
-import { Link } from 'gatsby';
-
-
MeshMates: A New Way of Expanding Open Source Community Mentorship
-
-A lot of young developers especially college students who want to contribute to open source projects feel intimidated by the lack of experience and the size of the code. For a beginner, open source projects codebase can be intimidating at first. Traditionally they may contact community members or mentors to help them understand but it is not always the most effective solution.
-
-Therefore Layer5 ( a CNCF member company) introduced a program called Meshmates. MeshMates who are members part of the Layer5 community, provide one to one mentorship to new joiners in the community, from helping them identifying areas of projects to engage within, working groups to join, and in helping community members grow in their open source and cloud native knowledge.
-
-
-What makes the MeshMate program really successful is the 1 to 1 personalized mentorship with the aim to make new joiners comfortable with opens source and mentoring them to get their first open source commit! Thus making MeshMate one of the most engaging and amazing community experience possible.
-
-
+---
+title: 'Open Source Summit North America 2022'
+description: 'Explore open source with MeshMates, a mentorship program by Layer5. Designed to help new contributors, especially students, MeshMates offer personalized, one-on-one guidance, making open source participation accessible and enjoyable.'
+date: 2022-06-24
+thumbnail: ./oss-na-2022.webp
+darkthumbnail: ./oss-na-2022.webp
+eurl: https://events.linuxfoundation.org/open-source-summit-north-america/
+type: Event
+published: true
+upcoming: false
+feature: true
+speakers: ['Shivay Lamba']
+---
+
+
+
+
MeshMates: A New Way of Expanding Open Source Community Mentorship
+
+A lot of young developers especially college students who want to contribute to open source projects feel intimidated by the lack of experience and the size of the code. For a beginner, open source projects codebase can be intimidating at first. Traditionally they may contact community members or mentors to help them understand but it is not always the most effective solution.
+
+Therefore Layer5 ( a CNCF member company) introduced a program called Meshmates. MeshMates who are members part of the Layer5 community, provide one to one mentorship to new joiners in the community, from helping them identifying areas of projects to engage within, working groups to join, and in helping community members grow in their open source and cloud native knowledge.
+
+
+What makes the MeshMate program really successful is the 1 to 1 personalized mentorship with the aim to make new joiners comfortable with opens source and mentoring them to get their first open source commit! Thus making MeshMate one of the most engaging and amazing community experience possible.
+
+
diff --git a/src/collections/events/2022/servicemeshcon-EU-2022/index.mdx b/src/collections/events/2022/servicemeshcon-EU-2022/index.mdx
index d50dd4b0efbe..1f975cf5aa93 100644
--- a/src/collections/events/2022/servicemeshcon-EU-2022/index.mdx
+++ b/src/collections/events/2022/servicemeshcon-EU-2022/index.mdx
@@ -1,31 +1,31 @@
----
-title: "ServiceMeshCon EU 2022"
-description: "Unlock the true potential of your cloud-native infrastructure with MeshMark, a cutting-edge performance index by Layer5, ServiceMeshCon EU 2022"
-date: 2022-05-17
-thumbnail: ./servicemeshcon22.webp
-darkthumbnail: ./servicemeshcon22.webp
-eurl: https://events.linuxfoundation.org/servicemeshcon-europe/
-type: Event
-published: true
-upcoming: false
-speakers: ["Lee Calcote","Mrittika Ganguli"]
----
-
-import { Link } from "gatsby";
-import IntelLogo from "../../../../assets/images/partners/intel_blue.svg";
-import Layer5Logo from "../../../../assets/images/layer5/layer5-only/svg/layer5-no-trim.svg";
-
-Join Layer5 at ServiceMeshCon Europe 2022. ServiceMeshCon is a vendor-neutral conference on service mesh technologies. Topics include getting started with and adopting a mesh, lessons learned from production deployments, and technical sessions from service mesh maintainers.
-
-
-Still trying to understand how to best gauge the performance of your cloud native infrastructure? Confused as to whether self-published, performance benchmarks are trustworthy or simply biased marketing in disguise? Measurement data may not provide a clear and simple picture of how well those applications are performing from a business point of view, a characteristic desired in metrics that are used as key performance indicators. Behold MeshMark: a performance index that provides you with the ability to weigh the value vs overhead of your cloud native environment. Convert performance measurements into insights about the value of individual, cloud native application networking functions. Join us as we distill a variety of microarchitecture performance signals and application key performance indicators into a simple scale. Explore the other side of the performance measurement coin: value measurement.
-
-
Participating Organizations
-
-
-
-
-
-Read the recap blog post and find out more about MeshMark.
+---
+title: "ServiceMeshCon EU 2022"
+description: "Unlock the true potential of your cloud-native infrastructure with MeshMark, a cutting-edge performance index by Layer5, ServiceMeshCon EU 2022"
+date: 2022-05-17
+thumbnail: ./servicemeshcon22.webp
+darkthumbnail: ./servicemeshcon22.webp
+eurl: https://events.linuxfoundation.org/servicemeshcon-europe/
+type: Event
+published: true
+upcoming: false
+speakers: ["Lee Calcote","Mrittika Ganguli"]
+---
+
+import { Link } from "gatsby";
+import IntelLogo from "../../../../assets/images/partners/intel_blue.svg";
+import Layer5Logo from "../../../../assets/images/layer5/layer5-only/svg/layer5-no-trim.svg";
+
+Join Layer5 at ServiceMeshCon Europe 2022. ServiceMeshCon is a vendor-neutral conference on service mesh technologies. Topics include getting started with and adopting a mesh, lessons learned from production deployments, and technical sessions from service mesh maintainers.
+
+
+Still trying to understand how to best gauge the performance of your cloud native infrastructure? Confused as to whether self-published, performance benchmarks are trustworthy or simply biased marketing in disguise? Measurement data may not provide a clear and simple picture of how well those applications are performing from a business point of view, a characteristic desired in metrics that are used as key performance indicators. Behold MeshMark: a performance index that provides you with the ability to weigh the value vs overhead of your cloud native environment. Convert performance measurements into insights about the value of individual, cloud native application networking functions. Join us as we distill a variety of microarchitecture performance signals and application key performance indicators into a simple scale. Explore the other side of the performance measurement coin: value measurement.
+
+
Participating Organizations
+
+
+
+
+
+Read the recap blog post and find out more about MeshMark.
\ No newline at end of file
diff --git a/src/collections/events/2023/IstioCon 2023/index.mdx b/src/collections/events/2023/IstioCon 2023/index.mdx
index 31ecb63f95e7..ccfdb86c4aaf 100644
--- a/src/collections/events/2023/IstioCon 2023/index.mdx
+++ b/src/collections/events/2023/IstioCon 2023/index.mdx
@@ -1,18 +1,18 @@
----
-title: "IstioCon Virtual 2023"
-description: "Embark on a collaborative journey with Layer5 and Intel at IstioCon! Join us on September 25th to 26th for Multiplayer Istio: Collaborative WASM Plugins."
-date: 2023-09-25
-eurl: "https://events.linuxfoundation.org/istiocon/"
-thumbnail: ./IstioCon2023.png
-darkthumbnail: ./IstioCon2023.png
-type: Event
-published: true
-resource: true
-upcoming: false
-speakers: ["Lee Calcote", "Xin Huang"]
----
-
-
Multiplayer Istio: Collaborative WASM Plugins with Intel and Layer5
-
-
Join Layer5 and Intel at the Istio conference on Monday, Sept. 25th to Tuesday, Sep. 26th. IstioCon is a 100% virtual event that is designed to connect community members across the globe with Istio and the Istio ecosystem.
- Register Here
+---
+title: "IstioCon Virtual 2023"
+description: "Embark on a collaborative journey with Layer5 and Intel at IstioCon! Join us on September 25th to 26th for Multiplayer Istio: Collaborative WASM Plugins."
+date: 2023-09-25
+eurl: "https://events.linuxfoundation.org/istiocon/"
+thumbnail: ./IstioCon2023.png
+darkthumbnail: ./IstioCon2023.png
+type: Event
+published: true
+resource: true
+upcoming: false
+speakers: ["Lee Calcote", "Xin Huang"]
+---
+
+
Multiplayer Istio: Collaborative WASM Plugins with Intel and Layer5
+
+
Join Layer5 and Intel at the Istio conference on Monday, Sept. 25th to Tuesday, Sep. 26th. IstioCon is a 100% virtual event that is designed to connect community members across the globe with Istio and the Istio ecosystem.
+ Register Here
diff --git a/src/collections/events/2023/hacktoberfest-2023-docker-ext/index.mdx b/src/collections/events/2023/hacktoberfest-2023-docker-ext/index.mdx
index 3a863214dfda..68f4a79f4698 100644
--- a/src/collections/events/2023/hacktoberfest-2023-docker-ext/index.mdx
+++ b/src/collections/events/2023/hacktoberfest-2023-docker-ext/index.mdx
@@ -1,52 +1,53 @@
----
-title: "Hacktoberfest Prep 2023: Extending Docker Desktop"
-description: "Prepare for Hacktoberfest with Layer5 MeshMates and Maintainers. Join seasoned open source maintainers, hack through easy issues, and grow your skills. Discover Newcomers Resources and explore the Layer5 Community Handbook."
-thumbnail: ./hacktoberfest2023.png
-darkthumbnail: ./hacktoberfest2023.png
-date: 2023-10-03
-eurl: /community/calendar
-type: Event
-speakers: ["Gaurav Chadha", "Pranav Singh", "Uzair Shaikh", "Yash Sharma", "Anita Ihuman", "Saurabh Soni", "Ritik Saxena", "Senali Dilumika", "Sudhanshu Dasgupta", "Rex Joshua Ibegbu"]
-published: true
-upcoming: false
-register: false
----
-
-import { Link } from "gatsby" ;
-import { EventWrapper } from "../../Event.style.js";
-
-import hacktoberfestprepslides from "./hacktoberfest-prep-easing-into-cncf-open-source-projects.pdf";
-import hacktoberfestBadge from "./hacktoberfest-contributor.png";
-import dockerExtension from "./docker-extension-meshery.svg";
-import manageWithMeshery from "./docker-extension-meshery.svg";
-
-
-
-Hacktoberfest is just around the corner. You'd be surprised to know how small changes can make a big impact on a project. The more a project scales, the easier it is for small errors to live within it. You can make a real difference by fixing these relatively easier issues and continue to grow from there.
-
-
-
-Prepare for Hacktoberfest and ready yourself for contributing to Docker Extensions the easy way with Layer5 MeshMates and Maintainers. Using the Docker Meshery Extension, spend an hour with seasoned, open source maintainers and hack your way through. To get a headstart, see our Newcomers Resources. Get familiar with the Layer5 community through our Community Handbook.
-
Earn a Hacktoberfest Contributor badge by contributing to Layer5 projects during this Hacktoberfest.
-
-
+---
+title: "Hacktoberfest Prep 2023: Extending Docker Desktop"
+description: "Prepare for Hacktoberfest with Layer5 MeshMates and Maintainers. Join seasoned open source maintainers, hack through easy issues, and grow your skills. Discover Newcomers Resources and explore the Layer5 Community Handbook."
+thumbnail: ./hacktoberfest2023.png
+darkthumbnail: ./hacktoberfest2023.png
+date: 2023-10-03
+eurl: /community/calendar
+type: Event
+speakers: ["Gaurav Chadha", "Pranav Singh", "Uzair Shaikh", "Yash Sharma", "Anita Ihuman", "Saurabh Soni", "Ritik Saxena", "Senali Dilumika", "Sudhanshu Dasgupta", "Rex Joshua Ibegbu"]
+published: true
+upcoming: false
+register: false
+---
+
+import { Link } from "gatsby" ;
+import { EventWrapper } from "../../Event.style.js";
+
+import hacktoberfestprepslides from "./hacktoberfest-prep-easing-into-cncf-open-source-projects.pdf";
+import hacktoberfestBadge from "./hacktoberfest-contributor.png";
+import dockerExtension from "./docker-extension-meshery.svg";
+import manageWithMeshery from "./docker-extension-meshery.svg";
+
+
+
+Hacktoberfest is just around the corner. You'd be surprised to know how small changes can make a big impact on a project. The more a project scales, the easier it is for small errors to live within it. You can make a real difference by fixing these relatively easier issues and continue to grow from there.
+
+
+
+Prepare for Hacktoberfest and ready yourself for contributing to Docker Extensions the easy way with Layer5 MeshMates and Maintainers. Using the Docker Meshery Extension, spend an hour with seasoned, open source maintainers and hack your way through. To get a headstart, see our Newcomers Resources. Get familiar with the Layer5 community through our Community Handbook.
+
Earn a Hacktoberfest Contributor badge by contributing to Layer5 projects during this Hacktoberfest.
+
+
\ No newline at end of file
diff --git a/src/collections/events/2023/hacktoberfest-2023/hacktoberfest-prep-easing-into-cncf-open-source-projects_compressed.pdf b/src/collections/events/2023/hacktoberfest-2023/hacktoberfest-prep-easing-into-cncf-open-source-projects_compressed.pdf
new file mode 100644
index 000000000000..f9d81a0b46ec
Binary files /dev/null and b/src/collections/events/2023/hacktoberfest-2023/hacktoberfest-prep-easing-into-cncf-open-source-projects_compressed.pdf differ
diff --git a/src/collections/events/2023/kcd-chennai-2023/index.mdx b/src/collections/events/2023/kcd-chennai-2023/index.mdx
index 313f38d3907b..cf0710532e39 100644
--- a/src/collections/events/2023/kcd-chennai-2023/index.mdx
+++ b/src/collections/events/2023/kcd-chennai-2023/index.mdx
@@ -1,18 +1,18 @@
----
-title: "KCD Chennai 2023"
-description: "Discover how Meshery transforms orchestration across multiple environments, leveraging GitOps principles and fostering multi-user collaboration. Join us for an insightful session at KCD Chennai 2023!"
-date: 2023-07-22
-thumbnail: ./kcd_chennai.webp
-darkthumbnail: ./kcd_chennai.webp
-eurl: https://www.kcdchennai.in/
-type: Event
-published: true
-product: Kanvas, Meshery
-resource: true
-upcoming: false
-speakers: ["Pranav Singh"]
----
-
-
-
Multiplayer Kubernetes: GitOps with Friends
+---
+title: "KCD Chennai 2023"
+description: "Discover how Meshery transforms orchestration across multiple environments, leveraging GitOps principles and fostering multi-user collaboration. Join us for an insightful session at KCD Chennai 2023!"
+date: 2023-07-22
+thumbnail: ./kcd_chennai.webp
+darkthumbnail: ./kcd_chennai.webp
+eurl: https://www.kcdchennai.in/
+type: Event
+published: true
+product: Kanvas, Meshery
+resource: true
+upcoming: false
+speakers: ["Pranav Singh"]
+---
+
+
+
Multiplayer Kubernetes: GitOps with Friends
Join Pranav Singh at KCD Chennai 2023 to witness firsthand how Meshery revolutionizes Kubernetes operations, enabling seamless orchestration across multiple environments made possible by GitOps principles and multi-user collaboration..
\ No newline at end of file
diff --git a/src/collections/events/2023/kickstarting-open-source-with-layer5-2023/index.mdx b/src/collections/events/2023/kickstarting-open-source-with-layer5-2023/index.mdx
index 48b9df1eb36d..d644338e3817 100644
--- a/src/collections/events/2023/kickstarting-open-source-with-layer5-2023/index.mdx
+++ b/src/collections/events/2023/kickstarting-open-source-with-layer5-2023/index.mdx
@@ -1,19 +1,19 @@
----
-title: "Kickstarting Open Source with Layer5"
-description: "Gain valuable insights into Layer5's projects as this dynamic duo guides you through the world of open source."
-date: 2023-08-19
-thumbnail: ./kickstarting_your_open_source_with_layer5.webp
-darkthumbnail: ./kickstarting_your_open_source_with_layer5.webp
-eurl: https://lu.ma/z5sjbqws
-type: Event
-published: true
-product: Kanvas, Meshery
-resource: true
-upcoming: false
-speakers: ["Yash Sharma", "Samyak Shah"]
----
-
-
-
Kickstarting Open Source with Layer5
-
Embark on your Open Source journey with an insightful session led by Layer5's community member Samyak . Joining him is Yash, our Intern, MeshMate and a valued member of the community. This dynamic duo will guide you through the realms of open-source, while providing valuable insights about Layer5's projects. Don't let this opportunity pass you by – seize the chance to embark on your open source adventure with us and explore the world of Layer5.
+---
+title: "Kickstarting Open Source with Layer5"
+description: "Gain valuable insights into Layer5's projects as this dynamic duo guides you through the world of open source."
+date: 2023-08-19
+thumbnail: ./kickstarting_your_open_source_with_layer5.webp
+darkthumbnail: ./kickstarting_your_open_source_with_layer5.webp
+eurl: https://lu.ma/z5sjbqws
+type: Event
+published: true
+product: Kanvas, Meshery
+resource: true
+upcoming: false
+speakers: ["Yash Sharma", "Samyak Shah"]
+---
+
+
+
Kickstarting Open Source with Layer5
+
Embark on your Open Source journey with an insightful session led by Layer5's community member Samyak . Joining him is Yash, our Intern, MeshMate and a valued member of the community. This dynamic duo will guide you through the realms of open-source, while providing valuable insights about Layer5's projects. Don't let this opportunity pass you by – seize the chance to embark on your open source adventure with us and explore the world of Layer5.
diff --git a/src/collections/events/2023/kubecon-EU-2023/index.mdx b/src/collections/events/2023/kubecon-EU-2023/index.mdx
index ede0c00c077f..a3929c76e56a 100644
--- a/src/collections/events/2023/kubecon-EU-2023/index.mdx
+++ b/src/collections/events/2023/kubecon-EU-2023/index.mdx
@@ -1,21 +1,21 @@
----
-title: "KubeCon + CloudNativeCon EU Amsterdam 2023"
-description: "CNCF Tag Network and Service mesh Working Group Deep Dive"
-date: 2023-04-18
-thumbnail: ./kubeconEU2023.webp
-darkthumbnail: ./kubeconEU2023.webp
-eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
-type: Event
-published: true
-upcoming: false
-feature: false
-speakers: ["Lee Calcote"]
-
----
-
-Join Layer5 at KubeCon + CloudNativeCon EU Amsterdam 2023!
-
-
CNCF Tag Network and Service mesh Working Group Deep Dive
-
-The Cloud Native Computing Foundation’s flagship conference gathers adopters and technologists from leading open source and cloud native communities in Amsterdam, The Netherlands from 18-21 April, 2023. Join our CNCF Graduated and Incubating Projects as the community gathers for four days to further the education and advancement of cloud native computing.
+---
+title: "KubeCon + CloudNativeCon EU Amsterdam 2023"
+description: "CNCF Tag Network and Service mesh Working Group Deep Dive"
+date: 2023-04-18
+thumbnail: ./kubeconEU2023.webp
+darkthumbnail: ./kubeconEU2023.webp
+eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
+type: Event
+published: true
+upcoming: false
+feature: false
+speakers: ["Lee Calcote"]
+
+---
+
+Join Layer5 at KubeCon + CloudNativeCon EU Amsterdam 2023!
+
+
CNCF Tag Network and Service mesh Working Group Deep Dive
+
+The Cloud Native Computing Foundation’s flagship conference gathers adopters and technologists from leading open source and cloud native communities in Amsterdam, The Netherlands from 18-21 April, 2023. Join our CNCF Graduated and Incubating Projects as the community gathers for four days to further the education and advancement of cloud native computing.
\ No newline at end of file
diff --git a/src/collections/events/2023/kubecon-NA-2023/index.mdx b/src/collections/events/2023/kubecon-NA-2023/index.mdx
index e5292111bd26..0c936aeb4cc3 100644
--- a/src/collections/events/2023/kubecon-NA-2023/index.mdx
+++ b/src/collections/events/2023/kubecon-NA-2023/index.mdx
@@ -1,16 +1,16 @@
----
-title: "KubeCon + CloudNativeCon North America Chicago 2023"
-description: "The Cloud Native Computing Foundation’s flagship conference gathers adopters and technologists from leading open source and cloud native communities."
-date: 2023-11-06
-thumbnail: ./kubeconNA2023.webp
-darkthumbnail: ./kubeconNA2023.webp
-eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
-type: Event
-published: true
-product: Meshery
-resource: true
-upcoming: false
-speakers: ["Lee Calcote"]
----
-Join the Meshery project office hours at KubeCon North America 2023 from 6th to 9th November, 2023 and get introduced to the cloud native management plane and to its open source maintainers.
-
+---
+title: "KubeCon + CloudNativeCon North America Chicago 2023"
+description: "The Cloud Native Computing Foundation’s flagship conference gathers adopters and technologists from leading open source and cloud native communities."
+date: 2023-11-06
+thumbnail: ./kubeconNA2023.webp
+darkthumbnail: ./kubeconNA2023.webp
+eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
+type: Event
+published: true
+product: Meshery
+resource: true
+upcoming: false
+speakers: ["Lee Calcote"]
+---
+Join the Meshery project office hours at KubeCon North America 2023 from 6th to 9th November, 2023 and get introduced to the cloud native management plane and to its open source maintainers.
+
diff --git a/src/collections/events/2023/maitainers-circle-2023/index.mdx b/src/collections/events/2023/maitainers-circle-2023/index.mdx
index 2931cdd86bf6..197f21c25257 100644
--- a/src/collections/events/2023/maitainers-circle-2023/index.mdx
+++ b/src/collections/events/2023/maitainers-circle-2023/index.mdx
@@ -1,15 +1,15 @@
----
-title: "May Maintainer's Circle 2023"
-description: "Join Lee Calcote and Nate Waddington in the upcoming Maintainer’s Circle special session and explore their insights, and experiences from their mentorship journey within the CNCF."
-date: 2023-05-30
-thumbnail: ./Maintainer-Circle.png
-darkthumbnail: ./Maintainer-Circle.png
-eurl: https://calendar.google.com/calendar/u/0/r?cid=linuxfoundation.org_o5avjlvt2cae9bq7a95emc4740@group.calendar.google.com
-type: Event
-published: true
-upcoming: false
-resource: true
-speakers: ["Lee Calcote", "Nate Waddington"]
----
-
+---
+title: "May Maintainer's Circle 2023"
+description: "Join Lee Calcote and Nate Waddington in the upcoming Maintainer’s Circle special session and explore their insights, and experiences from their mentorship journey within the CNCF."
+date: 2023-05-30
+thumbnail: ./Maintainer-Circle.png
+darkthumbnail: ./Maintainer-Circle.png
+eurl: https://calendar.google.com/calendar/u/0/r?cid=linuxfoundation.org_o5avjlvt2cae9bq7a95emc4740@group.calendar.google.com
+type: Event
+published: true
+upcoming: false
+resource: true
+speakers: ["Lee Calcote", "Nate Waddington"]
+---
+
Join Lee Calcote and Nate Waddington in the upcoming Maintainer’s Circle special session and explore their insights, and experiences from their mentorship journey within the CNCF.
\ No newline at end of file
diff --git a/src/collections/events/2024/enlightening/index.mdx b/src/collections/events/2024/enlightening/index.mdx
index 06a4455e8354..3cfac1869710 100644
--- a/src/collections/events/2024/enlightening/index.mdx
+++ b/src/collections/events/2024/enlightening/index.mdx
@@ -1,21 +1,22 @@
----
-title: "Infrastructure as Design by Meshery"
-date: 2024-08-16
-thumbnail: ./banner.jpeg
-eurl: https://www.linkedin.com/feed/update/urn:li:activity:7229161401427062785
-type: Event
-published: true
-upcoming: true
-feature: true
-speakers: ["Lee Calcote", "Whitney Lee"]
-
----
-
-Join host Whitney Lee and guest Lee Calcote to learn more!
-
-
Meshery is a self-service engineering platform that enables the collaborative design and operation of cloud and cloud native infrastructure. With over 320 built-in integrations, Meshery seamlessly integrates with every CNCF project and your existing tools, across multiple clouds and Kubernetes clusters.
-
-
-
-
+---
+title: "Infrastructure as Design by Meshery"
+date: 2024-08-16
+thumbnail: ./banner.jpeg
+eurl: https://www.linkedin.com/feed/update/urn:li:activity:7229161401427062785
+type: Event
+published: true
+upcoming: true
+feature: true
+speakers: ["Lee Calcote", "Whitney Lee"]
+
+---
+
+Join host Whitney Lee and guest Lee Calcote to learn more!
+
+
+ Meshery is a self-service engineering platform that enables the collaborative design and operation of cloud and cloud native infrastructure. With over 320 built-in integrations, Meshery seamlessly integrates with every CNCF project and your existing tools, across multiple clouds and Kubernetes clusters.
+
+
+
+
\ No newline at end of file
diff --git a/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-large.svg b/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-large.svg
index 578a6962683e..b3cc57addae3 100644
--- a/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-large.svg
+++ b/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-large.svg
@@ -1,39 +1,39 @@
-
+
diff --git a/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-small.svg b/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-small.svg
index c6d61b27dd6a..ff9852e12cdb 100644
--- a/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-small.svg
+++ b/src/collections/events/2024/hacktoberfest-2024/layer5-hacktoberfest-badge-small.svg
@@ -1,61 +1,61 @@
-
+
diff --git a/src/collections/events/2024/kubecon-hk/index.mdx b/src/collections/events/2024/kubecon-hk/index.mdx
index 6e905fe745ed..1a82d413911a 100644
--- a/src/collections/events/2024/kubecon-hk/index.mdx
+++ b/src/collections/events/2024/kubecon-hk/index.mdx
@@ -1,32 +1,32 @@
----
-title: "KubeCon + CloudNativeCon Open Source Summit + AI_dev Hong Kong, China"
-description: "Multiplayer Kubernetes: GitOps with Friends"
-date: 2024-08-22
-thumbnail: ./kubeconhk-2024.png
-darkthumbnail: ./kubeconhk-2024.png
-eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/reg/register/
-type: Event
-published: true
-upcoming: false
-feature: true
-speakers: ["Yash Sharma"]
-
----
-import Button from "../../../../reusecore/Button";
-
-
-Join the Meshery project at KubeCon + CloudNativeCon Hong Kong, China from August 21 to August 23, 2024. Engage with the Meshery open-source maintainers and discover collaborative cloud-native management.
-
-
-We’re excited to bring you a session that delves into the intricacies of managing your cloud-native infrastructure efficiently with Meshery. Whether you're an experienced practitioner or new to the cloud-native ecosystem, there’s something for everyone.
-
-### Multiplayer Kubernetes: GitOps with Friends
-
-Discover the transformative capabilities of Cloud Native Playground, powered by Meshery, an open-source, cloud-native manager. Experience the self-service engineering platform, simplifying provisioning, configuration, and management of your cloud-native infrastructure, enabling seamless operation of multi-Kubernetes deployments.
-With Cloud Native Playground, embrace the power of GitOps and collaborative workflows. Free yourself from YAML intricacies as Meshery's extensible platform enables visual and collaborative GitOps, fostering multi-user collaboration. Explore the Cloud Native Computing Foundation's graduated, incubation, and sandbox projects, along with many other popular open source projects, to enhance your capabilities and leverage the full potential of the ecosystem.
-
-**Join Yash Sharma** on Thursday, August 22, 2024 17:15 - 17:50 HKT at [Level 1, Hung Hom Room 5](https://www.shangri-la.com/en/hongkong/kerry/) to witness firsthand how Meshery revolutionizes Kubernetes operations, enabling seamless orchestration across multiple environments through GitOps principles and multi-user collaboration.
-
-We look forward to seeing you there!
-
-**[View the Presentation Slides](https://docs.google.com/presentation/d/1TW6k6NpDUd90xVkqTxakA0MbjzGjm3unIcxyf9DVg-E/edit?usp=sharing)**
+---
+title: "KubeCon + CloudNativeCon Open Source Summit + AI_dev Hong Kong, China"
+description: "Multiplayer Kubernetes: GitOps with Friends"
+date: 2024-08-22
+thumbnail: ./kubeconhk-2024.png
+darkthumbnail: ./kubeconhk-2024.png
+eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/reg/register/
+type: Event
+published: true
+upcoming: false
+feature: true
+speakers: ["Yash Sharma"]
+
+---
+import Button from "../../../../reusecore/Button";
+
+
+Join the Meshery project at KubeCon + CloudNativeCon Hong Kong, China from August 21 to August 23, 2024. Engage with the Meshery open-source maintainers and discover collaborative cloud-native management.
+
+
+We’re excited to bring you a session that delves into the intricacies of managing your cloud-native infrastructure efficiently with Meshery. Whether you're an experienced practitioner or new to the cloud-native ecosystem, there’s something for everyone.
+
+### Multiplayer Kubernetes: GitOps with Friends
+
+Discover the transformative capabilities of Cloud Native Playground, powered by Meshery, an open-source, cloud-native manager. Experience the self-service engineering platform, simplifying provisioning, configuration, and management of your cloud-native infrastructure, enabling seamless operation of multi-Kubernetes deployments.
+With Cloud Native Playground, embrace the power of GitOps and collaborative workflows. Free yourself from YAML intricacies as Meshery's extensible platform enables visual and collaborative GitOps, fostering multi-user collaboration. Explore the Cloud Native Computing Foundation's graduated, incubation, and sandbox projects, along with many other popular open source projects, to enhance your capabilities and leverage the full potential of the ecosystem.
+
+**Join Yash Sharma** on Thursday, August 22, 2024 17:15 - 17:50 HKT at [Level 1, Hung Hom Room 5](https://www.shangri-la.com/en/hongkong/kerry/) to witness firsthand how Meshery revolutionizes Kubernetes operations, enabling seamless orchestration across multiple environments through GitOps principles and multi-user collaboration.
+
+We look forward to seeing you there!
+
+**[View the Presentation Slides](https://docs.google.com/presentation/d/1TW6k6NpDUd90xVkqTxakA0MbjzGjm3unIcxyf9DVg-E/edit?usp=sharing)**
diff --git a/src/collections/events/2024/kubecon-na/index.mdx b/src/collections/events/2024/kubecon-na/index.mdx
index 8aab59c53420..f9b32b86f938 100644
--- a/src/collections/events/2024/kubecon-na/index.mdx
+++ b/src/collections/events/2024/kubecon-na/index.mdx
@@ -4,12 +4,12 @@ description: "CNCF Tag Network and Service mesh Working Group Deep Dive"
date: 2024-11-11
thumbnail: ./kubeconna-2024.png
darkthumbnail: ./kubeconna-2024.png
-
+eurl: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
type: Event
published: true
upcoming: true
feature: true
-speakers: ["Lee Calcote", "Nic Jackson", "Shivay Lamba", "Zack Butcher", "Zhonghu Xu"]
+speakers: ["Lee Calcote", "Nic Jackson", "Zack Butcher", "Zhonghu Xu"]
---
import Button from "../../../../reusecore/Button";
@@ -20,60 +20,5 @@ Join Layer5 at KubeCon + CloudNativeCon NA, Salt Lake City, Utah!
Join the Meshery project at KubeCon NA 2024 from November 11th to November 16th, 2024 and get introduced to collaborative cloud native management and Meshery open source maintainers.
-Meshery and its extensions empower you to navigate cloud native infrastructure in complex environments. This lighting talk delves into the human-computer interaction (HCI) principles that underpin MeshMap's intuitive visualization of Kubernetes resources and the various forms of inter/relationships with other CNCF projects' resources.
-
-Human-Computer Interaction Principles in Meshery:
-
-
-
Cognitive Load: How Meshery reduces cognitive load by presenting complex information in a structured and visually digestible manner.
-
Mental Models: How Meshery aligns with users' mental models of Kubernetes environments, facilitating comprehension and navigation.
-
Visual Perception: How Meshery leverages visual cues, colors, and layout to guide users' attention and highlight critical information.
-
-### Session: CNCF TAG Network - Intro & Deep Dive
-
-
-“It’s the network!” is the cry of every engineer. With the increased prevalence of microservices and distributed systems, it’s true - networking as a discipline has never been more critical in the well-architected design and efficient operation of modern infrastructure. Join this talk for an intro to the TAG, its charter and a deeper discussion of current cloud native networking topics being advanced in this TAG.
-
-Join the Meshery maintainers and community in improving the leading cloud native management plane. This is your chance to get hands-on with the tools shaping the future of collaborative cloud native management. Opportunities: Work on core functionality in the Server (Golang) or UI (React) or extend Meshery by building your own plugin. Contribute to the Meshery documentation by incorporating your own examples of cloud native solution architectures using Meshery Designer.
-
-
-Why Contribute to Meshery? - Gain experience with cloud native technologies, including essentially every CNCF project and open source development practices. As is the 10th fastest growing CNCF project, Meshery has a vibrant community. Work alongside passionate maintainers and contributors. No Prior Experience Needed: We welcome contributions from all levels of experience. Join us at Meshery Contribfest and be part of the growing community shaping the future of collaborative cloud native management.
-
-
-
+{/*
+ */}
diff --git a/src/collections/events/2024/making-the-cncf-landscape-interactive-with-meshery/index.mdx b/src/collections/events/2024/making-the-cncf-landscape-interactive-with-meshery/index.mdx
index 896dbc69cb50..346ddc6f1a6a 100644
--- a/src/collections/events/2024/making-the-cncf-landscape-interactive-with-meshery/index.mdx
+++ b/src/collections/events/2024/making-the-cncf-landscape-interactive-with-meshery/index.mdx
@@ -27,7 +27,7 @@ Whether you’re a developer, an operator, or simply a cloud-native enthusiast,
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!
-
+
Date: May 1st, 2024
Time: 11:00 AM CT / 09:30 PM IST
diff --git a/src/collections/events/2024/you-choose/index.mdx b/src/collections/events/2024/you-choose/index.mdx
index 9c96179747ac..6094a9a0ac0b 100644
--- a/src/collections/events/2024/you-choose/index.mdx
+++ b/src/collections/events/2024/you-choose/index.mdx
@@ -1,18 +1,19 @@
----
-title: "You Choose"
-date: 2024-09-03
-thumbnail: ./you-choose.jpeg
-eurl: https://www.youtube.com/watch?v=GhfRu3l4F8U
-type: Event
-published: true
-upcoming: true
-feature: true
-speakers: ["Whitney Lee", "Viktor Farcic"]
-
----
-
-Join hosts Whitney Lee and Viktor Farcic, along with guests Lee Calcote, Marc Boorshtein and René D to learn more!
-
-
Explore and learn about three CNCF projects that offer intuitive dashboards: Meshery, Headlamp and Kubernetes Dashboard. Cast your VOTE to decide which one you'd like to see implemented in the demo!
-
-
+---
+title: "You Choose"
+date: 2024-09-03
+thumbnail: ./you-choose.jpeg
+eurl: https://www.youtube.com/watch?v=GhfRu3l4F8U
+type: Event
+published: true
+upcoming: true
+feature: true
+speakers: ["Whitney Lee", "Viktor Farcic"]
+
+---
+
+Join hosts Whitney Lee and Viktor Farcic, along with guests Lee Calcote, Marc Boorshtein and René D to learn more!
+
+
+ Explore and learn about three CNCF projects that offer intuitive dashboards: Meshery, Headlamp and Kubernetes Dashboard. Cast your VOTE to decide which one you'd like to see implemented in the demo!
+
+
diff --git a/src/collections/events/Event.style.js b/src/collections/events/Event.style.js
index 545d085896de..739cc53a2ca5 100644
--- a/src/collections/events/Event.style.js
+++ b/src/collections/events/Event.style.js
@@ -1,5 +1,5 @@
import styled from "styled-components";
-export const EventWrapper = styled.div`
+const EventWrapper = styled.div`
color: ${(props) => props.theme.text};
.sub-heading {
color: gray;
@@ -363,3 +363,6 @@ code {
}
`;
+
+
+export default EventWrapper;
\ No newline at end of file
diff --git a/src/collections/events/Z_event-template/index.mdx b/src/collections/events/Z_event-template/index.mdx
index dbb503102cd0..863c9506ac9c 100644
--- a/src/collections/events/Z_event-template/index.mdx
+++ b/src/collections/events/Z_event-template/index.mdx
@@ -1,18 +1,18 @@
----
-title: "Event Title"
-description: "Event Description"
-date: 2023-05-17
-thumbnail: ./servicemeshcon22.webp
-darkthumbnail: ./servicemeshcon22.webp
-eurl: # external link to event
-type: Event
-published: false
-upcoming: false
-register: true
-speakers: ["First Last","First Last"]
----
-
-import { Link } from "gatsby";
-
-
+---
+title: "Event Title"
+description: "Event Description"
+date: 2023-05-17
+thumbnail: ./servicemeshcon22.webp
+darkthumbnail: ./servicemeshcon22.webp
+eurl: # external link to event
+type: Event
+published: false
+upcoming: false
+register: true
+speakers: ["First Last","First Last"]
+---
+
+
+
+
Join Layer5 at...
\ No newline at end of file
diff --git a/src/collections/integrations/_images/kanvas-designer.webp b/src/collections/integrations/_images/kanvas-designer.webp
index 8b02ec96053a..0c0ab2648dd8 100644
Binary files a/src/collections/integrations/_images/kanvas-designer.webp and b/src/collections/integrations/_images/kanvas-designer.webp differ
diff --git a/src/collections/integrations/_images/kanvas-regain-control.webp b/src/collections/integrations/_images/kanvas-regain-control.webp
index 89de0891c8ce..f692534e9919 100644
Binary files a/src/collections/integrations/_images/kanvas-regain-control.webp and b/src/collections/integrations/_images/kanvas-regain-control.webp differ
diff --git a/src/collections/integrations/_images/kanvas-visualizer.webp b/src/collections/integrations/_images/kanvas-visualizer.webp
index 445c475cd76a..b697cf789419 100644
Binary files a/src/collections/integrations/_images/kanvas-visualizer.webp and b/src/collections/integrations/_images/kanvas-visualizer.webp differ
diff --git a/src/collections/integrations/aad-pod-identity/index.mdx b/src/collections/integrations/aad-pod-identity/index.mdx
index 482c8ed5d1bc..04a613d544ff 100644
--- a/src/collections/integrations/aad-pod-identity/index.mdx
+++ b/src/collections/integrations/aad-pod-identity/index.mdx
@@ -1,57 +1,53 @@
----
-title: Azure Active Directory (AAD)
-subtitle: Collaborative and visual infrastructure as design for Azure Active Directory (AAD)
-integrationIcon: icons/color/aad-pod-identity-color.svg
-darkModeIntegrationIcon: icons/white/aad-pod-identity-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aad-pod-identity
-description:
-category: Provisioning
-subcategory: Security & Compliance
-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.",
- "Pod-managed identities are available on Linux node pools only."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Federate with any external identity provider"
-howItWorksDetails: "Azure AD workload identity authentication method replaces pod-managed identity, which integrates with the Kubernetes native capabilities to federate with any external identity providers on behalf of the application."
-published: TRUE
----
-
-Enables Kubernetes applications to access cloud resources securely with Azure Active Directory (AAD).
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Azure Active Directory (AAD)
+subtitle: Collaborative and visual infrastructure as design for Azure Active Directory (AAD)
+integrationIcon: icons/color/aad-pod-identity-color.svg
+darkModeIntegrationIcon: icons/white/aad-pod-identity-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aad-pod-identity
+description:
+category: Provisioning
+subcategory: Security & Compliance
+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.",
+ "Pod-managed identities are available on Linux node pools only."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Federate with any external identity provider"
+howItWorksDetails: "Azure AD workload identity authentication method replaces pod-managed identity, which integrates with the Kubernetes native capabilities to federate with any external identity providers on behalf of the application."
+published: TRUE
+---
+
+Enables Kubernetes applications to access cloud resources securely with Azure Active Directory (AAD).
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/accurate/index.mdx b/src/collections/integrations/accurate/index.mdx
index cb40bbdd19d4..147b73a63b40 100644
--- a/src/collections/integrations/accurate/index.mdx
+++ b/src/collections/integrations/accurate/index.mdx
@@ -1,39 +1,37 @@
----
-title: Accurate
-subtitle: Collaborative and visual infrastructure as design for Accurate
-integrationIcon: icons/color/accurate-color.svg
-darkModeIntegrationIcon: icons/white/accurate-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/accurate
-description:
-category: Provisioning
-subcategory: Security & Compliance
-registrant: GitHub
-components: [
-{
-"name": "sub-namespace",
-"colorIcon": "icons/components/sub-namespace/icons/color/sub-namespace-color.svg",
-"whiteIcon": "icons/components/sub-namespace/icons/white/sub-namespace-white.svg",
-"description": "",
-}]
-featureList: [
- "Resource propagation between namespaces.",
- "Inheriting labels and annotations creation/update from parent namespaces.",
- "SubNamespace custom resource for tenant users."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Accurate is a Kubernetes controller to help operations in large soft multi-tenancy environments.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Accurate
+subtitle: Collaborative and visual infrastructure as design for Accurate
+integrationIcon: icons/color/accurate-color.svg
+darkModeIntegrationIcon: icons/white/accurate-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/accurate
+description:
+category: Provisioning
+subcategory: Security & Compliance
+registrant: GitHub
+components:
+ - name: sub-namespace
+ colorIcon: icons/components/sub-namespace/icons/color/sub-namespace-color.svg
+ whiteIcon: icons/components/sub-namespace/icons/white/sub-namespace-white.svg
+ description: ""
+featureList: [
+ "Resource propagation between namespaces.",
+ "Inheriting labels and annotations creation/update from parent namespaces.",
+ "SubNamespace custom resource for tenant users."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Accurate is a Kubernetes controller to help operations in large soft multi-tenancy environments.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/actions-runner-controller/index.mdx b/src/collections/integrations/actions-runner-controller/index.mdx
index a3b8a9b1611e..1925dde86cac 100644
--- a/src/collections/integrations/actions-runner-controller/index.mdx
+++ b/src/collections/integrations/actions-runner-controller/index.mdx
@@ -1,63 +1,58 @@
----
-title: Actions Runner Controller (ARC)
-subtitle: Collaborative and visual infrastructure as design for Actions Runner Controller (ARC)
-integrationIcon: icons/color/actions-runner-controller-color.svg
-darkModeIntegrationIcon: icons/white/actions-runner-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/actions-runner-controller
-description:
-category: App Definition and Development
-subcategory: Continuous Integration & Delivery
-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.",
- "Setup across GitHub editions including GitHub Enterprise editions and GitHub Enterprise Cloud."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Actions Runner Controller (ARC)
+subtitle: Collaborative and visual infrastructure as design for Actions Runner Controller (ARC)
+integrationIcon: icons/color/actions-runner-controller-color.svg
+darkModeIntegrationIcon: icons/white/actions-runner-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/actions-runner-controller
+description:
+category: App Definition and Development
+subcategory: Continuous Integration & Delivery
+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.",
+ "Setup across GitHub editions including GitHub Enterprise editions and GitHub Enterprise Cloud."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/admin-console-operator/index.mdx b/src/collections/integrations/admin-console-operator/index.mdx
index 644f1f104f28..32c893a199fb 100644
--- a/src/collections/integrations/admin-console-operator/index.mdx
+++ b/src/collections/integrations/admin-console-operator/index.mdx
@@ -1,39 +1,38 @@
----
-title: EPAM Delivery Platform
-subtitle: Collaborative and visual infrastructure as design for EPAM Delivery Platform
-integrationIcon: icons/color/admin-console-operator-color.svg
-darkModeIntegrationIcon: icons/white/admin-console-operator-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/admin-console-operator
-description:
-category: Provisioning
-subcategory: Automation & Configuration
-registrant: Artifact Hub
-components: [
-{
-"name": "admin-console",
-"colorIcon": "icons/components/admin-console/icons/color/admin-console-color.svg",
-"whiteIcon": "icons/components/admin-console/icons/white/admin-console-white.svg",
-"description": "",
-}]
-featureList: [
- "Deployed and configured CI/CD toolset (Jenkins, Gerrit, Nexus, SonarQube)",
- "Kubernetes native approach (CRD, CR) to declare CI/CD pipelines",
- "Gerrit, GitLab or GitHub as a version control system for your code"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-EPAM Admin Console Operator
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: EPAM Delivery Platform
+subtitle: Collaborative and visual infrastructure as design for EPAM Delivery Platform
+integrationIcon: icons/color/admin-console-operator-color.svg
+darkModeIntegrationIcon: icons/white/admin-console-operator-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/admin-console-operator
+description:
+category: Provisioning
+subcategory: Automation & Configuration
+registrant: Artifact Hub
+components:
+ - name: admin-console
+ colorIcon: icons/components/admin-console/icons/color/admin-console-color.svg
+ whiteIcon: icons/components/admin-console/icons/white/admin-console-white.svg
+ description: ""
+
+featureList: [
+ "Deployed and configured CI/CD toolset (Jenkins, Gerrit, Nexus, SonarQube)",
+ "Kubernetes native approach (CRD, CR) to declare CI/CD pipelines",
+ "Gerrit, GitLab or GitHub as a version control system for your code"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+EPAM Admin Console Operator
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/akri/index.mdx b/src/collections/integrations/akri/index.mdx
index 7cac7994dfe2..df84d4f4f2ee 100644
--- a/src/collections/integrations/akri/index.mdx
+++ b/src/collections/integrations/akri/index.mdx
@@ -1,45 +1,43 @@
----
-title: Akri
-subtitle: Collaborative and visual infrastructure as design for Akri
-integrationIcon: icons/color/akri-color.svg
-darkModeIntegrationIcon: icons/white/akri-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/akri
-description:
-category: Provisioning
-subcategory: Automation & Configuration
-registrant: Artifact Hub
-components: [
-{
-"name": "configuration",
-"colorIcon": "icons/components/configuration/icons/color/configuration-color.svg",
-"whiteIcon": "icons/components/configuration/icons/white/configuration-white.svg",
-"description": "",
-},
-{
-"name": "instance",
-"colorIcon": "icons/components/instance/icons/color/instance-color.svg",
-"whiteIcon": "icons/components/instance/icons/white/instance-white.svg",
-"description": "",
-}]
-featureList: [
- "Expose heterogeneous leaf devices as resources in a Kubernetes cluster",
- "It is made for the edge and handles the dynamic appearance and disappearance of leaf devices.",
- "It provides an abstraction layer similar to CNI."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-A Kubernetes Resource Interface for the Edge
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Akri
+subtitle: Collaborative and visual infrastructure as design for Akri
+integrationIcon: icons/color/akri-color.svg
+darkModeIntegrationIcon: icons/white/akri-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/akri
+description:
+category: Provisioning
+subcategory: Automation & Configuration
+registrant: Artifact Hub
+components:
+ - name: configuration
+ colorIcon: icons/components/configuration/icons/color/configuration-color.svg
+ whiteIcon: icons/components/configuration/icons/white/configuration-white.svg
+ description: ""
+
+ - name: instance
+ colorIcon: icons/components/instance/icons/color/instance-color.svg
+ whiteIcon: icons/components/instance/icons/white/instance-white.svg
+ description: ""
+
+featureList: [
+ "Expose heterogeneous leaf devices as resources in a Kubernetes cluster",
+ "It is made for the edge and handles the dynamic appearance and disappearance of leaf devices.",
+ "It provides an abstraction layer similar to CNI."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+A Kubernetes Resource Interface for the Edge
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aks-appgw-fe/index.mdx b/src/collections/integrations/aks-appgw-fe/index.mdx
index ec8f594cbb98..0ff42d1d25b4 100644
--- a/src/collections/integrations/aks-appgw-fe/index.mdx
+++ b/src/collections/integrations/aks-appgw-fe/index.mdx
@@ -1,59 +1,55 @@
----
-title: Azure Application Gateway
-subtitle: Collaborative and visual infrastructure as design for Azure Application Gateway
-integrationIcon: icons/color/aks-appgw-fe-color.svg
-darkModeIntegrationIcon: icons/white/aks-appgw-fe-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aks-appgw-fe
-description:
-category: Cloud Native Network
-subcategory: Service Proxy
-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: [
- "URL routing and cookie-based affinity
-",
- "Support for public, private, and hybrid web sites and
-integrated web application firewall",
- "Secure Sockets Layer (SSL) termination and End-to-end SSL"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Application Gateway Ingress Controller runs in its own pod on the customer’s AKS. Ingress Controller monitors a subset of Kubernetes’ resources for changes. The state of the AKS cluster is translated to Application Gateway specific configuration and applied to the Azure Resource Manager. The continuous re-configuration of Application Gateway ensures uninterrupted flow of traffic to AKS’ services. The diagram below illustrates the flow of state and configuration changes from the Kubernetes API, via Application Gateway Ingress Controller, to Resource Manager and then Application Gateway."
-published: TRUE
----
-
-Create generic frontend web application in AKS with SSL termination on an Application Gateway
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Azure Application Gateway
+subtitle: Collaborative and visual infrastructure as design for Azure Application Gateway
+integrationIcon: icons/color/aks-appgw-fe-color.svg
+darkModeIntegrationIcon: icons/white/aks-appgw-fe-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aks-appgw-fe
+description:
+category: Cloud Native Network
+subcategory: Service Proxy
+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: [
+ "URL routing and cookie-based affinity
+",
+ "Support for public, private, and hybrid web sites and
+integrated web application firewall",
+ "Secure Sockets Layer (SSL) termination and End-to-end SSL"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Application Gateway Ingress Controller runs in its own pod on the customer’s AKS. Ingress Controller monitors a subset of Kubernetes’ resources for changes. The state of the AKS cluster is translated to Application Gateway specific configuration and applied to the Azure Resource Manager. The continuous re-configuration of Application Gateway ensures uninterrupted flow of traffic to AKS’ services. The diagram below illustrates the flow of state and configuration changes from the Kubernetes API, via Application Gateway Ingress Controller, to Resource Manager and then Application Gateway."
+published: TRUE
+---
+
+Create generic frontend web application in AKS with SSL termination on an Application Gateway
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Altinity ClickHouse is a managed ClickHouse service for Kubernetes.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Altinity ClickHouse is a managed ClickHouse service for Kubernetes.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-The Ambassador Edge Stack and its open source version Emissary-Ingress (FKA Ambassador API Gateway) offer a self-service, comprehensive API Gateway that is Kubernetes-native and built on Envoy.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+The Ambassador Edge Stack and its open source version Emissary-Ingress (FKA Ambassador API Gateway) offer a self-service, comprehensive API Gateway that is Kubernetes-native and built on Envoy.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
Antrea is a Kubernetes-native project that implements the Container Network Interface (CNI) and Kubernetes NetworkPolicy thereby providing network connectivity and security for pod workloads. Antrea extends the benefit of programmable networks from Open vSwitch (OVS) to Kubernetes.
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+ Antrea is a Kubernetes-native project that implements the Container Network Interface (CNI) and Kubernetes NetworkPolicy thereby providing network connectivity and security for pod workloads. Antrea extends the benefit of programmable networks from Open vSwitch (OVS) to Kubernetes.
+
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
diff --git a/src/collections/integrations/apache-shardingsphere-operator-charts/icons/components/compute-node/icons/white/compute-node-white.svg b/src/collections/integrations/apache-shardingsphere-operator-charts/icons/components/compute-node/icons/white/compute-node-white.svg
index a85c8eebbc97..92bafddf5410 100644
--- a/src/collections/integrations/apache-shardingsphere-operator-charts/icons/components/compute-node/icons/white/compute-node-white.svg
+++ b/src/collections/integrations/apache-shardingsphere-operator-charts/icons/components/compute-node/icons/white/compute-node-white.svg
@@ -1,34 +1,34 @@
-
+
diff --git a/src/collections/integrations/apache-shardingsphere-operator-charts/index.mdx b/src/collections/integrations/apache-shardingsphere-operator-charts/index.mdx
index 53116866e745..84c6d0a1524c 100644
--- a/src/collections/integrations/apache-shardingsphere-operator-charts/index.mdx
+++ b/src/collections/integrations/apache-shardingsphere-operator-charts/index.mdx
@@ -1,70 +1,64 @@
----
-title: Apache ShardingSphere
-subtitle: Collaborative and visual infrastructure as design for Apache ShardingSphere
-integrationIcon: icons/color/apache-shardingsphere-operator-charts-color.svg
-darkModeIntegrationIcon: icons/white/apache-shardingsphere-operator-charts-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/apache-shardingsphere-operator-charts
-description:
-category: App Definition and Development
-subcategory: Database
-registrant: Artifact Hub
-components: [
-{
-"name": "compute-node",
-"colorIcon": "icons/components/compute-node/icons/color/compute-node-color.svg",
-"whiteIcon": "icons/components/compute-node/icons/white/compute-node-white.svg",
-"description": "",
-},
-{
-"name": "sharding-sphere-proxy",
-"colorIcon": "icons/components/sharding-sphere-proxy/icons/color/sharding-sphere-proxy-color.svg",
-"whiteIcon": "icons/components/sharding-sphere-proxy/icons/white/sharding-sphere-proxy-white.svg",
-"description": "",
-},
-{
-"name": "sharding-sphere-proxy-server-config",
-"colorIcon": "icons/components/sharding-sphere-proxy-server-config/icons/color/sharding-sphere-proxy-server-config-color.svg",
-"whiteIcon": "icons/components/sharding-sphere-proxy-server-config/icons/white/sharding-sphere-proxy-server-config-white.svg",
-"description": "",
-},
-{
-"name": "chaos",
-"colorIcon": "icons/components/chaos/icons/color/chaos-color.svg",
-"whiteIcon": "icons/components/chaos/icons/white/chaos-white.svg",
-"description": "",
-},
-{
-"name": "storage-node",
-"colorIcon": "icons/components/storage-node/icons/color/storage-node-color.svg",
-"whiteIcon": "icons/components/storage-node/icons/white/storage-node-white.svg",
-"description": "",
-},
-{
-"name": "storage-provider",
-"colorIcon": "icons/components/storage-provider/icons/color/storage-provider-color.svg",
-"whiteIcon": "icons/components/storage-provider/icons/white/storage-provider-white.svg",
-"description": "",
-}]
-featureList: [
- "ShardingSphere provides a distributed database solution based on the underlying database, which can scale computing and storage horizontally.",
- "With a hybrid engine based on XA and BASE transactions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources.",
- "ShardingSphere provides flexible read/write splitting capabilities and can achieve read access load balancing based on the understanding of SQL semantics and the ability to perceive the underlying database topology."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-The ShardingSphere Kubernetes Operator automates provisioning, management, and operations of ShardingSphere Proxy clusters running on Kubernetes.
-
-
Apache ShardingSphere is an ecosystem to transform any database into a distributed database system, and enhance it with sharding, elastic scaling, encryption features & more.
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Apache ShardingSphere
+subtitle: Collaborative and visual infrastructure as design for Apache ShardingSphere
+integrationIcon: icons/color/apache-shardingsphere-operator-charts-color.svg
+darkModeIntegrationIcon: icons/white/apache-shardingsphere-operator-charts-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/apache-shardingsphere-operator-charts
+description:
+category: App Definition and Development
+subcategory: Database
+registrant: Artifact Hub
+components:
+ - name: compute-node
+ colorIcon: icons/components/compute-node/icons/color/compute-node-color.svg
+ whiteIcon: icons/components/compute-node/icons/white/compute-node-white.svg
+ description: ""
+
+ - name: sharding-sphere-proxy
+ colorIcon: icons/components/sharding-sphere-proxy/icons/color/sharding-sphere-proxy-color.svg
+ whiteIcon: icons/components/sharding-sphere-proxy/icons/white/sharding-sphere-proxy-white.svg
+ description: ""
+
+ - name: sharding-sphere-proxy-server-config
+ colorIcon: icons/components/sharding-sphere-proxy-server-config/icons/color/sharding-sphere-proxy-server-config-color.svg
+ whiteIcon: icons/components/sharding-sphere-proxy-server-config/icons/white/sharding-sphere-proxy-server-config-white.svg
+ description: ""
+
+ - name: chaos
+ colorIcon: icons/components/chaos/icons/color/chaos-color.svg
+ whiteIcon: icons/components/chaos/icons/white/chaos-white.svg
+ description: ""
+
+ - name: storage-node
+ colorIcon: icons/components/storage-node/icons/color/storage-node-color.svg
+ whiteIcon: icons/components/storage-node/icons/white/storage-node-white.svg
+ description: ""
+
+ - name: storage-provider
+ colorIcon: icons/components/storage-provider/icons/color/storage-provider-color.svg
+ whiteIcon: icons/components/storage-provider/icons/white/storage-provider-white.svg
+ description: ""
+
+featureList: [
+ "ShardingSphere provides a distributed database solution based on the underlying database, which can scale computing and storage horizontally.",
+ "With a hybrid engine based on XA and BASE transactions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources.",
+ "ShardingSphere provides flexible read/write splitting capabilities and can achieve read access load balancing based on the understanding of SQL semantics and the ability to perceive the underlying database topology."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+The ShardingSphere Kubernetes Operator automates provisioning, management, and operations of ShardingSphere Proxy clusters running on Kubernetes.
+
+
Apache ShardingSphere is an ecosystem to transform any database into a distributed database system, and enhance it with sharding, elastic scaling, encryption features & more.
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aperture-agent/index.mdx b/src/collections/integrations/aperture-agent/index.mdx
index 61962d1061cd..646536c8653e 100644
--- a/src/collections/integrations/aperture-agent/index.mdx
+++ b/src/collections/integrations/aperture-agent/index.mdx
@@ -1,40 +1,39 @@
----
-title: Aperture Agent
-subtitle: Collaborative and visual infrastructure as design for Aperture Agent
-integrationIcon: icons/color/aperture-agent-color.svg
-darkModeIntegrationIcon: icons/white/aperture-agent-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aperture-agent
-description:
-category: Orchestration & Management
-subcategory: Scheduling & Orchestration
-registrant: Artifact Hub
-components: [
-{
-"name": "agent",
-"colorIcon": "icons/components/agent/icons/color/agent-color.svg",
-"whiteIcon": "icons/components/agent/icons/white/agent-white.svg",
-"description": "",
-}]
-featureList: [
- "Collects and analyzes telemetry data",
- "Provides traffic control and shaping",
- "Integrates with various observability tools"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Integrates Aperture Agent"
-howItWorksDetails: "Enhanced observability and security for Kubernetes applications"
-published: TRUE
----
-
-The Aperture Agent is the decision executor of the Aperture system. In addition to gathering data, the Aperture Agent functions as a gatekeeper, acting on traffic based on decisions made by the Aperture Controller. Specifically, depending on feedback from the Controller, the Agent will effectively allow or drop incoming requests. Further supporting the Controller, the Agent works to inject information into traffic, including the specific traffic-shaping decisions made and classification labels which can later be used in policing. One Agent is deployed per node.
-
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Aperture Agent
+subtitle: Collaborative and visual infrastructure as design for Aperture Agent
+integrationIcon: icons/color/aperture-agent-color.svg
+darkModeIntegrationIcon: icons/white/aperture-agent-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aperture-agent
+description:
+category: Orchestration & Management
+subcategory: Scheduling & Orchestration
+registrant: Artifact Hub
+components:
+ - name: agent
+ colorIcon: icons/components/agent/icons/color/agent-color.svg
+ whiteIcon: icons/components/agent/icons/white/agent-white.svg
+ description: ""
+
+featureList: [
+ "Collects and analyzes telemetry data",
+ "Provides traffic control and shaping",
+ "Integrates with various observability tools"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Integrates Aperture Agent"
+howItWorksDetails: "Enhanced observability and security for Kubernetes applications"
+published: TRUE
+---
+
+The Aperture Agent is the decision executor of the Aperture system. In addition to gathering data, the Aperture Agent functions as a gatekeeper, acting on traffic based on decisions made by the Aperture Controller. Specifically, depending on feedback from the Controller, the Agent will effectively allow or drop incoming requests. Further supporting the Controller, the Agent works to inject information into traffic, including the specific traffic-shaping decisions made and classification labels which can later be used in policing. One Agent is deployed per node.
+
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aperture-controller/index.mdx b/src/collections/integrations/aperture-controller/index.mdx
index 0c94b551bd71..414bfbf9682c 100644
--- a/src/collections/integrations/aperture-controller/index.mdx
+++ b/src/collections/integrations/aperture-controller/index.mdx
@@ -1,45 +1,42 @@
----
-title: Aperture Controller
-subtitle: Collaborative and visual infrastructure as design for Aperture Controller
-integrationIcon: icons/color/aperture-controller-color.svg
-darkModeIntegrationIcon: icons/white/aperture-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aperture-controller
-description:
-category: Orchestration & Management
-subcategory: Scheduling & Orchestration
-registrant: Artifact Hub
-components: [
-{
-"name": "controller",
-"colorIcon": "icons/components/controller/icons/color/controller-color.svg",
-"whiteIcon": "icons/components/controller/icons/white/controller-white.svg",
-"description": "",
-},
-{
-"name": "policy",
-"colorIcon": "icons/components/policy/icons/color/policy-color.svg",
-"whiteIcon": "icons/components/policy/icons/white/policy-white.svg",
-"description": "",
-}]
-featureList: [
- "Monitor golden signals to rapidly detect service deterioration and load build-up.",
- "Adjusts the concurrency limit of the service.",
- "Regulate and prioritize flows based on rules via a scheduler."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-The Aperture Controller functions as the brain of the Aperture system. Leveraging an advanced control loop, the Controller routinely analyzes polled metrics and indicators to determine how traffic should be shaped as defined by set policies. Once determined, these decisions are then exported to all Aperture Agents to effectively handle workloads.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Aperture Controller
+subtitle: Collaborative and visual infrastructure as design for Aperture Controller
+integrationIcon: icons/color/aperture-controller-color.svg
+darkModeIntegrationIcon: icons/white/aperture-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aperture-controller
+description:
+category: Orchestration & Management
+subcategory: Scheduling & Orchestration
+registrant: Artifact Hub
+components:
+ - name: controller
+ colorIcon: icons/components/controller/icons/color/controller-color.svg
+ whiteIcon: icons/components/controller/icons/white/controller-white.svg
+ description: ""
+ - name: policy
+ colorIcon: icons/components/policy/icons/color/policy-color.svg
+ whiteIcon: icons/components/policy/icons/white/policy-white.svg
+ description: ""
+
+featureList: [
+ "Monitor golden signals to rapidly detect service deterioration and load build-up.",
+ "Adjusts the concurrency limit of the service.",
+ "Regulate and prioritize flows based on rules via a scheduler."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+The Aperture Controller functions as the brain of the Aperture system. Leveraging an advanced control loop, the Controller routinely analyzes polled metrics and indicators to determine how traffic should be shaped as defined by set policies. Once determined, these decisions are then exported to all Aperture Agents to effectively handle workloads.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/apisix-ingress-controller/index.mdx b/src/collections/integrations/apisix-ingress-controller/index.mdx
index c991f2ac15c9..b6cd84f7b8b4 100644
--- a/src/collections/integrations/apisix-ingress-controller/index.mdx
+++ b/src/collections/integrations/apisix-ingress-controller/index.mdx
@@ -1,75 +1,62 @@
----
-title: APISIX Ingress Controller
-subtitle: Collaborative and visual infrastructure as design for APISIX Ingress Controller
-integrationIcon: icons/color/apisix-ingress-controller-color.svg
-darkModeIntegrationIcon: icons/white/apisix-ingress-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/apisix-ingress-controller
-description:
-category: Cloud Native Network
-subcategory: API Gateway
-registrant: Artifact Hub
-components: [
-{
-"name": "apisix-cluster-config",
-"colorIcon": "icons/components/apisix-cluster-config/icons/color/apisix-cluster-config-color.svg",
-"whiteIcon": "icons/components/apisix-cluster-config/icons/white/apisix-cluster-config-white.svg",
-"description": "",
-},
-{
-"name": "apisix-consumer",
-"colorIcon": "icons/components/apisix-consumer/icons/color/apisix-consumer-color.svg",
-"whiteIcon": "icons/components/apisix-consumer/icons/white/apisix-consumer-white.svg",
-"description": "",
-},
-{
-"name": "apisix-route",
-"colorIcon": "icons/components/apisix-route/icons/color/apisix-route-color.svg",
-"whiteIcon": "icons/components/apisix-route/icons/white/apisix-route-white.svg",
-"description": "",
-},
-{
-"name": "apisix-tls",
-"colorIcon": "icons/components/apisix-tls/icons/color/apisix-tls-color.svg",
-"whiteIcon": "icons/components/apisix-tls/icons/white/apisix-tls-white.svg",
-"description": "",
-},
-{
-"name": "apisix-upstream",
-"colorIcon": "icons/components/apisix-upstream/icons/color/apisix-upstream-color.svg",
-"whiteIcon": "icons/components/apisix-upstream/icons/white/apisix-upstream-white.svg",
-"description": "",
-},
-{
-"name": "apisix-plugin-config",
-"colorIcon": "icons/components/apisix-plugin-config/icons/color/apisix-plugin-config-color.svg",
-"whiteIcon": "icons/components/apisix-plugin-config/icons/white/apisix-plugin-config-white.svg",
-"description": "",
-},
-{
-"name": "apisix-global-rule",
-"colorIcon": "icons/components/apisix-global-rule/icons/color/apisix-global-rule-color.svg",
-"whiteIcon": "icons/components/apisix-global-rule/icons/white/apisix-global-rule-white.svg",
-"description": "",
-}]
-featureList: [
- "The Apache APISIX Dashboard is designed to make it as easy as possible for users to operate through a frontend interface.",
- "The Apache APISIX dashboard is flexible to User demands.",
- "Built-in and customizable plugins available."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-The Cloud-Native API Gateway
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: APISIX Ingress Controller
+subtitle: Collaborative and visual infrastructure as design for APISIX Ingress Controller
+integrationIcon: icons/color/apisix-ingress-controller-color.svg
+darkModeIntegrationIcon: icons/white/apisix-ingress-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/apisix-ingress-controller
+description:
+category: Cloud Native Network
+subcategory: API Gateway
+registrant: Artifact Hub
+components:
+ - name: apisix-cluster-config
+ colorIcon: icons/components/apisix-cluster-config/icons/color/apisix-cluster-config-color.svg
+ whiteIcon: icons/components/apisix-cluster-config/icons/white/apisix-cluster-config-white.svg
+ description: ""
+ - name: apisix-consumer
+ colorIcon: icons/components/apisix-consumer/icons/color/apisix-consumer-color.svg
+ whiteIcon: icons/components/apisix-consumer/icons/white/apisix-consumer-white.svg
+ description: ""
+ - name: apisix-route
+ colorIcon: icons/components/apisix-route/icons/color/apisix-route-color.svg
+ whiteIcon: icons/components/apisix-route/icons/white/apisix-route-white.svg
+ description: ""
+ - name: apisix-tls
+ colorIcon: icons/components/apisix-tls/icons/color/apisix-tls-color.svg
+ whiteIcon: icons/components/apisix-tls/icons/white/apisix-tls-white.svg
+ description: ""
+ - name: apisix-upstream
+ colorIcon: icons/components/apisix-upstream/icons/color/apisix-upstream-color.svg
+ whiteIcon: icons/components/apisix-upstream/icons/white/apisix-upstream-white.svg
+ description: ""
+ - name: apisix-plugin-config
+ colorIcon: icons/components/apisix-plugin-config/icons/color/apisix-plugin-config-color.svg
+ whiteIcon: icons/components/apisix-plugin-config/icons/white/apisix-plugin-config-white.svg
+ description: ""
+ - name: apisix-global-rule
+ colorIcon: icons/components/apisix-global-rule/icons/color/apisix-global-rule-color.svg
+ whiteIcon: icons/components/apisix-global-rule/icons/white/apisix-global-rule-white.svg
+ description: ""
+
+featureList: [
+ "The Apache APISIX Dashboard is designed to make it as easy as possible for users to operate through a frontend interface.",
+ "The Apache APISIX dashboard is flexible to User demands.",
+ "Built-in and customizable plugins available."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+The Cloud-Native API Gateway
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Enables Kubernetes applications to access cloud resources securely with Azure Active Directory (AAD).
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Enables Kubernetes applications to access cloud resources securely with Azure Active Directory (AAD).
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/appmesh-controller/index.mdx b/src/collections/integrations/appmesh-controller/index.mdx
index 011c672d5bbb..8d70bf937a2c 100644
--- a/src/collections/integrations/appmesh-controller/index.mdx
+++ b/src/collections/integrations/appmesh-controller/index.mdx
@@ -1,72 +1,59 @@
----
-title: AWS App Mesh
-subtitle: Collaborative and visual infrastructure as design for AWS App Mesh
-integrationIcon: icons/color/appmesh-controller-color.svg
-darkModeIntegrationIcon: icons/white/appmesh-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/appmesh-controller
-description:
-category: Cloud Native Network
-subcategory: Service Mesh
-registrant: Artifact Hub
-components: [
-{
-"name": "backend-group",
-"colorIcon": "icons/components/backend-group/icons/color/backend-group-color.svg",
-"whiteIcon": "icons/components/backend-group/icons/white/backend-group-white.svg",
-"description": "",
-},
-{
-"name": "gateway-route",
-"colorIcon": "icons/components/gateway-route/icons/color/gateway-route-color.svg",
-"whiteIcon": "icons/components/gateway-route/icons/white/gateway-route-white.svg",
-"description": "",
-},
-{
-"name": "mesh",
-"colorIcon": "icons/components/mesh/icons/color/mesh-color.svg",
-"whiteIcon": "icons/components/mesh/icons/white/mesh-white.svg",
-"description": "",
-},
-{
-"name": "virtual-gateway",
-"colorIcon": "icons/components/virtual-gateway/icons/color/virtual-gateway-color.svg",
-"whiteIcon": "icons/components/virtual-gateway/icons/white/virtual-gateway-white.svg",
-"description": "",
-},
-{
-"name": "virtual-node",
-"colorIcon": "icons/components/virtual-node/icons/color/virtual-node-color.svg",
-"whiteIcon": "icons/components/virtual-node/icons/white/virtual-node-white.svg",
-"description": "",
-},
-{
-"name": "virtual-router",
-"colorIcon": "icons/components/virtual-router/icons/color/virtual-router-color.svg",
-"whiteIcon": "icons/components/virtual-router/icons/white/virtual-router-white.svg",
-"description": "",
-},
-{
-"name": "virtual-service",
-"colorIcon": "icons/components/virtual-service/icons/color/virtual-service-color.svg",
-"whiteIcon": "icons/components/virtual-service/icons/white/virtual-service-white.svg",
-"description": "",
-}]
-featureList: [
- "Keep revision history and audit trail of all configuration changes",
- "Use MeshMap‘s visual designer to explore your App Mesh configuration",
- "Deploy Meshery on your EKS clusters for App Mesh management"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-AWS App Mesh is a service mesh that provides application-level networking to make it easy for your services to communicate with each other across multiple types of compute infrastructure. App Mesh standardizes how your services communicate, giving you end-to-end visibility and ensuring high-availability for your applications.
-
-
- Deploy and manage the configuration of your AWS App Mesh using the Meshery Adapter for App Mesh. Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+AWS App Mesh is a service mesh that provides application-level networking to make it easy for your services to communicate with each other across multiple types of compute infrastructure. App Mesh standardizes how your services communicate, giving you end-to-end visibility and ensuring high-availability for your applications.
+
+
+ Deploy and manage the configuration of your AWS App Mesh using the Meshery Adapter for App Mesh. Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/argo-cd/index.mdx b/src/collections/integrations/argo-cd/index.mdx
index a44abedc6ebb..66631fe5a850 100644
--- a/src/collections/integrations/argo-cd/index.mdx
+++ b/src/collections/integrations/argo-cd/index.mdx
@@ -1,57 +1,50 @@
----
-title: Argo CD Applications
-subtitle: Collaborative and visual infrastructure as design for Argo CD Applications
-integrationIcon: icons/color/argo-cd-color.svg
-darkModeIntegrationIcon: icons/white/argo-cd-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/argo-cd
-description:
-category: App Definition and Development
-subcategory: Continuous Integration & Delivery
-registrant: Artifact Hub
-components: [
-{
-"name": "argo-cd-extension",
-"colorIcon": "icons/components/argo-cd-extension/icons/color/argo-cd-extension-color.svg",
-"whiteIcon": "icons/components/argo-cd-extension/icons/white/argo-cd-extension-white.svg",
-"description": "",
-},
-{
-"name": "application",
-"colorIcon": "icons/components/application/icons/color/application-color.svg",
-"whiteIcon": "icons/components/application/icons/white/application-white.svg",
-"description": "",
-},
-{
-"name": "application-set",
-"colorIcon": "icons/components/application-set/icons/color/application-set-color.svg",
-"whiteIcon": "icons/components/application-set/icons/white/application-set-white.svg",
-"description": "",
-},
-{
-"name": "app-project",
-"colorIcon": "icons/components/app-project/icons/color/app-project-color.svg",
-"whiteIcon": "icons/components/app-project/icons/white/app-project-white.svg",
-"description": "",
-}]
-featureList: [
- "Gain mastery over Argo as a workflow engine for Kubernetes",
- "Design application definitions using the intuitive, context-aware visual designer, MeshMap.",
- "Visualize your declarative, GitOps continuous delivery tool for Kubernetes."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Workflow engine for Kubernetes
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Argo CD Applications
+subtitle: Collaborative and visual infrastructure as design for Argo CD Applications
+integrationIcon: icons/color/argo-cd-color.svg
+darkModeIntegrationIcon: icons/white/argo-cd-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/argo-cd
+description:
+category: App Definition and Development
+subcategory: Continuous Integration & Delivery
+registrant: Artifact Hub
+components:
+ - name: argo-cd-extension
+ colorIcon: icons/components/argo-cd-extension/icons/color/argo-cd-extension-color.svg
+ whiteIcon: icons/components/argo-cd-extension/icons/white/argo-cd-extension-white.svg
+ description: ""
+ - name: application
+ colorIcon: icons/components/application/icons/color/application-color.svg
+ whiteIcon: icons/components/application/icons/white/application-white.svg
+ description: ""
+ - name: application-set
+ colorIcon: icons/components/application-set/icons/color/application-set-color.svg
+ whiteIcon: icons/components/application-set/icons/white/application-set-white.svg
+ description: ""
+ - name: app-project
+ colorIcon: icons/components/app-project/icons/color/app-project-color.svg
+ whiteIcon: icons/components/app-project/icons/white/app-project-white.svg
+ description: ""
+
+featureList: [
+ "Gain mastery over Argo as a workflow engine for Kubernetes",
+ "Design application definitions using the intuitive, context-aware visual designer, MeshMap.",
+ "Visualize your declarative, GitOps continuous delivery tool for Kubernetes."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Workflow engine for Kubernetes
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/argocd-operator/index.mdx b/src/collections/integrations/argocd-operator/index.mdx
index 40f335d0165f..2214a3ca2a71 100644
--- a/src/collections/integrations/argocd-operator/index.mdx
+++ b/src/collections/integrations/argocd-operator/index.mdx
@@ -1,63 +1,54 @@
----
-title: Argo CD Operator
-subtitle: Collaborative and visual infrastructure as design for Argo CD Operator
-integrationIcon: icons/color/argocd-operator-color.svg
-darkModeIntegrationIcon: icons/white/argocd-operator-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/argocd-operator
-description:
-category: App Definition and Development
-subcategory: Continuous Integration & Delivery
-registrant: Artifact Hub
-components: [
-{
-"name": "argo-cd-export",
-"colorIcon": "icons/components/argo-cd-export/icons/color/argo-cd-export-color.svg",
-"whiteIcon": "icons/components/argo-cd-export/icons/white/argo-cd-export-white.svg",
-"description": "",
-},
-{
-"name": "argo-cd",
-"colorIcon": "icons/components/argo-cd/icons/color/argo-cd-color.svg",
-"whiteIcon": "icons/components/argo-cd/icons/white/argo-cd-white.svg",
-"description": "",
-},
-{
-"name": "application",
-"colorIcon": "icons/components/application/icons/color/application-color.svg",
-"whiteIcon": "icons/components/application/icons/white/application-white.svg",
-"description": "",
-},
-{
-"name": "application-set",
-"colorIcon": "icons/components/application-set/icons/color/application-set-color.svg",
-"whiteIcon": "icons/components/application-set/icons/white/application-set-white.svg",
-"description": "",
-},
-{
-"name": "app-project",
-"colorIcon": "icons/components/app-project/icons/color/app-project-color.svg",
-"whiteIcon": "icons/components/app-project/icons/white/app-project-white.svg",
-"description": "",
-}]
-featureList: [
- "Declarative continuous delivery with a fully-loaded UI.",
- "Application definitions, configurations, and environments can be declarative and version controlled.",
- "Application deployment and lifecycle management can be automated, auditable, and easy to understand."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Deploys and manages Argo CD"
-howItWorksDetails: "Simplified Argo CD management within Kubernetes"
-published: TRUE
----
-
-Argo CD Operator is a Kubernetes operator for managing Argo CD, a declarative, GitOps continuous delivery tool.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Argo CD Operator
+subtitle: Collaborative and visual infrastructure as design for Argo CD Operator
+integrationIcon: icons/color/argocd-operator-color.svg
+darkModeIntegrationIcon: icons/white/argocd-operator-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/argocd-operator
+description:
+category: App Definition and Development
+subcategory: Continuous Integration & Delivery
+registrant: Artifact Hub
+components:
+ - name: argo-cd-export
+ colorIcon: icons/components/argo-cd-export/icons/color/argo-cd-export-color.svg
+ whiteIcon: icons/components/argo-cd-export/icons/white/argo-cd-export-white.svg
+ description: ""
+ - name: argo-cd
+ colorIcon: icons/components/argo-cd/icons/color/argo-cd-color.svg
+ whiteIcon: icons/components/argo-cd/icons/white/argo-cd-white.svg
+ description: ""
+ - name: application
+ colorIcon: icons/components/application/icons/color/application-color.svg
+ whiteIcon: icons/components/application/icons/white/application-white.svg
+ description: ""
+ - name: application-set
+ colorIcon: icons/components/application-set/icons/color/application-set-color.svg
+ whiteIcon: icons/components/application-set/icons/white/application-set-white.svg
+ description: ""
+ - name: app-project
+ colorIcon: icons/components/app-project/icons/color/app-project-color.svg
+ whiteIcon: icons/components/app-project/icons/white/app-project-white.svg
+ description: ""
+
+featureList: [
+ "Declarative continuous delivery with a fully-loaded UI.",
+ "Application definitions, configurations, and environments can be declarative and version controlled.",
+ "Application deployment and lifecycle management can be automated, auditable, and easy to understand."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Deploys and manages Argo CD"
+howItWorksDetails: "Simplified Argo CD management within Kubernetes"
+published: TRUE
+---
+
+Argo CD Operator is a Kubernetes operator for managing Argo CD, a declarative, GitOps continuous delivery tool.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/armory-spinnaker-operator/index.mdx b/src/collections/integrations/armory-spinnaker-operator/index.mdx
index 0262b2d50afb..d66e73b25b92 100644
--- a/src/collections/integrations/armory-spinnaker-operator/index.mdx
+++ b/src/collections/integrations/armory-spinnaker-operator/index.mdx
@@ -1,45 +1,42 @@
----
-title: Armory Spinnaker Operator
-subtitle: Collaborative and visual infrastructure as design for Armory Spinnaker Operator
-integrationIcon: icons/color/armory-spinnaker-operator-color.svg
-darkModeIntegrationIcon: icons/white/armory-spinnaker-operator-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/armory-spinnaker-operator
-description:
-category: App Definition and Development
-subcategory: Continuous Integration & Delivery
-registrant: Artifact Hub
-components: [
-{
-"name": "armory-account",
-"colorIcon": "icons/components/armory-account/icons/color/armory-account-color.svg",
-"whiteIcon": "icons/components/armory-account/icons/white/armory-account-white.svg",
-"description": "",
-},
-{
-"name": "spinnaker-service",
-"colorIcon": "icons/components/spinnaker-service/icons/color/spinnaker-service-color.svg",
-"whiteIcon": "icons/components/spinnaker-service/icons/white/spinnaker-service-white.svg",
-"description": "",
-}]
-featureList: [
- "Stop using Halyard commands: just kubectl apply your Spinnaker configuration.",
- "Expose Spinnaker to the outside world (via LoadBalancer).",
- "Keep secrets separate from your config."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Armory Spinnaker Operator
+subtitle: Collaborative and visual infrastructure as design for Armory Spinnaker Operator
+integrationIcon: icons/color/armory-spinnaker-operator-color.svg
+darkModeIntegrationIcon: icons/white/armory-spinnaker-operator-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/armory-spinnaker-operator
+description:
+category: App Definition and Development
+subcategory: Continuous Integration & Delivery
+registrant: Artifact Hub
+components:
+ - name: armory-account
+ colorIcon: icons/components/armory-account/icons/color/armory-account-color.svg
+ whiteIcon: icons/components/armory-account/icons/white/armory-account-white.svg
+ description: ""
+ - name: spinnaker-service
+ colorIcon: icons/components/spinnaker-service/icons/color/spinnaker-service-color.svg
+ whiteIcon: icons/components/spinnaker-service/icons/white/spinnaker-service-white.svg
+ description: ""
+
+featureList: [
+ "Stop using Halyard commands: just kubectl apply your Spinnaker configuration.",
+ "Expose Spinnaker to the outside world (via LoadBalancer).",
+ "Keep secrets separate from your config."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/artifact-hub/index.mdx b/src/collections/integrations/artifact-hub/index.mdx
index bbf0da038a89..64341a0b8a35 100644
--- a/src/collections/integrations/artifact-hub/index.mdx
+++ b/src/collections/integrations/artifact-hub/index.mdx
@@ -1,33 +1,33 @@
----
-title: Artifact Hub
-subtitle: Collaborative and visual infrastructure as design for Artifact Hub
-integrationIcon: icons/color/artifact-hub-color.svg
-darkModeIntegrationIcon: icons/white/artifact-hub-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/artifact-hub
-description:
-category: App Definition and Development
-subcategory: Application Definition & Image Build
-registrant: Artifact Hub
-components: []
-featureList: [
- "Discover, install and publish packages and configurations.",
- "Explore content like Helm charts schemas and templates in an interactive way.",
- "Subscribe to packages new releases and security alerts notifications, via email or webhooks."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Find, install and publish Kubernetes packages
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Artifact Hub
+subtitle: Collaborative and visual infrastructure as design for Artifact Hub
+integrationIcon: icons/color/artifact-hub-color.svg
+darkModeIntegrationIcon: icons/white/artifact-hub-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/artifact-hub
+description:
+category: App Definition and Development
+subcategory: Application Definition & Image Build
+registrant: Artifact Hub
+components: []
+featureList: [
+ "Discover, install and publish packages and configurations.",
+ "Explore content like Helm charts schemas and templates in an interactive way.",
+ "Subscribe to packages new releases and security alerts notifications, via email or webhooks."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Find, install and publish Kubernetes packages
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/athenz/index.mdx b/src/collections/integrations/athenz/index.mdx
index 613e4c6a3162..fbbd1567b69b 100644
--- a/src/collections/integrations/athenz/index.mdx
+++ b/src/collections/integrations/athenz/index.mdx
@@ -1,33 +1,33 @@
----
-title: Athenz
-subtitle: Collaborative and visual infrastructure as design for Athenz
-integrationIcon: icons/color/athenz-color.svg
-darkModeIntegrationIcon: icons/white/athenz-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/athenz
-description:
-category: Provisioning
-subcategory: Key Management
-registrant: Artifact Hub
-components: []
-featureList: [
- "Identities for all workloads in your hybrid environment.",
- "Authorization and identity provider solution for your Kubernetes clusters.",
- "Industry Standard Authorization mTLS bound access token."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Open source platform for X.509 certificate based service authentication and fine grained access control in dynamic infrastructures
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Athenz
+subtitle: Collaborative and visual infrastructure as design for Athenz
+integrationIcon: icons/color/athenz-color.svg
+darkModeIntegrationIcon: icons/white/athenz-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/athenz
+description:
+category: Provisioning
+subcategory: Key Management
+registrant: Artifact Hub
+components: []
+featureList: [
+ "Identities for all workloads in your hybrid environment.",
+ "Authorization and identity provider solution for your Kubernetes clusters.",
+ "Industry Standard Authorization mTLS bound access token."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Open source platform for X.509 certificate based service authentication and fine grained access control in dynamic infrastructures
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-api-gateway-operator/index.mdx b/src/collections/integrations/aws-api-gateway-operator/index.mdx
index 2c755525b01f..dbead267c929 100644
--- a/src/collections/integrations/aws-api-gateway-operator/index.mdx
+++ b/src/collections/integrations/aws-api-gateway-operator/index.mdx
@@ -1,39 +1,38 @@
----
-title: AWS API Gateway
-subtitle: Collaborative and visual infrastructure as design for AWS API Gateway
-integrationIcon: icons/color/aws-api-gateway-operator-color.svg
-darkModeIntegrationIcon: icons/white/aws-api-gateway-operator-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-api-gateway-operator
-description:
-category: Cloud Native Network
-subcategory: Service Proxy
-registrant: Artifact Hub
-components: [
-{
-"name": "awsapi-gateway",
-"colorIcon": "icons/components/awsapi-gateway/icons/color/awsapi-gateway-color.svg",
-"whiteIcon": "icons/components/awsapi-gateway/icons/white/awsapi-gateway-white.svg",
-"description": "",
-}]
-featureList: [
- "Create, publish, maintain, monitor, and secure REST, HTTP, and WebSocket APIs at any scale.",
- "Create APIs that access AWS or other web services, as well as data stored in the AWS Cloud.",
- "API Gateway creates RESTful APIs that enable stateless client-server communication."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS API Gateway
+subtitle: Collaborative and visual infrastructure as design for AWS API Gateway
+integrationIcon: icons/color/aws-api-gateway-operator-color.svg
+darkModeIntegrationIcon: icons/white/aws-api-gateway-operator-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-api-gateway-operator
+description:
+category: Cloud Native Network
+subcategory: Service Proxy
+registrant: Artifact Hub
+component:
+ - name: awsapi-gateway
+ colorIcon: icons/components/awsapi-gateway/icons/color/awsapi-gateway-color.svg
+ whiteIcon: icons/components/awsapi-gateway/icons/white/awsapi-gateway-white.svg
+ description: ""
+
+featureList: [
+ "Create, publish, maintain, monitor, and secure REST, HTTP, and WebSocket APIs at any scale.",
+ "Create APIs that access AWS or other web services, as well as data stored in the AWS Cloud.",
+ "API Gateway creates RESTful APIs that enable stateless client-server communication."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. APIs act as the "front door" for applications to access data, business logic, or functionality from your backend services. Using API Gateway, you can create RESTful APIs and WebSocket APIs that enable real-time two-way communication applications. API Gateway supports containerized and serverless workloads, as well as web applications.
-
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. APIs act as the "front door" for applications to access data, business logic, or functionality from your backend services. Using API Gateway, you can create RESTful APIs and WebSocket APIs that enable real-time two-way communication applications. API Gateway supports containerized and serverless workloads, as well as web applications.
+
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-AWS Auto Scaling monitors your applications and automatically adjusts capacity to maintain steady, predictable performance at the lowest possible cost. Using AWS Auto Scaling, it’s easy to setup application scaling for multiple resources across multiple services in minutes.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+AWS Auto Scaling monitors your applications and automatically adjusts capacity to maintain steady, predictable performance at the lowest possible cost. Using AWS Auto Scaling, it’s easy to setup application scaling for multiple resources across multiple services in minutes.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon CloudFront is a content delivery network (CDN) service built for high performance, security, and developer convenience.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon CloudFront is a content delivery network (CDN) service built for high performance, security, and developer convenience.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-cloudtrail-controller/index.mdx b/src/collections/integrations/aws-cloudtrail-controller/index.mdx
index 8f2dee22f72f..d747287e13aa 100644
--- a/src/collections/integrations/aws-cloudtrail-controller/index.mdx
+++ b/src/collections/integrations/aws-cloudtrail-controller/index.mdx
@@ -1,57 +1,50 @@
----
-title: AWS CloudTrail
-subtitle: Collaborative and visual infrastructure as design for AWS CloudTrail
-integrationIcon: icons/color/aws-cloudtrail-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-cloudtrail-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudtrail-controller
-description:
-category: Observability and Analysis
-subcategory: Logging
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "event-data-store",
-"colorIcon": "icons/components/event-data-store/icons/color/event-data-store-color.svg",
-"whiteIcon": "icons/components/event-data-store/icons/white/event-data-store-white.svg",
-"description": "",
-},
-{
-"name": "trail",
-"colorIcon": "icons/components/trail/icons/color/trail-color.svg",
-"whiteIcon": "icons/components/trail/icons/white/trail-white.svg",
-"description": "",
-}]
-featureList: [
- "Data events that capture data plane actions within a resource, such as reading or writing an Amazon S3 object.",
- "Configuration items from AWS Config that capture resource configuration history and resource compliance history as evaluated by AWS Config rules.",
- "Audit evidence from AWS Audit Manager that contains the information needed to demonstrate compliance with the requirements as specified by Audit Manager controls."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-AWS CloudTrail monitors and records account activity across your AWS infrastructure, giving you control over storage, analysis, and remediation actions.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS CloudTrail
+subtitle: Collaborative and visual infrastructure as design for AWS CloudTrail
+integrationIcon: icons/color/aws-cloudtrail-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-cloudtrail-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudtrail-controller
+description:
+category: Observability and Analysis
+subcategory: Logging
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: event-data-store
+ colorIcon: icons/components/event-data-store/icons/color/event-data-store-color.svg
+ whiteIcon: icons/components/event-data-store/icons/white/event-data-store-white.svg
+ description: ""
+ - name: trail
+ colorIcon: icons/components/trail/icons/color/trail-color.svg
+ whiteIcon: icons/components/trail/icons/white/trail-white.svg
+ description: ""
+
+featureList: [
+ "Data events that capture data plane actions within a resource, such as reading or writing an Amazon S3 object.",
+ "Configuration items from AWS Config that capture resource configuration history and resource compliance history as evaluated by AWS Config rules.",
+ "Audit evidence from AWS Audit Manager that contains the information needed to demonstrate compliance with the requirements as specified by Audit Manager controls."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+AWS CloudTrail monitors and records account activity across your AWS infrastructure, giving you control over storage, analysis, and remediation actions.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-cloudwatch-controller/index.mdx b/src/collections/integrations/aws-cloudwatch-controller/index.mdx
index beb4a0c38acb..10035ac60bb3 100644
--- a/src/collections/integrations/aws-cloudwatch-controller/index.mdx
+++ b/src/collections/integrations/aws-cloudwatch-controller/index.mdx
@@ -1,51 +1,48 @@
----
-title: AWS CloudWatch
-subtitle: Collaborative and visual infrastructure as design for AWS CloudWatch
-integrationIcon: icons/color/aws-cloudwatch-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-cloudwatch-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudwatch-controller
-description:
-category: Observability and Analysis
-subcategory: Management Governance
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "metric-alarm",
-"colorIcon": "icons/components/metric-alarm/icons/color/metric-alarm-color.svg",
-"whiteIcon": "icons/components/metric-alarm/icons/white/metric-alarm-white.svg",
-"description": "",
-}]
-featureList: [
- "Provides you with data and actionable insights to monitor your applications, respond to system-wide performance changes, and optimize resource utilization.",
- "Collects monitoring and operational data in the form of logs, metrics, and traces.",
- "Get a unified view of operational health and gain complete visibility of your AWS resources, applications, and services running on AWS and on-premises."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-CloudWatch enables you to monitor and observe your AWS and on-premises resources and applications.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS CloudWatch
+subtitle: Collaborative and visual infrastructure as design for AWS CloudWatch
+integrationIcon: icons/color/aws-cloudwatch-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-cloudwatch-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudwatch-controller
+description:
+category: Observability and Analysis
+subcategory: Management Governance
+registrant: GitHub
+components:
+ - name: "field-export"
+ colorIcon: "icons/components/field-export/icons/color/field-export-color.svg"
+ whiteIcon: "icons/components/field-export/icons/white/field-export-white.svg"
+ description: ""
+
+ - name: "adopted-resource"
+ colorIcon: "icons/components/adopted-resource/icons/color/adopted-resource-color.svg"
+ whiteIcon: "icons/components/adopted-resource/icons/white/adopted-resource-white.svg"
+ description: ""
+
+ - name: "metric-alarm"
+ colorIcon: "icons/components/metric-alarm/icons/color/metric-alarm-color.svg"
+ whiteIcon: "icons/components/metric-alarm/icons/white/metric-alarm-white.svg"
+ description: ""
+
+featureList: [
+ "Provides you with data and actionable insights to monitor your applications, respond to system-wide performance changes, and optimize resource utilization.",
+ "Collects monitoring and operational data in the form of logs, metrics, and traces.",
+ "Get a unified view of operational health and gain complete visibility of your AWS resources, applications, and services running on AWS and on-premises."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+CloudWatch enables you to monitor and observe your AWS and on-premises resources and applications.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-cloudwatchlogs-controller/index.mdx b/src/collections/integrations/aws-cloudwatchlogs-controller/index.mdx
index 6763f018b0b3..1c95abf67486 100644
--- a/src/collections/integrations/aws-cloudwatchlogs-controller/index.mdx
+++ b/src/collections/integrations/aws-cloudwatchlogs-controller/index.mdx
@@ -1,51 +1,46 @@
----
-title: AWS CloudWatch Logs
-subtitle: Collaborative and visual infrastructure as design for AWS CloudWatch Logs
-integrationIcon: icons/color/aws-cloudwatchlogs-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-cloudwatchlogs-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudwatchlogs-controller
-description:
-category: Observability and Analysis
-subcategory: Management Governance
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "log-group",
-"colorIcon": "icons/components/log-group/icons/color/log-group-color.svg",
-"whiteIcon": "icons/components/log-group/icons/white/log-group-white.svg",
-"description": "",
-}]
-featureList: [
- "Two classes of log groups for flexibility – CloudWatch Logs offers two classes of log groups so that you can have a cost-effective option for logs that you access infrequently. ",
- "Query your log data – You can use CloudWatch Logs Insights to interactively search and analyze your log data. ",
- "Detect and debug using Live Tail – You can use Live Tail to quickly troubleshoot incidents by viewing a streaming list of new log events as they are ingested. "
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-CloudWatch Logs enables you to centralize the logs from all of your systems, applications, and AWS services that you use, in a single, highly scalable service.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS CloudWatch Logs
+subtitle: Collaborative and visual infrastructure as design for AWS CloudWatch Logs
+integrationIcon: icons/color/aws-cloudwatchlogs-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-cloudwatchlogs-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudwatchlogs-controller
+description:
+category: Observability and Analysis
+subcategory: Management Governance
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: log-group
+ colorIcon: icons/components/log-group/icons/color/log-group-color.svg
+ whiteIcon: icons/components/log-group/icons/white/log-group-white.svg
+ description: ""
+
+featureList: [
+ "Two classes of log groups for flexibility – CloudWatch Logs offers two classes of log groups so that you can have a cost-effective option for logs that you access infrequently. ",
+ "Query your log data – You can use CloudWatch Logs Insights to interactively search and analyze your log data. ",
+ "Detect and debug using Live Tail – You can use Live Tail to quickly troubleshoot incidents by viewing a streaming list of new log events as they are ingested. "
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+CloudWatch Logs enables you to centralize the logs from all of your systems, applications, and AWS services that you use, in a single, highly scalable service.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon DocumentDB (with MongoDB compatibility) is a fully managed native JSON document database that makes it easy and cost effective to operate critical document workloads at virtually any scale without managing infrastructure.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon DocumentDB (with MongoDB compatibility) is a fully managed native JSON document database that makes it easy and cost effective to operate critical document workloads at virtually any scale without managing infrastructure.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-dynamodb-controller/index.mdx b/src/collections/integrations/aws-dynamodb-controller/index.mdx
index 1ac42e0613a4..5d205dfbec93 100644
--- a/src/collections/integrations/aws-dynamodb-controller/index.mdx
+++ b/src/collections/integrations/aws-dynamodb-controller/index.mdx
@@ -1,64 +1,55 @@
----
-title: AWS DynamoDB
-subtitle: Collaborative and visual infrastructure as design for AWS DynamoDB
-integrationIcon: icons/color/aws-dynamodb-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-dynamodb-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-dynamodb-controller
-description:
-category: App Definition and Development
-subcategory: Database
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "backup",
-"colorIcon": "icons/components/backup/icons/color/backup-color.svg",
-"whiteIcon": "icons/components/backup/icons/white/backup-white.svg",
-"description": "",
-},
-{
-"name": "table",
-"colorIcon": "icons/components/table/icons/color/table-color.svg",
-"whiteIcon": "icons/components/table/icons/white/table-white.svg",
-"description": "",
-},
-{
-"name": "global-table",
-"colorIcon": "icons/components/global-table/icons/color/global-table-color.svg",
-"whiteIcon": "icons/components/global-table/icons/white/global-table-white.svg",
-"description": "",
-}]
-featureList: [
- "Handle more than 10 trillion requests per day and can support peaks of more than 20 million requests per second.
-",
- "Secure your data with encryption at rest, automatic backup and restore, and guaranteed reliability with an SLA of up to 99.999% availability.",
- "Fast and flexible NoSQL database service for any scale"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon DynamoDB is a serverless, NoSQL, fully managed database with single-digit millisecond performance at any scale
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS DynamoDB
+subtitle: Collaborative and visual infrastructure as design for AWS DynamoDB
+integrationIcon: icons/color/aws-dynamodb-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-dynamodb-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-dynamodb-controller
+description:
+category: App Definition and Development
+subcategory: Database
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: backup
+ colorIcon: icons/components/backup/icons/color/backup-color.svg
+ whiteIcon: icons/components/backup/icons/white/backup-white.svg
+ description: ""
+ - name: table
+ colorIcon: icons/components/table/icons/color/table-color.svg
+ whiteIcon: icons/components/table/icons/white/table-white.svg
+ description: ""
+ - name: global-table
+ colorIcon: icons/components/global-table/icons/color/global-table-color.svg
+ whiteIcon: icons/components/global-table/icons/white/global-table-white.svg
+ description: ""
+
+featureList: [
+ "Handle more than 10 trillion requests per day and can support peaks of more than 20 million requests per second.
+",
+ "Secure your data with encryption at rest, automatic backup and restore, and guaranteed reliability with an SLA of up to 99.999% availability.",
+ "Fast and flexible NoSQL database service for any scale"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon DynamoDB is a serverless, NoSQL, fully managed database with single-digit millisecond performance at any scale
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon Elastic Compute Cloud (Amazon EC2) offers the broadest and deepest compute platform, with over 750 instances and choice of the latest processor, storage, networking, operating system, and purchase model to help you best match the needs of your workload.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon Elastic Compute Cloud (Amazon EC2) offers the broadest and deepest compute platform, with over 750 instances and choice of the latest processor, storage, networking, operating system, and purchase model to help you best match the needs of your workload.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-ecr-controller/index.mdx b/src/collections/integrations/aws-ecr-controller/index.mdx
index f83949e48101..087d006a7de0 100644
--- a/src/collections/integrations/aws-ecr-controller/index.mdx
+++ b/src/collections/integrations/aws-ecr-controller/index.mdx
@@ -1,59 +1,52 @@
----
-title: AWS Elastic Container Registry
-subtitle: Collaborative and visual infrastructure as design for AWS Elastic Container Registry
-integrationIcon: icons/color/aws-ecr-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-ecr-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-ecr-controller
-description:
-category: Provisioning
-subcategory: Containers
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "pull-through-cache-rule",
-"colorIcon": "icons/components/pull-through-cache-rule/icons/color/pull-through-cache-rule-color.svg",
-"whiteIcon": "icons/components/pull-through-cache-rule/icons/white/pull-through-cache-rule-white.svg",
-"description": "",
-},
-{
-"name": "repository",
-"colorIcon": "icons/components/repository/icons/color/repository-color.svg",
-"whiteIcon": "icons/components/repository/icons/white/repository-white.svg",
-"description": "",
-}]
-featureList: [
- "OCI and Docker support",
- "Public container image and artifact gallery
-
-",
- "Amazon ECR supports the ability to define and organize repositories in your registry using namespaces."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon Elastic Container Registry (Amazon ECR) is a fully managed container registry offering high-performance hosting, so you can reliably deploy application images and artifacts anywhere.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Elastic Container Registry
+subtitle: Collaborative and visual infrastructure as design for AWS Elastic Container Registry
+integrationIcon: icons/color/aws-ecr-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-ecr-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-ecr-controller
+description:
+category: Provisioning
+subcategory: Containers
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: pull-through-cache-rule
+ colorIcon: icons/components/pull-through-cache-rule/icons/color/pull-through-cache-rule-color.svg
+ whiteIcon: icons/components/pull-through-cache-rule/icons/white/pull-through-cache-rule-white.svg
+ description: ""
+ - name: repository
+ colorIcon: icons/components/repository/icons/color/repository-color.svg
+ whiteIcon: icons/components/repository/icons/white/repository-white.svg
+ description: ""
+
+featureList: [
+ "OCI and Docker support",
+ "Public container image and artifact gallery
+
+",
+ "Amazon ECR supports the ability to define and organize repositories in your registry using namespaces."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon Elastic Container Registry (Amazon ECR) is a fully managed container registry offering high-performance hosting, so you can reliably deploy application images and artifacts anywhere.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon Elastic Container Service (Amazon ECS) will launch, monitor, and scale your application across flexible compute options with automatic integrations to other supporting AWS services that your application needs.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon Elastic Container Service (Amazon ECS) will launch, monitor, and scale your application across flexible compute options with automatic integrations to other supporting AWS services that your application needs.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon Elastic File System (Amazon EFS) automatically grows and shrinks as you add and remove files with no need for management or provisioning.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon Elastic File System (Amazon EFS) automatically grows and shrinks as you add and remove files with no need for management or provisioning.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that you can use to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that you can use to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-elasticache-controller/index.mdx b/src/collections/integrations/aws-elasticache-controller/index.mdx
index 34412b0d1201..acb1884bbd98 100644
--- a/src/collections/integrations/aws-elasticache-controller/index.mdx
+++ b/src/collections/integrations/aws-elasticache-controller/index.mdx
@@ -1,87 +1,70 @@
----
-title: AWS ElastiCache
-subtitle: Collaborative and visual infrastructure as design for AWS ElastiCache
-integrationIcon: icons/color/aws-elasticache-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-elasticache-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-elasticache-controller
-description:
-category: App Definition and Development
-subcategory: Database
-registrant: GitHub
-components: [
-{
-"name": "cache-parameter-group",
-"colorIcon": "icons/components/cache-parameter-group/icons/color/cache-parameter-group-color.svg",
-"whiteIcon": "icons/components/cache-parameter-group/icons/white/cache-parameter-group-white.svg",
-"description": "",
-},
-{
-"name": "cache-subnet-group",
-"colorIcon": "icons/components/cache-subnet-group/icons/color/cache-subnet-group-color.svg",
-"whiteIcon": "icons/components/cache-subnet-group/icons/white/cache-subnet-group-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "snapshot",
-"colorIcon": "icons/components/snapshot/icons/color/snapshot-color.svg",
-"whiteIcon": "icons/components/snapshot/icons/white/snapshot-white.svg",
-"description": "",
-},
-{
-"name": "user",
-"colorIcon": "icons/components/user/icons/color/user-color.svg",
-"whiteIcon": "icons/components/user/icons/white/user-white.svg",
-"description": "",
-},
-{
-"name": "user-group",
-"colorIcon": "icons/components/user-group/icons/color/user-group-color.svg",
-"whiteIcon": "icons/components/user-group/icons/white/user-group-white.svg",
-"description": "",
-},
-{
-"name": "replication-group",
-"colorIcon": "icons/components/replication-group/icons/color/replication-group-color.svg",
-"whiteIcon": "icons/components/replication-group/icons/white/replication-group-white.svg",
-"description": "",
-},
-{
-"name": "cache-cluster",
-"colorIcon": "icons/components/cache-cluster/icons/color/cache-cluster-color.svg",
-"whiteIcon": "icons/components/cache-cluster/icons/white/cache-cluster-white.svg",
-"description": "",
-}]
-featureList: [
- "Fully managed Redis and Memcached",
- "Add a cache to your relational database",
- "You can create an ElastiCache Serverless cache in a few steps by specifying a cache name in Meshery"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon ElastiCache allows you to seamlessly set up, run, and scale an in-memory cache in the cloud. ElastiCache is compatible with both Redis and Memcached.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS ElastiCache
+subtitle: Collaborative and visual infrastructure as design for AWS ElastiCache
+integrationIcon: icons/color/aws-elasticache-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-elasticache-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-elasticache-controller
+description:
+category: App Definition and Development
+subcategory: Database
+registrant: GitHub
+components:
+ - name: cache-parameter-group
+ colorIcon: icons/components/cache-parameter-group/icons/color/cache-parameter-group-color.svg
+ whiteIcon: icons/components/cache-parameter-group/icons/white/cache-parameter-group-white.svg
+ description: ""
+ - name: cache-subnet-group
+ colorIcon: icons/components/cache-subnet-group/icons/color/cache-subnet-group-color.svg
+ whiteIcon: icons/components/cache-subnet-group/icons/white/cache-subnet-group-white.svg
+ description: ""
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: snapshot
+ colorIcon: icons/components/snapshot/icons/color/snapshot-color.svg
+ whiteIcon: icons/components/snapshot/icons/white/snapshot-white.svg
+ description: ""
+ - name: user
+ colorIcon: icons/components/user/icons/color/user-color.svg
+ whiteIcon: icons/components/user/icons/white/user-white.svg
+ description: ""
+ - name: user-group
+ colorIcon: icons/components/user-group/icons/color/user-group-color.svg
+ whiteIcon: icons/components/user-group/icons/white/user-group-white.svg
+ description: ""
+ - name: replication-group
+ colorIcon: icons/components/replication-group/icons/color/replication-group-color.svg
+ whiteIcon: icons/components/replication-group/icons/white/replication-group-white.svg
+ description: ""
+ - name: cache-cluster
+ colorIcon: icons/components/cache-cluster/icons/color/cache-cluster-color.svg
+ whiteIcon: icons/components/cache-cluster/icons/white/cache-cluster-white.svg
+ description: ""
+
+featureList: [
+ "Fully managed Redis and Memcached",
+ "Add a cache to your relational database",
+ "You can create an ElastiCache Serverless cache in a few steps by specifying a cache name in Meshery"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon ElastiCache allows you to seamlessly set up, run, and scale an in-memory cache in the cloud. ElastiCache is compatible with both Redis and Memcached.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-elasticsearchservice-controller/index.mdx b/src/collections/integrations/aws-elasticsearchservice-controller/index.mdx
index 55f9ed5c0d75..725c0854ff43 100644
--- a/src/collections/integrations/aws-elasticsearchservice-controller/index.mdx
+++ b/src/collections/integrations/aws-elasticsearchservice-controller/index.mdx
@@ -1,45 +1,42 @@
----
-title: AWS ElasticSearch Service
-subtitle: Collaborative and visual infrastructure as design for AWS ElasticSearch Service
-integrationIcon: icons/color/aws-elasticsearchservice-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-elasticsearchservice-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-elasticsearchservice-controller
-description:
-category: Observability and Analysis
-subcategory: Logging
-registrant: GitHub
-components: [
-{
-"name": "elasticsearch-domain",
-"colorIcon": "icons/components/elasticsearch-domain/icons/color/elasticsearch-domain-color.svg",
-"whiteIcon": "icons/components/elasticsearch-domain/icons/white/elasticsearch-domain-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-}]
-featureList: [
- "Scalable search and analytics",
- "Easy to deploy and manage",
- "Integrates with other AWS services"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Deploys and manages Elasticsearch"
-howItWorksDetails: "Simplified Elasticsearch management and integration with AWS"
-published: TRUE
----
-
-AWS ElasticSearch Service makes it easy for you to perform interactive log analytics, real-time application monitoring, website search, and more.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS ElasticSearch Service
+subtitle: Collaborative and visual infrastructure as design for AWS ElasticSearch Service
+integrationIcon: icons/color/aws-elasticsearchservice-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-elasticsearchservice-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-elasticsearchservice-controller
+description:
+category: Observability and Analysis
+subcategory: Logging
+registrant: GitHub
+components:
+ - name: elasticsearch-domain
+ colorIcon: icons/components/elasticsearch-domain/icons/color/elasticsearch-domain-color.svg
+ whiteIcon: icons/components/elasticsearch-domain/icons/white/elasticsearch-domain-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+featureList: [
+ "Scalable search and analytics",
+ "Easy to deploy and manage",
+ "Integrates with other AWS services"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Deploys and manages Elasticsearch"
+howItWorksDetails: "Simplified Elasticsearch management and integration with AWS"
+published: TRUE
+---
+
+AWS ElasticSearch Service makes it easy for you to perform interactive log analytics, real-time application monitoring, website search, and more.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-emrcontainers-controller/index.mdx b/src/collections/integrations/aws-emrcontainers-controller/index.mdx
index 49f91c8a82bf..e439c9d3ef3c 100644
--- a/src/collections/integrations/aws-emrcontainers-controller/index.mdx
+++ b/src/collections/integrations/aws-emrcontainers-controller/index.mdx
@@ -1,57 +1,50 @@
----
-title: AWS EMR Containers
-subtitle: Collaborative and visual infrastructure as design for AWS EMR Containers
-integrationIcon: icons/color/aws-emrcontainers-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-emrcontainers-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-emrcontainers-controller
-description:
-category: Analytics
-subcategory: Analytics
-registrant: GitHub
-components: [
-{
-"name": "virtual-cluster",
-"colorIcon": "icons/components/virtual-cluster/icons/color/virtual-cluster-color.svg",
-"whiteIcon": "icons/components/virtual-cluster/icons/white/virtual-cluster-white.svg",
-"description": "",
-},
-{
-"name": "job-run",
-"colorIcon": "icons/components/job-run/icons/color/job-run-color.svg",
-"whiteIcon": "icons/components/job-run/icons/white/job-run-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-}]
-featureList: [
- "Runs Spark, Hive, and Presto on Kubernetes",
- "Integrates with other AWS services",
- "Cost-effective big data processing"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Runs containers on EMR"
-howItWorksDetails: "Easier big data processing on Kubernetes with EMR"
-published: TRUE
----
-
-Amazon EMR on EKS provides a deployment option for Amazon EMR that allows you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS EMR Containers
+subtitle: Collaborative and visual infrastructure as design for AWS EMR Containers
+integrationIcon: icons/color/aws-emrcontainers-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-emrcontainers-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-emrcontainers-controller
+description:
+category: Analytics
+subcategory: Analytics
+registrant: GitHub
+components:
+ - name: virtual-cluster
+ colorIcon: icons/components/virtual-cluster/icons/color/virtual-cluster-color.svg
+ whiteIcon: icons/components/virtual-cluster/icons/white/virtual-cluster-white.svg
+ description: ""
+ - name: job-run
+ colorIcon: icons/components/job-run/icons/color/job-run-color.svg
+ whiteIcon: icons/components/job-run/icons/white/job-run-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+featureList: [
+ "Runs Spark, Hive, and Presto on Kubernetes",
+ "Integrates with other AWS services",
+ "Cost-effective big data processing"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Runs containers on EMR"
+howItWorksDetails: "Easier big data processing on Kubernetes with EMR"
+published: TRUE
+---
+
+Amazon EMR on EKS provides a deployment option for Amazon EMR that allows you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-eventbridge-controller/index.mdx b/src/collections/integrations/aws-eventbridge-controller/index.mdx
index c5830c8b9f7a..e949bd0e1e22 100644
--- a/src/collections/integrations/aws-eventbridge-controller/index.mdx
+++ b/src/collections/integrations/aws-eventbridge-controller/index.mdx
@@ -1,69 +1,58 @@
----
-title: AWS EventBridge
-subtitle: Collaborative and visual infrastructure as design for AWS EventBridge
-integrationIcon: icons/color/aws-eventbridge-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-eventbridge-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-eventbridge-controller
-description:
-category: App Definition and Development
-subcategory: Streaming & Messaging
-registrant: GitHub
-components: [
-{
-"name": "archive",
-"colorIcon": "icons/components/archive/icons/color/archive-color.svg",
-"whiteIcon": "icons/components/archive/icons/white/archive-white.svg",
-"description": "",
-},
-{
-"name": "endpoint",
-"colorIcon": "icons/components/endpoint/icons/color/endpoint-color.svg",
-"whiteIcon": "icons/components/endpoint/icons/white/endpoint-white.svg",
-"description": "",
-},
-{
-"name": "event-bus",
-"colorIcon": "icons/components/event-bus/icons/color/event-bus-color.svg",
-"whiteIcon": "icons/components/event-bus/icons/white/event-bus-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "rule",
-"colorIcon": "icons/components/rule/icons/color/rule-color.svg",
-"whiteIcon": "icons/components/rule/icons/white/rule-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-}]
-featureList: [
- "Amazon EventBridge Event Bus is a serverless event bus that helps you receive, filter, transform, route, and deliver events.",
- "Amazon EventBridge Pipes is a serverless point-to-point integration resource that helps you connect event producers to event consumers with optional filtering, enrichment, and transformation capabilities.",
- "Use Amazon EventBridge Scheduler to schedule tasks and events at scale."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon EventBridge enables you to build event-driven applications at scale across AWS, existing systems, or SaaS applications
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS EventBridge
+subtitle: Collaborative and visual infrastructure as design for AWS EventBridge
+integrationIcon: icons/color/aws-eventbridge-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-eventbridge-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-eventbridge-controller
+description:
+category: App Definition and Development
+subcategory: Streaming & Messaging
+registrant: GitHub
+components:
+ - name: archive
+ colorIcon: icons/components/archive/icons/color/archive-color.svg
+ whiteIcon: icons/components/archive/icons/white/archive-white.svg
+ description: ""
+ - name: endpoint
+ colorIcon: icons/components/endpoint/icons/color/endpoint-color.svg
+ whiteIcon: icons/components/endpoint/icons/white/endpoint-white.svg
+ description: ""
+ - name: event-bus
+ colorIcon: icons/components/event-bus/icons/color/event-bus-color.svg
+ whiteIcon: icons/components/event-bus/icons/white/event-bus-white.svg
+ description: ""
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: rule
+ colorIcon: icons/components/rule/icons/color/rule-color.svg
+ whiteIcon: icons/components/rule/icons/white/rule-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+featureList: [
+ "Amazon EventBridge Event Bus is a serverless event bus that helps you receive, filter, transform, route, and deliver events.",
+ "Amazon EventBridge Pipes is a serverless point-to-point integration resource that helps you connect event producers to event consumers with optional filtering, enrichment, and transformation capabilities.",
+ "Use Amazon EventBridge Scheduler to schedule tasks and events at scale."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon EventBridge enables you to build event-driven applications at scale across AWS, existing systems, or SaaS applications
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-AWS Identity and Access Management securely manage identities and access to AWS services and resources
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+AWS Identity and Access Management securely manage identities and access to AWS services and resources
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-kinesis-controller/index.mdx b/src/collections/integrations/aws-kinesis-controller/index.mdx
index 94ca074ddfc6..8e5d1ab579bc 100644
--- a/src/collections/integrations/aws-kinesis-controller/index.mdx
+++ b/src/collections/integrations/aws-kinesis-controller/index.mdx
@@ -1,51 +1,46 @@
----
-title: AWS Kinesis
-subtitle: Collaborative and visual infrastructure as design for AWS Kinesis
-integrationIcon: icons/color/aws-kinesis-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-kinesis-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-kinesis-controller
-description:
-category: App Definition and Development
-subcategory: Streaming & Messaging
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "stream",
-"colorIcon": "icons/components/stream/icons/color/stream-color.svg",
-"whiteIcon": "icons/components/stream/icons/white/stream-white.svg",
-"description": "",
-}]
-featureList: [
- "Collects, processes, and analyzes streaming data",
- "Scalable and durable",
- "Integrates with various AWS services"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Integrates with Kinesis Data Streams"
-howItWorksDetails: "Real-time data processing and analytics in AWS"
-published: TRUE
----
-
-AWS Kinesis enables you to collect, process, and analyze video and data streams in real time
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Kinesis
+subtitle: Collaborative and visual infrastructure as design for AWS Kinesis
+integrationIcon: icons/color/aws-kinesis-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-kinesis-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-kinesis-controller
+description:
+category: App Definition and Development
+subcategory: Streaming & Messaging
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: stream
+ colorIcon: icons/components/stream/icons/color/stream-color.svg
+ whiteIcon: icons/components/stream/icons/white/stream-white.svg
+ description: ""
+
+featureList: [
+ "Collects, processes, and analyzes streaming data",
+ "Scalable and durable",
+ "Integrates with various AWS services"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Integrates with Kinesis Data Streams"
+howItWorksDetails: "Real-time data processing and analytics in AWS"
+published: TRUE
+---
+
+AWS Kinesis enables you to collect, process, and analyze video and data streams in real time
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-kms-controller/index.mdx b/src/collections/integrations/aws-kms-controller/index.mdx
index 861fe00dec54..117c8d623fa4 100644
--- a/src/collections/integrations/aws-kms-controller/index.mdx
+++ b/src/collections/integrations/aws-kms-controller/index.mdx
@@ -1,63 +1,54 @@
----
-title: AWS KMS
-subtitle: Collaborative and visual infrastructure as design for AWS KMS
-integrationIcon: icons/color/aws-kms-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-kms-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-kms-controller
-description:
-category: Security & Compliance
-subcategory: Key Management Service
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "alias",
-"colorIcon": "icons/components/alias/icons/color/alias-color.svg",
-"whiteIcon": "icons/components/alias/icons/white/alias-white.svg",
-"description": "",
-},
-{
-"name": "grant",
-"colorIcon": "icons/components/grant/icons/color/grant-color.svg",
-"whiteIcon": "icons/components/grant/icons/white/grant-white.svg",
-"description": "",
-},
-{
-"name": "key",
-"colorIcon": "icons/components/key/icons/color/key-color.svg",
-"whiteIcon": "icons/components/key/icons/white/key-white.svg",
-"description": "",
-}]
-featureList: [
- "Secure key management",
- "Encrypts data at rest and in transit",
- "Integrates with other AWS services"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Integrates with KMS"
-howItWorksDetails: "Enhanced security for Kubernetes applications and data on AWS"
-published: TRUE
----
-
-AWS Key Management Service (AWS KMS) is a managed service that makes it easy for you to create and control the cryptographic keys that are used to protect your data.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS KMS
+subtitle: Collaborative and visual infrastructure as design for AWS KMS
+integrationIcon: icons/color/aws-kms-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-kms-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-kms-controller
+description:
+category: Security & Compliance
+subcategory: Key Management Service
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: alias
+ colorIcon: icons/components/alias/icons/color/alias-color.svg
+ whiteIcon: icons/components/alias/icons/white/alias-white.svg
+ description: ""
+ - name: grant
+ colorIcon: icons/components/grant/icons/color/grant-color.svg
+ whiteIcon: icons/components/grant/icons/white/grant-white.svg
+ description: ""
+ - name: key
+ colorIcon: icons/components/key/icons/color/key-color.svg
+ whiteIcon: icons/components/key/icons/white/key-white.svg
+ description: ""
+
+featureList: [
+ "Secure key management",
+ "Encrypts data at rest and in transit",
+ "Integrates with other AWS services"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Integrates with KMS"
+howItWorksDetails: "Enhanced security for Kubernetes applications and data on AWS"
+published: TRUE
+---
+
+AWS Key Management Service (AWS KMS) is a managed service that makes it easy for you to create and control the cryptographic keys that are used to protect your data.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-lambda-controller/index.mdx b/src/collections/integrations/aws-lambda-controller/index.mdx
index c10f7e4dea9f..ec3b9783379a 100644
--- a/src/collections/integrations/aws-lambda-controller/index.mdx
+++ b/src/collections/integrations/aws-lambda-controller/index.mdx
@@ -1,87 +1,70 @@
----
-title: AWS Lambda
-subtitle: Collaborative and visual infrastructure as design for AWS Lambda
-integrationIcon: icons/color/aws-lambda-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-lambda-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-lambda-controller
-description:
-category: App Definition and Development
-subcategory: Serverless
-registrant: GitHub
-components: [
-{
-"name": "code-signing-config",
-"colorIcon": "icons/components/code-signing-config/icons/color/code-signing-config-color.svg",
-"whiteIcon": "icons/components/code-signing-config/icons/white/code-signing-config-white.svg",
-"description": "",
-},
-{
-"name": "event-source-mapping",
-"colorIcon": "icons/components/event-source-mapping/icons/color/event-source-mapping-color.svg",
-"whiteIcon": "icons/components/event-source-mapping/icons/white/event-source-mapping-white.svg",
-"description": "",
-},
-{
-"name": "function-url-config",
-"colorIcon": "icons/components/function-url-config/icons/color/function-url-config-color.svg",
-"whiteIcon": "icons/components/function-url-config/icons/white/function-url-config-white.svg",
-"description": "",
-},
-{
-"name": "layer-version",
-"colorIcon": "icons/components/layer-version/icons/color/layer-version-color.svg",
-"whiteIcon": "icons/components/layer-version/icons/white/layer-version-white.svg",
-"description": "",
-},
-{
-"name": "function",
-"colorIcon": "icons/components/function/icons/color/function-color.svg",
-"whiteIcon": "icons/components/function/icons/white/function-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "alias",
-"colorIcon": "icons/components/alias/icons/color/alias-color.svg",
-"whiteIcon": "icons/components/alias/icons/white/alias-white.svg",
-"description": "",
-},
-{
-"name": "version",
-"colorIcon": "icons/components/version/icons/color/version-color.svg",
-"whiteIcon": "icons/components/version/icons/white/version-white.svg",
-"description": "",
-}]
-featureList: [
- "Run code for virtually any type of application or backend service. ",
- "Write Lambda functions in your favorite language ",
- "Bring your own code"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-AWS Lambda enables you to run code without provisioning or managing servers, creating workload-aware cluster scaling logic, maintaining event integrations, or managing runtimes.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Lambda
+subtitle: Collaborative and visual infrastructure as design for AWS Lambda
+integrationIcon: icons/color/aws-lambda-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-lambda-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-lambda-controller
+description:
+category: App Definition and Development
+subcategory: Serverless
+registrant: GitHub
+components:
+ - name: code-signing-config
+ colorIcon: icons/components/code-signing-config/icons/color/code-signing-config-color.svg
+ whiteIcon: icons/components/code-signing-config/icons/white/code-signing-config-white.svg
+ description: ""
+ - name: event-source-mapping
+ colorIcon: icons/components/event-source-mapping/icons/color/event-source-mapping-color.svg
+ whiteIcon: icons/components/event-source-mapping/icons/white/event-source-mapping-white.svg
+ description: ""
+ - name: function-url-config
+ colorIcon: icons/components/function-url-config/icons/color/function-url-config-color.svg
+ whiteIcon: icons/components/function-url-config/icons/white/function-url-config-white.svg
+ description: ""
+ - name: layer-version
+ colorIcon: icons/components/layer-version/icons/color/layer-version-color.svg
+ whiteIcon: icons/components/layer-version/icons/white/layer-version-white.svg
+ description: ""
+ - name: function
+ colorIcon: icons/components/function/icons/color/function-color.svg
+ whiteIcon: icons/components/function/icons/white/function-white.svg
+ description: ""
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+ - name: alias
+ colorIcon: icons/components/alias/icons/color/alias-color.svg
+ whiteIcon: icons/components/alias/icons/white/alias-white.svg
+ description: ""
+ - name: version
+ colorIcon: icons/components/version/icons/color/version-color.svg
+ whiteIcon: icons/components/version/icons/white/version-white.svg
+ description: ""
+
+featureList: [
+ "Run code for virtually any type of application or backend service. ",
+ "Write Lambda functions in your favorite language ",
+ "Bring your own code"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+AWS Lambda enables you to run code without provisioning or managing servers, creating workload-aware cluster scaling logic, maintaining event integrations, or managing runtimes.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-load-balancer-controller/index.mdx b/src/collections/integrations/aws-load-balancer-controller/index.mdx
index 4e055fc1642d..1c72c841d010 100644
--- a/src/collections/integrations/aws-load-balancer-controller/index.mdx
+++ b/src/collections/integrations/aws-load-balancer-controller/index.mdx
@@ -1,41 +1,40 @@
----
-title: AWS Load Balancer
-subtitle: Collaborative and visual infrastructure as design for AWS Load Balancer
-integrationIcon: icons/color/aws-load-balancer-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-load-balancer-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-load-balancer-controller
-description:
-category: Cloud Native Network
-subcategory: Service Proxy
-registrant: Artifact Hub
-components: [
-{
-"name": "ingress-class-params",
-"colorIcon": "icons/components/ingress-class-params/icons/color/ingress-class-params-color.svg",
-"whiteIcon": "icons/components/ingress-class-params/icons/white/ingress-class-params-white.svg",
-"description": "",
-}]
-featureList: [
- "Manage AWS Elastic Load Balancers for a Kubernetes cluster.",
- "Provide high performance traffic serving that can scale to millions of requests per second.",
- "Supports IP address targeting mode for Network Load Balancers."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones (AZs)."
-published: TRUE
----
-
-Distribute network traffic to improve application scalability
-Get Started with Elastic Load Balancing
-
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Load Balancer
+subtitle: Collaborative and visual infrastructure as design for AWS Load Balancer
+integrationIcon: icons/color/aws-load-balancer-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-load-balancer-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-load-balancer-controller
+description:
+category: Cloud Native Network
+subcategory: Service Proxy
+registrant: Artifact Hub
+components:
+ - name: ingress-class-params
+ colorIcon: icons/components/ingress-class-params/icons/color/ingress-class-params-color.svg
+ whiteIcon: icons/components/ingress-class-params/icons/white/ingress-class-params-white.svg
+ description: ""
+
+featureList: [
+ "Manage AWS Elastic Load Balancers for a Kubernetes cluster.",
+ "Provide high performance traffic serving that can scale to millions of requests per second.",
+ "Supports IP address targeting mode for Network Load Balancers."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones (AZs)."
+published: TRUE
+---
+
+Distribute network traffic to improve application scalability
+Get Started with Elastic Load Balancing
+
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-memorydb-controller/index.mdx b/src/collections/integrations/aws-memorydb-controller/index.mdx
index 8e0a2e2399b9..78041d2b1588 100644
--- a/src/collections/integrations/aws-memorydb-controller/index.mdx
+++ b/src/collections/integrations/aws-memorydb-controller/index.mdx
@@ -1,81 +1,73 @@
----
-title: AWS MemoryDB for Redis
-subtitle: Collaborative and visual infrastructure as design for AWS MemoryDB for Redis
-integrationIcon: icons/color/aws-memorydb-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-memorydb-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-memorydb-controller
-description:
-category: Provisioning
-subcategory: Database
-registrant: GitHub
-components: [
-{
-"name": "cluster",
-"colorIcon": "icons/components/cluster/icons/color/cluster-color.svg",
-"whiteIcon": "icons/components/cluster/icons/white/cluster-white.svg",
-"description": "",
-},
-{
-"name": "snapshot",
-"colorIcon": "icons/components/snapshot/icons/color/snapshot-color.svg",
-"whiteIcon": "icons/components/snapshot/icons/white/snapshot-white.svg",
-"description": "",
-},
-{
-"name": "subnet-group",
-"colorIcon": "icons/components/subnet-group/icons/color/subnet-group-color.svg",
-"whiteIcon": "icons/components/subnet-group/icons/white/subnet-group-white.svg",
-"description": "",
-},
-{
-"name": "user",
-"colorIcon": "icons/components/user/icons/color/user-color.svg",
-"whiteIcon": "icons/components/user/icons/white/user-white.svg",
-"description": "",
-},
-{
-"name": "parameter-group",
-"colorIcon": "icons/components/parameter-group/icons/color/parameter-group-color.svg",
-"whiteIcon": "icons/components/parameter-group/icons/white/parameter-group-white.svg",
-"description": "",
-},
-{
-"name": "acl",
-"colorIcon": "icons/components/acl/icons/color/acl-color.svg",
-"whiteIcon": "icons/components/acl/icons/white/acl-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-}]
-featureList: [
- "Amazon MemoryDB for Redis enables machine learning (ML) and generative artificial intelligence (AI) models to work with data stored in Amazon MemoryDB in real-time and without moving your data.",
- "Amazon MemoryDB provides native support for JavaScript Object Notation (JSON) documents in addition to the data structures included in open source Redis, at no additional cost.",
- "MemoryDB stores your entire dataset in memory to deliver microsecond read latency, single-digit millisecond write latency, and high throughput. It can handle more than 13 trillion requests per day and support peaks of 160 million requests per second."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon MemoryDB for Redis is a durable database with microsecond reads, low single-digit millisecond writes, scalability, and enterprise security. MemoryDB delivers 99.99% availability and near instantaneous recovery without any data loss.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS MemoryDB for Redis
+subtitle: Collaborative and visual infrastructure as design for AWS MemoryDB for Redis
+integrationIcon: icons/color/aws-memorydb-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-memorydb-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-memorydb-controller
+description:
+category: Provisioning
+subcategory: Database
+registrant: GitHub
+components:
+ - name: cluster
+ colorIcon: icons/components/cluster/icons/color/cluster-color.svg
+ whiteIcon: icons/components/cluster/icons/white/cluster-white.svg
+ description: ""
+
+ - name: snapshot
+ colorIcon: icons/components/snapshot/icons/color/snapshot-color.svg
+ whiteIcon: icons/components/snapshot/icons/white/snapshot-white.svg
+ description: ""
+
+ - name: subnet-group
+ colorIcon: icons/components/subnet-group/icons/color/subnet-group-color.svg
+ whiteIcon: icons/components/subnet-group/icons/white/subnet-group-white.svg
+ description: ""
+
+ - name: user
+ colorIcon: icons/components/user/icons/color/user-color.svg
+ whiteIcon: icons/components/user/icons/white/user-white.svg
+ description: ""
+
+ - name: parameter-group
+ colorIcon: icons/components/parameter-group/icons/color/parameter-group-color.svg
+ whiteIcon: icons/components/parameter-group/icons/white/parameter-group-white.svg
+ description: ""
+
+ - name: acl
+ colorIcon: icons/components/acl/icons/color/acl-color.svg
+ whiteIcon: icons/components/acl/icons/white/acl-white.svg
+ description: ""
+
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+featureList: [
+ "Amazon MemoryDB for Redis enables machine learning (ML) and generative artificial intelligence (AI) models to work with data stored in Amazon MemoryDB in real-time and without moving your data.",
+ "Amazon MemoryDB provides native support for JavaScript Object Notation (JSON) documents in addition to the data structures included in open source Redis, at no additional cost.",
+ "MemoryDB stores your entire dataset in memory to deliver microsecond read latency, single-digit millisecond write latency, and high throughput. It can handle more than 13 trillion requests per day and support peaks of 160 million requests per second."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon MemoryDB for Redis is a durable database with microsecond reads, low single-digit millisecond writes, scalability, and enterprise security. MemoryDB delivers 99.99% availability and near instantaneous recovery without any data loss.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-mq-controller/index.mdx b/src/collections/integrations/aws-mq-controller/index.mdx
index 0dacf20cb5ee..f6b7df41e0af 100644
--- a/src/collections/integrations/aws-mq-controller/index.mdx
+++ b/src/collections/integrations/aws-mq-controller/index.mdx
@@ -1,51 +1,45 @@
----
-title: AWS MQ
-subtitle: Collaborative and visual infrastructure as design for AWS MQ
-integrationIcon: icons/color/aws-mq-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-mq-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-mq-controller
-description:
-category: App Definition and Development
-subcategory: Streaming & Messaging
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "broker",
-"colorIcon": "icons/components/broker/icons/color/broker-color.svg",
-"whiteIcon": "icons/components/broker/icons/white/broker-white.svg",
-"description": "",
-}]
-featureList: [
- "Reliable and scalable message brokering",
- "Supports various messaging protocols",
- "Integrates with other AWS services"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Integrates with AWS MQ"
-howItWorksDetails: "Simplified message brokering for Kubernetes applications on AWS"
-published: TRUE
----
-
-AWS MQ offers fully managed service for open-source message brokers
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS MQ
+subtitle: Collaborative and visual infrastructure as design for AWS MQ
+integrationIcon: icons/color/aws-mq-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-mq-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-mq-controller
+description:
+category: App Definition and Development
+subcategory: Streaming & Messaging
+registrant: GitHub
+components:
+- name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description:
+- name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description:
+- name: broker
+ colorIcon: icons/components/broker/icons/color/broker-color.svg
+ whiteIcon: icons/components/broker/icons/white/broker-white.svg
+ description:
+featureList: [
+ "Reliable and scalable message brokering",
+ "Supports various messaging protocols",
+ "Integrates with other AWS services"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Integrates with AWS MQ"
+howItWorksDetails: "Simplified message brokering for Kubernetes applications on AWS"
+published: TRUE
+---
+
+AWS MQ offers fully managed service for open-source message brokers
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
\ No newline at end of file
diff --git a/src/collections/integrations/aws-node-termination-handler-2/index.mdx b/src/collections/integrations/aws-node-termination-handler-2/index.mdx
index 47d275108efb..e46c422f49b7 100644
--- a/src/collections/integrations/aws-node-termination-handler-2/index.mdx
+++ b/src/collections/integrations/aws-node-termination-handler-2/index.mdx
@@ -1,42 +1,40 @@
----
-title: AWS Node Termination Handler
-subtitle: Collaborative and visual infrastructure as design for AWS Node Termination Handler
-integrationIcon: icons/color/aws-node-termination-handler-2-color.svg
-darkModeIntegrationIcon: icons/white/aws-node-termination-handler-2-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-node-termination-handler-2
-description:
-category: Provisioning
-subcategory: Automation & Configuration
-registrant: Artifact Hub
-components: [
-{
-"name": "terminator",
-"colorIcon": "icons/components/terminator/icons/color/terminator-color.svg",
-"whiteIcon": "icons/components/terminator/icons/white/terminator-white.svg",
-"description": "",
-}]
-featureList: [
- "Keep revision history and audit trail of all configuration changes",
- "Use MeshMap‘s visual designer to explore your App Mesh configuration",
- "Deploy Meshery on your EKS clusters for App Mesh management"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Gracefully handle EC2 instance shutdown within Kubernetes
-
-
-
AWS Node Termination Handler ensures that the Kubernetes control plane responds appropriately to events that can cause your EC2 instance to become unavailable, such as EC2 maintenance events, EC2 Spot interruptions, ASG Scale-In, ASG AZ Rebalance, and EC2 Instance Termination via the API or Console. If not handled, your application code may not stop gracefully, take longer to recover full availability, or accidentally schedule work to nodes that are going down.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Node Termination Handler
+subtitle: Collaborative and visual infrastructure as design for AWS Node Termination Handler
+integrationIcon: icons/color/aws-node-termination-handler-2-color.svg
+darkModeIntegrationIcon: icons/white/aws-node-termination-handler-2-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-node-termination-handler-2
+description:
+category: Provisioning
+subcategory: Automation & Configuration
+registrant: Artifact Hub
+components:
+ - name: terminator
+ colorIcon: icons/components/terminator/icons/color/terminator-color.svg
+ whiteIcon: icons/components/terminator/icons/white/terminator-white.svg
+ description: ""
+
+featureList: [
+ "Keep revision history and audit trail of all configuration changes",
+ "Use MeshMap‘s visual designer to explore your App Mesh configuration",
+ "Deploy Meshery on your EKS clusters for App Mesh management"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Gracefully handle EC2 instance shutdown within Kubernetes
+
+
+
AWS Node Termination Handler ensures that the Kubernetes control plane responds appropriately to events that can cause your EC2 instance to become unavailable, such as EC2 maintenance events, EC2 Spot interruptions, ASG Scale-In, ASG AZ Rebalance, and EC2 Instance Termination via the API or Console. If not handled, your application code may not stop gracefully, take longer to recover full availability, or accidentally schedule work to nodes that are going down.
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-prometheusservice-controller/index.mdx b/src/collections/integrations/aws-prometheusservice-controller/index.mdx
index 3c3b59b5c783..a93ef6cbc143 100644
--- a/src/collections/integrations/aws-prometheusservice-controller/index.mdx
+++ b/src/collections/integrations/aws-prometheusservice-controller/index.mdx
@@ -1,69 +1,63 @@
----
-title: AWS Managed Service for Prometheus
-subtitle: Collaborative and visual infrastructure as design for AWS Managed Service for Prometheus
-integrationIcon: icons/color/aws-prometheusservice-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-prometheusservice-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-prometheusservice-controller
-description:
-category: Observability and Analysis
-subcategory: Metrics
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "alert-manager-definition",
-"colorIcon": "icons/components/alert-manager-definition/icons/color/alert-manager-definition-color.svg",
-"whiteIcon": "icons/components/alert-manager-definition/icons/white/alert-manager-definition-white.svg",
-"description": "",
-},
-{
-"name": "workspace",
-"colorIcon": "icons/components/workspace/icons/color/workspace-color.svg",
-"whiteIcon": "icons/components/workspace/icons/white/workspace-white.svg",
-"description": "",
-},
-{
-"name": "logging-configuration",
-"colorIcon": "icons/components/logging-configuration/icons/color/logging-configuration-color.svg",
-"whiteIcon": "icons/components/logging-configuration/icons/white/logging-configuration-white.svg",
-"description": "",
-},
-{
-"name": "rule-groups-namespace",
-"colorIcon": "icons/components/rule-groups-namespace/icons/color/rule-groups-namespace-color.svg",
-"whiteIcon": "icons/components/rule-groups-namespace/icons/white/rule-groups-namespace-white.svg",
-"description": "",
-}]
-featureList: [
- "No collection agents required",
- "Amazon Managed Service for Prometheus includes a remote write-compatible API that can ingest metrics from OpenTelemetry, Prometheus libraries, and existing Prometheus servers.",
- "Amazon Managed Service for Prometheus includes a query-compatible HTTP API that allows you to query metrics, metric labels, metric metadata, and time series metrics. "
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon Managed Service for Prometheus is a Prometheus-compatible service that monitors and provides alerts on containerized applications and infrastructure at scale. The service is integrated with Amazon Elastic Kubernetes Service (EKS), Amazon Elastic Container Service (ECS), and AWS Distro for OpenTelemetry.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Managed Service for Prometheus
+subtitle: Collaborative and visual infrastructure as design for AWS Managed Service for Prometheus
+integrationIcon: icons/color/aws-prometheusservice-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-prometheusservice-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-prometheusservice-controller
+description:
+category: Observability and Analysis
+subcategory: Metrics
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: alert-manager-definition
+ colorIcon: icons/components/alert-manager-definition/icons/color/alert-manager-definition-color.svg
+ whiteIcon: icons/components/alert-manager-definition/icons/white/alert-manager-definition-white.svg
+ description: ""
+
+ - name: workspace
+ colorIcon: icons/components/workspace/icons/color/workspace-color.svg
+ whiteIcon: icons/components/workspace/icons/white/workspace-white.svg
+ description: ""
+
+ - name: logging-configuration
+ colorIcon: icons/components/logging-configuration/icons/color/logging-configuration-color.svg
+ whiteIcon: icons/components/logging-configuration/icons/white/logging-configuration-white.svg
+ description: ""
+
+ - name: rule-groups-namespace
+ colorIcon: icons/components/rule-groups-namespace/icons/color/rule-groups-namespace-color.svg
+ whiteIcon: icons/components/rule-groups-namespace/icons/white/rule-groups-namespace-white.svg
+ description: ""
+
+featureList: [
+ "No collection agents required",
+ "Amazon Managed Service for Prometheus includes a remote write-compatible API that can ingest metrics from OpenTelemetry, Prometheus libraries, and existing Prometheus servers.",
+ "Amazon Managed Service for Prometheus includes a query-compatible HTTP API that allows you to query metrics, metric labels, metric metadata, and time series metrics. "
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon Managed Service for Prometheus is a Prometheus-compatible service that monitors and provides alerts on containerized applications and infrastructure at scale. The service is integrated with Amazon Elastic Kubernetes Service (EKS), Amazon Elastic Container Service (ECS), and AWS Distro for OpenTelemetry.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-rds-controller/index.mdx b/src/collections/integrations/aws-rds-controller/index.mdx
index f7b824ed94fd..2e4a5bf6ac30 100644
--- a/src/collections/integrations/aws-rds-controller/index.mdx
+++ b/src/collections/integrations/aws-rds-controller/index.mdx
@@ -1,105 +1,88 @@
----
-title: AWS Relational Database Service
-subtitle: Collaborative and visual infrastructure as design for AWS Relational Database Service
-integrationIcon: icons/color/aws-rds-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-rds-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-rds-controller
-description:
-category: App Definition and Development
-subcategory: Database
-registrant: GitHub
-components: [
-{
-"name": "db-cluster",
-"colorIcon": "icons/components/db-cluster/icons/color/db-cluster-color.svg",
-"whiteIcon": "icons/components/db-cluster/icons/white/db-cluster-white.svg",
-"description": "",
-},
-{
-"name": "db-cluster-parameter-group",
-"colorIcon": "icons/components/db-cluster-parameter-group/icons/color/db-cluster-parameter-group-color.svg",
-"whiteIcon": "icons/components/db-cluster-parameter-group/icons/white/db-cluster-parameter-group-white.svg",
-"description": "",
-},
-{
-"name": "db-instance",
-"colorIcon": "icons/components/db-instance/icons/color/db-instance-color.svg",
-"whiteIcon": "icons/components/db-instance/icons/white/db-instance-white.svg",
-"description": "",
-},
-{
-"name": "db-parameter-group",
-"colorIcon": "icons/components/db-parameter-group/icons/color/db-parameter-group-color.svg",
-"whiteIcon": "icons/components/db-parameter-group/icons/white/db-parameter-group-white.svg",
-"description": "",
-},
-{
-"name": "db-proxy",
-"colorIcon": "icons/components/db-proxy/icons/color/db-proxy-color.svg",
-"whiteIcon": "icons/components/db-proxy/icons/white/db-proxy-white.svg",
-"description": "",
-},
-{
-"name": "db-subnet-group",
-"colorIcon": "icons/components/db-subnet-group/icons/color/db-subnet-group-color.svg",
-"whiteIcon": "icons/components/db-subnet-group/icons/white/db-subnet-group-white.svg",
-"description": "",
-},
-{
-"name": "global-cluster",
-"colorIcon": "icons/components/global-cluster/icons/color/global-cluster-color.svg",
-"whiteIcon": "icons/components/global-cluster/icons/white/global-cluster-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "db-snapshot",
-"colorIcon": "icons/components/db-snapshot/icons/color/db-snapshot-color.svg",
-"whiteIcon": "icons/components/db-snapshot/icons/white/db-snapshot-white.svg",
-"description": "",
-},
-{
-"name": "db-cluster-snapshot",
-"colorIcon": "icons/components/db-cluster-snapshot/icons/color/db-cluster-snapshot-color.svg",
-"whiteIcon": "icons/components/db-cluster-snapshot/icons/white/db-cluster-snapshot-white.svg",
-"description": "",
-},
-{
-"name": "db-cluster-snapshot",
-"colorIcon": "icons/components/db-cluster-snapshot/icons/color/db-cluster-snapshot-color.svg",
-"whiteIcon": "icons/components/db-cluster-snapshot/icons/white/db-cluster-snapshot-white.svg",
-"description": "",
-}]
-featureList: [
- "Amazon RDS integrates with AWS Config to support compliance and enhance security by recording and auditing changes to the configuration of your DB instance",
- "Amazon Aurora supports quick, efficient cloning operations, where entire multi-terabyte database clusters can be cloned in minutes.",
- "Amazon RDS provides Amazon CloudWatch metrics for your database instances at no additional charge."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon Relational Database Service (Amazon RDS) is a collection of managed services that makes it simple to set up, operate, and scale databases in the cloud.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Relational Database Service
+subtitle: Collaborative and visual infrastructure as design for AWS Relational Database Service
+integrationIcon: icons/color/aws-rds-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-rds-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-rds-controller
+description:
+category: App Definition and Development
+subcategory: Database
+registrant: GitHub
+components:
+ - name: db-cluster
+ colorIcon: icons/components/db-cluster/icons/color/db-cluster-color.svg
+ whiteIcon: icons/components/db-cluster/icons/white/db-cluster-white.svg
+ description: ""
+
+ - name: db-cluster-parameter-group
+ colorIcon: icons/components/db-cluster-parameter-group/icons/color/db-cluster-parameter-group-color.svg
+ whiteIcon: icons/components/db-cluster-parameter-group/icons/white/db-cluster-parameter-group-white.svg
+ description: ""
+
+ - name: db-instance
+ colorIcon: icons/components/db-instance/icons/color/db-instance-color.svg
+ whiteIcon: icons/components/db-instance/icons/white/db-instance-white.svg
+ description: ""
+
+ - name: db-parameter-group
+ colorIcon: icons/components/db-parameter-group/icons/color/db-parameter-group-color.svg
+ whiteIcon: icons/components/db-parameter-group/icons/white/db-parameter-group-white.svg
+ description: ""
+
+ - name: db-proxy
+ colorIcon: icons/components/db-proxy/icons/color/db-proxy-color.svg
+ whiteIcon: icons/components/db-proxy/icons/white/db-proxy-white.svg
+ description: ""
+
+ - name: db-subnet-group
+ colorIcon: icons/components/db-subnet-group/icons/color/db-subnet-group-color.svg
+ whiteIcon: icons/components/db-subnet-group/icons/white/db-subnet-group-white.svg
+ description: ""
+
+ - name: global-cluster
+ colorIcon: icons/components/global-cluster/icons/color/global-cluster-color.svg
+ whiteIcon: icons/components/global-cluster/icons/white/global-cluster-white.svg
+ description: ""
+
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: db-snapshot
+ colorIcon: icons/components/db-snapshot/icons/color/db-snapshot-color.svg
+ whiteIcon: icons/components/db-snapshot/icons/white/db-snapshot-white.svg
+ description: ""
+
+ - name: db-cluster-snapshot
+ colorIcon: icons/components/db-cluster-snapshot/icons/color/db-cluster-snapshot-color.svg
+ whiteIcon: icons/components/db-cluster-snapshot/icons/white/db-cluster-snapshot-white.svg
+ description: ""
+
+featureList: [
+ "Amazon RDS integrates with AWS Config to support compliance and enhance security by recording and auditing changes to the configuration of your DB instance",
+ "Amazon Aurora supports quick, efficient cloning operations, where entire multi-terabyte database clusters can be cloned in minutes.",
+ "Amazon RDS provides Amazon CloudWatch metrics for your database instances at no additional charge."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon Relational Database Service (Amazon RDS) is a collection of managed services that makes it simple to set up, operate, and scale databases in the cloud.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-route53-controller/index.mdx b/src/collections/integrations/aws-route53-controller/index.mdx
index acca8aef2515..79897d7452b4 100644
--- a/src/collections/integrations/aws-route53-controller/index.mdx
+++ b/src/collections/integrations/aws-route53-controller/index.mdx
@@ -1,63 +1,58 @@
----
-title: AWS Route 53
-subtitle: Collaborative and visual infrastructure as design for AWS Route 53
-integrationIcon: icons/color/aws-route53-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-route53-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-route53-controller
-description:
-category: Cloud Native Network
-subcategory: Networking Content Delivery
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "hosted-zone",
-"colorIcon": "icons/components/hosted-zone/icons/color/hosted-zone-color.svg",
-"whiteIcon": "icons/components/hosted-zone/icons/white/hosted-zone-white.svg",
-"description": "",
-},
-{
-"name": "record-set",
-"colorIcon": "icons/components/record-set/icons/color/record-set-color.svg",
-"whiteIcon": "icons/components/record-set/icons/white/record-set-white.svg",
-"description": "",
-},
-{
-"name": "health-check",
-"colorIcon": "icons/components/health-check/icons/color/health-check-color.svg",
-"whiteIcon": "icons/components/health-check/icons/white/health-check-white.svg",
-"description": "",
-}]
-featureList: [
- "Route end users to your site reliably with globally-dispersed Domain Name System (DNS) servers and automatic scaling.",
- "Set up your DNS routing in minutes with domain name registration and straightforward visual traffic flow tools.",
- "Customize your DNS routing policies to reduce latency, improve application availability, and maintain compliance."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. Route 53 connects user requests to internet applications running on AWS or on-premises.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Route 53
+subtitle: Collaborative and visual infrastructure as design for AWS Route 53
+integrationIcon: icons/color/aws-route53-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-route53-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-route53-controller
+description:
+category: Cloud Native Network
+subcategory: Networking Content Delivery
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: hosted-zone
+ colorIcon: icons/components/hosted-zone/icons/color/hosted-zone-color.svg
+ whiteIcon: icons/components/hosted-zone/icons/white/hosted-zone-white.svg
+ description: ""
+
+ - name: record-set
+ colorIcon: icons/components/record-set/icons/color/record-set-color.svg
+ whiteIcon: icons/components/record-set/icons/white/record-set-white.svg
+ description: ""
+
+ - name: health-check
+ colorIcon: icons/components/health-check/icons/color/health-check-color.svg
+ whiteIcon: icons/components/health-check/icons/white/health-check-white.svg
+ description: ""
+
+featureList: [
+ "Route end users to your site reliably with globally-dispersed Domain Name System (DNS) servers and automatic scaling.",
+ "Set up your DNS routing in minutes with domain name registration and straightforward visual traffic flow tools.",
+ "Customize your DNS routing policies to reduce latency, improve application availability, and maintain compliance."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. Route 53 connects user requests to internet applications running on AWS or on-premises.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-route53resolver-controller/index.mdx b/src/collections/integrations/aws-route53resolver-controller/index.mdx
index 397686dfc848..9c3744e715c9 100644
--- a/src/collections/integrations/aws-route53resolver-controller/index.mdx
+++ b/src/collections/integrations/aws-route53resolver-controller/index.mdx
@@ -1,60 +1,56 @@
----
-title: AWS Route 53 Resolver
-subtitle: Collaborative and visual infrastructure as design for AWS Route 53 Resolver
-integrationIcon: icons/color/aws-route53resolver-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-route53resolver-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-route53resolver-controller
-description:
-category: Cloud Native Network
-subcategory: Networking Content Delivery
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "resolver-endpoint",
-"colorIcon": "icons/components/resolver-endpoint/icons/color/resolver-endpoint-color.svg",
-"whiteIcon": "icons/components/resolver-endpoint/icons/white/resolver-endpoint-white.svg",
-"description": "",
-},
-{
-"name": "resolver-rule",
-"colorIcon": "icons/components/resolver-rule/icons/color/resolver-rule-color.svg",
-"whiteIcon": "icons/components/resolver-rule/icons/white/resolver-rule-white.svg",
-"description": "",
-}]
-featureList: [
- "Local VPC domain names for EC2 instances (for example, ec2-192-0-2-44.compute-1.amazonaws.com).
-",
- "Records in private hosted zones (for example, acme.example.com).
-",
- "For public domain names, Route 53 Resolver performs recursive lookups against public name servers on the internet.
-"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Route 53 Resolver
+subtitle: Collaborative and visual infrastructure as design for AWS Route 53 Resolver
+integrationIcon: icons/color/aws-route53resolver-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-route53resolver-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-route53resolver-controller
+description:
+category: Cloud Native Network
+subcategory: Networking Content Delivery
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: resolver-endpoint
+ colorIcon: icons/components/resolver-endpoint/icons/color/resolver-endpoint-color.svg
+ whiteIcon: icons/components/resolver-endpoint/icons/white/resolver-endpoint-white.svg
+ description: ""
+
+ - name: resolver-rule
+ colorIcon: icons/components/resolver-rule/icons/color/resolver-rule-color.svg
+ whiteIcon: icons/components/resolver-rule/icons/white/resolver-rule-white.svg
+ description: ""
+
+featureList: [
+ "Local VPC domain names for EC2 instances (for example, ec2-192-0-2-44.compute-1.amazonaws.com).
+",
+ "Records in private hosted zones (for example, acme.example.com).
+",
+ "For public domain names, Route 53 Resolver performs recursive lookups against public name servers on the internet.
+"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-s3-controller/index.mdx b/src/collections/integrations/aws-s3-controller/index.mdx
index 3e1f8ca86bbb..cb0da110e21d 100644
--- a/src/collections/integrations/aws-s3-controller/index.mdx
+++ b/src/collections/integrations/aws-s3-controller/index.mdx
@@ -1,51 +1,48 @@
----
-title: AWS Simple Storage Service (S3)
-subtitle: Collaborative and visual infrastructure as design for AWS Simple Storage Service (S3)
-integrationIcon: icons/color/aws-s3-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-s3-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-s3-controller
-description:
-category: Cloud Native Storage
-subcategory: Storage
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "bucket",
-"colorIcon": "icons/components/bucket/icons/color/bucket-color.svg",
-"whiteIcon": "icons/components/bucket/icons/white/bucket-white.svg",
-"description": "",
-}]
-featureList: [
- "Stores and retrieves any amount of data",
- "Highly scalable and durable",
- "Integrates with various AWS services"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Integrates S3 storage"
-howItWorksDetails: "Provides scalable and reliable storage for Kubernetes applications"
-published: TRUE
----
-
-Amazon Simple Storage Service (Amazon S3) is an object storage service offering industry-leading scalability, data availability, security, and performance.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Simple Storage Service (S3)
+subtitle: Collaborative and visual infrastructure as design for AWS Simple Storage Service (S3)
+integrationIcon: icons/color/aws-s3-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-s3-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-s3-controller
+description:
+category: Cloud Native Storage
+subcategory: Storage
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: bucket
+ colorIcon: icons/components/bucket/icons/color/bucket-color.svg
+ whiteIcon: icons/components/bucket/icons/white/bucket-white.svg
+ description: ""
+
+featureList: [
+ "Stores and retrieves any amount of data",
+ "Highly scalable and durable",
+ "Integrates with various AWS services"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Integrates S3 storage"
+howItWorksDetails: "Provides scalable and reliable storage for Kubernetes applications"
+published: TRUE
+---
+
+Amazon Simple Storage Service (Amazon S3) is an object storage service offering industry-leading scalability, data availability, security, and performance.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Amazon SageMaker is a fully managed service that brings together a broad set of tools to enable high-performance, low-cost machine learning (ML) for any use case.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Amazon SageMaker is a fully managed service that brings together a broad set of tools to enable high-performance, low-cost machine learning (ML) for any use case.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-secretsmanager-controller/index.mdx b/src/collections/integrations/aws-secretsmanager-controller/index.mdx
index caa175626ca6..e23821c60155 100644
--- a/src/collections/integrations/aws-secretsmanager-controller/index.mdx
+++ b/src/collections/integrations/aws-secretsmanager-controller/index.mdx
@@ -1,51 +1,48 @@
----
-title: AWS Secrets Manager
-subtitle: Collaborative and visual infrastructure as design for AWS Secrets Manager
-integrationIcon: icons/color/aws-secretsmanager-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-secretsmanager-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-secretsmanager-controller
-description:
-category: Security & Compliance
-subcategory: Security Identity Compliance
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "secret",
-"colorIcon": "icons/components/secret/icons/color/secret-color.svg",
-"whiteIcon": "icons/components/secret/icons/white/secret-white.svg",
-"description": "",
-}]
-featureList: [
- "Centrally store and manage credentials, API keys, and other secrets.",
- "Use AWS Identity and Access Management (IAM) permissions policies to manage access to your secrets.",
- "Rotate secrets on demand or on a schedule, without redeploying or disrupting active applications."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-AWS Secrets Manager helps you manage, retrieve, and rotate database credentials, API keys, and other secrets throughout their lifecycles.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Secrets Manager
+subtitle: Collaborative and visual infrastructure as design for AWS Secrets Manager
+integrationIcon: icons/color/aws-secretsmanager-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-secretsmanager-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-secretsmanager-controller
+description:
+category: Security & Compliance
+subcategory: Security Identity Compliance
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: secret
+ colorIcon: icons/components/secret/icons/color/secret-color.svg
+ whiteIcon: icons/components/secret/icons/white/secret-white.svg
+ description: ""
+
+featureList: [
+ "Centrally store and manage credentials, API keys, and other secrets.",
+ "Use AWS Identity and Access Management (IAM) permissions policies to manage access to your secrets.",
+ "Rotate secrets on demand or on a schedule, without redeploying or disrupting active applications."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+AWS Secrets Manager helps you manage, retrieve, and rotate database credentials, API keys, and other secrets throughout their lifecycles.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-sfn-controller/index.mdx b/src/collections/integrations/aws-sfn-controller/index.mdx
index 417f27ac76eb..02fde7e76673 100644
--- a/src/collections/integrations/aws-sfn-controller/index.mdx
+++ b/src/collections/integrations/aws-sfn-controller/index.mdx
@@ -1,57 +1,53 @@
----
-title: AWS Step Functions
-subtitle: Collaborative and visual infrastructure as design for AWS Step Functions
-integrationIcon: icons/color/aws-sfn-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-sfn-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-sfn-controller
-description:
-category: Serverless
-subcategory: Serverless
-registrant: GitHub
-components: [
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "activity",
-"colorIcon": "icons/components/activity/icons/color/activity-color.svg",
-"whiteIcon": "icons/components/activity/icons/white/activity-white.svg",
-"description": "",
-},
-{
-"name": "state-machine",
-"colorIcon": "icons/components/state-machine/icons/color/state-machine-color.svg",
-"whiteIcon": "icons/components/state-machine/icons/white/state-machine-white.svg",
-"description": "",
-}]
-featureList: [
- "Step Functions is based on state machines and tasks.",
- "Supports Catch and Retry statements",
- "Examine the state of each step in your workflow to make sure that your application runs in order and as expected"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-AWS Step Functions is a serverless orchestration service that lets you integrate with AWS Lambda functions and other AWS services to build business-critical applications.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Step Functions
+subtitle: Collaborative and visual infrastructure as design for AWS Step Functions
+integrationIcon: icons/color/aws-sfn-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-sfn-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-sfn-controller
+description:
+category: Serverless
+subcategory: Serverless
+registrant: GitHub
+components:
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: activity
+ colorIcon: icons/components/activity/icons/color/activity-color.svg
+ whiteIcon: icons/components/activity/icons/white/activity-white.svg
+ description: ""
+
+ - name: state-machine
+ colorIcon: icons/components/state-machine/icons/color/state-machine-color.svg
+ whiteIcon: icons/components/state-machine/icons/white/state-machine-white.svg
+ description: ""
+
+featureList: [
+ "Step Functions is based on state machines and tasks.",
+ "Supports Catch and Retry statements",
+ "Examine the state of each step in your workflow to make sure that your application runs in order and as expected"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+AWS Step Functions is a serverless orchestration service that lets you integrate with AWS Lambda functions and other AWS services to build business-critical applications.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-sns-controller/index.mdx b/src/collections/integrations/aws-sns-controller/index.mdx
index 51dca52f7a06..35feb0d8a4fe 100644
--- a/src/collections/integrations/aws-sns-controller/index.mdx
+++ b/src/collections/integrations/aws-sns-controller/index.mdx
@@ -1,69 +1,63 @@
----
-title: AWS Simple Notification Service
-subtitle: Collaborative and visual infrastructure as design for AWS Simple Notification Service
-integrationIcon: icons/color/aws-sns-controller-color.svg
-darkModeIntegrationIcon: icons/white/aws-sns-controller-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-sns-controller
-description:
-category: App Definition and Development
-subcategory: App Integration
-registrant: GitHub
-components: [
-{
-"name": "platform-endpoint",
-"colorIcon": "icons/components/platform-endpoint/icons/color/platform-endpoint-color.svg",
-"whiteIcon": "icons/components/platform-endpoint/icons/white/platform-endpoint-white.svg",
-"description": "",
-},
-{
-"name": "platform-application",
-"colorIcon": "icons/components/platform-application/icons/color/platform-application-color.svg",
-"whiteIcon": "icons/components/platform-application/icons/white/platform-application-white.svg",
-"description": "",
-},
-{
-"name": "field-export",
-"colorIcon": "icons/components/field-export/icons/color/field-export-color.svg",
-"whiteIcon": "icons/components/field-export/icons/white/field-export-white.svg",
-"description": "",
-},
-{
-"name": "adopted-resource",
-"colorIcon": "icons/components/adopted-resource/icons/color/adopted-resource-color.svg",
-"whiteIcon": "icons/components/adopted-resource/icons/white/adopted-resource-white.svg",
-"description": "",
-},
-{
-"name": "subscription",
-"colorIcon": "icons/components/subscription/icons/color/subscription-color.svg",
-"whiteIcon": "icons/components/subscription/icons/white/subscription-white.svg",
-"description": "",
-},
-{
-"name": "topic",
-"colorIcon": "icons/components/topic/icons/color/topic-color.svg",
-"whiteIcon": "icons/components/topic/icons/white/topic-white.svg",
-"description": "",
-}]
-featureList: [
- "Message fanout: Each account can support 100,000 Standard topics and each topic supports up to 12.5M subscriptions.",
- "Amazon SNS supports VPC Endpoints (VPCE) via AWS PrivateLink.",
- "Amazon SNS mobile notifications make it simple and cost effective to fan out mobile push notifications to iOS, Android, Fire, Windows, and Baidu devices."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Amazon Simple Notification Service (Amazon SNS) sends notifications two ways, A2A and A2P.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Simple Notification Service
+subtitle: Collaborative and visual infrastructure as design for AWS Simple Notification Service
+integrationIcon: icons/color/aws-sns-controller-color.svg
+darkModeIntegrationIcon: icons/white/aws-sns-controller-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-sns-controller
+description:
+category: App Definition and Development
+subcategory: App Integration
+registrant: GitHub
+components:
+ - name: platform-endpoint
+ colorIcon: icons/components/platform-endpoint/icons/color/platform-endpoint-color.svg
+ whiteIcon: icons/components/platform-endpoint/icons/white/platform-endpoint-white.svg
+ description: ""
+
+ - name: platform-application
+ colorIcon: icons/components/platform-application/icons/color/platform-application-color.svg
+ whiteIcon: icons/components/platform-application/icons/white/platform-application-white.svg
+ description: ""
+
+ - name: field-export
+ colorIcon: icons/components/field-export/icons/color/field-export-color.svg
+ whiteIcon: icons/components/field-export/icons/white/field-export-white.svg
+ description: ""
+
+ - name: adopted-resource
+ colorIcon: icons/components/adopted-resource/icons/color/adopted-resource-color.svg
+ whiteIcon: icons/components/adopted-resource/icons/white/adopted-resource-white.svg
+ description: ""
+
+ - name: subscription
+ colorIcon: icons/components/subscription/icons/color/subscription-color.svg
+ whiteIcon: icons/components/subscription/icons/white/subscription-white.svg
+ description: ""
+
+ - name: topic
+ colorIcon: icons/components/topic/icons/color/topic-color.svg
+ whiteIcon: icons/components/topic/icons/white/topic-white.svg
+ description: ""
+
+featureList: [
+ "Message fanout: Each account can support 100,000 Standard topics and each topic supports up to 12.5M subscriptions.",
+ "Amazon SNS supports VPC Endpoints (VPCE) via AWS PrivateLink.",
+ "Amazon SNS mobile notifications make it simple and cost effective to fan out mobile push notifications to iOS, Android, Fire, Windows, and Baidu devices."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.png,
+ ../_images/kanvas-designer.png
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Amazon Simple Notification Service (Amazon SNS) sends notifications two ways, A2A and A2P.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-target-group-binding/index.mdx b/src/collections/integrations/aws-target-group-binding/index.mdx
index dd8d0b5873a2..b2d8bc46b95b 100644
--- a/src/collections/integrations/aws-target-group-binding/index.mdx
+++ b/src/collections/integrations/aws-target-group-binding/index.mdx
@@ -1,39 +1,38 @@
----
-title: AWS Target Group Binding
-subtitle: Collaborative and visual infrastructure as design for AWS Target Group Binding
-integrationIcon: icons/color/aws-target-group-binding-color.svg
-darkModeIntegrationIcon: icons/white/aws-target-group-binding-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-target-group-binding
-description:
-category: Cloud Native Network
-subcategory: Service Proxy
-registrant: Artifact Hub
-components: [
-{
-"name": "target-group-binding",
-"colorIcon": "icons/components/target-group-binding/icons/color/target-group-binding-color.svg",
-"whiteIcon": "icons/components/target-group-binding/icons/white/target-group-binding-white.svg",
-"description": "",
-}]
-featureList: [
- "Expose your pods using an existing ALB TargetGroup or NLB TargetGroup.",
- "Allows you to provision the load balancer infrastructure completely outside of Kubernetes.",
- "Used by AWS LoadBalancer controller internally to support the functionality for Ingress and Service resource as well."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Povision a TargetGroupBinding resource that can be combined with an externally provisioned AWS Loadbalancer to provide an ingress route into the defined kubernetes service.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS Target Group Binding
+subtitle: Collaborative and visual infrastructure as design for AWS Target Group Binding
+integrationIcon: icons/color/aws-target-group-binding-color.svg
+darkModeIntegrationIcon: icons/white/aws-target-group-binding-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-target-group-binding
+description:
+category: Cloud Native Network
+subcategory: Service Proxy
+registrant: Artifact Hub
+components:
+ - name: target-group-binding
+ colorIcon: icons/components/target-group-binding/icons/color/target-group-binding-color.svg
+ whiteIcon: icons/components/target-group-binding/icons/white/target-group-binding-white.svg
+ description: ""
+
+featureList: [
+ "Expose your pods using an existing ALB TargetGroup or NLB TargetGroup.",
+ "Allows you to provision the load balancer infrastructure completely outside of Kubernetes.",
+ "Used by AWS LoadBalancer controller internally to support the functionality for Ingress and Service resource as well."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Povision a TargetGroupBinding resource that can be combined with an externally provisioned AWS Loadbalancer to provide an ingress route into the defined kubernetes service.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/aws-vpc-cni/index.mdx b/src/collections/integrations/aws-vpc-cni/index.mdx
index 932b8c78c0c2..4ef00d4a1cd1 100644
--- a/src/collections/integrations/aws-vpc-cni/index.mdx
+++ b/src/collections/integrations/aws-vpc-cni/index.mdx
@@ -1,46 +1,43 @@
----
-title: AWS VPC CNI
-subtitle: Collaborative and visual infrastructure as code for AWS VPC CNI
-integrationIcon: icons/color/aws-vpc-cni-color.svg
-darkModeIntegrationIcon: icons/white/aws-vpc-cni-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/aws-vpc-cni
-description:
-category: Cloud Native Network
-subcategory: Cloud Native Network
-registrant: Artifact Hub
-components: [
-{
-"name": "eni-config",
-"colorIcon": "icons/components/eni-config/icons/color/eni-config-color.svg",
-"whiteIcon": "icons/components/eni-config/icons/white/eni-config-white.svg",
-"description": "",
-},
-{
-"name": "policy-endpoint",
-"colorIcon": "icons/components/policy-endpoint/icons/color/policy-endpoint-color.svg",
-"whiteIcon": "icons/components/policy-endpoint/icons/white/policy-endpoint-white.svg",
-"description": "",
-}]
-featureList: [
- "Keep revision history and audit trail of all configuration changes",
- "Use MeshMap‘s visual designer to explore your App Mesh configuration",
- "Deploy Meshery on your EKS clusters for App Mesh management"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Networking plugin for pod networking in Kubernetes using Elastic Network Interfaces on AWS.
-
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWS VPC CNI
+subtitle: Collaborative and visual infrastructure as code for AWS VPC CNI
+integrationIcon: icons/color/aws-vpc-cni-color.svg
+darkModeIntegrationIcon: icons/white/aws-vpc-cni-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/aws-vpc-cni
+description:
+category: Cloud Native Network
+subcategory: Cloud Native Network
+registrant: Artifact Hub
+components:
+ - name: eni-config
+ colorIcon: icons/components/eni-config/icons/color/eni-config-color.svg
+ whiteIcon: icons/components/eni-config/icons/white/eni-config-white.svg
+ description: ""
+ - name: policy-endpoint
+ colorIcon: icons/components/policy-endpoint/icons/color/policy-endpoint-color.svg
+ whiteIcon: icons/components/policy-endpoint/icons/white/policy-endpoint-white.svg
+ description: ""
+
+featureList: [
+ "Keep revision history and audit trail of all configuration changes",
+ "Use MeshMap‘s visual designer to explore your App Mesh configuration",
+ "Deploy Meshery on your EKS clusters for App Mesh management"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Networking plugin for pod networking in Kubernetes using Elastic Network Interfaces on AWS.
+
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
\ No newline at end of file
diff --git a/src/collections/integrations/awx-operator/index.mdx b/src/collections/integrations/awx-operator/index.mdx
index f18a7e4b9434..857f5d08fc56 100644
--- a/src/collections/integrations/awx-operator/index.mdx
+++ b/src/collections/integrations/awx-operator/index.mdx
@@ -1,58 +1,51 @@
----
-title: AWX Operator
-subtitle: Collaborative and visual infrastructure as design for AWX Operator
-integrationIcon: icons/color/awx-operator-color.svg
-darkModeIntegrationIcon: icons/white/awx-operator-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/awx-operator
-description:
-category: Orchestration & Management
-subcategory: Automation & Configuration
-registrant: Artifact Hub
-components: [
-{
-"name": "awx-backup",
-"colorIcon": "icons/components/awx-backup/icons/color/awx-backup-color.svg",
-"whiteIcon": "icons/components/awx-backup/icons/white/awx-backup-white.svg",
-"description": "",
-},
-{
-"name": "awx-restore",
-"colorIcon": "icons/components/awx-restore/icons/color/awx-restore-color.svg",
-"whiteIcon": "icons/components/awx-restore/icons/white/awx-restore-white.svg",
-"description": "",
-},
-{
-"name": "awx",
-"colorIcon": "icons/components/awx/icons/color/awx-color.svg",
-"whiteIcon": "icons/components/awx/icons/white/awx-white.svg",
-"description": "",
-},
-{
-"name": "awx-mesh-ingress",
-"colorIcon": "icons/components/awx-mesh-ingress/icons/color/awx-mesh-ingress-color.svg",
-"whiteIcon": "icons/components/awx-mesh-ingress/icons/white/awx-mesh-ingress-white.svg",
-"description": "",
-}]
-featureList: [
- "Keep revision history and audit trail of all configuration changes",
- "Use MeshMap‘s visual designer to explore your App Mesh configuration",
- "Deploy Meshery on your EKS clusters for App Mesh management"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible.
-
-
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: AWX Operator
+subtitle: Collaborative and visual infrastructure as design for AWX Operator
+integrationIcon: icons/color/awx-operator-color.svg
+darkModeIntegrationIcon: icons/white/awx-operator-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/awx-operator
+description:
+category: Orchestration & Management
+subcategory: Automation & Configuration
+registrant: Artifact Hub
+components:
+ - name: awx-backup
+ colorIcon: icons/components/awx-backup/icons/color/awx-backup-color.svg
+ whiteIcon: icons/components/awx-backup/icons/white/awx-backup-white.svg
+ description: ""
+ - name: awx-restore
+ colorIcon: icons/components/awx-restore/icons/color/awx-restore-color.svg
+ whiteIcon: icons/components/awx-restore/icons/white/awx-restore-white.svg
+ description: ""
+ - name: awx
+ colorIcon: icons/components/awx/icons/color/awx-color.svg
+ whiteIcon: icons/components/awx/icons/white/awx-white.svg
+ description: ""
+ - name: awx-mesh-ingress
+ colorIcon: icons/components/awx-mesh-ingress/icons/color/awx-mesh-ingress-color.svg
+ whiteIcon: icons/components/awx-mesh-ingress/icons/white/awx-mesh-ingress-white.svg
+ description: ""
+
+featureList: [
+ "Keep revision history and audit trail of all configuration changes",
+ "Use MeshMap‘s visual designer to explore your App Mesh configuration",
+ "Deploy Meshery on your EKS clusters for App Mesh management"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible.
+
+
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
-Azure Orkestra is a Kubernetes-based platform for orchestrating hybrid and multi-cloud deployments.
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+Azure Orkestra is a Kubernetes-based platform for orchestrating hybrid and multi-cloud deployments.
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/backstage/index.mdx b/src/collections/integrations/backstage/index.mdx
index ae81dca4d9e5..b8ca4f24ec21 100644
--- a/src/collections/integrations/backstage/index.mdx
+++ b/src/collections/integrations/backstage/index.mdx
@@ -1,33 +1,33 @@
----
-title: Backstage
-subtitle: Collaborative and visual infrastructure as design for Backstage
-integrationIcon: icons/color/backstage-color.svg
-darkModeIntegrationIcon: icons/white/backstage-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/backstage
-description:
-category: App Definition and Development
-subcategory: Application Definition & Image Build
-registrant: Artifact Hub
-components: []
-featureList: [
- "Restore order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly — without compromising autonomy.",
- "Unifies all your infrastructure tooling, services, and documentation to create a streamlined development environment from end to end.",
- "Easily create, maintain, find, and use technical documentation, using a docs like code approach"
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
-Backstage is an open platform for building developer portals
-
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: Backstage
+subtitle: Collaborative and visual infrastructure as design for Backstage
+integrationIcon: icons/color/backstage-color.svg
+darkModeIntegrationIcon: icons/white/backstage-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/backstage
+description:
+category: App Definition and Development
+subcategory: Application Definition & Image Build
+registrant: Artifact Hub
+components: []
+featureList: [
+ "Restore order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly — without compromising autonomy.",
+ "Unifies all your infrastructure tooling, services, and documentation to create a streamlined development environment from end to end.",
+ "Easily create, maintain, find, and use technical documentation, using a docs like code approach"
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+Backstage is an open platform for building developer portals
+
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
diff --git a/src/collections/integrations/bfe/index.mdx b/src/collections/integrations/bfe/index.mdx
index 90c3060c0418..ec2a09d3921b 100644
--- a/src/collections/integrations/bfe/index.mdx
+++ b/src/collections/integrations/bfe/index.mdx
@@ -1,33 +1,33 @@
----
-title: BFE
-subtitle: Collaborative and visual infrastructure as design for BFE
-integrationIcon: icons/color/bfe-color.svg
-darkModeIntegrationIcon: icons/white/bfe-white.svg
-docURL: https://docs.meshery.io/extensibility/integrations/bfe
-description:
-category: Cloud Native Network
-subcategory: Service Proxy
-registrant: Artifact Hub
-components: []
-featureList: [
- "BFE has a builtin plugin framework that makes it possible to develop new features rapidly by writing plugins.",
- "BFE is designed to provide every tenant a dedicated share of the instance. Each tenant&ldquos configuration is isolated and remains invisible to other tenants",
- "BFE provides an advanced domain-specific language to describe routing rules which are easy to understand and maintain."
-]
-workingSlides: [
- ../_images/kanvas-visualizer.png,
- ../_images/kanvas-designer.png
-]
-howItWorks: "Collaborative Infrastructure as Design"
-howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
-published: TRUE
----
-
- Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
-
-
- Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
-
+---
+title: BFE
+subtitle: Collaborative and visual infrastructure as design for BFE
+integrationIcon: icons/color/bfe-color.svg
+darkModeIntegrationIcon: icons/white/bfe-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/bfe
+description:
+category: Cloud Native Network
+subcategory: Service Proxy
+registrant: Artifact Hub
+components: []
+featureList: [
+ "BFE has a builtin plugin framework that makes it possible to develop new features rapidly by writing plugins.",
+ "BFE is designed to provide every tenant a dedicated share of the instance. Each tenant&ldquos configuration is isolated and remains invisible to other tenants",
+ "BFE provides an advanced domain-specific language to describe routing rules which are easy to understand and maintain."
+]
+workingSlides: [
+ ../_images/kanvas-visualizer.webp,
+ ../_images/kanvas-designer.webp
+]
+howItWorks: "Collaborative Infrastructure as Design"
+howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs."
+published: TRUE
+---
+
+ Collaboratively and visually diagram your cloud native infrastructure with GitOps-style pipeline integration. Design, test, and manage configuration your Kubernetes-based, containerized applications as a visual topology.
+
+
+ Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in MeshMap. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, MeshMap, to create and deploy your own cloud native infrastructure designs.
+
Join the Layer5 Community by submitting your [community member form](https://layer5.io/newcomer).
+---
+name: 🐛 Bug Report
+about: Report an issue to help us improve
+title: ""
+labels: "kind/bug"
+assignees: ""
+---
+
+### Description
+
+
+
+### Expected Behavior
+
+
+
+### Screenshots
+
+
+
+### Environment:
+
+- Host OS:
+- Browser:
+
+---
+
+
Community
-- 
Docker Extension
-- 
Docs
-- 
Meshery Catalog
-- 
Kanvas
-- 
Landscape
-- 
ImageHub
-- 
Meshery
-- 
Meshery Operator
-- 
SMP
-- 
Nighthawk
-- 
Patterns
-- 
UI/UX Design
-- 
Writer Program
-
-## Updating the Service Mesh Landscape
-
-Another common site update includes the updation of the Service Mesh Landscape. The service mesh landscape is powered by Gatsby.js. To update the landscape, fork this repository, clone it, create a branch and navigate to the **src/collections/landscape** folder.
-
-Make sure to open a [new issue](https://github.com/layer5io/layer5/issues/new?assignees=&labels=area%2Flandscape&template=landscape.md&title=%5BLandscape%5D) first. Following is a list of files that you may edit and make the necessary updates (if appropriate):
-
-- [non-functional.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/non-functional.js) - overview of various service meshes
-- [meshes.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/meshes.js) - list of individual service mesh details
-- [proxies.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/proxies.js) - list of individual modern proxies
-- [gateway.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/gateways.js) - list of API gateways
-- [load-balancer.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/load-balancer.js) - list of load balancers
-
-Entries should be listed in alphabetical order. Data provided to the `smi.js` is dynamic and based upon results from conformance tests run using Meshery.
-
-To update the Service Mesh Timeline, add the new service mesh in the [non-functional.js](https://github.com/layer5io/layer5/blob/master/src/collections/landscape/non-functional.js) file. Add an `announce-date` key for the service mesh, then add a `timeline-order` key having a value 1+`maximum value of timeline-order` till now, to list the service mesh in the timeline correctly.
-
-# How to Contribute
-
-## Prerequisites
-
-Make sure you have the following prerequisites installed on your operating system before you start contributing:
-
-- [Nodejs and npm](https://nodejs.org/en/)
-
- To verify run:
-
- ```
- node -v
- ```
-
- ```
- npm -v
- ```
-
-- [Gatsby.js](https://www.gatsbyjs.com/)
-
- To verify run:
-
- ```
- gatsby --version
- ```
-
-**Note:** If you're on a _Windows environment_ then it is highly recommended that you install [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/install) both for performance and ease of use. Refer to the [documentation](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/gatsby-on-wsl) for the installation of _Gatsby.js on WSL_.
-
-## Set up your Local Development Environment
-
-Follow the following instructions to start contributing.
-
-**1.** Fork [this](https://github.com/layer5io/layer5) repository.
-
-**2.** Clone your forked copy of the project.
-
-```
-git clone --depth=1 https://github.com/
-
-## FYI regarding the dev environment
-
-### Dev and Browser Warnings You May Encounter
-
-Note:
-
-- These are **non-blocking warnings** you can expect to see in your terminal or browser while working in local development environment.
-- They do not impact the performance of the code and are unrelated to your contributions.
-- These will not show in `build` or `production` mode.
-- These are being documented to minimize confusion for the user while doing development.
-
----
-
-> warn ./node_modules/react-accessible-accordion/dist/es/index.js
-> Attempted import error: 'useId' is not exported from 'react' (imported as 'useId').
-
-and
-
-> client.js:196 export 'useId' (imported as 'useId') was not found in 'react' (possible exports: Children, Component, Fragment, Profiler, PureComponent, StrictMode, Suspense, \_\_SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED, cloneElement, createContext, createElement, createFactory, createRef, forwardRef, isValidElement, lazy, memo, useCallback, useContext, useDebugValue, useEffect, useImperativeHandle, useLayoutEffect, useMemo, useReducer, useRef, useState, version)
-
-Where/When:
-
-- In terminal: after `npm start`
-- In browser: loading https://layer5.io
-
-Reason: [https://github.com/springload/react-accessible-accordion/issues/351](https://github.com/springload/react-accessible-accordion/issues/351)
-
-> V5 is a release we cut explicitly for React 18 support (Hence the major upgrade, this was a breaking change, the webpack fix would not work as we are using React 18 new APIs), we are sticking with V4 for React 17 and under compatibility, using V4 has no functional difference outside of React version compatibility.
-
-Layer5 currently using:
-"react-accessible-accordion": "^5.0.0"
-react": "^17.0.2"
-
-To clear the warning:
-Upgrade the `react`package to ^18. However upgrading may introduce too many breaking changes and complexity.
-
----
-
-> Warning: Each child in a list should have a unique "key" prop.
-> Check the top-level render call using . See https://reactjs.org/link/warning-keys for more information.
-> at title
-
-Where/When:
-
-- In terminal: after `npm start` and loading page
-
-Reason: In this version of Gatsby (4.20), the file:
-`node_modules/gatsby/cache-dir/head/head-export-handler-for-ssr.js` is missing code to assign `key` prop to each head tag included in the `SEO` component.
-
-To clear the warning:
-This could be resolved by adding code to the package, but requires too much complexity to include for each user. This warning is cleared in later versions of Gatsby.
+# Contributing at Layer5
+
+We are beyond excited to see that you want to contribute! We would love to accept your contributions. Layer5 is built by the community and warmly welcomes collaboration. There are many ways in which one could contribute to Layer5 and every contribution is equally appreciated here. Navigate through the following to understand more about contributing here.
+
+- [Before You Get Started](#before-you-get-started)
+- [Contributing to Layer5 Projects](#contributing-to-layer5-projects)
+- [Contributing to Layer5's Blogs](#contributing-to-layer5s-blogs)
+- [Contributing to Layer5's Sistent](#contributing-to-layer5s-sistent)
+- [How to Contribute](#how-to-contribute)
+ - [Prerequisites](#prerequisites)
+ - [Set up your Local Development Environment](#set-up-your-local-development-environment)
+ - [Signing-off on Commits](#signing-off-on-commits)
+
+⚠️ Cloning this repository ⚠️
+
+Cloning the repo with all its history results in a ~6 GB download. To contribute to this site, you don't need its entire history. Use the `--depth=1` flag to significantly reduce the footprint this repo creates in your environment.
+
+```bash
+git clone --depth=1 https://github.com/layer5io/layer5.git
+```
+
+# Before You Get Started
+
+## Code of Conduct
+
+Layer5 follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting community@layer5.io.
+Violation of the code of conduct is taken seriously, kindly report any violations of the Code of Conduct by filling in the Incident report.
+The comfort and safety of Layer5 community members are our priority. Please do well to adhere to the Code of Conduct to participate in the Layer5 community.
+
+## For Newcomers
+
+To help you get started on contributing to Layer5 projects, refer to the [Layer5 Newcomers Guide](https://layer5.io/community/newcomers), which aims to make contributions easier for new folks like you! See the resources and tutorials to help you get started. Along with this we have an extensive handbook on how this community works , how folks inside the community wear different hats to run it and few of its guidelines, have a look inside the [Community Handbook](https://layer5.io/community/handbook).
+
+## Issues & Pull Requests
+
+### Creating an Issue
+
+Before **creating** an Issue i.e for `features`/`bugs`/`improvements` please follow these steps:
+
+
+1. Search existing Issues before creating a new Issue (look to see if the Issue has already been created).
+1. If it doesn't exist create a new Issue giving as much context as possible (please take note and select the correct Issue type, for example `bug`, `documentation` or `feature`.
+1. If you wish to work on the Issue once it has been triaged, please include this in your Issue description.
+
+### Working on an Issue
+
+Before working on an existing Issue please follow these steps:
+
+1. Comment asking for the Issue to be assigned to you.
+1. To best position yourself for Issues assignment, we recommend that you:
+ 1. Confirm that you have read the CONTRIBUTING.md.
+ 1. Have a functional development environment (have built and are able to run the project).
+ 1. Convey your intended approach to solving the issue.
+ 1. Put each of these items in writing in one or more comments.
+1. After the Issue is assigned to you, you can start working on it.
+1. In general, **only** start working on this Issue (and open a Pull Request) when it has been assigned to you. Doing so will prevent confusion, duplicate work (some of which may go unaccepted given its duplicity), incidental stepping on toes, and the headache involved for maintainers and contributors alike as Issue assignments collide and heads bump together.
+1. Reference the Issue in your Pull Request (for example `This PR fixes #123`). so that the corresponding Issue is automatically closed upon merge of your Pull Request.
+
+> Notes:
+>
+> - Check the `Assignees` box at the top of the page to see if the Issue has been assigned to someone else before requesting this be assigned to you. If the issue has a current Assignee, but appears to be inactive, politely inquire with the current Assignee as to whether they are still working on a solution and/or if you might collaborate with them.
+> - Only request to be assigned an Issue if you know how to work on it.
+> - If an Issue is unclear, ask questions to get more clarity before asking to have the Issue assigned to you; avoid asking "what do I do next? how do I fix this?" (see the item above this line)
+> - An Issue can be assigned to multiple people, if you all agree to collaborate on the Issue (the Pull Request can contain commits from different collaborators)
+> - Any Issues that has no activity after 2 weeks will be unassigned and re-assigned to someone else.
+
+## Reviewing Pull Requests
+
+We welcome everyone to review Pull Requests. It is a great way to learn, network, and support each other.
+
+### DOs
+
+- Use inline comments to explain your suggestions
+- Use inline suggestions to propose changes
+- Exercise patience and empathy while offering critiques of the works of others.
+
+### DON'Ts
+
+- Do not repeat feedback, this creates more noise than value (check the existing conversation), use GitHub reactions if you agree/disagree with a comment
+- Do not blindly approve Pull Requests to improve your GitHub contributors graph
+
+
+## Style Guide
+
+The Layer5 website is hosted in this repository and is built using Gatsbyjs. Before opening a Pull Request, please review the [design doc](https://docs.google.com/document/d/1rvUZy2_S1a2_14BAQIg6b9cMhUuu04kYzkOPDPaPptI/edit#) to learn more about the structure of the website. Once a Pull Request has been submitted, a preview deployment will be built and made available to you and other contributors on your PR to review.
+
+## Discussion Forum
+
+Join the [discussion forum](https://discuss.layer5.io/c/landscape/7) (the Landscape topic is appropriate for all layer5.io questions) to discuss suggested new features, possible bugs, enhancement in user experience, and any other aspects of the site. The discussion forum is our preferred method of communication, you can, however, also inquire in the [#websites](https://layer5io.slack.com/archives/C015QJKUMPU) channel in the Layer5 Slack workspace.
+
+# Contributing to Layer5 Projects
+
+Please follow these steps and note these guidelines to begin contributing:
+
+1. First step is to set up the local development environment.
+1. Bug fixes are always welcome. Start by reviewing the [list of bugs](https://github.com/layer5io/layer5/labels/kind%2Fbug).
+1. A good way to easily start contributing is to pick and work on a [good first issue](https://github.com/layer5io/layer5/labels/good%20first%20issue). We try to make these Issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the Issue.
+1. We regularly discuss new Issues to work on in our [discussion forum](https://discuss.layer5.io/c/landscape/7) and the [#websites](https://layer5io.slack.com/archives/C015QJKUMPU) channel. Feel free to join and discuss any Issue or any idea that you may have.
+
+# Contributing to Layer5's Blogs Section
+
+If you'd like to contribute a post to layer5.io/blog, please open an Issue and suggest a topic. If you don't have a topic, then hop into the [#blog-kitchen](https://layer5io.slack.com/archives/C0210TZRF88) channel, and we'll help you find one.
+
+## Things to keep in mind
+
+1. We use inbuilt components called Call to Action(CTAs), prominently in our MarkDown(.mdx) files. Check out our [guide to CTAs](https://github.com/layer5io/layer5/blob/master/src/components/Call-To-Actions/README.md).
+
+## Adding a Blog Post
+
+1. In order to contribute a blog post, fork this repository, clone it, create a new branch and navigate to the `src/collections/blog` directory.
+2. Create a copy of the [blog template](https://github.com/layer5io/layer5/tree/master/src/collections/blog/blog-template).
+3. Follow the instructions included in the blog template and name the new file after the title of the blog article.
+4. Entries will be listed in chronological order automatically.
+
+## Adding a Resource
+
+1. In order to contribute a resource, fork this repository, clone it, create a new branch and navigate to the `src/collections/resources` directory.
+2. Create a copy of the [resource template](https://github.com/layer5io/layer5/tree/master/src/collections/resources/resources-template).
+3. Follow the instructions included in the resource template and name the new file after the title of the resource.
+4. Please note that different types of resources like `article`,`tutorial`, `webinars` are organized into separate folders inside the `/resource` collection. Add your entries in the respective folders.
+5. To qualify any post as a resource, the field `resource: true` must be added. This applies for `/news`, `/blog`, `/events` as well.
+6. Each resource can be associated with 4 additional fields: `type`, `mesh`, `technology` and `product`. The current list of values can be found from these [options](https://github.com/layer5io/layer5/blob/master/src/sections/Resources/Resources-grid/options.js).
+
+## Adding News
+
+1. In order to add/update news items, fork this repository, clone it, create a new branch, and navigate to the `src/collections/news` directory.
+2. Create a copy of the [news template](https://github.com/layer5io/layer5/tree/master/src/collections/news/news-template/0000-00-00-news-title).
+3. Follow the instructions included in the news template and name the new file after the title of the news article.
+4. Entries will be listed in chronological order automatically.
+
+# Contributing to Layer5's Sistent
+
+If you'd like to contribute to Sistent, start by selecting the project/sistent label in the [#GitHub issue tracker](https://github.com/layer5io/layer5/labels/project%2Fsistent).
+
+### General Contribution Guidelines
+
+1. Select the [project/sistent](https://github.com/layer5io/layer5/labels/project%2Fsistent) label in the GitHub issue tracker.
+1. Navigate to the relevant directory, such as:
+ ```
+ src/sections/Projects/Sistent
+ ```
+ > Note: For other parts of the project, the file path may vary. Ensure you're working in the correct file associated with the area you're contributing to.
+1. Add or update content. The system dynamically generates pages and routes to maintain consistency.
+
+### Adding Sistent Component
+
+We've streamlined the process by introducing a dynamic page creation workflow, simplifying the addition of new pages and ensuring a consistent structure for all contributions.
+
+1. Navigate to the relevant directory, such as:
+ ```
+ src/sections/Projects/Sistent
+ ```
+1. To add a new page, simply update this `content.js` file with the necessary details. All content is managed in a centralized file:
+ ```
+ src/sections/Projects/Sistent/components/content.js
+ ```
+1. The system will dynamically generate pages based on this content and handle routing automatically.
+
+### Example
+Refer to the [**Button component**](https://layer5.io/projects/sistent/components/button) in the Sistent Library for an example of how to structure the content.
+
+# Common Types of Site Contributions
+
+The following list of instructions pertains to commonplace site updates by contributors.
+
+## Things to keep in mind
+
+1. Prioritize using only the theme colors and hexcodes that are already being used in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js) instead of introducing new color codes to the file.
+2. Avoid adding `rel="noreferrer"` attribute to internal links on the site. Use gatsby [`` component](https://www.gatsbyjs.com/docs/linking-between-pages/) for internal links on the site.
+
+## Adding dark mode for components
+
+The site currently has dark and light mode, the colors used in these two modes can be found in the dark and light theme objects in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js).
+
+These theme objects use a property whose value automatically changes based on the active theme without using a conditional.
+
+An example of a conditional:
+
+```
+theme === "dark" ? "white" : "black"
+```
+
+The preference is to **not use conditionals** for elements because they will flicker when reloading a page in dark mode.
+
+As currently constructed, the dark and light theme objects share similar property names that have different values.
+
+The property name will tell you how the value (color or hexcode) will change from dark mode to light mode. The first part is for dark mode, then "To", and the next part is for light mode.
+
+example #1: `whiteToBlack`
+
+"white" is the first part for dark mode
+"To"
+"Black" is the second part for light mode
+
+In dark mode the value of `whiteToBlack` will be `white`
+In light mode the value of `whiteToBlack` will be `black`
+
+example #2: `grey141414ToGreyF5F5F5`
+
+In dark mode this value will be `#141414` (a dark shade of grey)
+In light mode this value will be `#F5F5F5` (a light shade of grey).
+
+The hexcode in the property name is the indication of the color shade being used in the active theme. Always check the hexcode to confirm it is the desired shade/color.
+
+In a styled component, you can use the property name in the following way:
+
+#### Examples
+
+example #1:
+`color: ${props => props.theme.whiteToBlack};`
+
+example #2:
+`color: ${props => props.theme.greyDEE3DEToGreen3C494F}`
+
+### Adding a new color pair transition property
+
+It is recommended to use pre-existing styles, colors, hexcodes from the theme. Avoid adding your own CSS variables and incorporating new colors.
+
+If you must add a new property that changes with the theme:
+
+1. Add a new property with the same name to the dark and light theme objects in [themeStyles.js](https://github.com/layer5io/layer5/blob/master/src/theme/app/themeStyles.js) and the corresponding values you want them to have in each mode.
+
+#### Example:
+
+```
+const lighttheme = {
+ blue0000FFToRedFF0000: "#FF0000",
+```
+
+```
+const darktheme = {
+ blue0000FFToRedFF0000: "#0000FF",
+
+```
+
+2. Use that property name in your styled component
+
+```
+color: ${props => props.theme.blue0000FFToRedFF0000};
+```
+
+### Adding the transition property to the element in the styled component
+
+Transition property is not inherited. It must be added for each element that is changing colors and be consistent with the transition timing and style of the background color in [`GlobalStyle`](https://github.com/layer5io/layer5/blob/master/src/sections/app.style.js) to ensure uniform color change.
+
+Currently this property:value is
+
+```
+transition: 0.8s cubic-bezier(0.2, 0.8, 0.2, 1);
+```
+
+## Preferable SVG and Images
+
+- SVG or image does not need to change colors depending on the theme
+
+OR
+
+- SVG or image uses transparent sections that change with the background color to work with either theme.
+
+[Example of SVG file with transparent sections](https://github.com/layer5io/layer5/blob/master/src/assets/images/kanvas/icon-only/kanvas-icon-color.svg)
+
+[Example of image file with transparent sections](https://github.com/layer5io/layer5/blob/master/src/assets/images/app/projects/meshery-logo-light.webp)
+
+You can see these two examples in action [here](https://layer5.io/projects) by toggling the theme (located on the right side of the navigation bar).
+
+The above are the preferred kinds of SVG and images. If your SVG or image fits one of the descriptions above, then you do not need to read further.
+
+### Changing SVG according to theme
+
+SVG image formats are the preferred format because of the ability to control colors used to fill path or stroke with styled-components and have them change dependent on the theme without using a conditional.
+
+#### Importing SVG as a React Component
+
+To use the SVG as an `svg` element and not a source for an `img` element, we will import the SVG as a ReactComponent. You can see an example of importing the SVG as a ReactComponent in the code [here](https://github.com/layer5io/layer5/blob/master/src/sections/General/Navigation/index.js)
+
+```
+import { ReactComponent as Logo } from "../../../assets/images/app/layer5-colorMode.svg";
+```
+
+Then we include the component where you want to display it
+
+```
+
+ 
- 
- 
- 
- 
- 
- 
- 
- 
- 
{" "}
- Meshery
-
{" "}
- Meshery Operator
-
{" "}
- Patterns
-
{" "}
- Nighthawk
-
- Ekene Leonard Nwobodo +
-
- -### A Journey Never to forget - -My Layer5 journey began with this small issue. I gradually started learning more about the projects and made some impactful contributions. I started to engage in the community more prominently. With the help of these contributions, I learned new technologies and techniques. Contributing to the codebase gave me so much exposure to React.js, which would not have been possible if I had done it on my own. I took up issues that used React.js and started solving them, and in no time, I was comfortable with it. I am thankful that I didn’t wait for me to learn more about react and then start contributing. I have always applied this principle, learning more by doing actual stuff rather than sitting there and getting stuck in the tutorial loop. - -Another new technology I discovered was Jekyll, a static site generator. I was unfamiliar with this technology as well. I started contributing to issues involving Jekyll and slowly understood the basics and how the language works. I was very happy that I was able to make the [compatibility matrix](https://docs.meshery.io/project/compatibility-matrix), using Jekyll. Even my project for GSoC is written in Jekyll. So, going from not knowing what Jekyll is, to making some big changes, did make me happy. - -The community also helped me boost my confidence. The weekly meetings are responsible for this. The way the meetings required me to explain my fixes and give updates regarding the issues I was working on, helped me get vocal and comfortable with talking to various people. - -
- -I am excited to be accepted as a Google Summer of Code Intern for this Summer of 2022. I am looking forward to contributing more and making an impact here. The project assigned to me is to create a dashboard on SMP Website. Results from the [CNCF Cluster labs](https://github.com/layer5io/meshery-smp-action/actions) will be displayed here graphically. I wish to learn more about cloud native technologies and make contributions on the backend too. I also want to state that this will not be the end. I will be engaged with this community as long as I can and will try to give back as much as I can. - -### Appreciation for the Community - -Finally, I would like to thank the Layer5 Community for always being so supportive whenever I needed it. I took away a very significant lesson from this experience, there is always something to learn, and there is no harm in asking questions if you don't know the answer. It’s kinda hard to find such a welcoming community. There was not a day that I felt completely lost here, and that is what I adore about this community. - -Keep Meshing. Thank you. - -
When the operation involves a Kubernetes cluster(s), the kubeconfig(s) is sent as a parameter to the RPCs. It is then the job of the handling adapter to respect that and perform the operation across the passed clusters from kubeconfigs as needed. The operations not requiring a kubeconfig are managed through the same RPC, with the only difference being that the handling component would ignore the `kubeconfigs` field altogether making the system work not just for Kubernetes, but for other cloud native use cases. This approach of reusing the same RPC for different types of requests is pretty common and sometimes debatable with the other approach of being strict with the RPCs. This is what makes Meshery completely pluggable and extensible. - -## Using multi cluster with Meshery - -From a client's perspective, there are two uses of the multi context feature in general. While deploying a MeshMap design or performing any other operation on their cluster(s), selecting any number of Kubernetes contexts will allow them to uniformly and parallely perform the operation across the clusters. And while visualizing the state of their cluster(s), the same context switcher will allow them to filter across the clusters whose view they want to see. - -All cluster specific operations are now applied over a number of clusters uniformly. So if you have 10 clusters to manage and 8 of those start with the exact same set of pods, deployments, services, etc then Meshery can help you to apply these operations quickly and easily. - -It is as simple as selecting the specific cluster(s) from the Kubernetes context switcher in the navbar, and then applying whatever operation you wanted to, whether that be deploying a sample app, a Prometheus daemonset, or a MeshMap design. - -
-
-
-
-
- -Meshery also deploys Meshery operator across the cluster it’s about to manage. This operator manages the lifecycle of a Meshery broker and MeshSync. MeshSync pumps the blood into Meshery’s core, in other words, it is responsible for watching all different types of resources by establishing a watch stream over each of them. MeshSync then pumps that data into the NATS server, of which Meshery server itself is a client. From there, Meshery server gets all the relevant data related to activities in the cluster. - -By default, Meshery wants to be as much aware about your infrastructure as possible to provide value so it deploys its operator across each detected cluster. But you can fine tune this configuration by going over each one of them from the table as shown. - -
- -If you disconnect your cluster and do not want to persist the data from that cluster then you can perform a fine-grained deletion by deleting all MeshSync data (which are the Kubernetes objects) for that specific cluster. - -
-## Future of multi-cluster - -Meshery as an extension point to your infrastructure provides out-of-the-box value by adding components which can be Kubernetes specific, service mesh specific or custom components to add new functionality. We can now add multi-cluster specific components to provide more abstraction. This model can be used along with Meshery’s multi-mesh capabilities to give an overall multi-mesh multi-cluster experience to the user. For instance, your Istio service mesh spanning across multiple clusters can be abstracted and managed by Meshery using custom components such as VirtualGateway and VirtualDestinationRules. In this case, Meshery’s Istio adapter will handle the logic of converting a VirtualGateway into gateways across the clusters. This abstraction provides high value by powering the service mesh to span across the clusters while the Ops team can configure the mesh with minimal effort. - -Just like the example above, many such Meshery extension points are in Meshery to add logic into and add useful functionality. And as more of such extension points are added, Meshery will continue to give more and more power to your cloud native infrastructure. - -
- -Contributor statistics are tallied across all of the (currently nearly 30) repositories under the [Meshery GitHub organization](https://github.com/meshery). The most popular repository is meshery/meshery, however, there are many supporting components that live in sibling repositories, which receive active contribution. A contributor is an individual who made a review, comment, commit or created PR or issue in Meshery's code base. As of this blog post, over 500 code committers have contributed to Meshery. - - -
- - -Meshery is supported by the Layer5 community, which boasts an impressive 4,000 members. The Layer5 community stewards open source projects spanning 5 GitHub organizations and over 70 repositories, two of which are now within the Cloud Native Computing Foundation (CNCF). Meshery is one of Layer5's projects, and is highly extensible, enabling collaborative design and operation of cloud-native infrastructure. - -The Meshery platform provides a highly extensible self-service engineering platform, which makes it easy to manage and operate your cloud-native applications. It also enables you to collaborate with others, ensuring that your team can work together seamlessly to design, deploy, and operate cloud-native infrastructure. - -The Layer5 community is a warm, welcoming, and supportive community that has won many awards for its open-source contributions. We are proud to be a part of such a great community, and we encourage you to get involved and help us make Meshery even better! - -
-- -In conclusion, we would like to thank our amazing community of users and contributors for their dedication and support. It is thanks to you that Meshery has become such a popular and highly-regarded platform, and we look forward to continuing to work with you to make Meshery even better in the future. - +--- +title: Meshery Surpasses 1,000 Contributors +subtitle: and over 2,000 GitHub stars +date: 2023-04-12 08:00:00 -0530 +author: Layer5 Team +thumbnail: ./meshery-contrib-stats.webp +darkthumbnail: ./meshery-contrib-stats.webp +description: "Over 1,000 contributors to the Meshery cloud native management project." +type: Blog +category: Community +tags: + - Meshery + - Open Source +featured: true +published: true +--- + + + + +import MesheryStars from "./2000-github-stars.jpeg"; +import MesheryStats from "./meshery-contrib-stats.webp"; + +- -What makes the Layer5 community truly special, however, is not just its impressive technical achievements, but the warmth and welcoming atmosphere that it provides for its members. This is a community that is passionate about collaboration, inclusivity, and supporting each other to reach new heights. - - -Members of the Layer5 community come from all backgrounds and levels of experience, and everyone is encouraged to get involved, share their ideas, and contribute to the projects that they are interested in. The community is always open to new members, and there are plenty of resources available for those who are just starting out or looking to expand their skills. - -
-
-
- -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! 🎉🎈 - -Our users and contributors have always been celebrated at Layer5. Each participation milestone you achieve and every uplifting community interaction contributes to our shared mission of empowering engineers. - -Every aspect of what we do revolves around our users and contributors. We are thrilled to unveil our latest initiative that celebrates and rewards our invaluable users and contributors – Layer5 Badges! - -### What Are Layer5 Badges? - -These badges are a representation of your participation and milestones that you achieve together and in solidarity with the Layer5 community. Badges are how users demonstrate their prowess with the projects and how contributors identify their ownership, dedication, aand skills. There are several badges each representing a specific user achievement or contributor skill. - -Layer5 Badges are a tangible way for us to recognize and honor the exceptional efforts put forth by our contributors and the milestones achieved by our users. These badges are a symbol of your dedication, commitment, and passion for making a positive impact within the Layer5 community and projects. They serve as a testament to the hours spent using, coding, testing, documenting, and collaborating. - -Layer5 Badges are more than just virtual tokens; they represent the values we hold dear – openness, collaboration, and continuous improvement. Each badge is a unique recognition of the different roles and responsibilities you take on, reflecting your growth as a contributor and your journey within the Layer5 ecosystem. - -
- -### Why Are Badges Important? - -Contributors are the lifeblood of open-source projects, and Layer5 is no exception. Your contributions, large or small, shape the evolution of our projects, drive innovation, and foster a culture of shared learning. Layer5 Badges aims to acknowledge the diverse ways in which you contribute, ensuring that your dedication does not go unnoticed. - -Whether you're a power user, an experienced developer, a meticulous documenter, an outreach champion, or a supportive community member, there's a badge that reflects your unique contributions. These badges are our way of saying "thank you" for making Layer5 what it is – a thriving ecosystem of knowledge exchange and collaborative development. - - - **Recognition**: Badges provide tangible recognition for your hard work and commitment. They showcase your achievements and highlight the areas where you've made a positive impact. - - **Motivation**: Striving to earn badges can serve as a powerful motivator for every contributor. As you earn badges, you'll gain a sense of accomplishment, pushing you to set new goals and bring forth new ideas for the betterment of the Layer5 community. - - **Community Building**: Badges help foster a sense of belonging among contributors. They encourage collaboration, healthy competition, and the sharing of knowledge and experience. We recognize such individuals as [MeshMates](/community/meshmates). - - **Resume Boost**: Your Layer5 badges can help you stand out in your resume, LinkedIn profile, and other professional platforms. They serve as concrete evidence of your expertise and your dedication to open source hence helping your personal growth. - - **Social Media Showcase**: These badges can be shared on several social media platforms! Let your friends, family, colleagues, and your bosses know about your contributions, your journey, and your passion for cloud-native technology. - -### How Can I Earn Badges? -Earning Layer5 badges is both rewarding and straightforward. Each badge is tied to specific activities. For users, badges for activities such as using our projects, talking about the projects, sharing your successes and what you like about them. For contributors, badges include activities such as submitting code, assisting with documentation, participating in community events, and more. As you accumulate contributions in various areas, you'll begin to unlock badges that showcase your multifaceted involvement. - -These badges will be prominently displayed on your Layer5 community profile, visually representing your journey as a contributor. Not only does this serve as a source of personal pride, but it also helps others in the community recognize your expertise and dedication. - -
- -Earning Layer5 Badges is both exciting and achievable. As you continue to contribute to our projects, your accomplishments will be recognized with badges that reflect your dedication and expertise. Here are some ways you can earn Layer5 Badges: - -### How can I Share My Badge On My Profile - -
Design Pioneer 
Bring a Buddy 
- Sharing is Caring 
- Shipped 
- Need for Speed 
- Hip Hacker 
Log Streamer 
- GitOps with Friends 
- UI/UX 
- MeshMap 
- Service Mesh Performance 
- Community 
- Writer's Program 
- Meshery 
- Patterns 
- Landscape 
- Nighthawk 
- Meshery Catalog 
- Meshery Operator 
- Docker Extension 
Meshery Docs 
- MeshMaster 
- Coming Soon -
-
-
- -
- -### What skills do I need to get started? - -
- -
- -
- -
- -### Reflections on Personal and Professional Growth -
+In essence:
- -
- -
- -## Meshery: Leading in Open Source - -
- -## The Road Ahead: Inviting New Contributors - -
-
-
-
-
- -
- +--- +title: "Hacktoberfest Prep 2023: Extending Docker Desktop" +description: "Prepare for Hacktoberfest with Layer5 MeshMates and Maintainers. Join seasoned open source maintainers, hack through easy issues, and grow your skills. Discover Newcomers Resources and explore the Layer5 Community Handbook." +thumbnail: ./hacktoberfest2023.png +darkthumbnail: ./hacktoberfest2023.png +date: 2023-10-03 +eurl: /community/calendar +type: Event +speakers: ["Gaurav Chadha", "Pranav Singh", "Uzair Shaikh", "Yash Sharma", "Anita Ihuman", "Saurabh Soni", "Ritik Saxena", "Senali Dilumika", "Sudhanshu Dasgupta", "Rex Joshua Ibegbu"] +published: true +upcoming: false +register: false +--- + +import { Link } from "gatsby" ; +import { EventWrapper } from "../../Event.style.js"; + +import hacktoberfestprepslides from "./hacktoberfest-prep-easing-into-cncf-open-source-projects.pdf"; +import hacktoberfestBadge from "./hacktoberfest-contributor.png"; +import dockerExtension from "./docker-extension-meshery.svg"; +import manageWithMeshery from "./docker-extension-meshery.svg"; + +