From 8b1849b9d6e7d516734563ae8e8e332754ecb124 Mon Sep 17 00:00:00 2001
From: Micah Nagel <micah.nagel@parsons.com>
Date: Wed, 16 Feb 2022 10:43:43 -0700
Subject: [PATCH] Update Customer Template to Big Bang to v1.27.1
---
README.md | 10 +++++-----
base/kustomization.yaml | 4 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/README.md b/README.md
index 194dd6353..c26bcae62 100644
--- a/README.md
+++ b/README.md
@@ -222,8 +222,8 @@ Big Bang follows a [GitOps](https://www.weave.works/blog/what-is-gitops-really)
```shell
# Flux is used to sync Git with the the cluster configuration
- # If you are using a different version of Big Bang, make sure to update the `?ref=1.26.0` to the correct tag or branch.
- kustomize build https://repo1.dso.mil/platform-one/big-bang/bigbang.git//base/flux?ref=1.26.0 | kubectl apply -f -
+ # If you are using a different version of Big Bang, make sure to update the `?ref=1.27.1` to the correct tag or branch.
+ kustomize build https://repo1.dso.mil/platform-one/big-bang/bigbang.git//base/flux?ref=1.27.1 | kubectl apply -f -
# Wait for flux to complete
kubectl get deploy -o name -n flux-system | xargs -n1 -t kubectl rollout status -n flux-system
@@ -313,7 +313,7 @@ To minimize the risk of an unexpected deployment of a BigBang release, the BigBa
spec:
ref:
$patch: replace
- tag: "1.26.0"
+ tag: "1.27.1"
```
To update `dev/kustomization.yaml`, you would create a `mergePatch` like the following:
@@ -329,7 +329,7 @@ patchesStrategicMerge:
interval: 1m
ref:
$patch: replace
- tag: "1.13.0"
+ tag: "1.27.1"
```
> This does not update the kustomize base, but it is unusual for that to change.
@@ -338,7 +338,7 @@ Then, commit your change:
```shell
git add kustomization.yaml
- git commit -m "feat(dev): update bigbang to 1.13.0"
+ git commit -m "feat(dev): update bigbang to 1.27.1"
git push
```
diff --git a/base/kustomization.yaml b/base/kustomization.yaml
index 89430b74e..b354a6595 100644
--- a/base/kustomization.yaml
+++ b/base/kustomization.yaml
@@ -1,7 +1,7 @@
# When updating the version of BigBang, make sure to update
# both the bases reference and the GitRepository reference
bases:
-- git::https://repo1.dso.mil/platform-one/big-bang/bigbang.git//base?ref=1.26.0
+- git::https://repo1.dso.mil/platform-one/big-bang/bigbang.git//base?ref=1.27.1
configMapGenerator:
- name: common
behavior: merge
@@ -17,4 +17,4 @@ patchesStrategicMerge:
spec:
ref:
$patch: replace
- tag: "1.26.0"
+ tag: "1.27.1"
--
GitLab