Bundle Resource

Bundles are automatically created by Fleet when a GitRepo is created.

The content of the resource corresponds to the BundleSpec. For more information on how to use the Bundle resource Create a Bundle Resource.

  1. kind: Bundle
  2. apiVersion: fleet.cattle.io/v1alpha1
  3. metadata:
  4.   # Any name can be used here
  5.   name: my-bundle
  6.   # For single cluster use fleet-local, otherwise use the namespace of
  7.   # your choosing
  8.   namespace: fleet-local
  9. spec:
  10.   # Namespace used for resources that do not specify a namespace.
  11.   # This field is not used to enforce or lock down the deployment to a specific namespace.
  12.   # defaultNamespace: test
  14.   # If present will assign all resource to this
  15.   # namespace and if any cluster scoped resource exists the deployment will fail.
  16.   # targetNamespace: app
  18.   # Kustomize options for the deployment, like the dir containing the kustomization.yaml file.
  19.   # kustomize: ...
  21.   # Helm options for the deployment, like the chart name, repo and values.
  22.   # helm: ...
  24.   # ServiceAccount which will be used to perform this deployment.
  25.   # serviceAccount: sa
  27.   # ForceSyncGeneration is used to force a redeployment.
  28.   # forceSyncGeneration: 0
  30.   # YAML options, if using raw YAML these are names that map to overlays/{name} that will be used to replace or patch a resource.
  31.   # yaml: ...
  33.   # Diff can be used to ignore the modified state of objects which are amended at runtime.
  34.   # A specific commit or tag can also be watched.
  35.   #
  36.   # diff: ...
  38.   # KeepResources can be used to keep the deployed resources when removing the bundle.
  39.   # keepResources: false
  41.   # If set to true, will stop any BundleDeployments from being updated. It will be marked as out of sync.
  42.   # paused: false
  44.   # Controls the rollout of bundles, by defining partitions, canaries and percentages for cluster availability.
  45.   # rolloutStrategy: ...
  47.   # Contain the actual resources from the git repo which will be deployed.
  48.   resources:
  49.   - content: |
  50.       apiVersion: apps/v1
  51.       kind: Deployment
  52.       metadata:
  53.         name: nginx-deployment
  54.         labels:
  55.           app: nginx
  56.       spec:
  57.         replicas: 3
  58.         selector:
  59.           matchLabels:
  60.             app: nginx
  61.         template:
  62.           metadata:
  63.             labels:
  64.               app: nginx
  65.           spec:
  66.             containers:
  67.               - name: nginx
  68.                 image: nginx:1.14.2
  69.                 ports:
  70.                   - containerPort: 80
  71.     name: nginx.yaml
  73.   # Target clusters to deploy to if running Fleet in a multi-cluster
  74.   # style. Refer to the "Mapping to Downstream Clusters" docs for
  75.   # more information.
  76.   #
  77.   # targets: ...
  79.   # This field is used by Fleet internally, and it should not be modified manually.
  80.   # Fleet will copy all targets into targetRestrictions when a Bundle is created for a GitRepo.
  81.   # targetRestrictions: ...
  83.   # Refers to the bundles which must be ready before this bundle can be deployed.
  84.   # dependsOn: ...