Results 29 issues of Andreas Karis

When a service has a named targetPort, ExternalTrafficPolicy=local, and host-networked backend pods, ovn-kubernetes incorrectly uses the named port string directly in OpenFlow rules instead of resolving it to the numeric...

area/unit-testing
area/e2e-testing
feature/services&endpoints

Prerequisite for this PR: https://github.com/ovn-kubernetes/ovn-kubernetes/pull/5691 ## Summary This PR adds support for named ports with varying target ports in Kubernetes services. Previously, OVN-Kubernetes enforced a one-to-one mapping between service ports...

area/unit-testing
area/e2e-testing
feature/services&endpoints

cherry-pick of https://github.com/cri-o/cri-o/pull/9349 and of https://github.com/cri-o/cri-o/pull/9405/ #### What type of PR is this? #### What this PR does / why we need it: #### Which issue(s) this PR fixes: ####...

lifecycle/stale
do-not-merge/hold
release-note-none
ok-to-test
dco-signoff: yes
jira/severity-moderate
jira/invalid-bug
jira/valid-reference

cherry-pick of https://github.com/cri-o/cri-o/pull/9350 #### What type of PR is this? #### What this PR does / why we need it: #### Which issue(s) this PR fixes: #### Special notes for...

lifecycle/stale
do-not-merge/hold
release-note-none
ok-to-test
dco-signoff: yes
jira/severity-moderate
jira/invalid-bug
jira/valid-reference

The test for BFD profile configuration was failing with frr-k8s because it expects a different log statement format. frr-k8s uses "log stdout" while metallb's frr uses "log file /etc/frr/frr.log" as...

kind/failing

### MetalLB Version upstream ### Deployment method Charts ### Main CNI upstream kind ### Kubernetes Version _No response_ ### Cluster Distribution _No response_ ### Describe the bug In https://github.com/metallb/frr-k8s/actions/runs/20138674053/job/57804252558?pr=373, the...

bug

When calling AddProcessEnv on a Generator instance that was created using zero-value initialization (Generator{}) rather than through New(), the envMap field would be nil. This caused a panic when attempting...

## Description When creating a `Generator` instance using zero-value initialization (`Generator{}`), calling `AddProcessEnv` causes a nil pointer panic. ## Steps to Reproduce 1. Create a `Generator` using zero-value initialization instead...

Version(s): Issue: Link to docs preview: QE review: - [ ] QE has approved this change. Additional information:

size/XS
lifecycle/rotten
jira/valid-reference