Air gapped not supported

[floreseo2]

Since there are image that are hardcodec we can't deploy on a air gapped enviroment.
I worked on be able to configure all images with variables on https://github.com/floreseo2/kasm-helm

[bscarbrough]

@floreseo2, thanks for this, but if you take a look at the values.yaml file and scroll down to the kasmApp: block you'll see there all of the different image definitions we're using. You'll see multiple values listed there that you are free to modify as you have a need. For the image: value if you're using something besides Docker hub, you'll just need to set this to the full registry/container image path.

    kasmProxy:
      name: kasm-proxy
      addHealthChecks: true
      image: kasmweb/proxy    # Change this value to your mirrored image
      tag: 1.17.0                    # If you changed the tag in your mirror, then change this value
      replicas: null
      serviceKeepalive: 16

[floreseo2]

@bscarbrough Not all images has his own parameter to be configured. Let me share a list of file/image that are hardcode:

kasm-single-zone/templates/kasm-db/_db-pod-security.yaml: image: busybox
kasm-single-zone/templates/kasm-guac/guac.yaml: image: busybox
kasm-single-zone/templates/kasm-proxy/proxy.yaml: image: busybox
kasm-single-zone/templates/kasm-rdp-https-gateway/rdp-https-gateway.yaml: image: busybox
kasm-single-zone/templates/kasm-share/share.yaml: image: redis:5-alpine
kasm-single-zone/templates/_service-wait-containers.tpl: image: alpine/curl:8.8.0

[bscarbrough]

@floreseo2 , you're absolutely right, I must have forgotten about those. Until I can get an MR pushed, you can feel free to modify the busybox images and use the API server image as it has all the required binaries to do the same job as those helper containers. As for the redis:5-alpine, that's a part of our offline install container tarball (https://kasm-static-content.s3.amazonaws.com/kasm_release_service_images_amd64_1.17.0.7f020d.tar.gz), but it will require modifying the share.yaml file directly for now.

[geoffo-dev]

Just run into this issue as well - have a workaround for now, but would be nice to get it as part of the helm chart.

[bscarbrough]

@floreseo2, we've just made significant changes to the helm chart in the develop branch. These updates do a better job of presenting all the images required to launch kasm in Kubernetes and should give you a much better understanding of what's required and how to update the values to meet your environment.

Feel free to check it out and let me know if you have any other issues! I'll keep this ticket open till I hear back that this is resolved.