1. **When a simple FaaS with deep hyperscaler integration is required**
- Managed FaaS offerings such as AWS Lambda, Azure Functions, or Google Cloud Functions are more appropriate when tight native triggers, cloud-native IAM, and managed integrations are priorities and Kubernetes portability is not required.
2. **When operating small or edge Kubernetes clusters (k3s, low-memory nodes)**
- Community reports indicate Knative’s resource footprint and installation complexity can be too high for small clusters; alternatives such as OpenFaaS may be simpler for these environments.
- Source: https://www.reddit.com/r/kubernetes/comments/1h3zy2o/is_knative_still_a_no_go_for_small_edge_clusters_like_k3s/
3. **When workloads are primarily stateful or rely on StatefulSet semantics**
- Knative is designed for stateless workloads and may not meet requirements for ordered/stateful scaling.
- Source: https://community.ibm.com/community/user/aiops/blogs/guang-ya-liu/2021/08/09/serverless-model-to-reduce-footprint
4. **When cold-start latency cannot be tolerated and warm capacity cannot be funded**
- Vendor benchmarking shows substantial cold-start penalties; configuring minimum scale increases operational cost.
- Source: https://www.ibm.com/products/tutorials/exploring-cold-start-time-on-ibm-cloud-code-engine-with-the-knative-quarkus-bench
5. **When platform engineering capacity is unavailable**
- Self-managed Knative can require ongoing platform work (ingress, eventing backends, upgrades). Organizations lacking this capacity should evaluate managed serverless products (for example, Code Engine or Cloud Run) or simpler autoscaling approaches (such as KEDA).
1. **Stateless-oriented design**
Knative is designed for stateless, request-driven services. Community and vendor guidance indicate constraints when applying Knative semantics to stateful workloads.
- Source: https://community.ibm.com/community/user/aiops/blogs/guang-ya-liu/2021/08/09/serverless-model-to-reduce-footprint
2. **Cold starts**
Scale-to-zero can introduce high cold start latency; mitigation via minimum scale increases cost.
- Source: https://www.ibm.com/products/tutorials/exploring-cold-start-time-on-ibm-cloud-code-engine-with-the-knative-quarkus-bench
3. **Integration complexity (eventing backends and brokers)**
Integration with Kafka-compatible brokers and related tooling can require detailed configuration and debugging.
- Source: https://www.reddit.com/r/kubernetes/comments/1bijy10/anyone_managed_to_get_knative_working_with_redpanda_as_kafka_broker/
4. **Managed UI gaps**
Some users report that managed offerings may not expose all features via the UI, increasing CLI reliance.
- Source: https://www.trustradius.com/products/ibm-cloud-code-engine/reviews/all
5. **Roadmap and versioning visibility**
The Knative landing page is not a roadmap document; detailed version support and lifecycle information is available in service-specific IBM Cloud documentation.