github.com/Racer159/jackal@v0.32.7-0.20240401174413-0bd2339e4f2e/adr/0010-yolo-mode.md (about)

     1  # 10. YOLO Mode
     2  
     3  Date: 2022-12-14
     4  
     5  ## Status
     6  
     7  Accepted
     8  
     9  ## Context
    10  
    11  Jackal was rooted in the idea of declarative K8s deployments for disconnected environments. Many of the design decisions made in Jackal are based on this idea. However, in certain connected environments, Jackal can still be leveraged as a way to define declarative deployments and upgrades without the constraints of disconnected environments. To that end, providing a declarative way to deploy Jackal packages without the need for a Jackal init package would be useful in such environments.
    12  
    13  ## Decision
    14  
    15  YOLO mode is an optional boolean config set in the `metadata` section of the Jackal package manifest. Setting `metadata.yolo=true` will deploy the Jackal package "as is" without needing the Jackal state to exist or the Jackal Agent mutating webhook. Jackal packages with YOLO mode enabled are not allowed to specify components with container images or Git repos and validation will prevent the package from being created.
    16  
    17  ## Consequences
    18  
    19  YOLO mode provides a way for existing, connected clusters to use Jackal for declarative deployments and upgrades because there is no need to perform any Jackal bootstrapping in order to deploy Jackal-packaged workloads. The addition of the `metadata.yolo` config should not affect existing Jackal users as it is entirely optional. Additionally, requiring the `metadata.yolo` config to be set to `true` and not allowing a runtime flag to override it makes it very clear both in `package create` and `package deploy` the intent and usage of the package.