-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 DomainInternal to status for Route and Service #1586
Changes from all commits
3029a48
ef5d583
bc23435
19e5aaf
aa4ae46
4fa9d06
3be8173
c37655b
80d5f73
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -78,6 +78,10 @@ status: | |
# along with a cluster-specific prefix (here, mydomain.com). | ||
domain: my-service.default.mydomain.com | ||
|
||
# domainInternal: A DNS name for the default (traffic-split) route which can | ||
# be accessed without leaving the cluster environment. | ||
domainInternal: my-service.default.svc.cluster.local | ||
|
||
traffic: | ||
# current rollout status list. configurationName references | ||
# are dereferenced to latest revision | ||
|
@@ -286,6 +290,11 @@ status: | |
# Note that logs may still be access controlled separately from | ||
# access to the API object. | ||
logUrl: "http://logging.infra.mycompany.com/...?filter=revision_uid=a1e34&..." | ||
|
||
# serviceName: The name for the core Kubernetes Service that fronts this | ||
# revision. Typically, the name will be the same as the name of the | ||
# revision. | ||
serviceName: myservice-a1e34 | ||
``` | ||
|
||
|
||
|
@@ -367,7 +376,11 @@ status: | |
# domain: The hostname used to access the default (traffic-split) | ||
# route. Typically, this will be composed of the name and namespace | ||
# along with a cluster-specific prefix (here, mydomain.com). | ||
domain: my-service.default.mydomain.com | ||
domain: myservice.default.mydomain.com | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hah, thanks for fixing this name! |
||
|
||
# domainInternal: A DNS name for the default (traffic-split) route which can | ||
# be accessed without leaving the cluster environment. | ||
domainInternal: myservice.default.svc.cluster.local | ||
|
||
# current rollout status list. configurationName references | ||
# are dereferenced to latest revision | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -131,6 +131,12 @@ type RouteStatus struct { | |
// +optional | ||
Domain string `json:"domain,omitempty"` | ||
|
||
// DomainInternal holds the top-level domain that will distribute traffic over the provided | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The field name There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would avoid 'internal' because it's not clear what internal is referring to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is for concistency with Domain. We'll change these later but to minimize the name changes, wanted to keep them consistent for now. Ok with changing in a follow on PR? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm most definitely OK with it as a follow-on :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we'll rename this and "domain" in v1alpha2. (Ville doesn't like it either, and I agree that it sounds a little weird given what it actually does). Up here in Seattle, we've bandied around Kubernetes 1.11 has beta support for CRD versioning, which will enable transitioning cleanly from v1alpha1 to v1alpha2. |
||
// targets from inside the cluster. It generally has the form | ||
// {route-name}.{route-namespace}.svc.cluster.local | ||
// +optional | ||
DomainInternal string `json:"domainInternal,omitempty"` | ||
|
||
// Traffic holds the configured traffic distribution. | ||
// These entries will always contain RevisionName references. | ||
// When ConfigurationName appears in the spec, this will hold the | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want a serviceName/domainInternal on Revision -- a Revision may have zero traffic and be non-routable if it is not addressed by any Route (and clients should not assume that they will know when that transition may happen). If clients want a name for a specific Revision, they should use the
traffic.name
subrouting feature in Route.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ServiceName predates this PR on RevisionStatus, but was missing from the spec.md. I left the docs since the values should be documented.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sounds fine, as long as we don't suggest this is a good way to reach the revision. Thanks for documenting!