Friedrich

Results 11 issues of Friedrich

this is a followup to #14962 - [ ] add the `topology` key `zone` to `nats-server`'s `sts` to assure that, in case there are multiple zones available, the pods are...

area/eventing

**Description** In [epp](https://github.com/kyma-project/kyma/blob/e31467aff6de997979a5318e9ca5f53e6dd808d0/components/event-publisher-proxy/pkg/metrics/collector.go#L13) we don't follow [prometheus' naming conventions](https://prometheus.io/docs/practices/naming/) for quantities with units. The issue is when metrics are consumed the actual unit is unknown. All metrics exposed by our...

area/eventing

title says it all

do-not-merge/hold
size/XS

renamed all remaining test files from `_test.go` to `_unit_test.go` or `integration_test.go` accordingly. All test files in `event-publisher-proxy` should follow this naming pattern now.

do-not-merge/hold
size/XS

https://github.com/nats-io/nats-server/releases

area/eventing

[pre-main-kyma-gardener-gcp-eventing-upgrade](https://status.build.kyma-project.io/job-history/gs/kyma-prow-logs/pr-logs/directory/pre-main-kyma-gardener-gcp-eventing-upgrade) is flaky and regularly fails with: ``` 1) Eventing tests with Nats backend In-cluster event should have correct tracing spans: Error: cannot get jaeger trace 404: Not Found: {"data":null,"total":0,"limit":0,"offset":0,"errors":[{"code":404,"msg":"trace...

kind/bug

Clean up the [Makefile in epp](https://github.com/kyma-project/kyma/blob/main/components/event-publisher-proxy/Makefile): - remove the `include` of the generic Makefile. - For the modularisation of our components we need to be independent of the common, generic...

area/eventing

looks like the jaeger pods are not ready after upgrade so let's just wait for them.

size/M