Kubernetes
paulmarshall opened this issue · comments
What are hurdles in configuring/operating FTS to work as a containerised workload (in kubernetes) as opposed to a "standard" deployment ??
Currently you can try to use the docker version, but this is not full supported.
we plan to support kubernetes in the 2.X family.
I've tried using the docker image in an example k8s deployment. Whilst clients could connect to the deployment (via a k8s service exposing a loadbalancer), FTS was unable to correctly receive COT messages from a message generator and pass them onto connected WinTAK clients.
Moving this to the docker repo
@LargoUsagi can you please check this out?
@LargoUsagi maybe it's time to dig up my old helm chart for FTS?
@rlex On my project, we don't use helm, instead favouring kustomize. In fact, our deployment is based heavily on the resultant manifests if the helm project was used.
What's interesting is that FTS doesn't work (see above) if the container image is deployed to k8s but works ok if the latest bin install is used on a standard VM install.
Glad to help to understand the challenges and contribute to the resolution.
Ultimately, I want to get the position where I can attach multiple WinTAK clients to a k8s deployed instance of FTS.....and quickly :-)
@paulmarshall There was a PR submitted today to resolve some of the configuration issues we had been seeing. Hopefully with an image using the new configuration we will have in this repository a docker compose and a k8s manifest shortly, that has always been the goal of this repo.
Personally I am going to be targeting k8s for the deployment of FTS as its what I put all apps personally developed or COTS.
@rlex I do think a helm chart will be highly likely for targeting the most frequent deployment types and dusting that code off once the container is building and working again would be worth it at this point.