-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: support for dependencies downloading #1672
Comments
A new flag `disableDependencyUpdate` is added in order to disable the feature, which is active by default. Fixes: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added in order to disable the feature, which is active by default. Fixes: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added in order to disable the feature, which is active by default. Fixes: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. Fixes: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]> e2e
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. Fixes: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
A new flag `disableDependencyUpdate` is added to the `fleet.yaml` file in order to disable the feature, which is active by default. A new package `helmupdater` is added to implement the dependencies update. The implementation is based on helm's when ussing the `--dependency-update` flag in the install command. Dependencies are applied to the bundle (upstream) to they're resolved already when applying downstream. Refers to: rancher#1672 Signed-off-by: Xavi Garcia <[email protected]>
@0xavi0 QA Template is missing, can you please add it, Thanks 😄 |
QA TemplateSolutionChanged fleet to download dependencies found in helm charts by default. TestingRepository with helm chart and disableDependencyUpdate not setAdd a new apiVersion: fleet.cattle.io/v1alpha1
kind: GitRepo
metadata:
name: sample-deps-simple
namespace: fleet-local
spec:
repo: "https://github.com/0xavi0/fleet-examples"
branch: test-dependencies
paths:
- single-cluster/helm-dependencies/deps-simple This will install the typical sample application from fleet-examples, but will also deploy a Same as above but with disableDependencyUpdate setapiVersion: fleet.cattle.io/v1alpha1
kind: GitRepo
metadata:
name: sample-no-deps-simple
namespace: fleet-local
spec:
repo: "https://github.com/0xavi0/fleet-examples"
branch: test-dependencies
paths:
- single-cluster/helm-dependencies/no-deps-simple In this case the sample application should be deployed but not the Additional info |
System Information
TEST RESULT Scenarios
|
Is your feature request related to a problem?
Yes, I have a chart that has dependencies and currently it's not possible to install.
Solution you'd like
Rancher should automatically install dependencies.
helm install
documentation mentions--dependency-update
option which should solve the issue without having to deal withdependency update
ordependency build
(as mentioned in the docs: https://ranchermanager.docs.rancher.com/v2.7/how-to-guides/new-user-guides/deploy-apps-across-clusters/fleet#helm-chart-dependencies)Alternatives you've considered
One could put the chart tgz file in the repo, but it's not really feasible for external charts/repositories...
Anything else?
There is #250 but it was closed as "solved" (by adding documentation blurb that it doesn't work, which well... doesn't solve anything...)
The text was updated successfully, but these errors were encountered: