kubernetes#60525 introduced
Balanced attached node volumes feature gate to include volume
count for prioritizing nodes. The reason for introducing this
flag was its usefulness in Red Hat OpenShift Online environment
which is not being used any more. So, removing the flag
as it helps in maintainability of the scheduler code base
as mentioned at kubernetes#101489 (comment)
heketi that is dependency for glusterfs was updated to import a fork of jwt-go that fixes
a high severity CVE-2020-26160 by importing a forked repo (form3tech-oss/jwt-go) that fixes
the CVE as the original repo (dgrijalva/jwt-go) has a fix with breaking changes and
the repo is generally loosely maintained.
This fork is already being used in other places in kubernetes. Heketi 10.3.0 includes this fix.
NOTE: The vulnerable function is not used by heketi or kubernetes. So the vulnerable package is a
transitive dependency and this fix will reduce false postive CVE alerts on kubernetes
Bumped github.com/auth0/go-jwt-middleware to v1.0.0 which removes dgrijalva/jwt-go cleanly
Fixing test failures: pull-kubernetes-dependencies
Removing unused dependencies in replace block to fix test failures: pull-kubernetes-dependencies
Bump go-jwt-middleware to v1.0.1 to *not* pull in examples only deps
- verify memory manager data returned by `GetAllocatableResources`
- verify pod container memory manager data
Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
The test was flaking because the test was creating more connections
than expected.
Disabling connection pooling removes the flakes, and no more connections
are created that the necessary.
`--command-timeout` is supported in `ETCDCTL_API` version 3 and it is NOT supported in `ETCDCTL_API` version 2. Up to etcd 3.3 (inclusive) default version of `ETCDCTL_API` was 2. This change explicitly defines used `ETCDCTL_API` and allows usage of etcd versions below 3.4.
- Add `EncodeCaller` field in `encoderConfig`
- Use `ShortCallerEncoder` as `EncodeCaller
- Add CallerKey to encoderConfig
- Get frame of calling function based on what logging function is called (Info, Error, dPanic)
- Using obtained frame (if obtainable), set the Caller in the zapcore.Entry to indicate source code info
- Update tests to reflect the new format
Fix call frame depth implementation
- Implement zapLogger.WithCallDepth to implement the logr.CallDepthLogger interface
- Add a custom time encoder that use timeNow() stub instead of calling it manually in a zap Entry
- Update json logger unit tests and klog integration tests
Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
