Monorepo containing UIs for Flight Control

• Git, Node.js v22.x, npm v10.x, rsync, go (>= 1.24)

Checkout the repository and run:

cd flightctl-ui
npm ci
npm run build

The UI supports building containers for both Enterprise Linux 9 and 10. Containerfiles are organized by OS in a directory structure similar to the main FlightCtl repository:

packaging/images/el9/Containerfile       # EL9 standalone UI
packaging/images/el9/Containerfile.ocp   # EL9 OCP plugin UI
packaging/images/el10/Containerfile      # EL10 standalone UI
packaging/images/el10/Containerfile.ocp  # EL10 OCP plugin UI

Use the provided Makefile:

# Build for specific OS (default: el9)
make build-ui OS=el9        # Standalone UI for EL9
make build-ui OS=el10       # Standalone UI for EL10
make build-ocp-ui OS=el9    # OCP Plugin UI for EL9
make build-ocp-ui OS=el10   # OCP Plugin UI for EL10

# Build all variants
make build-all

# Show available targets
make help

Built images will use OS-qualified names:

• localhost/flightctl-ui-el9:latest and localhost/flightctl-ocp-ui-el9:latest
• localhost/flightctl-ui-el10:latest and localhost/flightctl-ocp-ui-el10:latest

If backend is running in your Kind cluster, use the following command to start the UI application. It will automatically detect your Flight Control deployment settings and it will configure the UI accordingly. (Requires kind, kubectl)

npm run dev:kind

See CONFIGURATION.md for complete configuration options.

If backend is not running in your Kind cluster, you need to specify your Flight Control deployment settings.

FLIGHTCTL_SERVER=<api_server_url> npm run dev

If the backend, or Auth provider is running self-signed certs, you will need to disable the verification via environment variables:

• FLIGHTCTL_SERVER_INSECURE_SKIP_VERIFY='true' - to disable verification of backend certs
• AUTH_INSECURE_SKIP_VERIFY='true' - to disable verification of auth server certs

or provide the CA certs:

• copy backend ca.crt to ./certs/ca.crt
• copy Auth ca.crt to ./certs/ca_auth.crt

See CONFIGURATION.md for complete configuration options.

With this option, the Flight Control UI will run as a Plugin in the OCP console. Note: this setup is only for development, do not use it in Production environments!

Login to OCP cluster and run:

npm run dev:ocp

By default, the latest available OpenShift console image will be used. To specify a different console version, set the CONSOLE_VERSION environment variable.

The following console versions are confirmed to be compatible: 4.16 to 4.20.