Marc Nuri

Hi @jessec, It's been while since I've worked on the project or even used it. As far as I remember, this usually happens when you've got spammy messages in your...

Hi @Khuzha. This is not the Minikube repository, but a repository for a GitHub Action that deploy Minikube in your pipeline. From you comment I guess you're not using this...

Hi @omus, There's already documentation about this in the [Optional input parameters](https://github.com/manusa/actions-setup-minikube#optional-input-parameters) section. However, if you missed it, it's probably not in the best place, or missing emphasis. Do you...

Last time I checked it was impossible because nested virtualization was not possible on GH action environment (https://github.com/actions/virtual-environments/issues/183). However, this may have changed, I will give it another look.

Yes. Could you please specify the authentication mechanism(s) you'd be interested in.

Hi, thanks for the input. My question is more about for you to clarify which of these authentication mechanisms are you specifically interested in.

The Fabric8-generated builders always initialize the List fields. The Fabric8-generated types have empty Maps and empty List as default values for these kind of fields. See: - https://github.com/fabric8io/kubernetes-client/issues/3625 - https://github.com/fabric8io/kubernetes-client/pull/4160...

> Commit issue is https://github.com/quarkusio/quarkus/commit/943784b27ed68a07c1f8fa3b9c7bb927a12e2b35: This is surprising, I'm not sure how this might be affecting the way the objects are serialized. > @manusa Are there any kubernetes serialization tests...

> In the absence of a serialization integration test (cc @manusa) Sorry for the delay, I expect to be able to work and complete this in a few days :sweat:.

> I'm intrigued on why the commit mentioned above causes a serialization issue. In the absence of a serialization integration test (cc @manusa), I need to do some further setup...