Manuel Zapf
Manuel Zapf
#### Proposal Currently, Maesh can only configure 3 different middlewares on the Maesh Pods (Traefik v2). I think, more middlewares should become configurable: - [ ] AddPrefix - [ ]...
#### Proposal Implementing mTLS between Hosts, rather than between pods. This would require to route a connection between two maesh proxies (one per node), instead of only one (on the...
If a user provides us his certificate data, we could create a `TLSStore` and attach the cert as a default certificate. Partially fixes #185
## Feature We have received feedback, that the community would be willing to try out RC versions through Helm Charts, rather than having to manually install that. This is possible,...
We want to implement a configuration option in the helm chart, to automatically start Traefik with a certResolver which either uses the HTTP or TLS challenge (and provide the needed...
Currently, by doing a basic helm installation, the dashboard is reachable only via a port forward, as for example explained [here](https://containo.us/blog/traefik-v2-helm/). We want to introduce a second option, to have...
Fixes #150 This PR adds a specification for a simple UDP Route. Linked https://github.com/servicemeshinterface/smi-sdk-go/pull/69
**Describe the proposal** For now, there is no specification for UDP traffic. A simple spec could look like that (similiar to the TCPRoute) Example: ``` apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata:...
Linked to https://github.com/servicemeshinterface/smi-spec/issues/150 This PR introduces the concept of "UDPRoute", similar to TCP. As this is a new ressource, I also bumped the API Version. I hope, that's fine.
Currently, the helm chart is very flexible and can be seen as a scaffolding base for further configuration and or enhancements by our users. However, we will try to implement...