docs: removed a question pr marketing's gudiance

This commit is contained in:
Karl Cardenas 2022-01-18 15:26:37 -07:00
parent 97e9b7cf4b
commit ba432f940f
No known key found for this signature in database
GPG Key ID: 0AC61D76B41F1EDC
1 changed files with 0 additions and 6 deletions

View File

@ -74,8 +74,6 @@ Organizations may need to route network traffic to other infrastructure environm
Service meshes offer the ability to enforce network traffic encryption (mTLS) and authentication between all services. The _service mesh_ can automatically generate an SSL certificate for each service and its instances.
The certificate authenticates with other services inside the mesh and encrypts the TCP/UDP/gRPC connection with SSL.
<!-- As mentioned earlier, the _service mesh_ is aware of all services and their respective state and can require authentication between all service to service communication. -->
Fine-grained policies that dictate what services are allowed to communicate with each other is another benefit of a _service mesh_.
Traditionally, services are permitted to communicate with other services through firewall rules.
The traditional firewall (IP-based) model is difficult to enforce with dynamic infrastructure resources with a short lifecycle and frequently recycling IP addresses.
@ -89,10 +87,6 @@ Service meshes are commonly installed in Kubernetes clusters. There are also pla
For Kubernetes, most service mesh can be installed by operators through a [Helm chart](https://artifacthub.io/). Additionally, the service mesh may offer a CLI tool that supports the installation and maintenance of the service mesh.
Non-Kubernetes based service meshes can be installed through infrastructure as code (IaC) products such as [Terraform](https://www.terraform.io/), CloudFormation, ARM Templates, Puppet, Chef, etc.
## What is Service Mesh Automation?
** Waiting to hear back from Marketing what this question means**.
## What is a Multi Platform Service Mesh?
A multi-platform service mesh is capable of supporting various infrastructure environments. This can range from having the service mesh support Kubernetes and non-Kubernetes workloads, to having a service mesh span across various cloud environments (multi-cloud).