forked from layer5io/layer5
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request layer5io#1358 from layer5io/operating-service-meshes
[NG] Operating Service Meshes (How It Works)
- Loading branch information
Showing
3 changed files
with
117 additions
and
91 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
104 changes: 104 additions & 0 deletions
104
src/pages/service-mesh-management/meshery/operating-service-meshes.js
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,104 @@ | ||
| import React from "react"; | ||
| import { ThemeProvider } from "styled-components"; | ||
|
|
||
| import Layout from "../../../components/layout"; | ||
| import SEO from "../../../components/seo"; | ||
|
|
||
| import Navigation from "../../../sections/Navigation"; | ||
| import Works from "../../../sections/ServiceMesh"; | ||
| import Footer from "../../../sections/Footer"; | ||
|
|
||
| import { GlobalStyle } from "../../../sections/app.style"; | ||
| import theme from "../../../theme/app/themeStyles"; | ||
| import { Container } from "../../../reusecore/Layout"; | ||
| import SectionTitle from "../../../reusecore/SectionTitle"; | ||
|
|
||
|
|
||
| import Button from "../../../reusecore/Button"; | ||
| import VintageBox from "../../../reusecore/VintageBox"; | ||
|
|
||
|
|
||
| const Howitworks = () => ( | ||
| <ThemeProvider theme={theme}> | ||
| <Layout> | ||
| <GlobalStyle /> | ||
| <SEO title="How the service mesh management plane, Meshery works" /> | ||
| <Navigation /> | ||
| <Container> | ||
| <br></br> | ||
| <Works | ||
| title="How Meshery Manages Meshes" | ||
| description="As the multi-mesh manager, Meshery offers support for more adapters than any other project or product in the world. Meshery uses adapters for managing the various service meshes." | ||
| features={[ | ||
| { | ||
| title: "Supporting Service Mesh Interface", | ||
| description: | ||
| "Adapters allow Meshery to interface with the different service meshes, exposing their differentiated value to users.", | ||
| }, | ||
| { | ||
| title: "Adapters should avoid wheel reinvention, but seek to leverage the functionality provided by service meshes under management.", | ||
| description: | ||
| " This both reduces sustaining costs and improves reliability", | ||
| }, | ||
| { | ||
| title: "Each service mesh adapter is unique", | ||
| description: | ||
| "Every Meshery Adapter provides a common substrate of support for every service mesh, offering a standard set of management features across all service meshes. Carre is taken in each Meshery Adapters to also expose the unique value of each service mesh. Consequently, each Meshery Adapter is not equally capable just as each service mesh is not equally capable as another service mesh.", | ||
| }, | ||
| { | ||
| title: "Main", | ||
| description: | ||
| "Automate credential injection to securely access services and hosts with HashiCorp Vault. Reduce risk of leaking credentials with dynamic secrets and just-in-time credentials.", | ||
| }, | ||
| { | ||
| title: "BG", | ||
| description: | ||
| "Automate credential injection to securely access services and hosts with HashiCorp Vault. Reduce risk of leaking credentials with dynamic secrets and just-in-time credentials.", | ||
| }, | ||
| { | ||
| title: "Managing multiple instances of the same type of service mesh", | ||
| description: | ||
| "Adapters establish communication with Kubernetes and a specific type of service mesh. Multiple adapters of the same type may be deployed concurrently. Although, this isn’t strictly necessary for Meshery to communicate to more than one instance of the same type of service mesh. See the <a href='https://docs.meshery.io/guides/multiple-adapters'>Using Multiple Adapters</a> guide for more information.", | ||
| }, | ||
| { | ||
| title: "BG", | ||
| description: | ||
| "Automate credential injection to securely access services and hosts with HashiCorp Vault. Reduce risk of leaking credentials with dynamic secrets and just-in-time credentials.", | ||
| }, | ||
| { | ||
| title: "BG", | ||
| description: | ||
| "Automate credential injection to securely access services and hosts with HashiCorp Vault. Reduce risk of leaking credentials with dynamic secrets and just-in-time credentials.", | ||
| }, | ||
| { | ||
| title: "BG", | ||
| description: | ||
| "Automate credential injection to securely access services and hosts with HashiCorp Vault. Reduce risk of leaking credentials with dynamic secrets and just-in-time credentials.", | ||
| }, | ||
| ]}/> | ||
| </Container> | ||
| <Container> | ||
| <SectionTitle | ||
| className="section-title section-bottom" | ||
| leftAlign={false} | ||
| UniWidth="100%" | ||
| > | ||
| <h3>Where you find a Kubernetes, | ||
| you’ll find a service mesh.</h3> | ||
| <p>Service meshes are the third major step in enterprises cloud native journeys.</p> | ||
| <VintageBox left={true} vintageTwo={true} > | ||
| <Button | ||
| primary | ||
| className="about-button" | ||
| url="./getting-started" | ||
| title="Install Meshery" | ||
| external="false" | ||
| /> | ||
| </VintageBox> | ||
| </SectionTitle> | ||
| </Container> | ||
| <Footer/> | ||
| </Layout> | ||
| </ThemeProvider> | ||
| ); | ||
| export default Howitworks; |
This file was deleted.
Oops, something went wrong.