-
Notifications
You must be signed in to change notification settings - Fork 184
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.
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
docs: add 0.9.1 upgrade guides and update related commands in 0.9.0 #8262
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8262 +/- ##
==========================================
+ Coverage 61.32% 62.85% +1.53%
==========================================
Files 348 353 +5
Lines 40357 42568 +2211
==========================================
+ Hits 24749 26757 +2008
- Misses 13371 13504 +133
- Partials 2237 2307 +70
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
||
## Upgrade from KubeBlocks v0.9.0 | ||
|
||
1. Set keepAddons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "Preserve Addon resources during upgrade"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "Preserve Addon resources during upgrade"?
Great suggestion! I've added this sentence as the purpose of step 1 in the section "Upgrade from KubeBlocks v0.8" and adjusted related contents in the upgrade guide for v0.9.0.
For the section "Upgrade from v0.9.0", the description is a little different since keepAddon
is set as true
by default in Helm. Users just need to check its value. But crd.enabled
should be set as false
to avoid automatic CRD installation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
crd.enabled
can be set when upgrade kubeblocks. For preserve addon resource, recommend to run follow command:
kubectl annotate addons.extensions.kubeblocks.io -l app.kubernetes.io/name=kubeblocks helm.sh/resource-policy=keep
docs/user_docs/upgrade/upgrade with helm/upgrade-kubeblocks-to-0.9.md
Outdated
Show resolved
Hide resolved
docs/user_docs/upgrade/upgrade with helm/upgrade-kubeblocks-to-0.9.1.md
Outdated
Show resolved
Hide resolved
docs/user_docs/upgrade/upgrade-with-helm/upgrade-kubeblocks-to-0.9.1.md
Outdated
Show resolved
Hide resolved
docs/user_docs/upgrade/faq.md
Outdated
If you want to add the annotation for a specified Addon, replace `{addonName}` with the actual Addon name and run the command below. | ||
|
||
```bash | ||
kubectl annotate http://addons.extensions.kubeblocks.io {addonName} helm.sh/resource-policy=keep |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
http?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
http?
Fixed.
docs/user_docs/upgrade/faq.md
Outdated
kubectl annotate http://addons.extensions.kubeblocks.io {addonName} helm.sh/resource-policy=keep | ||
``` | ||
|
||
If you want to check whether the annotation for an Addon was added succeddfully, replace `{addonName}` with the actual Addon name and run the command below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"succeddfully"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"succeddfully"
Fixed.
docs/user_docs/upgrade/faq.md
Outdated
kubectl get addon -o json | jq '.items[] | {name: .metadata.name, annotations: .metadata.annotations}' | ||
``` | ||
|
||
### Manually add an annotation for an Addon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "for Addons"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "for Addons"
Fixed.
```shell | ||
kubectl replace -f https://github.com/apecloud/kubeblocks/releases/download/v0.9.0/kubeblocks_crds.yaml | ||
```bash | ||
kubectl create -f https://github.com/apecloud/kubeblocks/releases/download/v0.9.0/dataprotection.kubeblocks.io_storageproviders.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why install this CRD only?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why install this CRD only?
The upgrade process only requires installing this CRD and the process will handle the others.
kbcli addon index update kubeblocks | ||
|
||
kbcli addon upgrade xxx --force | ||
#Search available Addon versions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"# Search"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"# Search"
Fixed.
```bash | ||
kubectl get addon -o json | jq '.items[] | {name: .metadata.name, annotations: .metadata.annotations}' | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recommend to use the following command for a more concise output
kubectl get addon -o json | jq '.items[] | {name: .metadata.name, resource_policy: .metadata.annotations["helm.sh/resource-policy"]}'
If you want to check whether the annotation for an Addon was added successfully, replace `{addonName}` with the actual Addon name and run the command below. | ||
|
||
```bash | ||
kubectl get addon {addonName} -o json | jq '{name: .metadata.name, annotations: .metadata.annotations}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kubectl get addon {addonName} -o json | jq '{name: .metadata.name, resource_policy: .metadata.annotations["helm.sh/resource-policy"]}'
|
||
# Update helm repo | ||
helm repo update | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
better to add command to search the addon available versions:
helm search repo kubeblocks-addons/{addon-name} --versions --devel
follow update command will specify the chart version x.y.z.
No description provided.