Service with Probes - Knative Typing CST Test

Primary Use Cases

• ▸Serverless applications on Kubernetes
• ▸Event-driven microservices
• ▸Automatic scaling workloads
• ▸Routing and traffic management for services
• ▸Integrating with cloud-native CI/CD pipelines

Notable Features

• ▸Automatic scaling to zero and scale up based on demand
• ▸Event-driven architecture with CloudEvents support
• ▸Routing and traffic splitting for versions
• ▸Integration with Kubernetes ecosystem
• ▸Extensible via custom components and operators

Origin & Creator

Knative was created by Google in 2018 as an open-source project to standardize serverless on Kubernetes.

Industrial Note

Knative is ideal for teams deploying cloud-native, event-driven, and serverless workloads in Kubernetes or OpenShift clusters.

Quick Explain

• ▸Knative provides a set of components to deploy and manage serverless applications on Kubernetes.
• ▸Supports automatic scaling up/down to zero based on workload.
• ▸Includes event-driven architecture for reactive applications.
• ▸Simplifies routing and traffic splitting for microservices.
• ▸Ideal for serverless functions, microservices, and cloud-native applications.

Core Features

• ▸Knative Serving: deploy and manage serverless services
• ▸Knative Eventing: event routing and consumption
• ▸Auto-scaling and scale-to-zero capabilities
• ▸Traffic splitting for versioned deployments
• ▸Integration with Kubernetes networking and storage

Learning Path

• ▸Learn Kubernetes basics
• ▸Understand containerized applications
• ▸Learn Knative Serving and Eventing concepts
• ▸Practice deploying services with YAML manifests
• ▸Integrate event sources and CI/CD pipelines

Practical Examples

• ▸Deploy a serverless API endpoint
• ▸Process CloudEvents from a message queue
• ▸Scale a microservice based on HTTP traffic
• ▸Run event-driven image processing service
• ▸A/B testing with traffic splitting between revisions

Comparisons

• ▸Knative vs OpenFaaS: Knative tightly integrates with Kubernetes; OpenFaaS focuses on simplicity and lightweight functions
• ▸Knative vs AWS Lambda: Knative runs on Kubernetes; Lambda is managed serverless
• ▸Knative vs Argo Workflows: Knative is event-driven; Argo is workflow/orchestration-focused
• ▸Knative vs Spring Boot: Knative is serverless; Spring Boot is traditional app framework
• ▸Knative vs Quarkus: Knative manages serverless workloads; Quarkus is a Java runtime/framework

Strengths

• ▸Automatic scaling reduces resource usage
• ▸Supports event-driven serverless architecture
• ▸Seamless Kubernetes integration
• ▸Flexible routing and traffic management
• ▸Extensible and cloud-native friendly

Limitations

• ▸Requires Kubernetes knowledge
• ▸Complex setup for beginners
• ▸Dependent on cluster resources and networking
• ▸Debugging can be more challenging than traditional apps
• ▸Limited built-in tooling compared to managed serverless platforms

When NOT to Use

• ▸Teams without Kubernetes knowledge
• ▸Small apps not needing autoscaling or serverless features
• ▸Projects requiring simple deployments outside Kubernetes
• ▸Legacy monolithic apps with stateful components
• ▸Low-latency workloads where cold start is unacceptable

Cheat Sheet

• ▸kubectl apply -f service.yaml -> deploy service
• ▸kubectl get ksvc -> check Knative services
• ▸kubectl apply -f event.yaml -> create event source
• ▸kubectl logs -l serving.knative.dev/service=your-service -> view logs
• ▸Annotations for scaling: autoscale.knative.dev/minScale/maxScale

FAQ

• ▸Is Knative free?
• ▸Yes - open-source under Apache License 2.0
• ▸Does Knative require Kubernetes?
• ▸Yes - it is built on Kubernetes
• ▸Can Knative scale to zero?
• ▸Yes - services can scale down to zero when idle
• ▸Does Knative support event-driven apps?
• ▸Yes - via Eventing and CloudEvents
• ▸How does Knative compare to Lambda?
• ▸Knative is self-hosted serverless on Kubernetes; Lambda is managed serverless on AWS

30-Day Skill Plan

• ▸Week 1: Kubernetes fundamentals and kubectl
• ▸Week 2: Container image creation and deployment
• ▸Week 3: Knative Serving - services and revisions
• ▸Week 4: Knative Eventing - triggers and brokers
• ▸Week 5: Advanced traffic splitting, scaling, and monitoring

Final Summary

• ▸Knative is a Kubernetes-based platform for building serverless and event-driven applications.
• ▸Supports autoscaling, including scale-to-zero, and traffic splitting.
• ▸Integrates with cloud-native tools, CI/CD, and messaging systems.
• ▸Ideal for microservices and serverless workloads.
• ▸Extensible and fully open-source under CNCF governance.

Project Structure

• ▸Dockerfile - container image definition
• ▸service.yaml - Knative Service manifest
• ▸event.yaml - Knative Event source configuration
• ▸config/ - optional configuration files
• ▸scripts/ - CI/CD and deployment scripts

Monetization

• ▸Serverless backend for SaaS
• ▸Event-driven platforms
• ▸Microservices with pay-per-use scaling
• ▸Cloud-native enterprise applications
• ▸Integration services in multi-cloud environments

Productivity Tips

• ▸Use templates for Knative manifests
• ▸Leverage cloud-native CI/CD pipelines
• ▸Monitor scaling and cold-starts
• ▸Reuse event triggers across services
• ▸Automate container builds and deployments

Basic Concepts

• ▸Service - Knative unit representing your workload
• ▸Revision - immutable snapshot of a service version
• ▸Configuration - desired state of a service
• ▸Route - traffic routing to revisions
• ▸Event - triggers that invoke serverless functions

Official Docs

• ▸https://knative.dev/
• ▸https://github.com/knative