Headlamp integration with Big Bang
-
Have you added a namespace.yamlinchart/templatesthat sets up the package's namespace -
Have you added pull secret creation to a resource? This may be in the namespace.yamlfile. -
Have you added a gitrepository.yamlinchart/templatesthat sets up a flux GitRepository resource pointing to the package's git repository? -
Have you added a helmrelease.yamlinchart/templatesthat sets up a flux HelmRelease resource pointing to the package's helm chart? -
Have you added default values to the HelmRelease that need to be passed downstream to the package? For example: hostname,istio.enabled,monitoring.enabled. -
Have you added image pull secret references to the HelmRelease to be passed downstream to the package? -
Have you added other package dependencies to the HelmRelease to ensure deployment order? -
Have you added a key for <package>.yamlintochart/templates/values.yamlso override values can be passed downstream to the package? -
Have you added a valuesFrom configuration in the HelmRelease pointing to the values secret with a valuesKey equal to <package>.yaml? -
Have you added the package into chart/values.yamlunder addons? Exception: core apps do not go under addons. -
Have you added enabled: false to your chart/values.yamland conditional statements on enabled: true for your namespace, pull secret, git repository, and helm release? -
Have you added git repo configuration to chart/values.yamlpointing to the packages git repo, helm chart path, and tag. -
Have you added a values: {} placeholder for you package in chart/values.yaml? -
Have you added any applicable default values from Fences and Party Bus to the package? Exception: Infrastructure specific implementations (e.g. AWS)
Edited by Sam Vongsay