• Step00: Deployment of devops tools
  • Introduction
  • Kubernetes and Helm
  • DevopTools
• Registration of the local DNSs
  • Notes

Introduction

This section prepares the host to be ready for the deployment of the components.

Kubernetes and Helm

This guideline uses Kubernetes and Helm to deploy the infrastructure.

• In case you do not have a kubernetes cluster on hand, the installMicrok8s.sh contains the steps to quickly deploy a microK8s cluster on the host server.

  . scripts/quickInstall/installMicrok8s.sh
  # This scripts opens a new shell so, to continue the installation, the same command with a "2" param has to be run (2nd phase)
  . scripts/quickInstall/installMicrok8s.sh 2
  

• You can also follow the Helm install documentation to install the Helm tool.

DevopTools

There are a set of tools that based on clues, ease the life of people working with different devops tools such as git, docker, k8s or helm.
NOTE: These tools are designed to work on Ubuntu based systems.

Clone the devopTools repository and follow its README.md to deploy these tools.
The repository contains a quick deploy script to make the devopTools usable to be run from CLI.

git clone https://github.com/cgonzalezITA/devopsTools.git
cd devopsTools
. quickDeployment/deployDevopTools.sh 
  # add exec permissions to the devopTools
  QUESTION: (timeout=15s. def=y)--># To use aliases, the ~/.bash_aliases file must contain a few aliases. Do you want to add them? (y*|n)
  y
  # Review the ~/.bash_aliases file to check the content is not duplicated nor contains errors.  

  # Activating the aliases...
  Check yq is installed
  ✅🆗
  Checking jq is installed
  ✅🆗

This guideline uses the devoptTools commands to execute the required actions during the deployment, although the kubernetes or helm equivalent commands are also shown as comments in case you do not have an Ubuntu OS or do not want to install these tools. eg:

kGet -n consu
  #   Running command [kubectl get pod  -n consumer  ]
  ...

Registration of the local DNSs

This HOL relies on different DNSs for the different phases. The documentation introduces them and explains how to register them when they are required. For the local DNSs used (eg: fiwaredsc-consumer.local), there is a script (dsQuickinstall-dnsRegistration) that registers all of them to avoid repeating the same steps several times.

sudo ./scripts/quickInstall/dsQuickinstall-dnsRegistration.sh
    # Registers the DNSs used by the dsQuickInstall* scripts at the '/etc/hosts' file to map them with the host IP address
    QUESTION: (timeout=30s. def=y)--># To use the local DNSs at the host, it is required to add the following line to the '/etc/hosts' file:
    
    1.1.1.1  fiwaredsc-trustanchor.local fiwaredsc-consumer.local fiwaredsc-provider.local

    Do you want to insert it automatically? (y*|n)
    y
    To access them from a windows browser, add the same line to the 'C:\Windows\System32\drivers\etc\hosts' file.
    (timeout=5s)Press any key to review the /etc/hosts file
        ...
        # local DNS used by the https://github.com/cgonzalezITA/DSFiware-hackathon repository
        1.1.1.1  fiwaredsc-trustanchor.local fiwaredsc-consumer.local fiwaredsc-provider.local

Notes

• To get familiar with some Helm basic commands, you can visit the section Helm Repo operations of the devop Tools.
• Before a Helm chart can be used, a command to update the referenced dependencies has to be executed. The hFileCommand provides the -b flag to run this action. The build action creates inside the Helm chart's folder a subfolder named ./chart with the charts used by the specific Helm.
  Next scripts show the deployment of the provider's service helm chart:

  # Deployment of a Helm chart without the dependencies installed.
  hFileCommand service 
      # Running CMD=[helm -n provider install -f "./Helms/provider/services(dataplane)/values.yaml" services "./Helms/provider/services(dataplane)/"  --create-namespace]
      Error: INSTALLATION FAILED: An error occurred while checking for chart dependencies. You may need to run `helm dependency build` to fetch missing dependencies: found in Chart.yaml, but missing in charts/ directory: scorpio, postgresql
  
  # Deployment of a Helm chart 'building' the dependencies to be installed.
  hFileCommand service -b
      # Running command [helm -n provider dependency update './Helms/provider/services(dataplane)/' ]
      Hang tight while we grab the latest from your chart repositories...
      ...Successfully got an update from the "bitnami" chart repository
      Update Complete. ⎈Happy Helming!⎈
      # Running command [helm -n provider dependency build './Helms/provider/services(dataplane)/' ]
      ...
      # Running CMD=[helm -n provider install -f "./Helms/provider/services(dataplane)/values.yaml" services "./Helms/provider/services(dataplane)/"]
      ...      
  

NOTE: Next phase is Deployment of the apisix as gateway