-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Apiregistration v1alpha1→v1beta1 #45247
Conversation
4cb46a4
to
0a0d1c4
Compare
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.
No changes to the types themselves?
// +k8s:deepcopy-gen=package,register | ||
// +k8s:conversion-gen=k8s.io/kubernetes/vendor/k8s.io/kube-aggregator/pkg/apis/apiregistration | ||
|
||
// API Registration is responsible for registering an API `Group`/`Version` with |
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.
"Package v1beta1 contains the API Registration API, which is..."
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.
Done.
|
||
// API Registration is responsible for registering an API `Group`/`Version` with | ||
// another kubernetes like API server. The `APIService` holds information | ||
// about the other API server in `APIServiceSpec` type as well as general |
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.
Suggest explaining the types in comments on the types instead of in the package comment?
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 was thinking a general idea of what these APIs are doing is helpful. I think I can sell this instead of one pager Brian asked for, what do you think?
@@ -68,7 +68,7 @@ func New() *Generator { | |||
`+k8s.io/apimachinery/pkg/runtime`, | |||
`k8s.io/apimachinery/pkg/apis/meta/v1`, | |||
`k8s.io/apiserver/pkg/apis/example/v1`, | |||
`k8s.io/kube-aggregator/pkg/apis/apiregistration/v1alpha1`, | |||
`k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1`, |
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.
not a thing to change in this PR but I think mixing api group sources in the client generator default list like this is a bad precedent.
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.
ack
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.
Correct. No change to API types themselves. I looked at them and they look fine to me. Any suggestion?
|
||
// API Registration is responsible for registering an API `Group`/`Version` with | ||
// another kubernetes like API server. The `APIService` holds information | ||
// about the other API server in `APIServiceSpec` type as well as general |
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 was thinking a general idea of what these APIs are doing is helpful. I think I can sell this instead of one pager Brian asked for, what do you think?
@@ -68,7 +68,7 @@ func New() *Generator { | |||
`+k8s.io/apimachinery/pkg/runtime`, | |||
`k8s.io/apimachinery/pkg/apis/meta/v1`, | |||
`k8s.io/apiserver/pkg/apis/example/v1`, | |||
`k8s.io/kube-aggregator/pkg/apis/apiregistration/v1alpha1`, | |||
`k8s.io/kube-aggregator/pkg/apis/apiregistration/v1beta1`, |
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.
ack
// +k8s:deepcopy-gen=package,register | ||
// +k8s:conversion-gen=k8s.io/kubernetes/vendor/k8s.io/kube-aggregator/pkg/apis/apiregistration | ||
|
||
// API Registration is responsible for registering an API `Group`/`Version` with |
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.
Done.
@smarterclayton do you know why the proto thing changed all the binary blobs? I have seen this in a few places now. @deads2k any objections to making this API beta? |
This will break the sample apiserver config, I guess. We can fix it up once this merges. (fyi @cheftako ) |
Sounds good to me. |
Proto change was because protobuf tar/gzs up the .proto into the |
LGTM, @deads2k any other comments? |
@k8s-bot pull-kubernetes-federation-e2e-gce test this |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, lavalamp, mbohlool
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 45247, 45810, 45034, 45898, 45899) |
Promoting apiregistration api from v1alpha1 to v1beta1.
API Registration is responsible for registering an API
Group
/Version
withanother kubernetes like API server. The
APIService
holds informationabout the other API server in
APIServiceSpec
type as well as generalTypeMeta
andObjectMeta
. TheAPIServiceSpec
type have the mainconfiguration needed to do the aggregation. Any request coming for
specified
Group
/Version
will be directed to the service defined byServiceReference
(on port 443) after validating the target using providedCABundle
or skipping validation if development flagInsecureSkipTLSVerify
is set.
Priority
is controlling the order of this API group in the overalldiscovery document.
The return status is a set of conditions for this aggregation. Currently
there is only one condition named "Available", if true, it means the
api/server requests will be redirected to specified API server.