Summary

kumactl install control-plane does not respect user overrides of kuma env variables passed with the --env-var flag. This makes it difficult to customize an install past what is officially supported.

Steps To Reproduce

1. kumactl install control-plane --env-var KUMA_DEFAULTS_SKIP_MESH_CREATION=true
2. See the duplicate entries for KUMA_DEFAULTS_SKIP_MESH_CREATION i

When having a long list of services, it is quite difficult to find one since they are ordered based on their creation date and not alphabetically.

Due to pagination that is built in the API used by the Bridge, it does not make sense to sort the services on the client-side (each page would be sorted, but not the entire list of, e.g., services). Consequently, this issue should implement the sort

This is an enhancement request within the control plane functionality.

I do not use docker and Kubernetes has now deprecated docker.
How can I get kube-vip to work without docker? Is it possible to generate the manifest with crictl? Maybe kube-vip can provide a ready manifest to use in documentation so docker is not needed?

Ref the Issue

List of filters

We already have the tooling and we can run envoy-control locally while connecting to an environment set up with docker-compose. However, current configuration files aren't utilizing more advanced features, like mTLS and RBAC. That hinders experimenting and testing with these functionalities. Also, creating a configuration for envoy-control and envoy connecting to is from the ground up every time I

Following the example in cotroller-runtime, add this in main.go. The opeartor manifests need to be updated appropriately to make use of this endpint for the liveness and readiness checks.

https://github.com/GrigoriyMikhalkin/controller-runtime/blob/f616cceba110dd3c0a27d4e007563a85932b87ed/pkg/manager/example_test.go#L92-L124