Ta-Ching ChenandSoam Vasani
5f14b9b0ae
Switch Fission's storage over to the new CustomResourceDefinitions, from the deprecated ThirdPartyResources. This allows us to be compatible with Kubernets 1.8 and onwards. This also adds a CLI tool for dumping state from an old fission version and restoring state into new CRDs. The storage service is unaffected by this change.
3.6 KiB
title, date, draft
| title | date | draft |
|---|---|---|
| Upgrading from Fission v0.3 to v0.4.x | 2017-11-04T03:38:29+08:00 | false |
TL;DR
ThirdPartyResource is replaced by CustomResource and will be entirely deprecated in Kubernetes 1.8. Since Fission stores state in TPR, we need to migrate from TPRs to CRDs for future Kubernetes release.
Below we describe a tool for migrating your TPRs to CRDs.
How to Upgrade
- Get the v0.4-rc CLI
- Get the Fission state from v0.3 install
- Upgrade to Fission v0.4.0-rc
- Upgrade Kubernetes cluster version to 1.7.x or higher
- Remove all TPR definition (for Kubernetes 1.7.x)
- Restore Fission state into CRDs
Get the new CLI
OS X
$ curl -Lo fission https://github.com/fission/fission/releases/download/v0.4.0-rc/fission-cli-osx && chmod +x fission && sudo mv fission /usr/local/bin/
Linux
$ curl -Lo fission https://github.com/fission/fission/releases/download/v0.4.0-rc/fission-cli-linux && chmod +x fission && sudo mv fission /usr/local/bin/
Windows
For Windows, you can use the linux binary on WSL. Or you can download this windows executable: fission.exe
Get Fission state from v0.3 install
fission --server <your v0.3 server> tpr2crd dump --file state.json
You can skip the --server argument if you have the environment
variable $FISSION_URL set to point at a v0.3 Fission server.
This will create a JSON file with all your fission state in the current directory.
Upgrade to Fission v0.4.0-rc
Upgrade fission with a command similar to this:
helm upgrade fission-all --namespace fission
Upgrade Kubernetes cluster version
Since CustomResource is only supported on Kubernetes v1.7+ and higher, please make sure that you upgrade to the right version that supports CustomResource.
Remove all TPR definition (for Kubernetes 1.7.x)
** NOTICE **: This step will remove TPR definition from your kubernetes cluster. Please make sure that you dump all TPRs at the second step!
Though Kubernetes will migrate TPRs to CRDs automatically when TPR definition is deleted if the same name CRD exists. We still need to make sure that there is no resource gets lost during the migration. Also, since we changed the capitalization of some CRDs to CamelCase (e.g. Httptrigger -> HTTPTrigger), we need to recreate those resources by ourselves.
fission tpr2crd delete
Restore your Fission state into Fission v0.4.0-rc
fission tpr2crd restore --file state.json
This commands needs $FISSION_URL set to point to new fission installation.
It uses the file created in the first step. It doesn't modify state.json.
(Note that you can run this restore on any cluster; it doesn't have the be the same kubernetes cluster as your old install.)
Verify
Let's check the migration result, first run following command to check CRD established state.
kubectl get crd -o 'custom-columns=NAME:{.metadata.name},ESTABLISHED:{.status.conditions[?(@.type=="Established")].status}'
The output should be like this
NAME ESTABLISHED
environments.fission.io True
functions.fission.io True
httptriggers.fission.io True
kuberneteswatchtriggers.fission.io True
messagequeuetriggers.fission.io True
packages.fission.io True
timetriggers.fission.io True
And check that CRD resources you expect are there.
COMMAND:
fission [resource] list
RESOURCES:
environments
functions
httptriggers
kuberneteswatchtriggers
messagequeuetriggers
packages
timetriggers