Possibility to set a port.name for the Service created for the MeshGatewayInstance
Would be nice to be able to set the port.name for the MeshGatewayInstance created Service: $ kubectl -n kuma-demo get svc edge-gateway -o yaml (...) ports: - name: "444" <<<<<<<<<<<<<<< nodePort: 31061 ...
Gerard Forns
3 months ago
in Mesh
0
Future consideration
MeshHTTPRoute: add support for https backend Services
At the moment MeshHTTPRoute can only connect to backend Services that has "appProtocol: http" Customer requires to connect to a Service that expose its own TLS
Gerard Forns
4 months ago
in Mesh
0
Under consideration
Policies are the features of Kong Mesh, and today they are too deep into the product. To create demand for Mesh in Konnect, we need to surface the capabilities in a more visible place. I suggest having "Policies" in the sidebar the same way we hav...
Marco Palladino
12 months ago
in Mesh
0
Future consideration
KUMA: Support Azure Managed Identity for authentication to postgresql on global control plane
Support "Azure Managed Identity" for authenticating a global control plane connecting to a postgres backend. Kuma global control plane only supports username and password to authenticate to PostgresSQL and doesn't support Azure MI which avoids hav...
Karl Kalckstein
over 2 years ago
in Mesh
0
Future consideration
Support for certificate rotation using cert-manager for General TLS Cert
We have a requirement to rotate the CP certificate automatically with cert-manager which is for the communication between CP and DP (kuma.controlPlane.tls.general settings).
Khairul Anuar
7 months ago
in Mesh
0
Under consideration
Kong Mesh GUI should redact both the certificate and key in displayed config dumps
Currently, the GUI redacts only the private keys but not the certificates Even if the client certificate without a private key is not useful we could consider hiding them both for extra security
Dimitri Koutsos
8 months ago
in Mesh
0
Future consideration
Create a new JWT policy -- could be "MeshJWT" -- to verify an incoming JWT. The goal is to be able to check: various claims (iss, aud, sub, azp, etc.) signature against an local/in-memory public key signature against a remote JWKS
Baptiste Collard
8 months ago
in Mesh
0
Under consideration