mirror of https://github.com/dapr/docs.git
				
				
				
			Merge pull request #1358 from dapr/wcs1only-patch-1
Update kubernetes-upgrade.md
This commit is contained in:
		
						commit
						2fa35c108d
					
				|  | @ -25,6 +25,26 @@ The example below shows how to upgrade to version 1.1.0: | ||||||
| You can provide all the available Helm chart configurations using the Dapr CLI. | You can provide all the available Helm chart configurations using the Dapr CLI. | ||||||
| See [here](https://github.com/dapr/cli#supplying-helm-values) for more info. | See [here](https://github.com/dapr/cli#supplying-helm-values) for more info. | ||||||
| 
 | 
 | ||||||
|  | #### Troubleshooting upgrade using the CLI | ||||||
|  | 
 | ||||||
|  | There is a known issue running upgrades on clusters that may have previously had a version prior to 1.0.0-rc.2 installed on a cluster. | ||||||
|  | 
 | ||||||
|  | Most users should not encounter this issue, but there are a few upgrade path edge cases that may leave an incompatible CustomResourceDefinition installed on your cluster. The error message for this case looks like this: | ||||||
|  | 
 | ||||||
|  | ``` | ||||||
|  | ❌  Failed to upgrade Dapr: Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply | ||||||
|  | The CustomResourceDefinition "configurations.dapr.io" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema | ||||||
|  | 
 | ||||||
|  | ``` | ||||||
|  | 
 | ||||||
|  | To resolve this issue please run the follow command to upgrade the CustomResourceDefinition to a compatible version: | ||||||
|  | 
 | ||||||
|  | ``` | ||||||
|  | kubectl replace -f https://raw.githubusercontent.com/dapr/dapr/5a15b3e0f093d2d0938b12f144c7047474a290fe/charts/dapr/crds/configuration.yaml | ||||||
|  | ``` | ||||||
|  | 
 | ||||||
|  | Then proceed with the `dapr upgrade --runtime-version 1.1.0 -k` command as above. | ||||||
|  | 
 | ||||||
| ### Helm | ### Helm | ||||||
| 
 | 
 | ||||||
| From version 1.0.0 onwards, upgrading Dapr using Helm is no longer a disruptive action since existing certificate values will automatically be re-used. | From version 1.0.0 onwards, upgrading Dapr using Helm is no longer a disruptive action since existing certificate values will automatically be re-used. | ||||||
|  | @ -64,4 +84,4 @@ From version 1.0.0 onwards, upgrading Dapr using Helm is no longer a disruptive | ||||||
| ## Next steps | ## Next steps | ||||||
| 
 | 
 | ||||||
| - [Dapr on Kubernetes]({{< ref kubernetes-overview.md >}}) | - [Dapr on Kubernetes]({{< ref kubernetes-overview.md >}}) | ||||||
| - [Dapr production guidelines]({{< ref kubernetes-production.md >}}) | - [Dapr production guidelines]({{< ref kubernetes-production.md >}}) | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue