Expanding Visibility Setting #198
Labels
kind/feature-request
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Comments
|
This should be worked on Gateway API v0.4.0 or later as Gateway API still changes the design. |
nak3
added a commit
to nak3/serving
that referenced
this issue
Dec 6, 2021
This patch removes `networking.knative.dev/visibility` validation. Curently only `cluster-local` can be specified. Fix knative#8185 Part of knative-extensions/net-gateway-api#198
nak3
added a commit
to nak3/serving
that referenced
this issue
Dec 6, 2021
This patch removes `networking.knative.dev/visibility` validation. Curently only `cluster-local` can be specified. Fix knative#8185 Part of knative-extensions/net-gateway-api#198
nak3
added a commit
to nak3/serving
that referenced
this issue
Dec 6, 2021
This patch removes `networking.knative.dev/visibility` validation. Curently only `cluster-local` can be specified. Fix knative#8185 Part of knative-extensions/net-gateway-api#198
knative-prow-robot
pushed a commit
to knative/serving
that referenced
this issue
Dec 8, 2021
This patch removes `networking.knative.dev/visibility` validation. Curently only `cluster-local` can be specified. Fix #8185 Part of knative-extensions/net-gateway-api#198
|
This issue is stale because it has been open for 90 days with no |
github-actions
bot
added
the
lifecycle/stale
nak3
added
lifecycle/frozen
|
Following up here we may want to add similar functionality that just landed in the net-istio about a greater control of gateway selection Details in the feature track https://docs.google.com/document/d/12X1-9nhjAhpf-Wlt3RbdoMbvx31zFBva/edit?pli=1#heading=h.gjdgxs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The background is described in original issue - knative/serving#6642
The original design introduced
RealmandDomainCRDs but it stopped developing as the design is difficult to align with Ingress v2 (Gateway API).The new Gateway API controller has visibility based setting (it maps one Visibility to one Gateway) like:
https://github.com/knative-sandbox/net-gateway-api/blob/9218e0d7ff957b2ea4ec106abfdd018988bf72a3/config/config-gateway.yaml#L42-L50
So it will be possible to achieve the goal what knative/serving#6642 tried to address.
The text was updated successfully, but these errors were encountered: