You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
enabled installCRDs: true flag after upgrade helm-2.12.x to helm-2.16.10, and during helm upgrade --install step getting schedule CRD deleted after schedule template being created, which lead to removing schedule template.
As I understand, it because of post-upgrade hook in CRD
Anything else you would like to add:
Here is part of tiller log which shows that we install schedule template first, and delete/install CRD after that
[kube] 2020/09/20 08:45:13 checking 6 resources for changes
[kube] 2020/09/20 08:45:13 Looks like there are no changes for ServiceAccount "velero-server" in "velero"
[kube] 2020/09/20 08:45:13 Looks like there are no changes for ClusterRoleBinding "velero-server" in ""
[kube] 2020/09/20 08:45:13 Looks like there are no changes for Role "velero-server" in "velero"
[kube] 2020/09/20 08:45:13 Looks like there are no changes for RoleBinding "velero-server" in "velero"
[kube] 2020/09/20 08:45:13 Looks like there are no changes for Deployment "velero" in "velero"
add ---> [kube] 2020/09/20 08:45:13 Created a new Schedule called "velero-daily" in velero
[kube] 2020/09/20 08:45:13 beginning wait for 6 resources with timeout of 5m0s
[tiller] 2020/09/20 08:45:16 executing 13 post-upgrade hooks for velero
[tiller] 2020/09/20 08:45:16 deleting post-upgrade hook default for release velero due to "before-hook-creation" policy
[kube] 2020/09/20 08:45:17 Starting delete for "default" BackupStorageLocation
[kube] 2020/09/20 08:45:17 backupstoragelocations.velero.io "default" not found
[kube] 2020/09/20 08:45:17 Waiting for 60 seconds for delete to be completed
[kube] 2020/09/20 08:45:19 building resources from manifest
[kube] 2020/09/20 08:45:19 creating 1 resource(s)
[kube] 2020/09/20 08:45:19 Watching for changes to BackupStorageLocation default in velero with timeout of 5m0s
[kube] 2020/09/20 08:45:19 Add/Modify event for default: ADDED
[tiller] 2020/09/20 08:45:19 deleting post-upgrade hook gcp for release velero due to "before-hook-creation" policy
[kube] 2020/09/20 08:45:19 Starting delete for "gcp" VolumeSnapshotLocation
[kube] 2020/09/20 08:45:19 volumesnapshotlocations.velero.io "gcp" not found
[kube] 2020/09/20 08:45:19 Waiting for 60 seconds for delete to be completed
[kube] 2020/09/20 08:45:21 building resources from manifest
[kube] 2020/09/20 08:45:22 creating 1 resource(s)
[kube] 2020/09/20 08:45:22 Watching for changes to VolumeSnapshotLocation gcp in velero with timeout of 5m0s
[kube] 2020/09/20 08:45:22 Add/Modify event for gcp: ADDED
[tiller] 2020/09/20 08:45:22 deleting post-upgrade hook schedules.velero.io for release velero due to "before-hook-creation" policy
delete ---> [kube] 2020/09/20 08:45:23 Starting delete for "schedules.velero.io" CustomResourceDefinition
[kube] 2020/09/20 08:45:23 Waiting for 60 seconds for delete to be completed
[kube] 2020/09/20 08:45:25 building resources from manifest
[kube] 2020/09/20 08:45:25 creating 1 resource(s)
[kube] 2020/09/20 08:45:25 Watching for changes to CustomResourceDefinition schedules.velero.io in with timeout of 5m0s
[kube] 2020/09/20 08:45:25 Add/Modify event for schedules.velero.io: ADDED
[tiller] 2020/09/20 08:45:25 hooks complete for post-upgrade velero
[storage] 2020/09/20 08:45:25 updating release "velero.v254"
Environment:
helm version: 2.16.10
helm chart version and app version:
chart: 2.12.13
velero app: 1.4.2
What steps did you take and what happened:
enabled
installCRDs: true
flag after upgrade helm-2.12.x to helm-2.16.10, and duringhelm upgrade --install
step getting schedule CRD deleted after schedule template being created, which lead to removing schedule template.As I understand, it because of post-upgrade hook in CRD
What did you expect to happen:
get Schedule template not deleted after install
Anything else you would like to add:
Here is part of tiller log which shows that we install schedule template first, and delete/install CRD after that
Environment:
chart: 2.12.13
velero app: 1.4.2
/etc/os-release
):The text was updated successfully, but these errors were encountered: