- Routing
-
By clicking the Routing link, you can perform the following actions:
-
Customize the hostname for the route.
-
Specify the path the router watches.
-
Select the target port for the traffic from the drop-down list.
-
Secure your route by selecting the Secure Route check box. Select the required TLS termination type and set a policy for insecure traffic from the respective drop-down lists.
For serverless applications, the Knative service manages all the routing options above. However, you can customize the target port for traffic, if required. If the target port is not specified, the default port of
8080is used.
-
- Health Checks
-
Click the Health Checks link to add Readiness, Liveness, and Startup probes to your application. All the probes have prepopulated default data; you can add the probes with the default data or customize it as required.
To customize the health probes:
-
Click Add Readiness Probe, if required, modify the parameters to check if the container is ready to handle requests, and select the check mark to add the probe.
-
Click Add Liveness Probe, if required, modify the parameters to check if a container is still running, and select the check mark to add the probe.
-
Click Add Startup Probe, if required, modify the parameters to check if the application within the container has started, and select the check mark to add the probe.
For each of the probes, you can specify the request type - HTTP GET, Container Command, or TCP Socket, from the drop-down list. The form changes as per the selected request type. You can then modify the default values for the other parameters, such as the success and failure thresholds for the probe, number of seconds before performing the first probe after the container starts, frequency of the probe, and the timeout value.
-
- Build Configuration and deployment
-
Click the Build Configuration and deployment links to see the respective configuration options. Some options are selected by default; you can customize them further by adding the necessary triggers and environment variables.
For serverless applications, the deployment option is not displayed as the Knative configuration resource maintains the desired state for your deployment instead of a
deploymentConfigresource.
- Scaling
-
Click the Scaling link to define the number of pods or instances of the application you want to deploy initially.
If you are creating a serverless deployment, you can also configure the following settings:
-
Min Pods determines the lower limit for the number of pods that must be running at any given time for a Knative service. This is also known as the
minScalesetting. -
Max Pods determines the upper limit for the number of pods that can be running at any given time for a Knative service. This is also known as the
maxScalesetting. -
Concurrency target determines the number of concurrent requests desired for each instance of the application at a given time.
-
Concurrency limit determines the limit for the number of concurrent requests allowed for each instance of the application at a given time.
-
Concurrency utilization determines the percentage of the concurrent requests limit that must be met before Knative scales up additional pods to handle additional traffic.
-
Autoscale window defines the time window over which metrics are averaged to provide input for scaling decisions when the autoscaler is not in panic mode. A service is scaled-to-zero if no requests are received during this window. The default duration for the autoscale window is
60s. This is also known as the stable window.
-
- Resource Limit
-
Click the Resource Limit link to set the amount of CPU and Memory resources a container is guaranteed or allowed to use when running.
- Labels
-
Click the Labels link to add custom labels to your application.
