diff --git a/docs/guides/deployment_scenarios/quickstart.md b/docs/guides/deployment_scenarios/quickstart.md
index 234fa2f8818c5e0f92e4efeb268fcff3d17d0334..86020421fec3aad0923a2c9ca45d43d115ae4fcf 100644
--- a/docs/guides/deployment_scenarios/quickstart.md
+++ b/docs/guides/deployment_scenarios/quickstart.md
@@ -9,7 +9,7 @@ This quick start guide explains in beginner-friendly terminology how to complete
1. Turn a virtual machine (VM) into a k3d single-node Kubernetes cluster.
1. Deploy Big Bang on the cluster using a demonstration and local development-friendly workflow.
- > Note: This guide mainly focuses on the scenario of deploying Big Bang to a remote VM with enough resources to run Big Bang [(see step 1 for recommended resources)](#step-1:-provision-a-virtual-machine). If your workstation has sufficient resources, or you are willing to disable packages to lower the resource requirements, then local development is possible. This quick start guide is valid for both remote and local deployment scenarios.
+ > Note: This guide mainly focuses on the scenario of deploying Big Bang to a remote VM with enough resources to run Big Bang [(see step 1 for recommended resources)](#step-1-provision-a-virtual-machine). If your workstation has sufficient resources, or you are willing to disable packages to lower the resource requirements, then local development is possible. This quick start guide is valid for both remote and local deployment scenarios.
1. Customize the demonstration deployment of Big Bang.
@@ -158,23 +158,21 @@ Note: This guide follows the DevOps best practice of left-shifting feedback on m
1. Install k3d
- > Note: k3d v4.4.8 has integration issues with Big Bang, v4.4.7 is known to work.
-
```shell
# [ubuntu@Ubuntu_VM:~]
- # The following downloads the 64 bit linux version of k3d v4.4.7, checks it
+ # The following downloads the 64 bit linux version of k3d v5.4.1, checks it
# against a copy of the sha256 checksum, if they match k3d gets installed
- wget -q -O - https://github.com/rancher/k3d/releases/download/v4.4.7/k3d-linux-amd64 > k3d
+ wget -q -O - https://github.com/k3d-io/k3d/releases/download/v5.4.1/k3d-linux-amd64 > k3d
- echo 51731ffb2938c32c86b2de817c7fbec8a8b05a55f2e4ab229ba094f5740a0f60 k3d | sha256sum -c | grep OK
- # 51731ffb2938c32c86b2de817c7fbec8a8b05a55f2e4ab229ba094f5740a0f60 came from
- # wget -q -O - https://github.com/rancher/k3d/releases/download/v4.4.7/sha256sum.txt | grep k3d-linux-amd64 | cut -d ' ' -f 1
+ echo 50f64747989dc1fcde5db5cb82f8ac132a174b607ca7dfdb13da2f0e509fda11 k3d | sha256sum -c | grep OK
+ # 50f64747989dc1fcde5db5cb82f8ac132a174b607ca7dfdb13da2f0e509fda11 came from running the following against a trusted internet connection.
+ # wget -q -O - https://github.com/k3d-io/k3d/releases/download/v5.4.1/k3d-linux-amd64 | sha256sum | cut -d ' ' -f 1
if [ $? == 0 ]; then chmod +x k3d && sudo mv k3d /usr/local/bin/k3d; fi
# Alternative command (less safe due to curl | bash, but more generic):
- # wget -q -O - https://raw.githubusercontent.com/rancher/k3d/main/install.sh | TAG=v4.4.7 bash
+ # wget -q -O - https://raw.githubusercontent.com/k3d-io/k3d/main/install.sh | TAG=v5.4.1 bash
```
1. Verify k3d installation
@@ -185,21 +183,21 @@ Note: This guide follows the DevOps best practice of left-shifting feedback on m
```
```console
- k3d version v4.4.7
- k3s version v1.21.2-k3s1 (default)
+ k3d version v5.4.1
+ k3s version v1.22.7-k3s1 (default)
```
1. Install kubectl
```shell
# [ubuntu@Ubuntu_VM:~]
- # The following downloads the 64 bit linux version of kubectl v1.22.1, checks it
+ # The following downloads the 64 bit linux version of kubectl v1.23.5, checks it
# against a copy of the sha256 checksum, if they match kubectl gets installed
- wget -q -O - https://dl.k8s.io/release/v1.22.1/bin/linux/amd64/kubectl > kubectl
+ wget -q -O - https://dl.k8s.io/release/v1.23.5/bin/linux/amd64/kubectl > kubectl
- echo 78178a8337fc6c76780f60541fca7199f0f1a2e9c41806bded280a4a5ef665c9 kubectl | sha256sum -c | grep OK
- # 78178a8337fc6c76780f60541fca7199f0f1a2e9c41806bded280a4a5ef665c9 came from
- # wget -q -O - https://dl.k8s.io/release/v1.22.1/bin/linux/amd64/kubectl.sha256
+ echo 715da05c56aa4f8df09cb1f9d96a2aa2c33a1232f6fd195e3ffce6e98a50a879 kubectl | sha256sum -c | grep OK
+ # 715da05c56aa4f8df09cb1f9d96a2aa2c33a1232f6fd195e3ffce6e98a50a879 came from
+ # wget -q -O - https://dl.k8s.io/release/v1.23.5/bin/linux/amd64/kubectl.sha256
if [ $? == 0 ]; then chmod +x kubectl && sudo mv kubectl /usr/local/bin/kubectl; fi
@@ -215,20 +213,20 @@ Note: This guide follows the DevOps best practice of left-shifting feedback on m
```
```console
- Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:45:37Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}
+ Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:58:47Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"linux/amd64"}
```
1. Install Kustomize
```shell
# [ubuntu@Ubuntu_VM:~]
- # The following downloads the 64 bit linux version of kustomize v4.3.0, checks it
+ # The following downloads the 64 bit linux version of kustomize v4.5.4, checks it
# against a copy of the sha256 checksum, if they match kustomize gets installed
- wget -q -O - https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.3.0/kustomize_v4.3.0_linux_amd64.tar.gz > kustomize.tar.gz
+ wget -q -O - https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.5.4/kustomize_v4.5.4_linux_amd64.tar.gz > kustomize.tar.gz
- echo d34818d2b5d52c2688bce0e10f7965aea1a362611c4f1ddafd95c4d90cb63319 kustomize.tar.gz | sha256sum -c | grep OK
- # d34818d2b5d52c2688bce0e10f7965aea1a362611c4f1ddafd95c4d90cb63319
- # came from https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.3.0/checksums.txt
+ echo 1159c5c17c964257123b10e7d8864e9fe7f9a580d4124a388e746e4003added3 kustomize.tar.gz | sha256sum -c | grep OK
+ # 1159c5c17c964257123b10e7d8864e9fe7f9a580d4124a388e746e4003added3
+ # came from https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.5.4/checksums.txt
if [ $? == 0 ]; then tar -xvf kustomize.tar.gz && chmod +x kustomize && sudo mv kustomize /usr/local/bin/kustomize && rm kustomize.tar.gz ; fi
@@ -247,20 +245,20 @@ Note: This guide follows the DevOps best practice of left-shifting feedback on m
```
```console
- {Version:kustomize/v4.3.0 GitCommit:cd17338759ef64c14307991fd25d52259697f1fb BuildDate:2021-08-24T19:24:28Z GoOs:linux GoArch:amd64}
+ {Version:kustomize/v4.5.4 GitCommit:cf3a452ddd6f83945d39d582243b8592ec627ae3 BuildDate:2022-03-28T23:12:45Z GoOs:linux GoArch:amd64}
```
1. Install Helm
```shell
# [ubuntu@Ubuntu_VM:~]
- # The following downloads the 64 bit linux version of helm v3.6.3, checks it
+ # The following downloads the 64 bit linux version of helm v3.8.1, checks it
# against a copy of the sha256 checksum, if they match helm gets installed
- wget -q -O - https://get.helm.sh/helm-v3.6.3-linux-amd64.tar.gz > helm.tar.gz
+ wget -q -O - https://get.helm.sh/helm-v3.8.1-linux-amd64.tar.gz > helm.tar.gz
- echo 07c100849925623dc1913209cd1a30f0a9b80a5b4d6ff2153c609d11b043e262 helm.tar.gz | sha256sum -c | grep OK
- # 07c100849925623dc1913209cd1a30f0a9b80a5b4d6ff2153c609d11b043e262
- # came from https://github.com/helm/helm/releases/tag/v3.6.3
+ echo d643f48fe28eeb47ff68a1a7a26fc5142f348d02c8bc38d699674016716f61cd helm.tar.gz | sha256sum -c | grep OK
+ # d643f48fe28eeb47ff68a1a7a26fc5142f348d02c8bc38d699674016716f61cd
+ # came from https://github.com/helm/helm/releases/tag/v3.8.1
if [ $? == 0 ]; then tar -xvf helm.tar.gz && chmod +x linux-amd64/helm && sudo mv linux-amd64/helm /usr/local/bin/helm && rm -rf linux-amd64 && rm helm.tar.gz ; fi
@@ -277,7 +275,7 @@ Note: This guide follows the DevOps best practice of left-shifting feedback on m
```
```console
- version.BuildInfo{Version:"v3.6.3", GitCommit:"d506314abfb5d21419df8c7e7e68012379db2354", GitTreeState:"dirty", GoVersion:"go1.16.5"}
+ version.BuildInfo{Version:"v3.8.1", GitCommit:"5cb9af4b1b271d11d7a97a71df3ac337dd94ad37", GitTreeState:"clean", GoVersion:"go1.17.5"}
```
## Step 4: Configure Host Operating System Prerequisites
@@ -326,7 +324,7 @@ After reading the notes on the purpose of k3d's command flags, you will be able
### Explanation of k3d Command Flags, Relevant to the Quick Start
-* `SERVER_IP="10.10.16.11"` and `--k3s-server-arg "--tls-san=$SERVER_IP"`:
+* `SERVER_IP="10.10.16.11"` and `--k3s-arg "--tls-san=$SERVER_IP@server:0"`:
These associate an extra IP to the Kubernetes API server's generated HTTPS certificate.
**Explanation of the effect:**
@@ -357,6 +355,9 @@ These flags are not used and shouldn't be added. This is because the image cachi
* `--port 80:80@loadbalancer` and `--port 443:443@loadbalancer`:
These map the virtual machine's port 80 and 443 to port 80 and 443 of a Dockerized LB that will point to the NodePorts of the Dockerized k3s node.
+* `--k3s-arg "--disable=traefik@server:0"`:
+This flag prevents the traefik ingress controller from being deployed. Without this flag traefik would provision a service of type LoadBalancer, and claim k3d's only LoadBalancer that works with ports 80 and 443. Disabling this makes it so the Istio Ingress Gateway will be able to claim the service of type LoadBalancer.
+
### k3d Cluster Creation Commands
```shell
@@ -369,10 +370,10 @@ IMAGE_CACHE=${HOME}/.k3d-container-image-cache
mkdir -p ${IMAGE_CACHE}
k3d cluster create \
- --k3s-server-arg "--tls-san=$SERVER_IP" \
+ --k3s-arg "--tls-san=$SERVER_IP@server:0" \
--volume /etc/machine-id:/etc/machine-id \
--volume ${IMAGE_CACHE}:/var/lib/rancher/k3s/agent/containerd/io.containerd.content.v1.content \
- --k3s-server-arg "--disable=traefik" \
+ --k3s-arg "--disable=traefik@server:0" \
--port 80:80@loadbalancer \
--port 443:443@loadbalancer \
--api-port 6443
@@ -388,8 +389,8 @@ kubectl get node
```console
Switched to context "k3d-k3s-default".
-NAME STATUS ROLES AGE VERSION
-k3d-k3s-default-server-0 Ready control-plane,master 11m v1.21.3+k3s1
+NAME STATUS ROLES AGE VERSION
+k3d-k3s-default-server-0 Ready control-plane,master 11m v1.22.7+k3s1
```
## Step 6: Verify Your IronBank Image Pull Credentials
@@ -427,11 +428,16 @@ k3d-k3s-default-server-0 Ready control-plane,master 11m v1.21.3+k3s1
# [ubuntu@Ubuntu_VM:~]
cd ~
git clone https://repo1.dso.mil/platform-one/big-bang/bigbang.git
-cd ~/bigbang
# Checkout version latest stable version of Big Bang
+cd ~/bigbang
git checkout tags/$(grep 'tag:' base/gitrepository.yaml | awk '{print $2}')
git status
+cd ~
+
+# Note you can do the following to checkout a specific version of bigbang
+# cd ~/bigbang
+# git checkout tags/1.30.1
```
```console
@@ -460,11 +466,11 @@ The `echo $REGISTRY1_USERNAME` is there to verify that the value of your environ
```
```console
- NAME READY STATUS RESTARTS AGE
- kustomize-controller-d689c6688-bnr96 1/1 Running 0 3m8s
- notification-controller-65dffcb7-zk796 1/1 Running 0 3m8s
- source-controller-5fdb69cc66-g5dlh 1/1 Running 0 3m8s
- helm-controller-6c67b58f78-cvxmv 1/1 Running 0 3m8s
+ NAME READY STATUS RESTARTS AGE
+ helm-controller-746d586c6-ln7dl 1/1 Running 0 3m8s
+ notification-controller-f6658d796-fdzjx 1/1 Running 0 3m8s
+ kustomize-controller-5887bb8dd7-jzp7m 1/1 Running 0 3m8s
+ source-controller-7c4564d74c-7ffrf 1/1 Running 0 3m8s
```
## Step 9: Create Helm Values .yaml Files To Act as Input Variables for the Big Bang Helm Chart
@@ -578,21 +584,21 @@ helm upgrade --install bigbang $HOME/bigbang/chart \
Explanation of flags used in the imperative helm install command:
-`upgrade --install`
-: This makes the command more idempotent by allowing the exact same command to work for both the initial installation and upgrade use cases.
+`upgrade --install`:
+This makes the command more idempotent by allowing the exact same command to work for both the initial installation and upgrade use cases.
-`bigbang $HOME/bigbang/chart`
-: bigbang is the name of the helm release that you'd see if you run `helm list -n=bigbang`. `$HOME/bigbang/chart` is a reference to the helm chart being installed.
+`bigbang $HOME/bigbang/chart`:
+bigbang is the name of the helm release that you'd see if you run `helm list -n=bigbang`. `$HOME/bigbang/chart` is a reference to the helm chart being installed.
-`--values https://repo1.dso.mil/platform-one/big-bang/bigbang/-/raw/master/chart/ingress-certs.yaml`
-: References demonstration HTTPS certificates embedded in the public repository. The *.bigbang.dev wildcard certificate is signed by Let's Encrypt, a free public internet Certificate Authority. Note the URL path to the copy of the cert on master branch is used instead of `$HOME/bigbang/chart/ingress-certs.yaml`, because the Let's Encrypt certs expire after 3 months, and if you deploy a tagged release of BigBang, like 1.15.0, the version of the cert stored in the tagged git commit / release of Big Bang could be expired. Referencing the master branches copy via URL ensures you receive the latest version of the cert, which won't be expired.
+`--values https://repo1.dso.mil/platform-one/big-bang/bigbang/-/raw/master/chart/ingress-certs.yaml`:
+References demonstration HTTPS certificates embedded in the public repository. The *.bigbang.dev wildcard certificate is signed by Let's Encrypt, a free public internet Certificate Authority. Note the URL path to the copy of the cert on master branch is used instead of `$HOME/bigbang/chart/ingress-certs.yaml`, because the Let's Encrypt certs expire after 3 months, and if you deploy a tagged release of BigBang, like 1.15.0, the version of the cert stored in the tagged git commit / release of Big Bang could be expired. Referencing the master branches copy via URL ensures you receive the latest version of the cert, which won't be expired.
-`--namespace=bigbang --create-namespace`
-: Means it will install the bigbang helm chart in the bigbang namespace and create the namespace if it doesn't exist.
+`--namespace=bigbang --create-namespace`:
+Means it will install the bigbang helm chart in the bigbang namespace and create the namespace if it doesn't exist.
## Step 11: Verify Big Bang Has Had Enough Time To Finish Installing
-* If you try to run the command in Step 12 too soon, you'll see an ignorable temporary error message
+* If you try to run the command in Step 11 too soon, you'll see an ignorable temporary error message
```shell
# [ubuntu@Ubuntu_VM:~]
@@ -613,26 +619,26 @@ Explanation of flags used in the imperative helm install command:
* If after running `kubectl get po -A` (which is the shorthand of `kubectl get pods --all-namespaces`) you see something like the following, then you need to wait longer
```console
- NAMESPACE NAME READY STATUS RESTARTS AGE
- kube-system metrics-server-86cbb8457f-dqsl5 1/1 Running 0 39m
- kube-system coredns-7448499f4d-ct895 1/1 Running 0 39m
- flux-system notification-controller-65dffcb7-qpgj5 1/1 Running 0 32m
- flux-system kustomize-controller-d689c6688-6dd5n 1/1 Running 0 32m
- flux-system source-controller-5fdb69cc66-s9pvw 1/1 Running 0 32m
- kube-system local-path-provisioner-5ff76fc89d-gnvp4 1/1 Running 1 39m
- flux-system helm-controller-6c67b58f78-6dzqw 1/1 Running 0 32m
- gatekeeper-system gatekeeper-controller-manager-5cf7696bcf-xclc4 0/1 Running 0 4m6s
- gatekeeper-system gatekeeper-audit-79695c56b8-qgfbl 0/1 Running 0 4m6s
- istio-operator istio-operator-5f6cfb6d5b-hx7bs 1/1 Running 0 4m8s
- eck-operator elastic-operator-0 1/1 Running 1 4m10s
- istio-system istiod-65798dff85-9rx4z 1/1 Running 0 87s
- istio-system public-ingressgateway-6cc4dbcd65-fp9hv 0/1 ContainerCreating 0 46s
- logging logging-fluent-bit-dbkxx 0/2 Init:0/1 0 44s
- monitoring monitoring-monitoring-kube-admission-create-q5j2x 0/1 ContainerCreating 0 42s
- logging logging-ek-kb-564d7779d5-qjdxp 0/2 Init:0/2 0 41s
- logging logging-ek-es-data-0 0/2 Init:0/2 0 44s
- istio-system svclb-public-ingressgateway-ggkvx 5/5 Running 0 39s
- logging logging-ek-es-master-0 0/2 Init:0/2 0 37s
+ NAMESPACE NAME READY STATUS RESTARTS AGE
+ kube-system metrics-server-86cbb8457f-dqsl5 1/1 Running 0 39m
+ kube-system coredns-7448499f4d-ct895 1/1 Running 0 39m
+ flux-system notification-controller-65dffcb7-qpgj5 1/1 Running 0 32m
+ flux-system kustomize-controller-d689c6688-6dd5n 1/1 Running 0 32m
+ flux-system source-controller-5fdb69cc66-s9pvw 1/1 Running 0 32m
+ kube-system local-path-provisioner-5ff76fc89d-gnvp4 1/1 Running 1 39m
+ flux-system helm-controller-6c67b58f78-6dzqw 1/1 Running 0 32m
+ gatekeeper-system gatekeeper-controller-manager-5cf7696bcf-xclc4 0/1 Running 0 4m6s
+ gatekeeper-system gatekeeper-audit-79695c56b8-qgfbl 0/1 Running 0 4m6s
+ istio-operator istio-operator-5f6cfb6d5b-hx7bs 1/1 Running 0 4m8s
+ eck-operator elastic-operator-0 1/1 Running 1 4m10s
+ istio-system istiod-65798dff85-9rx4z 1/1 Running 0 87s
+ istio-system public-ingressgateway-6cc4dbcd65-fp9hv 0/1 ContainerCreating 0 46s
+ logging logging-fluent-bit-dbkxx 0/2 Init:0/1 0 44s
+ monitoring monitoring-monitoring-kube-admission-create-q5j2x 0/1 ContainerCreating 0 42s
+ logging logging-ek-kb-564d7779d5-qjdxp 0/2 Init:0/2 0 41s
+ logging logging-ek-es-data-0 0/2 Init:0/2 0 44s
+ istio-system svclb-public-ingressgateway-ggkvx 5/5 Running 0 39s
+ logging logging-ek-es-master-0 0/2 Init:0/2 0 37s
```
* Wait up to 10 minutes then re-run `kubectl get po -A`, until all pods show STATUS Running
@@ -640,18 +646,18 @@ Explanation of flags used in the imperative helm install command:
* `helm list -n=bigbang` should also show STATUS deployed
```console
- NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
- bigbang bigbang 1 2022-01-18 10:37:02.088839018 -0500 EST deployed bigbang-1.25.0
- cluster-auditor-cluster-auditor cluster-auditor 1 2022-01-18 15:39:35.161101094 +0000 UTC deployed cluster-auditor-1.0.2-bb.0 0.0.3
- eck-operator-eck-operator eck-operator 1 2022-01-18 15:38:03.79179921 +0000 UTC deployed eck-operator-1.9.1-bb.0 1.9.1
- gatekeeper-system-gatekeeper gatekeeper-system 1 2022-01-18 15:37:06.758450515 +0000 UTC deployed gatekeeper-3.6.0-bb.2 v3.6.0
- istio-operator-istio-operator istio-operator 1 2022-01-18 15:37:07.432751828 +0000 UTC deployed istio-operator-1.11.3-bb.2
- istio-system-istio istio-system 1 2022-01-18 15:37:33.973068788 +0000 UTC deployed istio-1.11.3-bb.1
- jaeger-jaeger jaeger 1 2022-01-18 15:39:37.911181302 +0000 UTC deployed jaeger-operator-2.27.0-bb.2 1.28.0
- kiali-kiali kiali 1 2022-01-18 15:39:36.829012053 +0000 UTC deployed kiali-operator-1.44.0-bb.1 1.44.0
- logging-ek logging 1 2022-01-18 15:38:34.802230733 +0000 UTC deployed logging-0.5.0-bb.0 7.16.1
- logging-fluent-bit logging 1 2022-01-18 15:39:34.462639648 +0000 UTC deployed fluent-bit-0.19.16-bb.0 1.8.11
- monitoring-monitoring monitoring 1 2022-01-18 15:38:08.044148943 +0000 UTC deployed kube-prometheus-stack-23.1.6-bb.5 0.52.1
+ NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
+ bigbang bigbang 1 2022-03-31 12:07:49.239343968 +0000 UTC deployed bigbang-1.30.1
+ cluster-auditor-cluster-auditor cluster-auditor 1 2022-03-31 12:14:23.004377605 +0000 UTC deployed cluster-auditor-1.4.0-bb.0 0.0.4
+ eck-operator-eck-operator eck-operator 1 2022-03-31 12:09:52.921098159 +0000 UTC deployed eck-operator-2.0.0-bb.0 2.0.0
+ gatekeeper-system-gatekeeper gatekeeper-system 1 2022-03-31 12:07:53.52890717 +0000 UTC deployed gatekeeper-3.7.1-bb.0 v3.7.1
+ istio-operator-istio-operator istio-operator 1 2022-03-31 12:07:55.111321595 +0000 UTC deployed istio-operator-1.13.2-bb.1 1.13.2
+ istio-system-istio istio-system 1 2022-03-31 12:08:23.439981427 +0000 UTC deployed istio-1.13.2-bb.0 1.13.2
+ jaeger-jaeger jaeger 1 2022-03-31 12:12:58.068313509 +0000 UTC deployed jaeger-operator-2.29.0-bb.0 1.32.0
+ kiali-kiali kiali 1 2022-03-31 12:12:57.011215896 +0000 UTC deployed kiali-operator-1.47.0-bb.1 1.47.0
+ logging-ek logging 1 2022-03-31 12:10:52.785810021 +0000 UTC deployed logging-0.7.0-bb.0 7.17.1
+ logging-fluent-bit logging 1 2022-03-31 12:12:53.27612266 +0000 UTC deployed fluent-bit-0.19.20-bb.1 1.8.13
+ monitoring-monitoring monitoring 1 2022-03-31 12:10:02.31254196 +0000 UTC deployed kube-prometheus-stack-33.2.0-bb.0 0.54.1
```
## Step 12: Edit Your Workstation’s Hosts File To Access the Web Pages Hosted on the Big Bang Cluster
@@ -663,13 +669,13 @@ kubectl get vs -A
```
```console
-NAMESPACE NAME GATEWAYS HOSTS AGE
-logging kibana ["istio-system/public"] ["kibana.bigbang.dev"] 38m
-monitoring monitoring-monitoring-kube-grafana ["istio-system/public"] ["grafana.bigbang.dev"] 36m
-monitoring monitoring-monitoring-kube-alertmanager ["istio-system/public"] ["alertmanager.bigbang.dev"] 36m
-monitoring monitoring-monitoring-kube-prometheus ["istio-system/public"] ["prometheus.bigbang.dev"] 36m
-kiali kiali ["istio-system/public"] ["kiali.bigbang.dev"] 35m
-jaeger jaeger ["istio-system/public"] ["tracing.bigbang.dev"] 35m
+NAMESPACE NAME GATEWAYS HOSTS AGE
+logging kibana ["istio-system/public"] ["kibana.bigbang.dev"] 10m
+monitoring monitoring-monitoring-kube-alertmanager ["istio-system/public"] ["alertmanager.bigbang.dev"] 10m
+monitoring monitoring-monitoring-kube-grafana ["istio-system/public"] ["grafana.bigbang.dev"] 10m
+monitoring monitoring-monitoring-kube-prometheus ["istio-system/public"] ["prometheus.bigbang.dev"] 10m
+kiali kiali ["istio-system/public"] ["kiali.bigbang.dev"] 8m21s
+jaeger jaeger ["istio-system/public"] ["tracing.bigbang.dev"] 7m46s
```
### Linux/Mac Users
@@ -692,8 +698,8 @@ Add the following entries to the Hosts file, where x.x.x.x = k3d virtual machine
```plaintext
x.x.x.x kibana.bigbang.dev
-x.x.x.x grafana.bigbang.dev
x.x.x.x alertmanager.bigbang.dev
+x.x.x.x grafana.bigbang.dev
x.x.x.x prometheus.bigbang.dev
x.x.x.x kiali.bigbang.dev
x.x.x.x tracing.bigbang.dev
@@ -706,8 +712,8 @@ In a browser, visit one of the sites listed using the `kubectl get vs -A` comman
## Step 14: Play
-Here's an example of post deployment customization of Big Bang.
-After looking at <https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/chart/values.yaml>
+Here's an example of post deployment customization of Big Bang.
+After looking at <https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/chart/values.yaml>
It should make sense that the following is a valid edit
```shell