Antonin Stefanutti

For sure it is, and will always be, possible to break things by using Quarkus runtime properties directly. For that reason, having users relying on `--property=...` should be a last...

This comment may be outdated, and we may have to re-assess it. While it seems it's not yet possible to have different "service/userland" ports: https://github.com/knative/serving/issues/8471 It seems it's now possible...

> Multi-faceted controllers in k8s today may use SSR to determine which parts of their functionality are turned on - what might be analogous in our case to a specific...

I've amended the description with the above. as I realise I forgot to mention the original use case: > The use case is to have a controller / operator capable...

> I think istio support with mtls for the trainer component would already cover your needs. I wonder if Istio would support direct GPU interconnect and other high-performance network fabric.

> > > I think istio support with mtls for the trainer component would already cover your needs. > > > > > > I wonder if Istio would support...

> So on deman network policies that reference the job as owner will be automatically garbage collected with the job. That should be good enough I agree. NetworkPolicies are being...

> Not just an option, this should be enforced by default. I agree, +1 to this.

/remove-lifecycle stale

> > I have a clear idea for applying ingress policies and Istio sidecars. > > However, the main issue raised here is that during HPC jobs, the system interacts...