kenmoini / pilot-light Goto Github PK

The container is build, the steps, YAML, and service definition just needs to be added

This could be done by checking for a openshift-install-preprovided-path var in the config.yml file and skipping the download if it is there and the path is testable as a valid openshift-install binary path

For some reason when deployed to CentOS/RHEL the Golang DNS dialer is ignored and system /etc/resolv.conf DNS servers are still used.

So get this...use Pilot Light for a self-assembling environment based on DNS.
Add an extra custom_fcct_config key to the ignition_sets - include fcct into the functions of the program.
Then, pass that key to a file, fcct it up to ignition, serve OpenShift and custom CoreOS workloads assembled from Pilot Light.

A great example of this would be for the Pilot Light server itself, or HAProxy and DNS. This would speed up provisioning of complex OpenShift environments, like the ones driven into IBM Cloud via RHPDS.

Currently just gets "latest" - would be good to allow overriding with a specific version

Ability to log to multiple standard facilities, eg:

pilot_light:
  logging:
    - mode: stdout
      sinks:
        - name: sys_stdout
          target: stdout
        - name: file_stdout
          target: /var/log/pilot-light.log
    - mode: stderr
      sinks:
        - name: sys_stderr
          target: stderr
        - name: file_stderr
          target: /var/log/pilot-light-errors.log

Or something, idk, how does journald work again?