Skip to content

Release Notes - 1.46.1💣

Please see our documentation page for more information on how to consume and deploy BigBang.

Upgrade Notices💣

Patch Notes:💣

The only change in this patch was an update to Loki (version 3.2.1-bb.3) to resolve incorrect labels for mTLS on monolith (see MR !2243 for more details). If you are not deploying Loki, or using Loki Scalable you will see no changes from 1.46.0.

Other upgrade notices from 1.46.0 are included here for your convenience. To view the full list of changes make sure to check the 1.46.0 release notes page.

ArgoCD:💣

  • The argocd chart went through quite a few changes on this update from chart version 4.10.8 to 5.5.7
  • These parameters have breaking changes:
  • configs.repositoryCredentials
  • server.additionalApplications
  • server.additionalProjects
  • Please refer to the upstream upgrade notice for more info on how to successfully upgrade and migrate to the new argocd-apps chart for managing additional applications and projects.
  • configs.repositoryCredentials has moved to configs.credentialTemplates
  • Some new parameters were added to the values file:
  • crds.install, crds.keep and crds.annotations for managing argo crds as helm resources
  • We are currently opting to manage the crds outside of helm until we can provide a more seamless upgrade experience
  • configs.params replaces command line arguments for containers

Loki:💣

Enough has changed in this new release for monolith that PVC names, storagePaths, and other items are all different. Existing monolith users who want to attempt to retain their existing data:

  • Ensure your value for persistentVolumeReclaimPolicy within your PV for storage-loki-0 is set to Retain
  • Save the name of your PersistentVolume eg: pvc-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
  • delete the existing monolith statefulset:
kubectl delete statefulset loki -n logging
  • delete the existing PVC for loki:
kubectl delete pvc storage-loki-0 -n logging
  • run the following:
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  labels:
    app.kubernetes.io/component: single-binary
    app.kubernetes.io/instance: logging-loki
    app.kubernetes.io/name: logging-loki
  name: storage-logging-loki-0
  namespace: logging
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 12Gi
  storageClassName: local-path
  volumeMode: Filesystem
  volumeName: YOUR_PV_NAME_HERE
EOF

This will pre-create the PersistentVolumeClaim and associate it with your existing PV. You can then perform the upgrade to the new 3.2.1 based release.

BETA Packages:💣

  • Loki has graduated from and is no longer in BETA
  • Please continue to provide feedback via Repo1 issues and MM chat if you run into any issues with Loki

Upgrades from previous releases💣

If coming from a version pre-1.45.0, note the additional upgrade notices in any release in between. The BB team doesn’t test/guarantee upgrades from anything pre-1.45.0.

Known Issues💣

  • On some k8s distros certain components in the kube-system namespace are unable to be scraped by Prometheus due to the services default network interface binding - More Information

As always, we welcome and appreciate feedback from our community of users. Please feel free to:

Future💣

Don’t see your feature and/or bug fix? Check out our epics for estimates on when you can expect things to drop, and as always, feel free to comment or create issues if you have questions, comments, or concerns.