Merge branch 'master' into error404p-redirect

Author: Vivek Vishal

.github/workflows/slack.yml

@@ -2,6 +2,8 @@ name: Slack Notify
 on: 
   watch:
     types: [started]
+  issues:
+    types: [labeled]
 jobs:
   star-notify:
     if: github.event_name == 'watch'

src/assets/data/faq/index.js

@@ -320,114 +320,6 @@ const data = {
       ],
     },
 
-    //
-    // SERVICE MESH
-    //
-
-    {
-      question: "What value does a service mesh provide?",
-      category: "Service Mesh",
-      answer: [
-        "Service meshes provide visibility, resiliency, traffic, and security control of distributed application services. Much value is promised here, particularly to the extent that much is given without the need to change your application code.",
-      ],
-      link: "",
-      linktext: "",
-    },
-    // {
-    //     question: "What is the difference between a service mesh management, control, and data plane?",
-    //     category: "Service Mesh",
-    //     answer: "",
-    //     answer_2: "",
-    //     answer_3: "",
-    //     answer_4: "",
-    //     answer_5: "",
-    //     link: "/blog/service-mesh-planes",
-    //     linktext: "Blog: Understanding Service Mesh Planes",
-    // },
-    {
-      question:
-        "What if I deploy one service mesh, like Istio, then need to switch to another service mesh?",
-      category: "Service Mesh",
-      answer: [
-        "Use of Meshery and the Service Mesh Interface specification help avoid switching costs between service meshes.",
-        "The goal of Service Mesh Interface specifications are to provide an abstract, unified method of interacting with a service mesh.",
-        "See if your service mesh adheres to SMI specifications at the link below.",
-      ],
-      link: "/projects/service-mesh-interface-conformance",
-      linktext: "Service Mesh Interface",
-    },
-    {
-      question: "What are service mesh standards and why do they matter?",
-      category: "Service Mesh",
-      answer: [
-        "Three service mesh abstractions have arisen given the high number of service meshes available (see the Service Mesh Landscape)",
-        "Servcie Mesh Performance (SMP) - A standard for capturing and characterizing service mesh performance.",
-        "Service Mesh Interface (SMI) - A standard interface for using common service mesh functionality on Kubernetes.",
-        "Multi-Vendor Service Mesh Interoperation (Hamlet) - A set of API standards for enabling service mesh federation.",
-      ],
-      link: "https://calcotestudios.com/talks/decks/slides-open-infrastructure-summit-2020-its-a-multi-mesh-world.html",
-      linktext: "See Open Infrastructure Summit Presentation",
-    },
-    {
-      question: "How does a service mesh help me? in my role?",
-      category: "Service Mesh",
-      answer: [
-        "Operators don’t necessarily need to involve Developers to change how many times a service should retry before timing out or to run experiments (known as chaos engineering). They are empowered to affect service behavior independently.",
-        "Customer Success (support) teams can handle the revocation of client access without involving Operators.",
-        "Product Owners can use quota management to enforce price plan limitations for quantity-based consumption of particular services.",
-        "Developers can redirect their internal stakeholders to a canary with beta functionality without involving Operators.",
-        "Security Engineers can declaratively define authentication and authorization policies, enforced by the service mesh.",
-        "Network Engineers are empowered with an extraordinarily high degree of application-level control formerly simply unavailable to them.",
-      ],
-      link: "",
-      linktext: "",
-    },
-    // {
-    //     question: "Why do I need a service mesh?",
-    //     category: "Service Mesh",
-    //     answer: "",
-    //     answer_2: "",
-    //     answer_3: "",
-    //     answer_4: "",
-    //     answer_5: "",
-    //     link: "",
-    //     linktext: "",
-    // },
-    // {
-    //     question: "Which service mesh is right for me?",
-    //     category: "Service Mesh",
-    //     answer: "",
-    //     answer_2: "",
-    //     answer_3: "",
-    //     answer_4: "",
-    //     answer_5: "",
-    //     link: "/service-mesh-landscape",
-    //     linktext: "Service Mesh Landscape",
-    // },
-    // {
-    //   question: "What is a service mesh?",
-    //   category: "Service Mesh",
-    //   answer: [
-    //     "Service meshes provide intent-based networking for microservices describing desired behavior of the network in the face of constantly changing conditions and network topology. At their core, service meshes provide:",
-    //     "A services-first network; A developer-driven network;",
-    //     "A network that is primarily concerned with alleviating application developers from building infrastructure concerns into their application code; A network that empowers operators with the ability to declaratively define network behavior, node identity, and traffic flow through policy;",
-    //     "A network that enables service owners to control application logic without engaging developers to change its code.",
-    //     "Value derived from the layer of tooling that service meshes provide is most evident in the land of microservices. The more services, the more value derived from the mesh. In subsequent chapters, I show how service meshes provide value outside of the use of microservices and containers and help modernize existing services (running on virtual or bare metal servers) as well.",
-    //   ],
-    //   link: "",
-    //   linktext: "",
-    // },
-    {
-      question: "When should I adopt a service mesh?",
-      category: "Service Mesh",
-      answer: [
-        "There are many service meshes to choose from as well as a variety of deployment models. Which is right for you and your organization depends on where you are in your maturity curve (Cloud Native skill set), number of services, underlying infrastructure, and how centric technology is to your business. ",
-        "So, should you deploy a service mesh? More and more the answer is “yes”. Service meshes are quickly becoming a ubiquitous layer in modern infrastructures.",
-      ],
-      link: "/deploy-service-mesh",
-      linktext: "Factors When considering how strongly you need a service mesh",
-    },
-
      //
     // CAREERS / INTERNSHIPS
     //

src/collections/integrations/aws-cloudfront-controller/icons/components/vpc-origin/icons/color/vpc-origin-color.svg

@@ -62,6 +62,12 @@ components: [
 "colorIcon": "icons/components/origin-access-control/icons/color/origin-access-control-color.svg",
 "whiteIcon": "icons/components/origin-access-control/icons/white/origin-access-control-white.svg",
 "description": "",
+},
+{
+"name": "vpc-origin",
+"colorIcon": "icons/components/vpc-origin/icons/color/vpc-origin-color.svg",
+"whiteIcon": "icons/components/vpc-origin/icons/white/vpc-origin-white.svg",
+"description": "",
 }]
 featureList: [
   "Global content delivery",

src/collections/integrations/aws-cloudfront-controller/icons/components/vpc-origin/icons/white/vpc-origin-white.svg

@@ -0,0 +1,33 @@
+---
+title: Azure Operator
+subtitle: Collaborative and visual infrastructure as design for Azure Operator
+integrationIcon: icons/color/azure-operator-color.svg
+darkModeIntegrationIcon: icons/white/azure-operator-white.svg
+docURL: https://docs.meshery.io/extensibility/integrations/azure-operator
+description: 
+category: Runtime
+subcategory: Cloud Native Storage
+registrant: GitHub
+components: []
+featureList: [
+  "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.",
+  "Invite anyone to review and make changes to your private designs.",
+  "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters."
+]
+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
+---
+<p>
+
+</p>
+<p>
+    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.
+</p>
+<p>
+    Looking for best practice cloud native design and deployment best practices? Choose from thousands of pre-built components in Kanvas. Choose from hundreds of ready-made design patterns by importing templates from Meshery Catalog or use our low code designer, Kanvas, to create and deploy your own cloud native infrastructure designs.
+</p>