Starting: 1st of Every Month 
+91 8409492687 
Contact@DevOpsSchool.com
- Request Initiation:
- A user sends a request to an application hosted on Knative.
- This request first hits the
Istio Ingress Gateway, which is the entry point for external traffic into the Kubernetes cluster.
- VirtualService Routing:
- The
Istio Ingress Gatewayuses IstioVirtualServiceto determine where to route the request. Knative sets up these VirtualServices when a service is created or updated. - Typically, the
VirtualServicewill point to theKnative Activatorwhen the application is scaled to zero or during scaling up from zero.
- The
- Activator:
- The
Activatoris responsible for starting up instances of the application (Pods) when there are none running. It plays a crucial role in scale-to-zero functionality. - If an application is scaled to zero (no active pods), the
Activatorreceives the incoming request, triggers the Kubernetes deployment to start a new pod, and then buffers incoming requests until the pod is ready to handle them. - Once the pod is running and ready, the
Activatorforwards the buffered requests to the pod.
- The
- Autoscaler:
- The
Autoscalercomponent in Knative observes traffic load and scales the application pods up or down based on the configuration (like concurrency-based metrics) and actual traffic. - It receives metrics about ongoing traffic and makes decisions on when to scale. The
Activatoralso plays a part in this by sending metrics to theAutoscalerwhen it’s buffering requests for scaled-to-zero applications.
- The
- Knative Service and Revisions:
- In Knative, when you create a
Service(not to be confused with Kubernetes Service), it represents a specific configuration of your application. - Each time you modify the
Service, Knative creates a newRevision. EachRevisionis a snapshot of the code and configurations for a particular version of the service. - The actual running code is encapsulated in a Kubernetes deployment associated with that
Revision.
- In Knative, when you create a
- Knative Route:
- The
Routeis responsible for determining whichRevisionof aServicereceives traffic. You can set up theRouteto split traffic between multipleRevisionsfor blue-green deployments, canary releases, etc. - Combined with
VirtualService, it ensures the right revisions of your application are being routed traffic.
- The
- Request Completion:
- After the application processes the request, the response travels back through the same path: from the pod to (possibly) the
Activator, and then out through theIstio Ingress Gatewayto the user.
- After the application processes the request, the response travels back through the same path: from the pod to (possibly) the
I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I am working at Cotocus. I blog tech insights at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at I reviewed , and SEO strategies at Wizbrand.
Please find my social handles as below;
Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at PINTEREST
Rajesh Kumar at QUORA
Rajesh Kumar at WIZBRAND
