Federico Paolinelli

> @dusatvoj in my opinion we should try to come up with a dedicated metallb-config helm chart. Even if it will not solve the initial issue in the first place,...

> > > Helm has a special `crds` folder. That way helm will install the CRDs before other any other resources: https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you > > > > > > The problem...

Leaving this as open. Please note that this is STILL an issue if you enable both pod monitors and speaker monitors, as described in https://github.com/metallb/metallb/pull/1695#issuecomment-1311880582 What we can do is...

@goldyfruit please check https://github.com/metallb/metallb/pull/1695#issuecomment-1311880582

An easier way would be to panic in inv e2etest if no focus is provided, and print out the table of focus-es we need depending on the environment

Hey @sbshah97 , I changed my mind when writing this, and instead of automation, we could go simpler and do the following - running `inv e2etest` with no focus -...

@sbshah97 are you interested in working on this? Additionally, it would make sense to maintain / build the list of skips in a single configuration file that is used both...

> Hi, @fedepaol! I am interested in working on this issue. I am a first-time contributor to MetalLB. As of my understanding after reading your above comments, running `inv e2etest`...

Hi! Let me talk about the part "have the LB IP assigned from a dns query". This seems a reasonable feature to add. The part that I don't like, is...

> `We are trying to remove / migrate the configuration options from the service to something that is managed by the cluster administrator.` Not sure for which features this change...