Skip to content

Commit

Permalink
Update blog/docs/articles/demystifying-activator-on-path.md
Browse files Browse the repository at this point in the history
Co-authored-by: Roland Huß <[email protected]>
  • Loading branch information
skonto and rhuss authored Oct 13, 2023
1 parent 8073e3c commit 2a4be99
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion blog/docs/articles/demystifying-activator-on-path.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ _In this blog post you will learn how to recognize when activator is on the data

A knative service can operate in two modes: proxy mode and serve mode.
When in proxy mode, Activator is on the data path, and it will stay on the path until certain conditions (more on this later) are met.
When these conditions are met Activator is removed from the path and the service transitions to serve mode.
When these conditions are met, Activator is removed from the data path, and the service transitions to serve mode.
However, it was not always like that when a service scales from/to zero, the activator is added by default to the data path.
This default setting often confuses users for reasons we will see next as it is possible that activator will not
be removed unless enough capacity is available. This is intended as one of the Activator's roles is to offer backpressure capabilities so that a Knative service is not overloaded by incoming traffic.
Expand Down

0 comments on commit 2a4be99

Please sign in to comment.