docs(ecosystem): add Knative Installation Guide (S2)#807
Merged
Conversation
End-user installation guide for the Knative Operator on ACP 4.2/4.3, matching the ecosystem solution format (front-matter + Overview/Supported Versions/Prerequisites/ Install/Verify/Quick Start/Cleanup/FAQ). Covers the ACP-specific install details: KnativeServing must live in the knative-serving namespace (Kourier bootstrap), spec.registry.override + explicit queue-sidecar-image (operands are referenced by digest and the platform image allowlist cannot rewrite digests), and a Serving quick start. Documents the single-stack-IPv6 limitation (upstream autoscaler statforwarder hardcodes EndpointSlice AddressType=IPv4; fixed on main via knative/serving#16591, not yet in a released 1.22.x). Version-variable slots are fenced with factory:auto:* markers for later automated per-release updates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Validated knative rc.8 end-to-end on ACP 4.1 (long-term C g2-c2, ARM, single-stack IPv4): operator CSV Succeeded, KnativeServing Ready, sample Knative Service Ready with URL. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Title + overview now name the product per the S2 support-level convention (S2 = "Alauda support for XXX"), distinguishing this curated upstream-CNCF-Knative listing from Alauda's own "DevOps Eventing v3". Technical OperatorHub references kept as-is. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Match the renamed OLM package/CSV (alauda-support-for-knative), verified against a real build: OperatorHub tile + plugin package + CSV/subscription names updated. Kept the operator's own Deployment name (knative-operator) and the upstream bundle image, which are unchanged. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the end-user installation guide for the Knative Operator (S2 ecosystem plugin) on ACP 4.2/4.3, following the existing ecosystem solution format (front-matter + Overview / Supported Versions / Prerequisites / Install / Verify / Quick Start / Cleanup / FAQ).
Covers the ACP-specific install details
KnativeServingmust live in theknative-servingnamespace (the Kourier bootstrap ConfigMap hardcodesnet-kourier-controller.knative-serving).spec.registry.override+ explicitqueue-sidecar-image— the Operator references operands by digest and the platform image allowlist cannot rewrite digest references, so without this the Serving pods hitImagePullBackOff.Known limitation documented
Single-stack IPv6 / IPv6-primary clusters: the upstream autoscaler stat-forwarder hardcodes the bucket-lease
EndpointSliceAddressTypeto IPv4, so the autoscalerCrashLoopBackOffs andKnativeServingnever becomes Ready. Fixed upstream onmain(knative/serving#16591), not yet in a released 1.22.x.Validation
id: TBD(assigned by CIadd_id.sh). Version-variable slots are fenced withfactory:auto:*markers for later automated per-release updates.