Skip to content

Remove hardcoded registry and image from ML func.yaml files#6610

Merged
knative-prow[bot] merged 1 commit intoknative:mainfrom
vamsi-01:fix/issue-6471-dynamic-func-registry
Mar 31, 2026
Merged

Remove hardcoded registry and image from ML func.yaml files#6610
knative-prow[bot] merged 1 commit intoknative:mainfrom
vamsi-01:fix/issue-6471-dynamic-func-registry

Conversation

@vamsi-01
Copy link
Copy Markdown
Contributor

Fixes #6471

Proposed Changes

Remove hardcoded registry and image values from ML service func.yaml files to enable dynamic registry configuration.

  • Remove registry: localhost:5000 from ML-bad-word-filter/func.yaml
  • Remove registry: localhost:5000 from ML-sentiment-analysis/func.yaml
  • Remove hardcoded deploy.image fields with SHA256 digests from both files

Problem

The bookstore tutorial ML services had hardcoded registry: localhost:5000 and image SHA256 digests in their func.yaml files. This prevented users from using their own container registries via the FUNC_REGISTRY environment variable or --registry flag, contradicting the tutorial documentation and causing deployment failures.

Solution

By removing these hardcoded values, the func CLI can now dynamically determine the registry from:

  1. FUNC_REGISTRY environment variable
  2. --registry command flag
  3. Interactive prompts (if not set)

Testing

Users can now successfully deploy with their own registry:

export FUNC_REGISTRY=docker.io/username
cd ML-bad-word-filter
func deploy -b=s2i -v
# ✅ Uses docker.io/username instead of localhost:5000

Fixes knative#6471

Remove the hardcoded 'registry: localhost:5000' and image SHA256
digests from the ML service func.yaml files in the bookstore tutorial.

This allows users to configure their own container registry via the
FUNC_REGISTRY environment variable or --registry flag, as documented
in the tutorial instructions. The hardcoded values prevented dynamic
registry configuration and caused deployment failures when users tried
to follow the tutorial with their own registries.

Changes:
- Remove registry: localhost:5000 from both func.yaml files
- Remove deploy.image with hardcoded SHA256 digests
- Allow func CLI to handle registry configuration dynamically
@knative-prow knative-prow bot requested review from nainaz and skonto March 31, 2026 11:40
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 31, 2026

Deploy Preview for knative ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 8586d69
🔍 Latest deploy log https://app.netlify.com/projects/knative/deploys/69cbb2956b1c180008bea7d7
😎 Deploy Preview https://deploy-preview-6610--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla bot commented Mar 31, 2026

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: vamsi-01 / name: Vamsi Mathala (8586d69)

@knative-prow knative-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 31, 2026
@knative-prow
Copy link
Copy Markdown

knative-prow bot commented Mar 31, 2026

Welcome @vamsi-01! It looks like this is your first PR to knative/docs 🎉

@dprotaso
Copy link
Copy Markdown
Member

/assign @Leo6Leo @lkingland

@Leo6Leo
Copy link
Copy Markdown
Member

Leo6Leo commented Mar 31, 2026

The changes looks good to me
/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
@Leo6Leo
Copy link
Copy Markdown
Member

Leo6Leo commented Mar 31, 2026

/approve

@knative-prow
Copy link
Copy Markdown

knative-prow bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leo6Leo, vamsi-01

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@knative-prow knative-prow bot merged commit fc153a6 into knative:main Mar 31, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

E2E Tutorial: Use dynamic port & url for func yaml

4 participants