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

Fix FilterSpecByPathsWithoutSideEffects to handle cases without slash #495

Open
Jefftree opened this issue Jul 30, 2024 · 3 comments
Open
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Jefftree
Copy link
Member

The current FilterSpecByPathsWithoutSideEffects behavior is wrong for paths without a trailing slash. See comment thread for more details: https://github.com/kubernetes/kubernetes/pull/123770/files#r1516319191

cc @liggitt

@liangyuanpeng
Copy link

I agree that the safest thing to achieve the goal is to exclude exact matches on prefix and prefix+slash. The required modification looks small.

Is this something you want? If so I'll open a PR.

+++	prefixSet := sets.NewString(keepPathPrefixes...)
	for path, pathItem := range sp.Paths.Paths {
		if !prefixes.HasPrefix(path) {
			continue
		}
+++		if !strings.HasSuffix(path, "/") {
+++			continue
+++		}
+++		if !prefixSet.Has(path) {
+++			continue
+++		}
		ret.Paths.Paths[path] = pathItem
	}

@Jefftree
Copy link
Member Author

Jefftree commented Sep 4, 2024

From a quick glance I don't think it's correct but seems close. Here's a useful test case

FilterSpecByPathsWithoutSideEffects([]{"/apis/group/v1beta1/"}, []{"/apis/group/v1"}, ...} should return "" because despite v1 being a prefix of v1beta1, we should really be matching for "/apis/group/v1/...".

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants