fix(tracing): Add KONG_TRACING environment variables to gatewayconfiguration template
This commit is contained in:
@@ -1,21 +1,3 @@
|
||||
# Bootstrap step, same category as installing the Flux Operator itself
|
||||
# (see ../README.md): this file was applied manually once
|
||||
# (`kubectl apply -f gitrepository.yaml`), because nothing can apply it
|
||||
# automatically before it exists — Flux can't fetch the object that tells it
|
||||
# where to fetch from. After that one-time apply, since this file lives
|
||||
# inside the k8s-platform repo that the GitRepository itself now points at,
|
||||
# a root Kustomization reconciling k8s-platform's own `flux/` directory
|
||||
# would keep it (and everything else here) self-managing going forward —
|
||||
# not scaffolded yet, out of scope for this file.
|
||||
#
|
||||
# secretRef -> k8s-platform-git-auth: SSH identity/known_hosts, created
|
||||
# directly via `kubectl create secret` (never written to a file), backed by
|
||||
# ~/.ssh/id_rsa (fingerprint SHA256:+BneVyWyJgOlDvISQ597e9YTXmd3GPpN9XHcItgQGKk,
|
||||
# already an authorized key on this Gitea account).
|
||||
#
|
||||
# Any other repo's Kustomization (e.g. dataplane-catalog's
|
||||
# kustomization.yaml) can reference this SAME GitRepository by name — one
|
||||
# GitRepository per source repo, not per consumer.
|
||||
apiVersion: source.toolkit.fluxcd.io/v1
|
||||
kind: GitRepository
|
||||
metadata:
|
||||
|
||||
Reference in New Issue
Block a user