Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add localhost registry to the set avoiding tag resolution as a workaround for #467 #468

Merged
merged 2 commits into from
Nov 14, 2023

Conversation

evankanderson
Copy link
Contributor

Changes

  • 🐛 Add default registries-skipping-tag-resolving setting for localhost registry when configured. This saves a lot of debugging for new folks, since the actual registry will be reachable at kind-registry:5000 in the containerd config, but serving doesn't have equivalent configuration.

/kind bug

Fixes #467

Release Note

Automatically configure tag resolution to avoid errors when using `--registry` flag for `kn quickstart kind`.

Docs

We don't document the `--registry` flag today (though maybe we should?).

@knative-prow knative-prow bot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 11, 2023
@knative-prow knative-prow bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 11, 2023
if err := runCommand(ignoreRegistry); err != nil {
return fmt.Errorf("tag resolving configuration: %w", err)
}
fmt.Println(" Tag resolving configuration patched...")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add the why not so much the what or how. I.e. how it is patched, what does this change ?. Also not sure if the message itself might be too noisy and potentially confusing for a beginner who is running the quickstart. At the end it should just work, and a beginner should not worry about what a "tag resolving configuration" is.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy to remove the comment if we want, it's hard to briefly explain the feature.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Switched this to "enabling local registry deployments"

@rhuss
Copy link
Contributor

rhuss commented Nov 13, 2023

Thanks, looks good to me in general. For the Release notes I would add that this only affects kind based setups (not minikube), and yes, I think we should document --registry behaviour :-), but maybe not in this PR.

@psschwei
Copy link
Contributor

yes, I think we should document --registry behaviour

agree, somebody probably should've done that 😟 😆

Part of me also thinks that perhaps we should switch the default here (i.e. create the registry by default but allow users to opt out by passing a --no-registry flag), since I'm assuming a majority of folks are passing the registry flag...

@evankanderson
Copy link
Contributor Author

I'd be happy to change the default for the --registry flag for 1.13; I'd like to cherry-pick this bug-fix back to 1.11 if that's okay.

@evankanderson
Copy link
Contributor Author

From the earlier history, it looked like we disabled the registry flag due to Podman compatibility concerns, so we may want to check that before we re-enable it.

@psschwei
Copy link
Contributor

I'd be happy to change the default for the --registry flag for 1.13; I'd like to cherry-pick this bug-fix back to 1.11 if that's okay.

👍 I'm on board with merging/cherry picking your fix as is. I had meant my comment as something possibly for the future, but turns out I was misremembering how the registry flag works (for some reason I was thinking it was required rather than an optional component), so let's just pretend I never said anything about that 😉

Copy link
Contributor

@psschwei psschwei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 14, 2023
Copy link

knative-prow bot commented Nov 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: evankanderson, psschwei

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

The pull request process is described here

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 Nov 14, 2023
@knative-prow knative-prow bot merged commit 9cdb6ed into knative-extensions:main Nov 14, 2023
22 checks passed
@psschwei
Copy link
Contributor

/cherry-pick release-1.12
/cherry-pick release-1.11

@knative-prow-robot
Copy link

@psschwei: new pull request created: #469

In response to this:

/cherry-pick release-1.12
/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@psschwei
Copy link
Contributor

/cherry-pick release-1.11

@knative-prow-robot
Copy link

@psschwei: new pull request created: #470

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Local registry not working with tag -> digest resolution
4 participants