Patryk Małek

`openmetrics`: `openmetrics_endpoint` doesn't support Kubernetes' bearer token but `prometheus_url` does

2

**Additional environment details (Operating System, Cloud provider, etc):** Kubernetes, kind **Problem statement** https://docs.datadoghq.com/integrations/guide/prometheus-host-collection/#parameters-available mentions the usage of `bearer_token_path`, `bearer_token_auth` and `openmetrics_endpoint` but no `prometheus_url`, in order to make the agent...

Backport PRs created with this action trigger pull_request labelled event not pull_request

1

### Problem statement We have a CI that is configured to run on `pull_request` events on all branches: https://github.com/Kong/kubernetes-ingress-controller/blob/beac200706f81b9420d21b00653fd59a4040f8bb/.github/workflows/pr_checks.yaml#L12-L14. Given an exemplar PR https://github.com/Kong/kubernetes-ingress-controller/pull/4128 that got a label to be...

### Problem statement Recently we've introduced the `toolchain` keyword (as described in: https://go.dev/blog/toolchain) in our Go project https://github.com/Kong/kubernetes-ingress-controller/commit/4422d519b3912f524cacb93aec6c973ab0e51b86 and since then our [fossa scans yield](https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6104722910/job/16567157127#step:3:88): ``` An issue occurred >>>...

Tests: can't use e2e-framework's `[After|Before]EachFeature` to get conditional setup / teardown run

1

### Problem statement Related to https://github.com/Kong/kubernetes-ingress-controller/pull/4823 Can't use `[After|Before]EachFeature` like so: ``` tenv.BeforeEachFeature( featureSetup(env.Cluster(), runID), injectKlient(), ) tenv.AfterEachFeature( featureTeardown(env.Cluster(), runID), ) ``` because regardless of the skip criteria, we'd get...

`TestIngressRecoverFromInvalidPath` is failing when changing router flavor to `expressions`

3

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior After fixing the router flavor setting in integration tests #5112 (which...

Allow customization of DNS so that `<service>.<ns>.svc` resolve and do not require `cluster.local` suffix

1

**Is your feature request related to a problem? Please describe.** When trying to run locally, software that uses k8s dns names like `..svc` orbstack doesn't resolve those on the host....

### Problem statement Currently, there exist many test helper/util/(?) packages e.g. - https://github.com/Kong/kubernetes-ingress-controller/tree/main/test/helpers - https://github.com/Kong/kubernetes-ingress-controller/blob/main/test/internal - https://github.com/Kong/kubernetes-ingress-controller/blob/5a52b842e01c0462c5a5421b96671faf065cd5d4/test/tcp_utils.go - https://github.com/Kong/kubernetes-ingress-controller/tree/main/internal/util/test This issue tracks the reorganization of those into 1 or 2...

### Problem statement `TestKongArgoAddon` fails on CI: ``` kong_argo_addon_test.go:36: building the testing environment and Kubernetes cluster W0412 10:03:09.638889 12450 warnings.go:70] metadata.finalizers: "resources-finalizer.argocd.argoproj.io": prefer a domain-qualified finalizer name to avoid accidental...

### Problem statement https://github.com/Kong/kubernetes-testing-framework/pull/845 introduces an ability to deploy multiple kong addons into a cluster. `environment.Builder` allows adding addons via [`WithAddons()`](https://github.com/Kong/kubernetes-testing-framework/blob/0dab64760e88b208e0b7e4dd52a2ada3ca71e230/pkg/environments/builder.go#L46-L53) The problem with the current implementation is that it...

### Problem statement When trying to deploy the `metallb` addon (or another addon that depend on it) and there already exists an `IPAddressPool` which conflicts with the one to be...