-
Notifications
You must be signed in to change notification settings - Fork 332
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
Drop spec.generation support #234
Drop spec.generation support #234
Conversation
583ab64
to
b9969e7
Compare
/assign @vaikas-google I'll be glad to see this gone. I'll let @vaikas-google do the honors :) |
awesome!! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, vaikas-google The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
With Kubernetes 1.11+ metadata.generation now increments properly when the status subresource is enabled on CRDs For more details see: knative/serving#643
b9969e7
to
6b780d9
Compare
The following is the coverage report on pkg/.
|
/lgtm @dprotaso Remove the hold when you are ready to pull the trigger on the other repos? |
everything went green /hold cancel |
…ve#234) 1. add list cluster namespaces implemention for MultiClusterClient 2. add MultiClusterClient into testing context Signed-off-by: jtcheng <jtcheng@alauda.io>
With Kubernetes 1.11+ metadata.generation now increments properly
when the status subresource is enabled on CRDs
Thus we can drop
spec.generation
Addresses part of knative/serving#643
Holding for now - since I will prepare PRs in other repos incorporating this change
/hold