Tobias Klauser

In principle this shouldn't be a problem and the LLMNR RFC explicitly allows for this, see [section 4.2 of RFC 4795](https://tools.ietf.org/html/rfc4795#section-4.2) llmnrd currently doesn't support conflict resolution, so it will...

In principle I don't see a problem with responding to two (or more names). However, llmnrd currently only supports one name at a time, but support for it should be...

related to https://github.com/cilium/cilium/issues/24246

@gopherbot please consider this for backport to 1.20, it's a regression.

> * The [upload artifacts](https://github.com/cilium/hubble/blob/d09c85c0672696dd22689a443ac3a6afda765c54/.github/workflows/release.yml#L31-L38) action during releases fails quite often and needs manual restarts (c.f. upstream issue [Repeated failures uploading binaries, `curl: (55) OpenSSL SSL_write: Connection reset by peer,...

Marked for backports to `v1.14` and `v1.15` as these are using little-vm-helper action v0.0.19 with the new parameter name as well.

/test