Community k8 charts

[matmair]

List of community sources for k8:

• https://github.com/laurensramandt/inventree-kubernetes
• https://github.com/ebauman/inventree-chart
• https://github.com/Frankkkkk/inventree-helm

EDIT: New home for this will be https://github.com/inventree/inventree-helm-chart

[SchrodingersGat]

@matmair should we add this to the docs? Or the website under third party?

[matmair]

My preference would be to get some of these ppl together and create an official chart, this was more meant as a public place to collect them

[matmair]

@laurensramandt @ebauman @Frankkkkk

would you be interested in helping with an official kubernetes chart? There seems to be interested/confused users and the core team lacks the knowledge to create proper charts. If there are things that should be changed in core to make it easier I am more than willing to help with it, k8 is just not something I use in production.

[laurensramandt]

@matmair I can certainly help. As commented in another topic, I do consider helm charts superior to "ordinary" manifests so let's proceed with the foundation @Frankkkkk has made 🤞

[Frankkkkk]

With pleasure! Give me some days/a week and I can try to make a pr with a helmchart inspired by by the 3 repos :-)

[matmair]

That is really great! I would have imagined that we keep the charts in a separate repo in the InvenTree org. That way we can you / anyone else that wants help more rights on the repo as rights for InvenTree/InvenTree are pretty tightly controlled

[matmair]

@Frankkkkk / @laurensramandt I have gone ahead and created a new repo for this endeavour - feel free to create PRs and discussions there

https://github.com/inventree/inventree-helm-chart

[peterbaumert]

I saw in an issue a link to master...gusmann:InvenTree:helm-chart
There also seems to be already quite some work done regarding the helm chart.

[Frankkkkk]

Interesting. I was monitoring the other repo as I hadn't yet the time to work on it. I'd advocate for a separate repo though, makes things simpler :)

[peterbaumert]

Seperate repo makes sense yes. The one I posted also was several month ago and nothing happened anymore I think. But maybe some bits and pieces might be useful :)

[Mattie112]

We are running inventree in k8s, just not via helm. We are using the "normal" deployments / yaml.

Perhaps it is enough to provide some example yaml files for people that want it in k8s? Without the need for a helm chart? I'd be happy to share what we have.

[barrowkwan]

@Mattie112 I also deploy inventree with kubernetes deployment manifest (yaml), do you deploy with multiple replica? if so how do you handle the local storage ( eg media files ). Right now I only deploy with 1 replica and wonder if media file or any file upload from one replica , it will save in that replica local fs only.

[Mattie112]

We are using an AWS EKS Cluster. Storage is handled by AWS. We currently use EBS (which indeed can only be used once and only in a single region) but are planning to move it to EFS which also supports concurrent uses.

I must say that for us having a single InvenTree instance is fine. If it happens to crash / restarts it is back up quick enough that it is not a real problem for us.

[kquinsland]

I also run inventree in k8s using kustomize (helm is ... complicated; the number of "nice" things I can say about it is a rounding-error away from 0).

It's worth pointing out that inventree is similar to netbox in structure so a lot of the supporting deployment/pod/service ... etc that you'd use for that applies here.

The documentation I have for "the very first deploy" basically boils down to:

• Un-comment the sleep hook in the deployment
• scale the deployment to 1
• shell into the pod
• run bash init.sh invoke update and wait until you get the Settings cleaned successfully message
• exit the shell, update the deployment to use the regular entrypoint

            containers:
                - name: inventree-server
                  image: inventree/inventree:1.1.5@sha256:329d7b254bc8bc1bb83be54603bc6a99685445d237f27e0c79a0622a1a5608a4
                  imagePullPolicy: Always
                  # Debugging and initial setup only
                  # See: https://docs.inventree.org/en/latest/start/docker_install/#initial-database-setup
                  ##
                  #   command: ["/bin/sh"]
                  #   args: ["-c", "sleep infinity"]

It would be relatively straight forward to add a super basic check in the init.sh or similar to effectively look for either a flag/file on the PVC that indicates the initial setup has been run before and go straight to the current/regular code-path. If the flag is not present, do the init work and then jump to the regular code path.

[matmair]

Thank you for your off topic contribution. Your comment exactly shows why the goal is a helm chart and not some "simple" yaml that needs manual, nonstandardized action to stand up an environment.

[Mattie112]

Just for the funs of it, here are the files I use to deploy it. Perhaps someone can use it. We use our regular DB setup so we don't have a DB included in the deployment here. We do have S3 added for backups. The PVC setup might not be the best, see #8823 (reply in thread)

We also use kustomize, I did not add those files.

cache-deployment.yaml
cache-service.yaml
cm-configmap.yaml
cm-nginx-config.yaml
deployment.yaml
pvc.yaml
service.yaml
worker-deployment.yaml
ingress.yaml
patch-deployment.yaml

Perhaps someone can use this as input!