UNCLASSIFIED - NO CUI

Skip to content

Add warning for redis or redis-bb

Danilo Patruccorequested to merge
test-redis-function into master

General MR

Summary

Warning on usage of subchart/internal redis

Relevant logs/screenshots

Example with no redis or redis-bb value in values.yaml file

Release "bigbang" does not exist. Installing it now.
NAME: bigbang
LAST DEPLOYED: Wed Oct 15 10:20:41 2025
NAMESPACE: bigbang
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for supporting Platform One!


PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Example with redis or redis-bb enabled = true in values.yaml file

Release "bigbang" has been upgraded. Happy Helming!
NAME: bigbang
LAST DEPLOYED: Wed Oct 15 10:22:11 2025
NAMESPACE: bigbang
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
Thank you for supporting Platform One!


PLATFORM ONE REDIS WARNING:
  You have enabled an internal redis instance in the BigBang configuration.
  Platform One does not support this option for production deployments because your persistent data can be permanently lost.
  This option should only be used for development or CI pipelines.
PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Redis-bb enabled set to false

Release "bigbang" has been upgraded. Happy Helming!
NAME: bigbang
LAST DEPLOYED: Wed Oct 15 10:27:28 2025
NAMESPACE: bigbang
STATUS: deployed
REVISION: 3
TEST SUITE: None
NOTES:
Thank you for supporting Platform One!


PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Redis under upstream enabled set to false

addons:
  minioOperator:
    enabled: false
  argocd:
    redis-bb:
      enabled: false
    enabled: true
    values:
      upstream:
        istio:
          redis:
            enabled: false
        configs:
          secret: 


Release "bigbang" has been upgraded. Happy Helming!
NAME: bigbang
LAST DEPLOYED: Wed Oct 15 10:35:16 2025
NAMESPACE: bigbang
STATUS: deployed
REVISION: 4
TEST SUITE: None
NOTES:
Thank you for supporting Platform One!


PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Redis under upstream enabled set to true

addons:
  minioOperator:
    enabled: false
  argocd:
    redis-bb:
      enabled: false
    enabled: true
    values:
      upstream:
        istio:
          redis:
            enabled: true
        configs:
          secret: 



PLATFORM ONE REDIS WARNING:
  You have enabled an internal redis instance in the BigBang configuration.
  Platform One does not support this option for production deployments because your persistent data can be permanently lost.
  This option should only be used for development or CI pipelines.
PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Redis-bb and Redis both set to enable true:

addons:
  minioOperator:
    enabled: false
  argocd:
    redis-bb:
      enabled: true
    enabled: true
    values:
      upstream:
        istio:
          redis:
            enabled: true
        configs:
          secret: 

Release "bigbang" has been upgraded. Happy Helming!
NAME: bigbang
LAST DEPLOYED: Wed Oct 15 10:50:14 2025
NAMESPACE: bigbang
STATUS: deployed
REVISION: 7
TEST SUITE: None
NOTES:
Thank you for supporting Platform One!


PLATFORM ONE REDIS WARNING:
  You have enabled an internal redis instance in the BigBang configuration.
  Platform One does not support this option for production deployments because your persistent data can be permanently lost.
  This option should only be used for development or CI pipelines.
PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Added Redis as package


packages:
  redis:
    enabled: true
    namespace:
      name: redis
    git:

Release "bigbang" has been upgraded. Happy Helming!
NAME: bigbang
LAST DEPLOYED: Wed Oct 15 10:57:44 2025
NAMESPACE: bigbang
STATUS: deployed
REVISION: 14
TEST SUITE: None
NOTES:
Thank you for supporting Platform One!


PLATFORM ONE REDIS WARNING:
  You have enabled an internal redis instance in the BigBang configuration.
  Platform One does not support this option for production deployments because your persistent data can be permanently lost.
  This option should only be used for development or CI pipelines.
PLATFORM ONE LOGGING WARNING:
  You have enabled Alloy with logging but a logging destination has not been configured.
  Resolution Options:
    1. Enable Loki: Set .Values.loki.enabled=true
    2. For external or custom destinations, add an additional destination of type "loki": Configure .Values.alloy.additionalDestinations see https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/destinations
    3. Disable Alloy Logging: Set .Values.alloy.alloyLogs.enabled=false

Final test value file:

Tested with the following:

  • all enabled
  • all disabled
  • some enabled & some disabled (e.g. redis enabled redis-bb disabled)
  • only one app redis enabled
  • only one app redis disabled
monitoring:
  enabled: false
grafana:
  enabled: false
neuvector:
  enabled: false
loki:
  enabled: false
tempo:
  enabled: false
kyvernoReporter:
  enabled: false
kiali:
  enabled: false
addons:
  harbor:
    enabled: true
    redis-bb:
      enabled: false
    upstream:
      auth:
        enabled: false
      istio:
        redis:
          enabled: true
  minioOperator:
    enabled: false
  authservice:
    enabled: true
    redis:
      enabled: false
    redis-bb:
      istio:
        redis:
          enabled: false
  argocd:
    redis-bb:
      enabled: false
    enabled: true
    values:
      upstream:
        istio:
          redis:
            enabled: false
        configs:
          secret: 
            argocdServerAdminPassword: ''
kyvernoPolicies:
  values:
    bbtests:
      enabled: false
    policies:
      update-automountserviceaccounttokens:
        namespaces:
          - namespace: argocd
            pods:
              allow:
              - argocd-argocd-script-test
kyverno:
  values:
    bbtests:
      enabled: false
bbctl:
  enabled: false

packages:
  redis:
    enabled: false
    namespace:
      name: redis
    git:
      repo: "https://repo1.dso.mil/big-bang/product/maintained/redis.git"
    values:
      istio:
        enabled: true
      networkPolicies:
        enabled: true
        controlPlaneCidr: 172.16.0.0/12
      upstream:
        global:
          redis:
            password: ""

Note:

This assumes that the redis or redis-bb enable: true is set in the anywhere in the value file used by the customer, meaning that if redis is set upstream then BB won't render the message.

Linked Issue

issue

Upgrade Notices

The Big Bang deployment will now output a message saying that Redis is enabled and it should only be used in Dev/testing/CI if Redis or Redis-bb are set to enabled: true

Edited by Andrew Shoell

Merge request reports

UNCLASSIFIED - NO CUI