Skip to main content

7. Install the Controller

We are now going to install the Controller which exposes a RESTful API and web interface. The web interface enables you to easily manage your FSC installation using the browser.

The web interface of the Controller can be exposed through an ingress. In this tutorial we expect you to have a hostname for the Controller. E.g. 'controller-ui.example.com'.

If you have not installed Postgres as described in this guide then you need to make sure that a database called fsc_controller exists.

Install internal certificate​

Run the following command to install the internal Controller certificate on the Kubernetes cluster

kubectl apply -f controller-internal-tls.yaml

Check if the certificate has been created:

kubectl -n fsc get secrets | grep controller-internal-tls

The output should look similar to:

controller-internal-tls             kubernetes.io/tls    3      35s

Controller chart​

We are now going to create a configuration file for the Controller installation. Open the file controller-values.yaml in a text editor and edit the values below:

  • <hostname controller> replace this with the hostname of the Controller UI. E.g. controller-ui.example.com
  • <postgres-password> replace this with the Postgres password you saved earlier.
  • The value <file: ca.crt> must be replaced by the content of the file ca.crt. You have this file in your working directory.
    • Copy the content of the file excluding the '-----BEGIN XXXXXXXXX-----' and '-----END XXXXXXXXX-----' lines.
    • Paste the content between the start and end lines and make sure the alignment is the same as the start and end lines
    • Save the modified file

Make sure to save the file. Next, let's install the Controller:

helm -n fsc upgrade --install controller -f controller-values.yaml oci://registry-1.docker.io/federatedserviceconnectivity/open-fsc-controller

Check if the Controller is running:

kubectl -n fsc get pods

The output should look similar to:

NAME                                             READY   STATUS            RESTARTS   AGE
controller-open-fsc-controller-7fb775cc75-hjg76   1/1     Running           0          9s
postgresql-0                                      1/1     Running           0          14m
txlog-api-open-fsc-txlog-api-69f9487bf5-fqj2w     1/1     Running           0          6m32s

Open your browser and navigate to the path /contracts of the Controller UI. The address of the Controller is determined by the value you used for <hostname controller> in this step. E.g. https://controller-ui.example.com/contracts

You should see an empty overview of your Contracts. This means both your Manager and Controller are running.