-
Notifications
You must be signed in to change notification settings - Fork 30
/
Copy pathconfig.toml
110 lines (87 loc) · 3.35 KB
/
config.toml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
title = "Network Service Mesh"
baseURL = "/"
languageCode = "en-us"
disableKinds = ["taxonomy", "taxonomyTerm"]
# Syntax highlighting settings
[markup]
[markup.goldmark]
[markup.goldmark.renderer]
unsafe = true
[markup.highlight]
lineNos = true
lineNumbersInTable = true
noClasses = true
style = 'monokailight'
[menu]
[[menu.navbar]]
name = "Docs"
url = "/docs/concepts/enterprise_users/"
weight = 1
[[menu.navbar]]
name = "Community"
url = "/community/multirepo"
weight = 2
[[menu.navbar]]
name = "Events"
url = "/events"
weight = 3
[[menu.navbar]]
name = "Blog"
url = "/blog"
weight = 4
# The site's parameters
[params]
twitter = "nservicemesh"
fontawesomeversion = "5.8.1"
dateFormat = "02.01.2006"
subtitle = "The Hybrid/Multi-cloud IP Service Mesh"
description = """
The Hybrid/Multi-cloud IP Service Mesh"""
explanation = """
Network Service Mesh frees individual Kubernetes Pods to network with other workloads across multiple clusters/clouds using a simple set of APIs designed to facilitate attaching those Pods to zero or more "Network Services"
that provide exactly the
* Connectivity
* Security
* Observability
they need - independent of where they are running.
"""
usecases = """
Examples:
* A common flat vL3 domain allowing DBs running in multiple clusters/clouds/hybrid to communicate just with each other for DB replication
* A single L7 Service Mesh (Istio/Linkerd/Consul/Kuma) connecting workloads running in multiple clusters/clouds/on-prem
* A single workload connecting to multiple L7 Service Meshes
* Workloads from multiple companies connecting to a single 'collaborative' Service Mesh for cross company interactions
"""
features = [
"L3 Zero Trust",
"Per workload granularity",
"Per Network Service Connectivity/Security/Observability",
"No changes to K8s",
"Works with your existing CNI",
"No changes to your workloads",
]
[params.logos]
cncf = "cncf-color.png"
navbar = "networkservicemesh-horizontal-color.png"
hero = "networkservicemesh-icon-color.png"
[params.wrapper]
enable = true
title = "Problem Statement"
italic = "Multifaceted networks such as Telcos, ISPs, and advanced enterprise networks are rearchitecting their solutions with the advent of NFV, 5G networks, edge computing, and IoT devices. Each of these technologies brings a significant increase in the total number of connected devices, increased bandwidth available per device, and a significant increase in cloud service load."
paragraph = "Operators of multifaceted networks with advanced L2/L3 use cases currently find container networking solutions ill-suited for their next-generation architecture. Cloud native solution's lack of support for advanced networking use cases is actively excluding multiple industries from adopting the new cloud native paradigm."
[params.blog]
enable = false
title = "Get The Latest On What We're doing"
subtitle = "Catch up with us, anytime and anywhere"
[params.social]
github = "https://github.com/networkservicemesh/"
twitter = "https://twitter.com/nservicemesh"
devstats = "https://networkservicemesh.devstats.cncf.io/d/2/commits-repository-groups?orgId=1&var-period=w&var-repogroups=All&from=now-1y&to=now"
[[params.fonts]]
name = "Nunito Sans"
sizes = [300, 400, 600, 700]
type = "sans_serif"
[[params.fonts]]
name = "Roboto Mono"
sizes = [300, 400, 600, 700]
type = "monospace"