-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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 APIService conditions #43301
add APIService conditions #43301
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: deads2k
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
0f2f645
to
c45e3df
Compare
|
@deads2k will you rebase this one anytime soon? |
type APIServiceConditionType string | ||
|
||
const ( | ||
// ServiceAvailable indicates that the service exists and has endpoints |
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.
Given other changes: "indicates that the service exists and is reachable"
const ( | ||
ConditionTrue ConditionStatus = "True" | ||
ConditionFalse ConditionStatus = "False" | ||
ConditionUnknown ConditionStatus = "Unknown" |
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.
Are missing conditions treated as Unknown
, or is that decided per condition type?
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.
Are missing conditions treated as Unknown, or is that decided per condition type?
There is no guarantee that every condition will be present and there is no defaulting on these conditions.. How a client uses the data is up to them. There is a difference between "Unknown" and <missing>
, so hopefully clients know which one they want to test for.
assuming this is mostly replicating conditions from other API objects |
correct. |
c45e3df
to
4a97b3e
Compare
Comments addressed. |
4a97b3e
to
df3fdfa
Compare
df3fdfa
to
a3c9ec6
Compare
@k8s-bot cvm gce e2e test this |
type APIServiceConditionType string | ||
|
||
const ( | ||
// Available indicates that the service exists and is reachable |
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.
does this single condition type encompass indicating the resource/group/version was not claimed by another API service, and that the backend service was reachable?
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.
does this single condition type encompass indicating the resource/group/version was not claimed by another API service, and that the backend service was reachable?
Request from @smarterclayton. I think it lacks granularity, but I need something more than I need my preferred thing and as a summary it's an ok name.
one question, no other comments |
a3c9ec6
to
afc5ae1
Compare
top level stuff is straight generated. approving. |
LGTM, thank you @deads2k! |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue (batch tested with PRs 44044, 44766, 44930, 45109, 43301) |
@deads2k: The following test(s) failed:
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Adds conditions to the APIServiceStatus struct and fixes up generators that appear to have slipped.
The first condition is "ServiceAvailable" which will provide the status currently derived in the discovery handler that decides about whether to expose the version in discovery.
@kubernetes/sig-api-machinery-pr-reviews @liggitt @ncdc