Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump cert-manager version from 1.8.0 to 1.14.5 #208

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Bump cert-manager version from 1.8.0 to 1.14.5 #208

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
32eff9b
Bump cert-manager version from 1.8.0 to 1.14.5
carlohamalainen May 30, 2024
2f90ba6
Formatting.
carlohamalainen May 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 ...manifests/cert-manager-values-v1.8.0.yaml → ...anifests/cert-manager-values-v1.14.5.yaml
View file
Open in desktop
File renamed without changes.
18 changes: 9 additions & 9 deletions 03-setup-ingress-controller/guides/wildcard_certificates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,15 +60,15 @@ helm repo update jetstack
Then, open and inspect the `Helm` values file for `Cert-Manager` provided in the `Starter Kit` repository, using an editor of your choice (preferably with `YAML` lint support). For example, you can use [VS Code](https://code.visualstudio.com):

```shell
CERT_MANAGER_HELM_CHART_VERSION="1.8.0"
CERT_MANAGER_HELM_CHART_VERSION="1.14.5"

code 03-setup-ingress-controller/assets/manifests/cert-manager-values-v${CERT_MANAGER_HELM_CHART_VERSION}.yaml
```

Finally, you can install the `jetstack/cert-manager` chart using Helm:

```shell
CERT_MANAGER_HELM_CHART_VERSION="1.8.0"
CERT_MANAGER_HELM_CHART_VERSION="1.14.5"

helm install cert-manager jetstack/cert-manager --version "$CERT_MANAGER_HELM_CHART_VERSION" \
--namespace cert-manager \
Expand All @@ -86,7 +86,7 @@ The output looks similar to (notice the `STATUS` column which has the `deployed`

```text
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
cert-manager cert-manager 1 2021-10-20 12:13:05.124264 +0300 EEST deployed cert-manager-v1.8.0 v1.8.0
cert-manager cert-manager 1 2021-10-20 12:13:05.124264 +0300 EEST deployed cert-manager-v1.14.5 v1.14.5
```

Inspect `Kubernetes` resources created by the `cert-manager` Helm release:
Expand Down Expand Up @@ -440,11 +440,11 @@ Finally, you can verify the `Kubernetes` secret which contains your `TLS` certif
Annotations: cert-manager.io/alt-names: *.starter-kit.online,starter-kit.online
cert-manager.io/certificate-name: starter-kit.online
cert-manager.io/common-name: *.starter-kit.online
cert-manager.io/ip-sans:
cert-manager.io/ip-sans:
cert-manager.io/issuer-group: cert-manager.io
cert-manager.io/issuer-kind: Issuer
cert-manager.io/issuer-name: letsencrypt-ambassador-wcard
cert-manager.io/uri-sans:
cert-manager.io/uri-sans:

Type: kubernetes.io/tls

Expand All @@ -469,11 +469,11 @@ Finally, you can verify the `Kubernetes` secret which contains your `TLS` certif
Annotations: cert-manager.io/alt-names: *.starter-kit.online,starter-kit.online
cert-manager.io/certificate-name: starter-kit.online
cert-manager.io/common-name: *.starter-kit.online
cert-manager.io/ip-sans:
cert-manager.io/ip-sans:
cert-manager.io/issuer-group: cert-manager.io
cert-manager.io/issuer-kind: Issuer
cert-manager.io/issuer-name: letsencrypt-nginx-wcard
cert-manager.io/uri-sans:
cert-manager.io/uri-sans:

Type: kubernetes.io/tls

Expand Down Expand Up @@ -631,7 +631,7 @@ Content-Length: 164
Connection: keep-alive
Location: https://echo.starter-kit.online

HTTP/2 200
HTTP/2 200
date: Mon, 08 Nov 2021 15:53:47 GMT
content-type: text/plain
content-length: 351
Expand Down Expand Up @@ -670,7 +670,7 @@ Content-Length: 164
Connection: keep-alive
Location: https://quote.starter-kit.online

HTTP/2 200
HTTP/2 200
date: Mon, 08 Nov 2021 15:54:13 GMT
content-type: application/json
content-length: 162
Expand Down
12 changes: 6 additions & 6 deletions 03-setup-ingress-controller/nginx.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -502,16 +502,16 @@ Next, update the `jetstack` chart repository:
helm repo update jetstack
```

Then, open and inspect the `03-setup-ingress-controller/assets/manifests/cert-manager-values-v1.8.0.yaml` file provided in the `Starter Kit` repository, using an editor of your choice (preferably with `YAML` lint support). For example, you can use [VS Code](https://code.visualstudio.com):
Then, open and inspect the `03-setup-ingress-controller/assets/manifests/cert-manager-values-v1.14.5.yaml` file provided in the `Starter Kit` repository, using an editor of your choice (preferably with `YAML` lint support). For example, you can use [VS Code](https://code.visualstudio.com):

```shell
code 03-setup-ingress-controller/assets/manifests/cert-manager-values-v1.8.0.yaml
code 03-setup-ingress-controller/assets/manifests/cert-manager-values-v1.14.5.yaml
```

Finally, you can install the `jetstack/cert-manager` chart using Helm:

```shell
CERT_MANAGER_HELM_CHART_VERSION="1.8.0"
CERT_MANAGER_HELM_CHART_VERSION="1.14.5"

helm install cert-manager jetstack/cert-manager --version "$CERT_MANAGER_HELM_CHART_VERSION" \
--namespace cert-manager \
Expand All @@ -529,7 +529,7 @@ The output looks similar to (notice the `STATUS` column which has the `deployed`

```text
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
cert-manager cert-manager 1 2021-10-20 12:13:05.124264 +0300 EEST deployed cert-manager-v1.8.0 v1.8.0
cert-manager cert-manager 1 2021-10-20 12:13:05.124264 +0300 EEST deployed cert-manager-v1.14.5 v1.14.5
```

Inspect `Kubernetes` resources created by the `cert-manager` Helm release:
Expand Down Expand Up @@ -709,7 +709,7 @@ Content-Length: 164
Connection: keep-alive
Location: https://echo.starter-kit.online

HTTP/2 200
HTTP/2 200
date: Thu, 04 Nov 2021 16:00:10 GMT
content-type: text/plain
content-length: 351
Expand Down Expand Up @@ -746,7 +746,7 @@ Content-Length: 164
Connection: keep-alive
Location: https://quote.starter-kit.online

HTTP/2 200
HTTP/2 200
date: Tue, 07 Jun 2022 06:10:27 GMT
content-type: application/json
content-length: 159
Expand Down
22 changes: 11 additions & 11 deletions 14-continuous-delivery-using-gitops/argocd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,7 +235,7 @@ Please follow below steps to complete the Helm based installation:
```shell
helm repo add argo https://argoproj.github.io/argo-helm

helm repo update argo
helm repo update argo
```

3. Now, search the `argo` Helm repository for available charts to install:
Expand All @@ -247,8 +247,8 @@ Please follow below steps to complete the Helm based installation:
The output looks similar to:

```text
NAME CHART VERSION APP VERSION DESCRIPTION
argo/argo 1.0.0 v2.12.5 A Helm chart for Argo Workflows
NAME CHART VERSION APP VERSION DESCRIPTION
argo/argo 1.0.0 v2.12.5 A Helm chart for Argo Workflows
argo/argo-cd 4.9.4 v2.4.0 A Helm chart for Argo CD, a declarative, GitOps...
...
```
Expand Down Expand Up @@ -387,7 +387,7 @@ Usage:
Examples:
# List all the applications.
argocd app list

# Get the details of a application
argocd app get my-app
...
Expand All @@ -409,7 +409,7 @@ First you need to prepare your Git repository to use a consistent layout. In the
clusters
└── dev
└── helm
├── cert-manager-v1.8.0.yaml
├── cert-manager-v1.14.5.yaml
├── nginx-v4.1.3.yaml
├── prometheus-stack-v35.5.1.yaml
├── sealed-secrets-v2.4.0.yaml
Expand All @@ -435,7 +435,7 @@ Please open a terminal, and follow below steps to create the layout for your Git
3. Copy application manifests provided for each component in the Starter Kit repository (you can also take a look and see how each [manifest](assets/manifests/argocd/applications/helm) is structured):

```shell
CERT_MANAGER_CHART_VERSION="1.8.0"
CERT_MANAGER_CHART_VERSION="1.14.5"
NGINX_CHART_VERSION="4.1.3"
PROMETHEUS_CHART_VERSION="35.5.1"
SEALED_SECRETS_CHART_VERSION="2.4.0"
Expand Down Expand Up @@ -503,15 +503,15 @@ Above command will create a new `Argo CD application` named `starter-kit-apps` i
Next, you need to sync the `starter-kit-apps` application (remember that Argo CD doesn't sync anything by default, unless specified):

```shell
argocd app sync starter-kit-apps
argocd app sync starter-kit-apps
```

The output looks similar to:

```text
TIMESTAMP GROUP KIND NAMESPACE NAME STATUS HEALTH ...
2022-03-23T17:39:38+02:00 argoproj.io Application argocd sealed-secrets-controller OutOfSync Missing ...
2022-03-23T17:39:38+02:00 argoproj.io Application argocd velero OutOfSync Missing ...
2022-03-23T17:39:38+02:00 argoproj.io Application argocd sealed-secrets-controller OutOfSync Missing ...
2022-03-23T17:39:38+02:00 argoproj.io Application argocd velero OutOfSync Missing ...
2022-03-23T17:39:38+02:00 argoproj.io Application argocd ingress-nginx OutOfSync Missing ...
...
GROUP KIND NAMESPACE NAME STATUS HEALTH HOOK MESSAGE
Expand Down Expand Up @@ -540,7 +540,7 @@ ingress-nginx https://kubernetes.default.svc ingress-nginx defau
cert-manager https://kubernetes.default.svc cert-manager default OutOfSync Missing Auto-Prune ...
kube-prometheus-stack https://kubernetes.default.svc monitoring default OutOfSync Missing Auto-Prune ...
sealed-secrets-controller https://kubernetes.default.svc sealed-secrets default OutOfSync Missing Auto-Prune ...
starter-kit-apps https://kubernetes.default.svc argocd default Synced Healthy <none> ...
starter-kit-apps https://kubernetes.default.svc argocd default Synced Healthy <none> ...
velero https://kubernetes.default.svc velero default OutOfSync Missing Auto-Prune ...
```

Expand Down Expand Up @@ -607,7 +607,7 @@ Bootstrapping the parent application is a one-time operation. On subsequent Git
URL: https://argocd.example.com/applications/velero
Repo: https://vmware-tanzu.github.io/helm-charts
Target: 2.27.3
Path:
Path:
SyncWindow: Sync Allowed
Sync Policy: Automated (Prune)
Sync Status: OutOfSync from 2.27.3
Expand Down
2 changes: 1 addition & 1 deletion ...ions/helm/cert-manager-values-v1.8.0.yaml → ...ons/helm/cert-manager-values-v1.14.5.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ spec:
source:
chart: cert-manager
repoURL: https://charts.jetstack.io
targetRevision: 1.8.0
targetRevision: 1.14.5
helm:
releaseName: cert-manager
values: |
Expand Down
2 changes: 1 addition & 1 deletion ...cd/helm/releases/cert-manager-v1.8.0.yaml → ...d/helm/releases/cert-manager-v1.14.5.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ spec:
sourceRef:
kind: HelmRepository
name: jetstack
version: 1.8.0
version: 1.14.5
install:
createNamespace: true
remediation:
Expand Down
64 changes: 32 additions & 32 deletions 14-continuous-delivery-using-gitops/fluxcd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,11 +296,11 @@ flux get all
The output looks similar to the following (you can notice the `gitrepository/flux-system` component fetching the latest revision from your main branch, as well as the `kustomization/flux-system` component):

```text
NAME READY MESSAGE REVISION SUSPENDED
gitrepository/flux-system True Fetched revision: main/6e9b41b main/6e9b41b False
NAME READY MESSAGE REVISION SUSPENDED
gitrepository/flux-system True Fetched revision: main/6e9b41b main/6e9b41b False

NAME READY MESSAGE REVISION SUSPENDED
kustomization/flux-system True Applied revision: main/6e9b41b main/6e9b41b False
NAME READY MESSAGE REVISION SUSPENDED
kustomization/flux-system True Applied revision: main/6e9b41b main/6e9b41b False
```

In case you need to perform some troubleshooting, and see what `Flux CD` is doing, you can access the logs via:
Expand All @@ -313,14 +313,14 @@ The output looks similar to the following:

```text
...
2022-03-17T10:47:21.976Z info Kustomization/flux-system.flux-system - server-side apply completed
2022-03-17T10:47:22.662Z info Kustomization/flux-system.flux-system - server-side apply completed
2022-03-17T10:47:22.702Z info Kustomization/flux-system.flux-system - Reconciliation finished in 9.631064885s, next run in 10m0s
2022-03-17T10:47:19.167Z info GitRepository/flux-system.flux-system - Discarding event, no alerts found for the involved object
2022-03-17T10:47:22.691Z info Kustomization/flux-system.flux-system - Discarding event, no alerts found for the involved object
2022-03-17T10:47:22.709Z info Kustomization/flux-system.flux-system - Discarding event, no alerts found for the involved object
2022-03-17T10:47:19.168Z info GitRepository/flux-system.flux-system - Reconciliation finished in 7.79283477s, next run in 1m0s
2022-03-17T10:48:20.594Z info GitRepository/flux-system.flux-system - Reconciliation finished in 1.424279853s, next run in 1m0s
2022-03-17T10:47:21.976Z info Kustomization/flux-system.flux-system - server-side apply completed
2022-03-17T10:47:22.662Z info Kustomization/flux-system.flux-system - server-side apply completed
2022-03-17T10:47:22.702Z info Kustomization/flux-system.flux-system - Reconciliation finished in 9.631064885s, next run in 10m0s
2022-03-17T10:47:19.167Z info GitRepository/flux-system.flux-system - Discarding event, no alerts found for the involved object
2022-03-17T10:47:22.691Z info Kustomization/flux-system.flux-system - Discarding event, no alerts found for the involved object
2022-03-17T10:47:22.709Z info Kustomization/flux-system.flux-system - Discarding event, no alerts found for the involved object
2022-03-17T10:47:19.168Z info GitRepository/flux-system.flux-system - Reconciliation finished in 7.79283477s, next run in 1m0s
2022-03-17T10:48:20.594Z info GitRepository/flux-system.flux-system - Reconciliation finished in 1.424279853s, next run in 1m0s
...
```

Expand Down Expand Up @@ -369,10 +369,10 @@ Please make sure that the following steps are performed in order:
FLUXCD_SYNC_PATH="clusters/dev"
FLUXCD_HELM_MANIFESTS_PATH="${FLUXCD_SYNC_PATH}/helm"

mkdir -p "${FLUXCD_HELM_MANIFESTS_PATH}/repositories"
mkdir -p "${FLUXCD_HELM_MANIFESTS_PATH}/releases"
mkdir -p "${FLUXCD_HELM_MANIFESTS_PATH}/repositories"

mkdir -p "${FLUXCD_HELM_MANIFESTS_PATH}/releases"

mkdir -p "${FLUXCD_HELM_MANIFESTS_PATH}/secrets"
```

Expand Down Expand Up @@ -547,12 +547,12 @@ After a few moments, please inspect the Flux CD `Sealed Secrets` Helm release:
```shell
flux get helmrelease sealed-secrets-controller
```

The output looks similar to:

```text
NAME READY MESSAGE REVISION SUSPENDED
sealed-secrets-controller True Release reconciliation succeeded 2.4.0 False
NAME READY MESSAGE REVISION SUSPENDED
sealed-secrets-controller True Release reconciliation succeeded 2.4.0 False
```

Look for the `READY` column value - it should say `True`. Reconciliation status is displayed in the `MESSAGE` column, along with the `REVISION` number, which represents the `Helm` chart `version`. Please bear in mind that some releases take longer to complete (like `Prometheus` stack, for example), so please be patient.
Expand Down Expand Up @@ -590,7 +590,7 @@ If for some reason the `kubeseal` certificate fetch command hangs (or you get an
- First, open a new terminal window, and `expose` the `Sealed Secrets Controller` service on your `localhost` (you can use `CTRL - C` to terminate, after fetching the public key):

```shell
kubectl port-forward service/sealed-secrets-controller 8080:8080 -n flux-system
kubectl port-forward service/sealed-secrets-controller 8080:8080 -n flux-system
```

- Then, you can go back to your working terminal and fetch the public key (please replace the `<>` placeholders accordingly):
Expand Down Expand Up @@ -631,23 +631,23 @@ Steps to follow:
3. Now, fetch the Cert-Manager `HelmRelease` manifest file provided by the `Starter Kit` Git repository:

```shell
CERT_MANAGER_CHART_VERSION="1.8.0"
CERT_MANAGER_CHART_VERSION="1.14.5"

curl "https://raw.githubusercontent.com/digitalocean/Kubernetes-Starter-Kit-Developers/main/14-continuous-delivery-using-gitops/assets/manifests/fluxcd/helm/releases/cert-manager-v${CERT_MANAGER_CHART_VERSION}.yaml" > "${FLUXCD_HELM_MANIFESTS_PATH}/releases/cert-manager-v${CERT_MANAGER_CHART_VERSION}.yaml"
```

4. Next, inspect the downloaded `HelmRelease` manifest file using an editor of your choice (preferably with `YAML` lint support), and adjust to your needs. For example, you can use [VS Code](https://code.visualstudio.com) (make sure to replace the `<>` placeholders accordingly, if present):

```shell
CERT_MANAGER_CHART_VERSION="1.8.0"
CERT_MANAGER_CHART_VERSION="1.14.5"

code "${FLUXCD_HELM_MANIFESTS_PATH}/releases/cert-manager-v${CERT_MANAGER_CHART_VERSION}.yaml"
```

5. Finally, commit `Git` changes to `remote` branch:

```shell
CERT_MANAGER_CHART_VERSION="1.8.0"
CERT_MANAGER_CHART_VERSION="1.14.5"

git add "${FLUXCD_HELM_MANIFESTS_PATH}/repositories/jetstack.yaml"

Expand All @@ -669,12 +669,12 @@ After a few moments, please inspect the `HelmRelease` status:
```shell
flux get helmrelease cert-manager
```

The output looks similar to:

```text
NAME READY MESSAGE REVISION SUSPENDED
cert-manager True Release reconciliation succeeded v1.6.1 False
NAME READY MESSAGE REVISION SUSPENDED
cert-manager True Release reconciliation succeeded v1.6.1 False
```

Look for the `READY` column value - it should say `True`. Reconciliation status is displayed in the `MESSAGE` column, along with the `REVISION` number, which represents the `Helm` chart `version`. Please bear in mind that some releases take longer to complete (like `Prometheus` stack, for example), so please be patient.
Expand Down Expand Up @@ -850,7 +850,7 @@ Look for the `READY` column value - it should say `True`. Reconciliation status
```shell
flux logs --kind=HelmRelease
```

- In case the `Flux` logs do not offer sufficient information you can use the `describe` command on the `helmrelease` using `kubectl` as follows:

```shell
Expand Down Expand Up @@ -941,11 +941,11 @@ After a few moments, please inspect the Prometheus `HelmRelease`:
```shell
flux get helmrelease kube-prometheus-stack
```

The output looks similar to:

```text
NAME READY MESSAGE REVISION SUSPENDED
NAME READY MESSAGE REVISION SUSPENDED
kube-prometheus-stack True Release reconciliation succeeded 35.5.1 False
```

Expand Down Expand Up @@ -1070,11 +1070,11 @@ After a few moments, please inspect the Loki `HelmRelease`:
```shell
flux get helmrelease loki-stack
```

The output looks similar to:

```text
NAME READY MESSAGE REVISION SUSPENDED
NAME READY MESSAGE REVISION SUSPENDED
loki-stack True Release reconciliation succeeded 2.6.4 False
```

Expand Down Expand Up @@ -1210,7 +1210,7 @@ flux get helmrelease velero-stack
The output looks similar to:

```text
NAME READY MESSAGE REVISION SUSPENDED
NAME READY MESSAGE REVISION SUSPENDED
velero-stack True Release reconciliation succeeded 2.29.7 False
```

Expand Down