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.

Sign up for GitHub

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

Jump to bottom

One httpproxy supports multiple fqdn #5649

Closed
yangyy93 opened this issue Aug 1, 2023 · 5 comments
Closed

One httpproxy supports multiple fqdn #5649

yangyy93 opened this issue Aug 1, 2023 · 5 comments
Labels
area/httpproxy Issues or PRs related to the HTTPProxy API. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@yangyy93
Copy link
Member

yangyy93 commented Aug 1, 2023

Now a root http proxy supports one fqdn field, but now we have a requirement that multiple different domain names can access the same service. Now I have to create multiple root httpproxy and multiple child httpproxy to realize this function. If a root httpproxy can support multiple domain names, it can simplify a lot of configuration. Envoy's domain itself supports multiple domain names.Is it possible to consider updating fqdn as an array?
@yangyy93 yangyy93 added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Aug 1, 2023
@tsaarni
Copy link
Member

tsaarni commented Aug 4, 2023

Linking (somewhat) related discussion about pluralization of subjectName field in HTTPProxy : #5520 and the API conventions doc link #5520 (comment).

@yangyy93
Copy link
Member Author

yangyy93 commented Aug 8, 2023

Yes, implementations for singular and plural compatibility are a concern. Will you consider increasing the plural form of fqdn on this basis?

@github-actions
Copy link

github-actions bot commented Oct 8, 2023

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2023
@skriss skriss added the area/httpproxy Issues or PRs related to the HTTPProxy API. label Nov 2, 2023
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 3, 2023
@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 4, 2024

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 8, 2024

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/httpproxy Issues or PRs related to the HTTPProxy API. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tsaarni @skriss @yangyy93