Open lahabana opened 9 months ago
Triage: use case for ConfigMap in Datasource - Kong Mesh uses data source for MeshOPA plugin
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Description
Currently to add a cert to a gateway listener you need a kuma secret: https://kuma.io/docs/2.6.x/using-mesh/managing-ingress-traffic/builtin-listeners/#server-certificate-secrets
This is not very practical if you use cert-manager or something like this to manage your certs. We should be able to use regular kubernetes tls secrets: https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets
I think this can be more generic configMap and all other k8s secrets should be feasible. For compat I guess you'd need to not validate in k8s and in universal zone the policy would just be invalid.
I think this would greatly improve UX for pure k8s use-cases.