Closed vianchiel closed 10 months ago
Hi @Ornias1993 and @xstar97 , thanks for the following up the issue. I've tried the new version 4.1.6 by both upgrading and fresh installing the app. The issue still persists and ports are still not mapped between pod and host.
I tried: Activating a win11 hyper-v VM per instructions at https://github.com/mikolatero/docker-vlmcsd (No connection) and Using my above mentioned k3s kubectl describe pod (Ports are still None)
The catalog item doesn't have the updated code, so the rpc port isn't even exposed yet 🤦♂️
Thanks for the clarification, I'll wait patiently in this case.
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists
App Name
vlmcsd-kms-server
Operating System
TrueNAS SCALE 23.10.1
App Version
4.1.5
Application Events
Application Logs
Application Configuration
Describe the bug
The application in the pod does not have a host port mapped to 1688. This results in failure to contact the kms server inside the pod.
Following results using k3s kubectl describe pod
To Reproduce
# k3s kubectl get namespaces
to get the app's namespace, likelyix-[appname]
# k3s kubectl -n ix-[appname] get pods
to get the pod's name# k3s kubectl -n ix-[appname] describe pod [podname]
and get the running configurationExpected Behavior
The application should automatically map host port 1688 to pod port 1688
Screenshots
NA
Additional Context
The chart should either automatically map port 1688 between pod and host OR The chart should allow customised port for the pod and host
I've read and agree with the following