Configuring containers in the Kubernetes session pod

FastX separates the FastX image and the running application image in separate containers so that an admin can use an already existing container when setting up an application. Admins may wish to standardize on a stable container to guarantee consistency across pods. This guide will help you set up the ConfigMap necessary to achieve this.

patches/patches-launcher-configmap.yaml

If you ran the create-cluster.sh file a patch configmap will be created. You can edit this file as needed

apiVersion: v1
kind: ConfigMap
metadata:
  name: launcher 
  namespace: fastx
data:
  # prefix of the image (ie its repo)
  # us-central1-docker.pkg.dev/starnet-containers/fastx
  FASTX_IMAGE_PREFIX: " us-central1-docker.pkg.dev/starnet-containers/fastx"
  # Set to never to no longer pull the newest version
  FASTX_IMAGE_PULL_POLICY: "Always"
  # set the fastx image tag.  There is no 'latest'.
  # latest-x86_64
  # latest-aarch64
  FASTX_IMAGE_TAG: "latest-x86_64"
  # this is the image tag for the default
  DEFAULT_IMAGE_TAG: "latest"
  # if no image is set in the app, this will be set
  # us-central1-docker.pkg.dev/starnet-containers/public-images/apps_xterm
  # us-central1-docker.pkg.dev/starnet-containers/public-images-arm/apps_xterm
  DEFAULT_IMAGE: "us-central1-docker.pkg.dev/starnet-containers/public-images/apps_xterm"

  

The default variables necessary to change the images are located in fastx-cluster/base/launcher/launcher-configmap.yaml.

app-image.js

If you need programmatically created variables on a per session basis, you can use a script to add these variables. The app-image.js file is created as a ConfigMap which can be edited and changed. This is for advanced users.

fastx-kubernetes/config/launcher-pod/app-image.js