Description of the illustration continous_delivery_mechanism

  1. All configuration for Flux-CD, Kustomize and OSM CN is stored in a git repository.
  2. Flux-CD is instructed to monitor and process this using a bootstrap command.
  3. This reads the configuration and installs Flux-CD controllers in a flux-CD namespace for this OSM instance.
  4. Using one of these controllers - the Kustomization controller, Flux-CD generates resources in the OSM CN namespace to hold configuration from git that will be required at runtime.
  5. Finally, the Flux-CD Helm controller invokes the OSM CN Introspector Helm chart. The OSM CN Introspector Job then compares the desired target state configuration (as relayed from git) with the actual state of the instance. It calculates the operations required to reconcile the two states and runs them.
  6. This results in the OSM cloud native instance being brought in line with the configuration.