| Remove references to openstack and cinder Signed-off-by: Davanum Srinivas <davanum@gmail.com> Kubernetes-commit: 9bbf01bae93600d3314bce0acbff1f3a0a42e74b | 4 年前 |
| Remove references to openstack and cinder Signed-off-by: Davanum Srinivas <davanum@gmail.com> Kubernetes-commit: 9bbf01bae93600d3314bce0acbff1f3a0a42e74b | 4 年前 |
| remove import doc comments The "// import <path>" comment has been superseded by Go modules. We don't have to remove them, but doing so has some advantages: - They are used inconsistently, which is confusing. - We can then also remove the (currently broken) hack/update-vanity-imports.sh. - Last but not least, it would be a first step towards avoiding the k8s.io domain. This commit was generated with sed -i -e 's;^package \(.*\) // import.*;package \1;' $(git grep -l '^package.*// import' | grep -v 'vendor/') Everything was included, except for package labels // import k8s.io/kubernetes/pkg/util/labels because that package is marked as "read-only". Kubernetes-commit: 8a908e0c0bd96a3455edf7e3b5f5af90564e65b0 | 1 年前 |
| client-go: remove obsolete auth plugins from examples The azure and gcp plugins no longer do anything other than point to the corresponding external credential plugins. Client code should no longer try to load them, so they should be removed from the examples. Signed-off-by: Stephen Kitt <skitt@redhat.com> Kubernetes-commit: 4531c6de760ec42941d9f509103f1b29c88bfae0 | 1 年前 |
| chore(leader-election): modify leader-election comment to OnStoppedLeading callback is always called when the LeaderElector exits, even if it did not start leading. Kubernetes-commit: 7d2fbc7cfd49bca7d58160ed25dfd1f838629bb9 | 1 年前 |
| client-go: remove obsolete auth plugins from examples The azure and gcp plugins no longer do anything other than point to the corresponding external credential plugins. Client code should no longer try to load them, so they should be removed from the examples. Signed-off-by: Stephen Kitt <skitt@redhat.com> Kubernetes-commit: 4531c6de760ec42941d9f509103f1b29c88bfae0 | 1 年前 |
| client-go/tools/cache: add APIs with context parameter The context is used for cancellation and to support contextual logging. In most cases, alternative *WithContext APIs get added, except for NewIntegerResourceVersionMutationCache where code searches indicate that the API is not used downstream. An API break around SharedInformer couldn't be avoided because the alternative (keeping the interface unchanged and adding a second one with the new method) would have been worse. controller-runtime needs to be updated because it implements that interface in a test package. Downstream consumers of controller-runtime will work unless they use those test package. Converting Kubernetes to use the other new alternatives will follow. In the meantime, usage of the new alternatives cannot be enforced via logcheck yet (see https://github.com/kubernetes/kubernetes/issues/126379 for the process). Passing context through and checking it for cancellation is tricky for event handlers. A better approach is to map the context cancellation to the normal removal of an event handler via a helper goroutine. Thanks to the new HandleErrorWithLogr and HandleCrashWithLogr, remembering the logger is sufficient for handling problems at runtime. Kubernetes-commit: 4638ba971661497b147906b8977ae206c9dd6e44 | 2 年前 |
| client-go: remove reference to TPR in examples 5 years after third party resources were removed, we're probably just confusing readers with this reference. Kubernetes-commit: d21fc6e762276747e3306cfaf27b0ce1201071c2 | 3 年前 |