Skip to content

Commit c659b42

Browse files
authored
feat: added upgrade notes for v4.4.4 issues (#120)
1 parent 1f06f33 commit c659b42

File tree

4 files changed

+94
-0
lines changed

4 files changed

+94
-0
lines changed

docs/for-ops/upgrade-instructions.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
slug: upgrade-instructions
3+
title: Upgrade Instructions
4+
sidebar_label: Upgrade Instructions
5+
---
6+
7+
The Akamai App Platform is regularly updated to provide new features, improvements, and security enhancements. This page outlines the recommended approach for performing an upgrade.
8+
9+
## Upgrading through the Platform Dashboard
10+
11+
The primary method to upgrade the Akamai App Platform is via the platform dashboard. Within the dashboard you can see your current version in the top right corner, there is also a table listing all available versions, each accompanied by a brief description of the changes introduced in that release. To see the full release notes of that version you can click on the version tag. To initiate the upgrade, simply click the `Upgrade to vX.Y.Z` button to upgrade to the latest version.
12+
13+
1. As a platform admin go to the platform view.
14+
15+
2. In the left menu, click on `Dashboard`.
16+
17+
3. Click the `Upgrade to vX.Y.Z` button and the Akamai App Platform will be upgraded to the newest version.
18+
19+
![Upgrade through the dashboard](../img/upgrade-version-dashboard.png)
20+
21+
:::note
22+
If there is no newer version a message will be displayed instead showing that there are no new updates for your version.
23+
:::

docs/for-ops/upgrade-notes.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
slug: upgrade-notes
3+
title: Upgrade Notes
4+
sidebar_label: Upgrade Notes
5+
---
6+
7+
## About upgrade notes
8+
9+
In some cases between versions upgrades there are issues that can occur, on this page you will find fixes on how to deal with those issues.
10+
11+
## v4.4.4 to v4.7.0 or higher
12+
13+
From v4.4.4 to a higher version there might occur an issue with the harbor redis, which results in the harbor-redis-0 pod restarting indefinitely.
14+
15+
To solve this issue you have to delete the harbor redis data according to the following steps.
16+
17+
### Disable ArgoCD autoSync on harbor-harbor
18+
```shell
19+
kubectl patch application harbor-harbor \
20+
-n argocd \
21+
--type='json' \
22+
-p='[{"op": "remove", "path": "/spec/syncPolicy/automated"}]'
23+
```
24+
25+
### Scale down harbor-jobservice, harbor-core to zero
26+
```shell
27+
kubectl scale deploy harbor-jobservice --replicas=0 -n harbor
28+
kubectl scale deploy harbor-core --replicas=0 -n harbor
29+
```
30+
31+
:::note
32+
If the version you are going to upgrade to is of v4.7.0 or higher you also have to scale down the apl-operator
33+
:::
34+
35+
```shell
36+
kubectl scale deploy apl-operator --replicas=0 -n apl-operator
37+
```
38+
39+
### Scale down the harbor redis to zero
40+
```shell
41+
kubectl scale sts harbor-redis --replicas=0 -n harbor
42+
```
43+
44+
### PVC data-harbor-redis-0 is deleted
45+
```shell
46+
kubectl delete pvc data-harbor-redis-0 -n harbor
47+
```
48+
49+
### Scale up harbor-redis to one
50+
```shell
51+
kubectl scale sts harbor-redis --replicas=1 -n harbor
52+
```
53+
54+
### Wait for pod ready status
55+
:::note
56+
If the version you are going to upgrade to is of v4.7.0 or higher you also have to scale up the apl-operator
57+
:::
58+
59+
```shell
60+
kubectl scale deploy apl-operator --replicas=1 -n apl-operator
61+
```
62+
63+
### Enable ArgoCD autoSync on harbor-harbor
64+
```shell
65+
kubectl patch application harbor-harbor \
66+
-n argocd \
67+
--type='json' \
68+
-p='[{"op": "add", "path": "/spec/syncPolicy/automated", "value": {"prune": true,"selfHeal": true}}]'
69+
```
94 KB
Loading

sidebar-docs.js

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,8 @@ module.exports = {
130130
"for-ops/disaster-recovery/platform-reinstall",
131131
],
132132
},
133+
"for-ops/upgrade-instructions",
134+
"for-ops/upgrade-notes",
133135
"for-ops/known-issues",
134136
"for-ops/security-best-practices",
135137
],

0 commit comments

Comments
 (0)