Merge pull request #38284 from abrennan89/SRVKS-573

SRVKS-573: Updating autoscaling docs

Author: abrennan89

_topic_map.yml

@@ -3189,9 +3189,6 @@ Topics:
     # Knative services
   - Name: Serverless applications
     File: serverless-applications
-    # Autoscaling
-  - Name: Configuring Knative Serving autoscaling
-    File: configuring-knative-serving-autoscaling
   - Name: Traffic management
     File: serverless-traffic-management
   - Name: Cluster logging with OpenShift Serverless
@@ -3208,6 +3205,17 @@ Topics:
   - Name: Metrics
     File: serverless-serving-metrics
 #
+# Autoscaling
+- Name: Autoscaling
+  Dir: autoscaling
+  Topics:
+  - Name: About autoscaling
+    File: serverless-autoscaling
+  - Name: Scale bounds
+    File: serverless-autoscaling-scale-bounds
+  - Name: Concurrency
+    File: serverless-autoscaling-concurrency
+#
 # Knative Eventing
 - Name: Knative Eventing
   Dir: knative_eventing

modules/configuring-scale-bounds-knative.adoc

@@ -0,0 +1,19 @@
+[id="serverless-autoscaling-maxscale-kn_{context}"]
+= Setting the maxScale annotation by using the Knative CLI
+
+You can use the `kn service` command with the `--max-scale` flag to create or modify the `--max-scale` value for a service.
+
+.Procedure
+
+* Set the maximum number of pods for the service by using the `--max-scale` flag:
++
+[source,terminal]
+----
+$ kn service create <service_name> --image <image_uri> --max-scale <integer>
+----
++
+.Example command
+[source,terminal]
+----
+$ kn service create example-service --image quay.io/openshift-knative/knative-eventing-sources-event-display:latest --max-scale 10
+----

modules/knative-serving-concurrent-autoscaling-requests.adoc

@@ -0,0 +1,21 @@
+[id="serverless-autoscaling-minscale_{context}"]
+= Setting the minScale annotation by using the Knative CLI
+
+You can use the `kn service` command with the `--min-scale` flag to create or modify the `--min-scale` value for a service.
+
+.Procedure
+
+* Set the maximum number of pods for the service by using the `--min-scale` flag:
++
+.Examples
+[source,terminal]
+----
+$ kn service create <service_name> --image <image_uri> --min-scale <integer>
+----
++
+[source,terminal]
+----
+$ kn service create example-service --image quay.io/openshift-knative/knative-eventing-sources-event-display:latest --min-scale 2
+----
+
+// TODO: Check if it can be used with update and other service commands.

modules/serverless-autoscaling-maxscale-kn.adoc

@@ -0,0 +1,42 @@
+[id="serverless-concurrency-limits-configure-hard_{context}"]
+= Configuring a hard concurrency limit
+
+You can specify a hard concurrency limit for your Knative service by modifying the `containerConcurrency` spec or by using the `kn service` command with the correct flags.
+
+// However, a default value can be set for the Revision's containerConcurrency field in config-defaults.yaml.
+// add note about this for admins to see? Need more details about config-defaults though
+
+.Procedure
+
+* Optional: Set the `containerConcurrency` spec for your Knative service in the spec of the `Service` custom resource:
++
+.Example service spec
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  name: example-service
+  namespace: default
+spec:
+  template:
+    spec:
+      containerConcurrency: 50
+----
++
+The default value is `0`, which means that there is no limit on the number of requests that are permitted to flow into one pod of the service at a time.
++
+A value greater than `0` specifies the exact number of requests that are permitted to flow into one pod of the service at a time. This example would enable a hard concurrency limit of 50 requests at a time.
+
+* Optional: Use the `kn service` command to specify the `--concurrency-limit` flag:
++
+[source,terminal]
+----
+$ kn service create <service_name> --image <image_uri> --concurrency-limit <integer>
+----
++
+.Example command to create a service with a concurrency limit of 50 requests
+[source,terminal]
+----
+$ kn service create example-service --image quay.io/openshift-knative/knative-eventing-sources-event-display:latest --concurrency-limit 50
+----

modules/serverless-autoscaling-minscale-kn.adoc

@@ -0,0 +1,36 @@
+[id="serverless-concurrency-limits-configure-soft_{context}"]
+= Configuring a soft concurrency target
+
+You can specify a soft concurrency target for your Knative service by setting the `autoscaling.knative.dev/target` annotation in the spec, or by using the `kn service` command with the correct flags.
+
+.Procedure
+
+* Optional: Set the `autoscaling.knative.dev/target` annotation for your Knative service in the spec of the `Service` custom resource:
++
+.Example service spec
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  name: example-service
+  namespace: default
+spec:
+  template:
+    metadata:
+      annotations:
+        autoscaling.knative.dev/target: "200"
+----
+
+* Optional: Use the `kn service` command to specify the `--concurrency-target` flag:
++
+[source,terminal]
+----
+$ kn service create <service_name> --image <image_uri> --concurrency-target <integer>
+----
++
+.Example command to create a service with a concurrency target of 50 requests
+[source,terminal]
+----
+$ kn service create example-service --image quay.io/openshift-knative/knative-eventing-sources-event-display:latest --concurrency-target 50
+----

modules/serverless-concurrency-limits-configure-hard.adoc

@@ -0,0 +1,17 @@
+[id="serverless-concurrency-limits_{context}"]
+= Concurrency limits and targets
+
+Concurrency can be configured as either a _soft limit_ or a _hard limit_:
+
+* A soft limit is a targeted requests limit, rather than a strictly enforced bound. For example, if there is a sudden burst of traffic, the soft limit target can be exceeded.
+
+* A hard limit is a strictly enforced upper bound requests limit. If concurrency reaches the hard limit, surplus requests are buffered and must wait until there is enough free capacity to execute the requests.
++
+[IMPORTANT]
+====
+Using a hard limit configuration is only recommended if there is a clear use case for it with your application. Having a low, hard limit specified may have a negative impact on the throughput and latency of an application, and might cause cold starts.
+====
+
+Adding a soft target and a hard limit means that the autoscaler targets the soft target number of concurrent requests, but imposes a hard limit of the hard limit value for the maximum number of requests.
+
+If the hard limit value is less than the soft limit value, the soft limit value is tuned down, because there is no need to target more requests than the number that can actually be handled.

modules/serverless-concurrency-limits-configure-soft.adoc

@@ -0,0 +1,13 @@
+[id="serverless-autoscaling-concurrency"]
+= Concurrency
+include::modules/common-attributes.adoc[]
+include::modules/serverless-document-attributes.adoc[]
+:context: serverless-autoscaling-concurrency
+
+toc::[]
+
+Concurrency determines the number of simultaneous requests that can be processed by each pod of an application at any given time.
+
+include::modules/serverless-concurrency-limits.adoc[leveloffset=+1]
+include::modules/serverless-concurrency-limits-configure-soft.adoc[leveloffset=+2]
+include::modules/serverless-concurrency-limits-configure-hard.adoc[leveloffset=+2]