Skip to main content
Version: 2.1.0

Deploy the RNR frontend

Docker Setup​

  1. Build docker image
docker build -t SERVICE_NAME . --build-arg GITHUB_TOKEN=GITHUB_TOKEN

  • Replace SERVICE_NAME with your service name

  • Replace GITHUB_TOKEN with your Github Personal Access Token

    note

    Refer to this guide to learn how to generate your GITHUB_TOKEN (Personal Access Token).

  1. Configure Environment Variables
  • Copy or rename the .env.example file into env.
  • Provide the necessary variables inside the .env file.
    info

    For detailed information on environment variables, refer to this.

  1. Run docker image
docker run --env-file .env SERVICE_NAME
  • Replace SERVICE_NAME with the service name you've set at step 1.

The RNR frontend service should now be running. You can access it using the host and port defined in the .env file.

Kubernetes Setup​

  1. Navigate to the "deployments" directory.

  2. Create the Deployment

kubectl apply -f deployment.yaml

This manifests file will instruct Kubernetes to deploy a Pod using rnr-web image from AGIL Ops Hub container registry.

  1. Create Service
kubectl apply -f service.yaml

This manifests file creates a ClusterIP services for accessing RNR-WEB pod. 4. Edit ingress.yaml and change the value of the Host field to the actual FQDN of your Kubernetes Cluster.

The example value in the ingress.yaml is using nip.io to create a FQDN to point to the Kubernetes Cluster. To use nip.io, simply replace 10.10.10.100 in the example value with the Ipv4 address of your Kubernetes Cluster.

  1. Create ingress
kubectl apply -f 03-ingress.yaml

Your RNR frontend service is now running with the host and port configured in the ingress (default is rnr-web.localhost).