openvnf / sftp-server Goto Github PK

Starting with Kubernetes v1.16 Deployment, StatefulSet, and DaemonSet are no longer available in API version extensions/v1beta1, as they are available in apps/v1 since v1.9: https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

The templates need to be updated to consider this and support k8s 1.16.

In production, 2 problems regarding the health-status of the sftp-server go unnoticed.
The sftp-server suddenly stops receiving files regularly, or they are not picked up anymore regularly.
We discussed in #9808 if a mechanism is needed to track if timeouts are happening on either side.

Imo, incoming senders should monitor their own file-pushing, i.e. add the sftp-server as a pingexporter-target. (CGW/rpg already allow this option).
But would a check if files are piling up on the server make sense, or should that be monitored on the outgoing containers as well (ipsec/BGP on CGW)?

Don't want to commit to using this till there's a license. If you could add one that would be great

This chart currently has no sidecar-container or NET_ADMIN capabilities in the main container, which makes testing routes (or MTU) tedious at times.

Hi,

for future reference,
https://github.com/openvnf/sftp-server/blob/master/templates/deployment.yaml#L83

is rendered like this :

          resources:            limits:
              cpu: 100m
              memory: 128Mi
            requests:
              cpu: 100m
              memory: 128Mi

it is rendered as expected if I change it to :

          resources:
{{ toYaml .Values.resources.sftp | indent 12 }}

When pushing to the sftp server as a user to subdirectories, they are not allowed to push anything by default.
Although sftp-server-pods have a long lifetime, they sometimes need to be manually "prepared" - making them non-stateless - like so:

/ # mkdir home/<user>/<subdirectory1>
/ # mkdir home/<user>/<subdirectory1>/<subdirectory2>
...
/ # chown -R roamcontrol:100 home/<user>/<subdirectory1>/

I suggest a mechanism that sets up the FS through containerscripting like above. The chart currently carries a KV sftpConfig.username so how about a range for sftpConfig.userdirectories?
e.g.:

sftpConfig:
   username: sftp
   userdirectories:
   - subdirectory1/subdirectory2
   - subdirectory3