Using the images with Helm
  • 15 Jan 2025
  • 1 Minute à lire
  • Sombre
    Lumière
  • PDF

Using the images with Helm

  • Sombre
    Lumière
  • PDF

The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article

You can use the example contained in the package (see Package overview) to set up a deployment using Helm.

The example files are for evaluation purposes only. They are a good starting point for your own deployment, but should not be used in productive environments "as is" without proper configuration.

The example files do not support minikube.

In particular, you need to do the following:

  • Update the pre-installed certificates.
  • Change the pre-defined credentials.

To run the images with Helm

  1. Import the image bundle archive into the local Docker registry:

    docker load ‑i images.tar
  2. Tag and push the images to a remote registry that can be accessed by your Kubernetes cluster:

    docker tag onespan_ias_maria:<release_version> <registry_url>/onespan_ias_maria:<release_version>
    
    docker tag onespan_mdc:<release_version> <registry_url>/onespan_mdc:<release_version>
    
    docker tag onespan_was:<release_version> <registry_url>/onespan_was:<release_version>
    
    docker push <registry_url>/onespan_ias_maria:<release_version>
    
    docker push <registry_url>/onespan_mdc:<release_version>
    
    docker push <registry_url>/onespan_was:<release_version>

    Replace the following:

    • release_version. The specific version of the images distributed in the package, e.g. 3.27.0.1234.
    • registry_url. The URL of the container image registry or repository that is intended to host/distribute the provided images, e.g. repo.myserver.com:5000.
  3. Change to the example deployment folder:

    cd package_folder/examples/helm

    Replace the following:

    • package_folder. The absolute path to the folder that contains the extracted package content.
  4. Set the values of the image fields in the following files in the templates folder accordingly:

    • was-deployment.yaml
    • ias-deployment.yaml
    • mdc-deployment.yaml
  5. Review and adapt the configuration for OneSpan Authentication Server and Message Delivery Component (MDC) using the GUI configuration image (see Using the GUI configuration image):

    sudo xhost +local:docker
    
    docker run --rm --user $(id -u) \
      -v $(pwd)/config:/mnt \
      -e DISPLAY=$DISPLAY \
      -v /tmp/.X11-unix/:/tmp/.X11-unix/ \
      onespan_config:<release_version>

    Replace the following:

    • release_version. The specific version of the images distributed in the package, e.g. 3.27.0.1234.
  6. Review and adapt the Helm chart configuration. In particular, note the following:

    • OneSpan Authentication Server and MDC log files are written to /dev/stdout of the respective pod. You need to configure the Kubernetes cluster to handle the log storage accordingly so you can retrieve the logs if required.
  7. Deploy the images:

    helm install . --name OAS

To stop running containers

  • Run the following command:

    helm del ‑‑purge OAS

Cet article vous a-t-il été utile ?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Ozzy, facilitant la découverte de connaissances grâce à l’intelligence conversationnelle