POC Deployment Framework for Alloy Sandbox

Upstream Big Bang Repo

Upstream Big Bang branch for Alloy is epic-347/grafana-alloy-sandbox.

IMPORTANT: The epic-347/grafana-alloy-sandbox should be treated as the Development branch where no direct commits are made against the branch other than MRs. No direct commit should be taken on the epic-347/grafana-alloy-sandbox. The process for MR to the branch should:

1. Create a branch.
2. Make changes to the new branch.
3. Create a MR with the Observability team as the Reviewers.
4. Approve and merge branch.

Test values.yaml

A basic test values

domain: dev.bigbang.mil

flux:
  interval: 1m
  rollback:
    cleanupOnFail: false

istio:
  enabled: true

addons:
  grafanaAlloy:
    # git:
    #   tag: null
    #   branch: "<test-branch>"
    enabled: true
    # values:
    #   istio: # Waiting on istio issues completion before enabling
    #     enabled: true
    #     hardened:
    #       enabled: true

kyverno:
  enabled: true

kyvernoPolicies:
  enabled: true
#   values:
#     exclude:
#       any:
#       # Allows k3d load balancer to bypass policies.
#       - resources:
#           namespaces:
#           - istio-system
#           names:
#           - svclb-*
#     policies:
#       restrict-host-path-mount-pv:
#         parameters:
#           allow:
#           - /var/lib/rancher/k3s/storage/pvc-*

Istio Authorization Policies

A default allow nothing policy has been added and should be removed in favor of the umbrella policy, and as we add connectors additional authorization policies should be added. Potential connectors may be but are not limited to: - Grafana - Tempo - Prometheus - Loki

Some Istio Authorization Policies References: - Istio Auth Policies Epic Cleanup - Older Istio Auth Policies Epic

---

Last update: 2024-08-26 by Jimmy Ungerman