How To Implement Zero Trust with a Service Mesh close
Tetrate Enterprise ready service mesh
Get Demo
Pricing

Frequently Asked Questions

What’s the difference between Tetrate products and Istio?

Do Tetrate products support multiple cloud deployments?

Are Tetrate products open source?

Do Tetrate products support non-Kubernetes workloads?

Why do I need Tetrate in addition to open source Istio?

Do Tetrate products run in the cloud and on premises?

Why do I need multitenancy in a service mesh?

How do I protect production from unauthorized access in a dynamic compute environment like Kubernetes?

How can I implement mTLS across my entire infrastructure, including between Kubernetes and VMs?

Will Tetrate Service Bridge work with my existing public key infrastructure?

How do I ensure and prove consistent application of authorization policy across all of my deployments?

How does Tetrate Service Bridge transparently shift traffic to public cloud services from my on-premises, self-managed infrastructure?

How does Tetrate Service Bridge help optimize locality and minimize egress?

How can I safely roll out my microservices implementation and roll back to the VM implementation if it’s not working?

How can I mitigate the damage of infrastructure outages by giving my developers tools to failover and build HA applications?

How does Tetrate Service Bridge help me keep my service mesh up to date without causing outages?

How do I enable my developers to build reliable applications using mesh primitives?

What is the difference between Tetrate Service Bridge and Tetrate Service Express?

What is an API?

What is an API gateway?

What does Kubernetes do?

What is ingress and egress in Kubernetes?

What does “proxied” mean?

What is ProxyPass?

What is a gateway in microservices?

What is ABAC?

What is a service mesh?

What is Istio?

What is Envoy Proxy?

What are the core principles of the zero trust model?

What are the benefits of choosing a zero trust architecture?

How does Tetrate Service Bridge help me keep my service mesh up to date without causing outages?

Tetrate Service Bridge (TSB) provides cluster details that include the deployed versions of Istio and Envoy to give you an up-to-date status of what’s running in your infrastructure at a glance. To upgrade, TSB runs the new version of the service mesh as a canary to give you the operational assurance that it’s safe to release the upgrade more broadly.