Axigen on K8s - Anyone had success?

Support Install / Uninstall
1

I’ve been trying to get Axigen installed via helm. I’m running into crashloops and not much in the logs/describe to go on to fix it. I can’t tell if there’s something required in the values.yaml that I’m just missing. Unfortunately I can’t share my yaml due to the nature of my env.
The sterilized version is that I’m on RKE2, plenty of resources, etc. I am setting clusterKey and adminPassword, storageclass…set the service account…what other variable is required to customize?
The failures are the fe-proxy deployment and the fe-smtp statefulset.
Any insights are much appreciated.

2

Hello @mpwilks

The FE pods are waiting for BE pods to have all the containers running.

To validate that your BE pod(s) are running please check/share the logs for axigen container on BE pod(s) obtained using a command similar with:

kubectl logs BE_POD_NAME -c axigen

Regards,
Florin

3

I can see axigen 10.5.6 container running in the pod, but the log command gives me no logs. There’s an axi-init container that shows completed, axigen, and fluentbit-sidecar. The lack of logs is puzzling.

4

This is strange, the axigen container should have logs from axigen service start.
To try to find the root cause for the reported behaviour please provide me the output of below commands:

  • kubectl get pods
  • kubectl exec BE_POD_NAME -c axigen – grep “MachineCount” /axigen/var/run/axigen_lk.txt
  • kubectl get events --sort-by=.metadata.creationTimestamp --field-selector involvedObject.name=FE_SMTP_POD
  • kubectl get events --sort-by=.metadata.creationTimestamp --field-selector involvedObject.name=FE_PROXY_POD

Regards,
Florin

5

Here’s my output.
*** kubectl get pods
NAME READY STATUS RESTARTS AGE
axigen-mail-axiclumgr-5bc87fc456-hczsh 2/2 Running 0 18h
axigen-mail-fluentd-75dc5854c6-t5d66 1/1 Running 0 18h
axigen-mail-be-0 2/2 Running 0 18h
axigen-mail-fe-smtp-0 0/2 Init:CrashLoopBackOff 136 (3m22s ago) 18h
axigen-mail-fe-proxy-767688796d-zkmgg 0/2 Init:CrashLoopBackOff 136 (2m57s ago) 18h
***kubectl exec BE_POD_NAME -c axigen – grep “MachineCount” axigen/var/run/axigen_lk.txt
MachineCount = 1
***kubectl get events --sort-by=.metadata.creationTimestamp --field-selector involvedObject.name=FE_SMTP_POD
LAST SEEN TYPE REASON OBJECT MESSAGE
5m54s Warning BackOff pod/axigen-mail-fe-smtp-0 Back-off restarting failed container
26m Normal Pulled pod/axigen-mail-fe-smtp-0 Container image “axigen/axigen:10.5.6” already present on machine
***kubectl get events --sort-by=.metadata.creationTimestamp --field-selector involvedObject.name=FE_PROXY_POD
LAST SEEN TYPE REASON OBJECT MESSAGE
119s Warning BackOff pod/axigen-mail-fe-proxy-767688796d-zkmgg Back-off restarting failed container

6

We found the issue, your license key does not allow you to use a cluster:

axigen/var/run/axigen_lk.txt
MachineCount = 1

You may try to obtain a Service Provide trial licenses key or contact Axigen sales team for the trial licenses key.

7

Well, that makes sense…wasn’t on my radar.
Thanks for the help!