Steps to reach with containers
Openshift > GCP > Istio
**Do the canary deployment and record it **
Istio is an open-source service mesh that provides a way to control how microservices share data with one another. It's designed to help manage complex deployments of microservices by providing capabilities like traffic management, service identity and security, policy enforcement, and observability.
Here are some of the key features and functionalities that Istio offers:
-
Traffic Management: Istio simplifies the configuration of service-level properties like circuit breakers, timeouts, and retries, and makes it easy to set up important tasks such as A/B testing, canary rollouts, and staged rollouts with percentage-based traffic splits.
-
Security: Istio provides robust security features, which help to secure inter-service communication and end-user authentication. This includes automatic encryption of traffic between pods, and management of authentication, authorization, and encryption.
-
Observability: Istio provides detailed insights into your service mesh, which includes monitoring, logging, and tracing capabilities. This helps operators to understand the performance and behavior of the microservices in their service mesh.
-
Policy Enforcement: Istio allows administrators to define and enforce policies at the service level, which can be used to enforce certain quality of service standards regarding throughput and latency.
-
Service Identity and Security: With Istio, each service in the mesh can have a strong identity that is used in access control decisions, and to encrypt traffic between services.
Istio is platform-independent, meaning it can be deployed across different cloud and on-premise environments. It works by inserting proxies (by default, Envoy proxies) alongside each service instance in the mesh. These proxies intercept and manage the network communication between microservices. This architecture allows Istio to manage traffic flows between services, enforce policies, and aggregate telemetry data, all without requiring changes to the microservices themselves.
Imported from rifaterdemsahin.com · 2024