UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects
Commit c2a0bbb5 authored by Branden Cobb's avatar Branden Cobb
Browse files

Release 1.15.1 changes

parent 2103e15c
No related branches found
Tags 1.15.1 1.15.1-rc.0
No related merge requests found
Pipeline #455931 passed
......@@ -3,43 +3,16 @@
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
---
## [1.15.0]
* [!1.15.0](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&milestone_title=1.15.0); List of merge requests in this release.
### Upgrade Notices
#### **MINIO INSTANCE CRITICAL UPGRADE INFORMATION - PLEASE READ BEFORE UPGRADING**
**If you have enabled the Minio Cluster Instance in the 'minio' namespace, this upgrade requires a backup and restore
of your Minio instance buckets. Failure to do so will result in data lose during the upgrade.**
By default, the update of the Minio Instance helm chart to V4.1.2 will keep the 2.0.9 instances in place and operational.
This allow a backup to be performed on the operational Minio Instances. After the back is complete, an upgrade to the V4.1.2
instance is required. This is accomplished by setting the upgrade key/value [in the values file] (show below) to TRUE.
```
# When true, upgradeTenants enables use of the V4.* Minio Operator CRD for creation of tenants is enabled.
upgradeTenants:
enabled: false
```
After execution of the helm chart with this value set to true, the new V4 instances will be running and you can restore the
backup data to the new instances.
**NOTE: If you have not enabled the deployment of a Minio Instance before the V4.1.2 release, you must set the above
mentioned upgradeTenants/enabled value to TRUE or the helm deployment will fail**
## [1.15.1]
One of the easiest ways to backup your Minio instance is to the the Minio MC command line tool on a different system.
The MC command line tool can be found here: https://github.com/minio/mc or you can use the Iron Bank approved container
located at registry1.dso.mil/ironbank/opensource/minio/mc:RELEASE.2021-06-08T01-29-37Z.
* https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/834 Update istio to version 1.9.8
* https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/818 Fix minio istio pass down
* https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/831 Fix monitoring hostNetwork violation
* https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/835 Fix fluentbit hostFilesystem violation
```
mc alias set <alais name> HOSTNAME ACCESSKEY SECRETKEY
mc mirror <alias name>/ <local storage location>
## [1.15.0]
```
* [!1.15.0](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&milestone_title=1.15.0); List of merge requests in this release.
## [1.14.1]
......
# bigbang
![Version: 1.15.0](https://img.shields.io/badge/Version-1.15.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
![Version: 1.15.1](https://img.shields.io/badge/Version-1.15.1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
Big Bang is a declarative, continuous delivery tool for core DoD hardened and approved packages into a Kubernetes cluster.
......@@ -145,7 +145,7 @@ To start using Big Bang, you will need to create your own Big Bang environment t
| monitoring.enabled | bool | `true` | Toggle deployment of Monitoring (Prometheus, Grafana, and Alertmanager). |
| monitoring.git.repo | string | `"https://repo1.dso.mil/platform-one/big-bang/apps/core/monitoring.git"` | |
| monitoring.git.path | string | `"./chart"` | |
| monitoring.git.tag | string | `"14.0.0-bb.8"` | |
| monitoring.git.tag | string | `"14.0.0-bb.9"` | |
| monitoring.flux | object | `{"install":{"crds":"CreateReplace"},"upgrade":{"crds":"CreateReplace"}}` | Flux reconciliation overrides specifically for the Monitoring Package |
| monitoring.ingress.gateway | string | `""` | |
| monitoring.sso.enabled | bool | `false` | Toggle SSO for monitoring components on and off |
......@@ -371,4 +371,4 @@ To start using Big Bang, you will need to create your own Big Bang environment t
## Contributing
Please see the [contributing guide](./CONTRIBUTING.md) if you are interested in contributing to Big Bang.
\ No newline at end of file
Please see the [contributing guide](./CONTRIBUTING.md) if you are interested in contributing to Big Bang.
......@@ -11,4 +11,4 @@ spec:
interval: 10m
url: https://repo1.dso.mil/platform-one/big-bang/bigbang.git
ref:
tag: 1.15.0
tag: 1.15.1
apiVersion: v2
name: bigbang
version: 1.15.0
version: 1.15.1
description: Big Bang is a declarative, continuous delivery tool for core DoD hardened and approved packages into a Kubernetes cluster.
type: application
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment