<#7302 Allow HTTP registry for Knative Serving in ...
# flyte-github
a
#7302 Allow HTTP registry for Knative Serving in devbox Pull request opened by pingsutw Why are the changes needed? When using a local HTTP registry (e.g.
localhost:30000
) in the devbox, Python task pods can pull images successfully but Knative Serving revisions fail. By default, Knative's controller resolves image tags to digests via the registry over HTTPS, which fails for the local HTTP registry, blocking revision creation. What changes were proposed in this pull request? Patch the
config-deployment
ConfigMap in the
knative-serving
namespace via the devbox kustomization: •
registries-skipping-tag-resolving: "localhost:30000,kind-registry:5000"
— skip tag→digest resolution for the local registry. •
allow-http-registry: "true"
— allow the controller to talk to the registry over HTTP. How was this patch tested? Built the devbox bundle and verified Knative Service revisions can pull images from the local HTTP registry. Labels • fixed Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. flyteorg/flyte