rancher
/
fleet-docs
mirror of https://github.com/rancher/fleet-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #72 from rancher/clarify-bundle-fields 

Notes about bundle fields limitations
This commit is contained in:
Mario Manno 2023-06-07 14:57:27 +02:00 committed by GitHub
parent eef1ecccfc 184950d291
commit d6a383ec45
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/bundle-add.md
View File

@ -50,8 +50,19 @@ spec:
image: nginx:1.14.2 image: nginx:1.14.2
ports: ports:
- containerPort: 80 - containerPort: 80
name: nginx.yaml name: nginx.yaml
targets: targets:
- clusterName: local - clusterName: local
``` ```
## Limitations
Helm options related to downloading the helm chart will be ignored. The helm chart is downloaded by the fleet-cli, which creates the bundles. The bundle has to contain all the resources from the chart. Therefore the bundle will ignore:
* `spec.helm.repo`
* `spec.helm.charts`
You can't use a `fleet.yaml` in resources, it is only used by the fleet-cli to create bundles.
The `spec.targetRestrictions` field is not useful, as it is an allow list for targets specified in `spec.targets`. It is not needed, since `targets` are explicitly given in a bundle and an empty `targetRestrictions` defaults to allow.