This "RecentStats: unable to find data in memory cache" error is not actionable,
in terms of kubelt, if the entry is not found in the memory cache.
Thus, proposing it to lower the log level to info.
Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
This update dropped the otelgrpc → cloud.google.com/go/compute dependency,
among others. This dropped out because genproto cleaned up it's dependencies
on google cloud libraries, and otel updated - details in #113366.
The plugin help text was not consistent - using `ns` in some cases and
`kubectl ns` in others.
With this change we always have `kubectl ns`:
$ kubectl ns -h
View or set the current namespace
Usage:
kubectl ns [new-namespace] [flags]
Examples:
# view the current namespace in your KUBECONFIG
kubectl ns
# view all of the namespaces in use by contexts in your KUBECONFIG
kubectl ns --list
# switch your current-context to one that contains the desired namespace
kubectl ns foo
Flags:
...
-h, --help help for kubectl ns
* Remove deprecated kubectl exec command execution without dash
* Use command execution with dash in kubectl exec
* Modify unit tests to only use command after dash
Although CBOR can roundtrip arbitrary precision integers, they don't roundtrip properly through
Unstructured because Unstructured is limited to the dynamic numeric types int64 and float64. Rather
than serializing them (and potentially losing information), reject them explicitly with an error.
testify is used throughout the codebase; this switches mocks from
gomock to testify with the help of mockery for code generation.
Handlers and mocks in test/utils/oidc are moved to a new package:
mockery operates package by package, and requires packages to build
correctly; test/utils/oidc/testserver.go relies on the mocks and fails
to build when they are removed. Moving the interface and mocks to a
different package allows mockery to process that package without
having to build testserver.go.
Signed-off-by: Stephen Kitt <skitt@redhat.com>
According to the contract of json.Unmarshaler: "UnmarshalJSON must copy the JSON data if it wishes
to retain the data after returning." If the input is not copied, the underlying array of Raw could
be reused by the caller of UnmarshalJSON, and any modifications would be visible in Raw (and vice
versa).
