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
I have an application that is being migrated to fleet. The original platform does not use helm. During the first migration, the two resources in the release, one is a native resource and the other is a custom resource. The native resource can be updated normally, but the custom resource cannot be updated. I think this is a problem with helm. I looked up some issues in helm and it seems to be related to this helm/helm#12827.
Then I set helm.force to true in fleet.yaml, hoping to update the resource using the replace method, but I found that fleet does not pass in the force parameter when installing, which makes it ineffective.But when updating, force is allowed.
This is the fleet code I saw
Is there an existing issue for this?
Current Behavior
I have an application that is being migrated to fleet. The original platform does not use helm. During the first migration, the two resources in the release, one is a native resource and the other is a custom resource. The native resource can be updated normally, but the custom resource cannot be updated. I think this is a problem with helm. I looked up some issues in helm and it seems to be related to this helm/helm#12827.
Then I set
helm.force
totrue
in fleet.yaml, hoping to update the resource using the replace method, but I found that fleet does not pass in theforce
parameter when installing, which makes it ineffective.But when updating,force
is allowed.This is the fleet code I saw
fleet/internal/helmdeployer/install.go
Lines 129 to 155 in 8765f42
fleet/internal/helmdeployer/install.go
Lines 158 to 179 in 8765f42
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: