-
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
Remove k8s.io/client-go/util/cert/triple #70966
Conversation
/assign @liggitt |
/approve some verify scripts are failing |
cdb7fd4
to
6c226ae
Compare
PTAL, re-formatted BUILD file to make verify happy |
/retest |
The package is unused.
6c226ae
to
09db5bc
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awly, liggitt 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 |
/lgtm |
Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966
Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966
Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966
Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966
* Use downstream triple package Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966 * WIP * Update fixtures * Override cluster-api dependency * Fix linting
* Use downstream triple package (#2910) Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966 * Remove test occurence of the upstream triple package
* Use downstream triple package Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966 * WIP * Update fixtures * Override cluster-api dependency * Fix linting
* Update client-go to 1.13.1 (#2911) * Use downstream triple package Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966 * WIP * Update fixtures * Override cluster-api dependency * Fix linting * Explicitly add errors package * Remove explicit dependency declaration
* Use downstream triple package Upstream removed the triple package[0], in order to be able to upgrade client-go we need to have a downsream version. [0] kubernetes/kubernetes#70966 * WIP * Update fixtures * Override cluster-api dependency * Fix linting * Split Kubermatic alerts into master and seed (#2909) * split kubermatic alerts into master and seed * rebuild outdated alerting rules * Remove clusterv1alpha1 clientset dependecy from cluster controller * Remove unused script * Use ctrlruntimeClient in pkg/handler/node_v1.go * Finish moving handler to ctrlruntimeClient * Remove GetAdminKubernetesClientForCustomerCluster from Clusterprovider * Use dynamic client for machines in conformance tester * Fix handler tests * Remove unused script * Fix linting * Actually fix linting error * Register schemes * Register clusterapi scheme in usercluster connection provider * Remove redundant options to the dynamic client * Filter list calls * Put impersonated users into system:authenticated group This is required for some very basic things like API discovery to work * Dep ensure * Add permissions to get nodes * Rbac generator script: Use a different metrics serving port than cluster controller * Fixup rbac for usercluster nodes * Dont fatalf outside of main * Print reconciling info on level four
The package is unused.
#71004