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
Customer is running Kasten K10 as backup software using Fleet. However, the recent changes in the kasten chart introduce the directory named
{values} and it prevant the upgrade using Fleet. Normal helm install works fine
Following is the error from Fleet
_*While calculating status.ResourceKey, error running helm template for bundle kasten-kasten with target options from internal-apps: error while running post render on files: illegal name '{values}
' in directory creation.*_
Issue is with the presence of Kustomization.yaml with patchesStrategicMerge and customer required to patch it as they have a strict ‘infra-as-code’ policy and patching the service manually can have unpredictable implications.
Business impact:
They are planning on a Rancher upgrade in their env , but they would prefer to update Kasten first before Rancher.
Repro steps:
Install the attached Kasten chart which has 6.0.10
You will see the error
Same wont happen with v6.0.6 version, changing the version to 6.0.10 causes issues
Workaround:
Is a workaround available and implemented? yes, partial workaround
Remove the ovelays directory in the git repository or kustomization.yaml, but it removes the ability to patch the service, which is not desired
Actual behavior:
Fleet fails to deploy the application due to the presence of a directory contains curly braces in chart
Expected behavior:
Fleet should successfully deploy chart with
{values}
directory
The text was updated successfully, but these errors were encountered:
SURE-9505
Issue description:
Customer is running Kasten K10 as backup software using Fleet. However, the recent changes in the kasten chart introduce the directory named
{values} and it prevant the upgrade using Fleet. Normal helm install works fine
Following is the error from Fleet
Issue is with the presence of Kustomization.yaml with patchesStrategicMerge and customer required to patch it as they have a strict ‘infra-as-code’ policy and patching the service manually can have unpredictable implications.
Business impact:
They are planning on a Rancher upgrade in their env , but they would prefer to update Kasten first before Rancher.
Repro steps:
Install the attached Kasten chart which has 6.0.10
You will see the error
Same wont happen with v6.0.6 version, changing the version to 6.0.10 causes issues
Workaround:
Is a workaround available and implemented? yes, partial workaround
Remove the ovelays directory in the git repository or kustomization.yaml, but it removes the ability to patch the service, which is not desired
Actual behavior:
Fleet fails to deploy the application due to the presence of a directory contains curly braces in chart
Expected behavior:
Fleet should successfully deploy chart with
directory
The text was updated successfully, but these errors were encountered: