[Starlingx-discuss] question about how to use helmV3 bin tool
Hi After helm upgrade to helmV3, I find I should use this command to list installed helm chart. controller-0:~$ helmv2-cli helm list NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE cm-cert-manager 1 Sun Jul 12 13:05:59 2020 DEPLOYED cert-manager-v0.1.0 cert-manager cm-cert-manager-psp-rolebinding 1 Sun Jul 12 13:06:10 2020 DEPLOYED psp-rolebinding-0.1.0 cert-manager ic-nginx-ingress 1 Sun Jul 12 13:04:34 2020 DEPLOYED nginx-ingress-1.4.0 kube-system stx-rook-ceph 1 Mon Jul 13 04:46:19 2020 DEPLOYED rook-ceph-0.0.1 kube-system stx-rook-ceph-provisioner 1 Mon Jul 13 04:48:01 2020 DEPLOYED rook-ceph-provisioner-0.1.0 kube-system controller-0:~$ But helm delete doesn't works. After I use helm delete, helm chart still could be listed. controller-0:~$ helmv2-cli 'helm delete --tiller-namespace kube-system stx-rook-ceph-provisioner' Error: the release named "stx-rook-ceph-provisioner" is already deleted command terminated with exit code 1 controller-0:~$ controller-0:~$ helmv2-cli helm list NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE cm-cert-manager 1 Sun Jul 12 13:05:59 2020 DEPLOYED cert-manager-v0.1.0 cert-manager cm-cert-manager-psp-rolebinding 1 Sun Jul 12 13:06:10 2020 DEPLOYED psp-rolebinding-0.1.0 cert-manager ic-nginx-ingress 1 Sun Jul 12 13:04:34 2020 DEPLOYED nginx-ingress-1.4.0 kube-system stx-rook-ceph 1 Mon Jul 13 04:46:19 2020 DEPLOYED rook-ceph-0.0.1 kube-system stx-rook-ceph-provisioner 1 Mon Jul 13 04:48:01 2020 DEPLOYED rook-ceph-provisioner-0.1.0 kube-system controller-0:~$ Any idea? Thanks Martin, Chen IOTG, Software Engineer 021-61164330
participants (1)
-
Chen, Haochuan Z