* DRY on image name
* Enable e2e testing possibility on other architectures as well
* Replace correct image name in manifest
* Don't build binary anymore, it's now included in the image build
process
Signed-off-by: Manuel Rüger <manuel@rueg.eu>
use clientgofix library
add context parameter in verticalpodautoscaler
rename PodDisruptionsAllowed to DisruptionsAllowed because of PR 85863 in k8s repo
lint fixes and rename PodDisruptionsAllowed to DisruptionsAllowed in test file
run go mod tidy
The coordination.k8s.io/Lease used in e2e tests had an ownerReference,
referencing non-existing node "kube-master" (non-existing in default
Minikube deployments), so the lease was never created, and there was
an (ignored) error during deletion.
But, as a lease is automatically created for each node, there will always
be leases in e2e, so there's no need to add one.
- `make container` now uses already built `kube-state-metrics`
binary, if exists
- make it possible to use another CLI tool instead of docker (e.g. podman)
- use a separate profile for Minikube, when possible
As we are expecting v1 we should also create a watch on v1. Otherwise
see the following error in the logs:
"expected type *v1.ValidatingWebhookConfiguration, but watch
event object had type *v1beta1.ValidatingWebhookConfiguration"
- To allow other external Stores, remove the `FamilyByteSlicer` interface
and give access directly to `metric.Family`.
- Move functions present in `pkg/metric/generator.go` to a dedicated package
`generator` in `pkg/metric_generator/generator.go`.
Signed-off-by: cedric lamoriniere <cedric.lamoriniere@datadoghq.com>
Kubernetes has a new resource type: `VolumeAttachments`. They provide
helpful information on where a volume is attached and to alert on
unexpected attachment status (for example, differences between
information scraped from node-exporter and kube-state-metrics).
The collector adds a bunch of new metrics. Each VolumeAttachment (ie.,
each CSI-attached volume) will have one of each, so we do not overly
pollute the metrics space. Most metrics are rather unsurprising.
- `kube_volumeattachment_status_attachment_metadata`: provides a
label-like export of the attachment metadata map. Generalizing the
label-conversion function slightly helps at providing this metric.
- `kube_volumeattachment_created`: as VolumeAttachments are
automatically created and we already suffered from duplicate
`VolumeAttachments`, this can be invaluable for debugging
misattachments.
- `kube_volumeattachment_spec_source_persistentvolume`: will only be
generated when the volume source is of `PersistentVolume` type. The
other type `inlineVolumeSpec` is still alpha-level and hard to map to
metrics.
No end-to-end test manifest was added, as `VolumeAttachment`s are
automatically generated when mounting volumes.
Signed-off-by: Jens Erat <email@jenserat.de>
Sharding and autosharding introduced a number of manifests that are
very similar, but not identical to the standard manifests. This
introduces generating all manifests using jsonnet and moves them to
the explicit `/examples` directory.
main_test.go: Add model based test for sharding
In order to ensure a sharded system behaves equal to an unsharded
system, a model based test has been introduced. It scrapes an unsharded
setup and compares its output with the union of a sharded setup
therefore ensuring semantic equality.
Lili Cosic