Jeff McCune 6e545b13dd (#104) Deploy crunchy monitoring stack for ZITADEL ...

Not exposed via the ingress gateway, but accessible via

    kubectl port-forward svc/crunchy-grafana 3000

Refer to [day two monitoring][1].  This is pretty much a straight copy
of the upstream kustomize configs at [2].

[1]: https://access.crunchydata.com/documentation/postgres-operator/5.5/tutorials/day-two/monitoring
[2]: https://github.com/CrunchyData/postgres-operator-examples/tree/main/kustomize/monitoring

2024-04-04 15:40:07 -07:00

..

clusters

(#104) Deploy crunchy monitoring stack for ZITADEL

2024-04-04 15:40:07 -07:00

certificates.cue

(#47) Bind ALL VirtualServices to the default gateway

2024-04-03 14:56:40 -07:00

meshconfig.cue

(#82) ingressgateway ExtAuthzHttp provider

2024-04-01 16:53:11 -07:00

namespaces.cue

(#47) Remove the prod-iam-zitadel namespace

2024-04-03 15:10:30 -07:00

platform_projects.cue

(#47) Bind ALL VirtualServices to the default gateway

2024-04-03 14:56:40 -07:00

project_constraints.cue

(#64) Manage one system namespace per project

2024-03-26 12:23:01 -07:00