Alexandre Perrin

how about `ASSUME_ALWAYS_YES=YES pkg whatever` ?

Well as far as I understand `ASSUME_ALWAYS_YES` cover every use case you provided, so maybe some clarifications and well chosen examples could help. Also note that it's `pkg(8)`, not `pkg(1)`.

I am interested by this too.

@alibo for update: * Support L7 traffic visualization in Hubble UI [has been implemented](https://github.com/cilium/hubble-ui/pull/198). * About Process Context for Syscall Visibility & Enforcement, We've released a OSS version of [Tetragon](https://github.com/cilium/tetragon)...

@lfundaro thanks! The PR LGTM. > warning No tests yet, waiting for Authors input first. I think we can start address testing now. I guess it would help if the...

@lfundaro yes using CI make sense to me. /cc @cilium/ci-structure

My two cents: I think we should go the cilium cli way, i.e. one CA shared for Hubble and ClusterMesh (and anything internal to Cilium). It's simpler that what we...

For context, the cluster name [is used as part for FQDNs names](https://github.com/cilium/cilium-cli/blob/57777b80f355da9db0a9ac7d14db9bacc1d0a491/install/certs.go#L22), see also [this commit](https://github.com/cilium/cilium-cli/commit/e6bc14b1bb0d50211727ee866cb1ff01bd2445ca). So our validation is stricter than what is allowed as kubeconfig context name.

Hi @slayer321, thanks for reviving this issue. We've recently switched to a Helm based approach for `cilium-cli` (since v0.11.0) so it's possible that upgrading to a different minor version is...

So if I understand correctly, we're looking to support upgrading to a different minor version. If correct, I suggest we close this issue and open a new one to add...