#7262 feat: bake Knative manifests into devbox image at build time
Pull request opened by
AdilFayyaz
Why are the changes needed?
The devbox previously ran a post-start setup-knative step to install Knative, which added boot latency and a moving dependency. Bundling Knative Serving and net-kourier directly into the devbox manifests makes the devbox self-contained and reproducible.
What changes were proposed in this pull request?
• Added knative-serving 1.18.3 as a Helm dependency of charts/flyte-devbox (Chart.yaml/Chart.lock/values).
• Updated docker/devbox-bundled/Makefile to pull the knative-serving Helm repo and append a static kustomize/net-kourier.yaml to both complete.yaml and dev.yaml manifests.
• Patched both kustomize overlays (complete/, dev/) to wire Kourier as the ingress class, set config-domain to localhost, and delete the unused net-istio-* resources shipped by the chart.
• Removed the setup-knative invocation from make devbox-run (Knative is now pre-baked).
• Set ingressAppsPort: 30081 for app routing in manager/config.yaml and the chart values.
How was this patch tested?
• make -C docker/devbox-bundled manifests regenerates complete.yaml / dev.yaml cleanly with Kourier appended.
• make devbox-build && make devbox-run brings up the devbox; verify knative-serving and kourier-system pods
reach Ready without the old setup-knative step.
• Deploy a sample Flyte app and confirm it's reachable through the Kourier ingress at
<name>-<ns>.localhost:30081
.
• make devbox-stop cleans up.
Setup process
Screenshots
Check all the applicable boxes
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
Related PRs
Docs link
•
main
•
#6583
•
feat: bake Knative manifests into devbox image at build time 👈
flyteorg/flyte