Improvement for k8s.io/docs/concepts/services-networking/ingress/

[EdmundsEcho]

[Edit: https://kubernetes.io/docs/concepts/services-networking/ingress/#examples]

The content is well presented. It made it easy for me to see a gap: how to map a /foo/*/bar to a service. The document indicates use of a wildcard for hosts, but not paths. Whether or not supported, this information might be useful if explicitly clarified. Thank you!!

[sftim]

/sig network
/kind feature
/language en

[sftim]

/priority backlog

[sftim]

/triage accepted

It'd be useful if you could put a hyperlink to that concept page in the description of the issue @EdmundsEcho. Are you willing to make that change?

[kundan2707]

@EdmundsEcho Can you describe section which needs improvement ?

[EdmundsEcho]

Here is the link to the section - path types/examples

If memory servers, the table of examples does a good job. I believe there was a gap of sorts for what I was needing.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[kundan2707]

/triage accepted

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

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