Issue with NFS and configmaps

[reddyskp]

@adiroiban I am trying to deploy sftp plus. I am using configmaps to store the sftp configuration. When I create or update user configuration getting below error.
20049 DEFAULT-MANAGER admin 10.0.1.1:34124 Failed to save configuration changes to the local files. Changes will be discarded after server restart. Failed to write the configuration cache at /opt/sftpplus-ubuntu2004-x64-trial/configuration/server.ini.cache

Also I mounted storage at /srv/storage through NFS but I am unable to write the data thorugh admin panel. I tried manually creating files also by exec into the pod, getting the same error.

PFB for NFS error and file permission snippets.

Invalid account configuration for "test". Failed to create missing path in home "/srv/storage/test". [Errno 13] Permission denied: '/srv/storage/test'

Please help me on this

[adiroiban]

Hi,

It looks like the NFS storage is configured to only allow the root os account to read/write files.

On the NFS server you can change the permission to allow read write for the sftpplus account.

Inside the container you can type id to get the user id for the sftpplus account.

Then on the NFS server you can change the owner or group from root to the sftpplus account.

Regards

[reddyskp]

@adiroiban Thanks for that, Now I understand. Will try that. but the main issue is, server.ini configuration through configmaps. As per my knowledge configmaps are not meant to be writable from POD, so If we create any user through SFTP admin panel and POD restarts, User configuration gets erased. So any alternative to make server.ini configuration also persistent.

Getting below error if I use configmap yaml mentioned in the repo.

20049 DEFAULT-MANAGER admin 10.0.1.1:34124 Failed to save configuration changes to the local files. Changes will be discarded after server restart. Failed to write the configuration cache at /opt/sftpplus-ubuntu2004-x64-trial/configuration/server.ini.cache

[adiroiban]

SFTPPlus has 2 main configuration methods:

• direct edit of the server.ini file - This is what k8s ConfigMap is using
• Using the Local Manager web interface to edit the server.ini

The 2 methods can't be mixed.
If you go for ConfigMap you will need to manually add your users to the ConfigMap option.

Our current customers are using SFTPPlus with Kubernetes without the Local Manager web interface.
SFTPPlus has a set of HTTP API that you can use to integrate with your micro-service infrastructure.

We are fully aware that for same cases you will want SFTPPlus in a cluster but continue to use the Local Manager web interface.
We are working to create an SFTPPlus Controller web interface that can be used to configure SFTPPlus in a cluster (Kubernets and any other cluster).
This functionality will be available before the end of the year. We are targeting the end of November.

What is the timeline of your project?