mirror of https://github.com/knative/docs.git
Add upgrading your install file (#2087)
* Add upgrading your install file * Update Eventing link to point to Eventing page * responding to feedback * further updates based on feedback * fix whitespace * one more whitespace tweak
This commit is contained in:
Sam O'Dell
GitHub
parent
aeebd0ab1f
commit
10c823ffd7
docs/install
|
|
@ -0,0 +1,141 @@
|
|||
---
|
||||
title: "Upgrading your installation"
|
||||
weight: 21
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
To upgrade your Knative components and plugins, run the `kubectl apply` command
|
||||
to install the subsequent release. We recommend upgrading by a single
|
||||
[minor](https://semver.org/) version number. For example, if you have v0.6.0 installed,
|
||||
you should upgrade to v0.7.0 before attempting to upgrade to v0.8.0. To verify the version
|
||||
number you currently have installed, see
|
||||
[Checking your installation version](./check-install-version.md).
|
||||
|
||||
If you installed Knative using the either the [eventing-operator](https://github.com/knative/eventing-operator) or [serving-operator](https://github.com/knative/serving-operator) plug-ins, the upgrade process will differ. See the [serving-operator upgrade guide](https://github.com/knative/serving-operator/blob/master/doc/upgrade_guide.md) and the [eventing-operator upgrade guide](https://github.com/knative/eventing-operator/blob/master/doc/upgrade_guide.md) to learn how to upgrade an install managed by the operators.
|
||||
|
||||
## Before you begin
|
||||
|
||||
Before upgrading, there are a few steps you must take to ensure a successful
|
||||
upgrade process.
|
||||
|
||||
### Identify breaking changes
|
||||
|
||||
You should be aware of any breaking changes between your current and desired
|
||||
versions of Knative. Breaking changes between Knative versions are documented in
|
||||
the Knative release notes. Before upgrading, review the release notes for the
|
||||
target version to learn about any changes you might need to make to your Knative
|
||||
applications:
|
||||
|
||||
- [Serving](https://github.com/knative/serving/releases)
|
||||
- [Eventing](https://github.com/knative/eventing/releases)
|
||||
- [Eventing-Contrib](https://github.com/knative/eventing-contrib/releases)
|
||||
|
||||
Release notes are published with each version on the "Releases" page of their
|
||||
respective repositories in GitHub.
|
||||
|
||||
### View current pod status
|
||||
|
||||
Before upgrading, view the status of the pods for the namespaces you plan on
|
||||
upgrading. This allows you to compare the before and after state of your
|
||||
namespace. For example, if you are upgrading Knative Serving, Eventing, and the
|
||||
monitoring plug-in, enter the following commands to see the current state of
|
||||
each namespace:
|
||||
|
||||
```bash
|
||||
kubectl get pods --namespace knative-serving
|
||||
```
|
||||
|
||||
```bash
|
||||
kubectl get pods --namespace knative-eventing
|
||||
```
|
||||
|
||||
```bash
|
||||
kubectl get pods --namespace knative-monitoring
|
||||
```
|
||||
|
||||
### Upgrading plug-ins
|
||||
|
||||
If you have a plug-in installed, make sure to upgrade it at the same time as
|
||||
you upgrade your Knative components. For example, if you have the
|
||||
monitoring plug-in installed, upgrade it alongside Knative Serving and Eventing.
|
||||
|
||||
## Performing the upgrade
|
||||
|
||||
To upgrade, apply the `.yaml` files for the subsequent minor versions of all
|
||||
your installed Knative components and features, remembering to only
|
||||
upgrade by one minor version at a time. For a cluster running v0.10.0 of the
|
||||
Knative Serving and Eventing components and the monitoring plug-in, the
|
||||
following command upgrades the installation to v0.11.0:
|
||||
|
||||
```bash
|
||||
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.11.0/serving.yaml \
|
||||
--filename https://github.com/knative/eventing/releases/download/v0.11.0/release.yaml \
|
||||
--filename https://github.com/knative/serving/releases/download/v0.11.0/monitoring.yaml
|
||||
```
|
||||
|
||||
## Verifying the upgrade
|
||||
|
||||
To confirm that your components and plugins have successfully upgraded, view the
|
||||
status of their pods in the relevant namespaces. All pods will restart during
|
||||
the upgrade and their age will reset. If you upgraded Knative Serving, Eventing,
|
||||
and the monitoring plug-in, enter the following commands to get information
|
||||
about the pods for each namespace:
|
||||
|
||||
```bash
|
||||
kubectl get pods --namespace knative-serving
|
||||
```
|
||||
|
||||
```bash
|
||||
kubectl get pods --namespace knative-eventing
|
||||
```
|
||||
|
||||
```bash
|
||||
kubectl get pods --namespace knative-monitoring
|
||||
```
|
||||
|
||||
These commands return something similar to:
|
||||
|
||||
```bash
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
activator-79f674fb7b-dgvss 2/2 Running 0 43s
|
||||
autoscaler-96dc49858-b24bm 2/2 Running 1 43s
|
||||
autoscaler-hpa-d887d4895-njtrb 1/1 Running 0 43s
|
||||
controller-6bcdd87fd6-zz9fx 1/1 Running 0 41s
|
||||
networking-istio-7fcd97cbf7-z2xmr 1/1 Running 0 40s
|
||||
webhook-747b799559-4sj6q 1/1 Running 0 41s
|
||||
```
|
||||
|
||||
```bash
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
eventing-controller-69ffcc6f7d-5l7th 1/1 Running 0 83s
|
||||
eventing-webhook-6c56fcd86c-42dr8 1/1 Running 0 81s
|
||||
imc-controller-6bcf5957b5-6ccp2 1/1 Running 0 80s
|
||||
imc-dispatcher-f59b7c57-q9xcl 1/1 Running 0 80s
|
||||
sources-controller-8596684d7b-jxkmd 1/1 Running 0 83s
|
||||
```
|
||||
|
||||
```bash
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
elasticsearch-logging-0 1/1 Running 0 117s
|
||||
elasticsearch-logging-1 1/1 Running 0 83s
|
||||
fluentd-ds-dqzr7 1/1 Running 0 116s
|
||||
fluentd-ds-dspjc 1/1 Running 0 116s
|
||||
fluentd-ds-x9xg7 1/1 Running 0 116s
|
||||
grafana-59568f8f48-bz2ll 1/1 Running 0 111s
|
||||
kibana-logging-b5d75f556-pwzkg 1/1 Running 0 116s
|
||||
kube-state-metrics-5cb5c6986b-qp6pw 1/1 Running 0 116s
|
||||
node-exporter-bgtsb 2/2 Running 0 112s
|
||||
node-exporter-cqrqv 2/2 Running 0 112s
|
||||
node-exporter-xwv7f 2/2 Running 0 112s
|
||||
prometheus-system-0 1/1 Running 0 110s
|
||||
prometheus-system-1 1/1 Running 0 110s
|
||||
```
|
||||
|
||||
If the age of all your pods has been reset and all pods are up and running, the
|
||||
upgrade was completed successfully. You might notice a status of "Terminating"
|
||||
for the old pods as they are cleaned up.
|
||||
|
||||
If necessary, repeat the upgrade process until your reach your desired minor
|
||||
version number.
|
||||
|
||||
Loading…
Reference in New Issue