Containers as a service gives application teams a simplified interface for running containers on demand without directly managing Kubernetes resources. Knative Serving provides this model through higher-level abstractions over Kubernetes. section 8.2 section 8.2.1
A Knative Service manages the application-facing workflow:
- Define a container image and configuration in a Knative Service resource. section 8.2.1
- Let Knative create and track the underlying services, deployments, ReplicaSets, revisions, and versions. section 8.2 section 8.2.1
- Use demand-based autoscaling, including scaling unused workloads down to zero replicas. section 8.2 section 8.2.1
- Expose the service through a stable endpoint while supporting advanced traffic handling and multiple simultaneous revisions. section 8.2
Notification service
A Knative Service can deploy the Conference application's notification container with an image and Kafka URL, then expose an endpoint that can be queried with curl. The resulting response reports the service name, pod details, source, and version. section 8.2.1
Listing 8.1 Knative Service definition
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
name: notifications-service #1
spec:
template:
spec:
containers:
- image: salaboy/notifications-service:v1.0.0 #2
Env: #3
- name: KAFKA_URL
value: <URL>
Use the manifest to inspect the minimal Knative Service contract: API version, resource kind, service name, container image, and environment configuration. section 8.2.1
