sj14 / helm-charts Goto Github PK

Maybe I missed something but I don't get the purpose of the optional Ingress in this Helm chart.

An Ingress can only handle HTTP/HTTPS protocol, while the underlying service exposes the SSH/SFTP protocol.

Is it possible to access the server with an SFTP client through an Ingress?

The Helm chart currently allows to choose a Service type (ClusterIP by default).

However, if I choose a NodePort type, I found no way to set the corresponding high port: it's generated by k8s where I would like to set it.

Helm charts frequently provide extraVolumes and extraVolumeMounts settings in values.yaml for that purpose

I use this helm chart on very low-resource devices, that can sometimes get overwhelmed by their workload.
In this case, it can become very slow to give answers to probes, and thus be restarted by k8s.

I'd like to be able to configure these probes (timeout, polling frequency etc), or even to disable some of them (like keeping only the startupProbe, and relying on the fact that the process will probably die if it can not listen on its port any more).

Another (minor) issue with current probes is that they pollute the logs of the pod with many lines like:

Connection closed by 10.42.9.1 port 45552
kex_exchange_identification: Connection closed by remote host

However, I'm not sure it's possible to easily avoid this log pollution (except by disabling them). It would have been possible if the underlying docker image had an sftp client binary, but it does not seem to be the case.