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
Release Does not reconcile after manually deleting helm release using helm cli
How can we reproduce it?
Install helm-provider:master and use providerconfig in-cluster.
Install release resource.
then delete the helm release using helm cli.
at least there's to much downtime after manually deleting the helm release(sometime the Release Object recreate the helm release)
But mostly, the release Object does not reconcile!
k get releases.helm.crossplane.io
NAME CHART VERSION SYNCED READY STATE REVISION DESCRIPTION AGE
opendistro opendistro-es 1.13.3 True True deployed 1 Install complete 15m
Status:
At Provider:
Release Description: Install complete
Revision: 1
State: deployed
Conditions:
Last Transition Time: 2021-07-16T15:32:46Z
Reason: Available
Status: True
Type: Ready
Last Transition Time: 2021-07-16T15:32:45Z
Reason: ReconcileSuccess
Status: True
Type: Synced
Synced: true
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal UpdatedExternalResource 16m managed/release.helm.crossplane.io Successfully requested update of external resource
Normal CreatedExternalResource 6m18s managed/release.helm.crossplane.io Successfully requested creation of external resource
The text was updated successfully, but these errors were encountered:
What happened?
Release Does not reconcile after manually deleting helm release using helm cli
How can we reproduce it?
Install helm-provider:master and use providerconfig in-cluster.
Install release resource.
then delete the helm release using helm cli.
at least there's to much downtime after manually deleting the helm release(sometime the Release Object recreate the helm release)
But mostly, the release Object does not reconcile!
What environment did it happen in?
Crossplane version: 1.3.0
Kubernetes version: v1.21.1
Kind Cluster.
The text was updated successfully, but these errors were encountered: