Skip to main content

CIFS / Network Mounts

Installing the CSI SMB Driver​

To use CIFS mounts in Webup, you must first configure AHD Commons to install the CSI SMB Driver.

To do that, update the AHD Commons configurations to include:

csiDriverSmb:
  enabled: true

Creating CIFS Mounts​

The end user can create any amount of mounts he/she wants, by simply filling the array in values.yaml under webup.shares

an example of a CIFS mount in the webup.shares field of Values.yaml:

webup:
  shares:
    # the share's name - must be an unique name!
  - name: share1
    # the remote server name + path to mount
    device: 172.16.2.19/smeup
    # the username used to authenticate with the remote server
    user: user1
    # the password used to authenticate with the remote server
    password: pwd1
    # (optional) the domain
    domain: domain1
    # (optional) the aliases for the share
    alias: [custom.domain/smeup]
    # (optional) additional mount configuration parameters for the mount
    additionalMountParams: []

To configure the same mounts for H53 too, you must also fill out the array h53.shares, like in the following example.

info

You can use the optional field overrideMountPath to mount the share in a custom directory!

h53:
  shares:
    # share1 will be mounted under /mnt/share1
    - name: share1
    - name: share2
      # use 'overrideMountPath' to mount to a specific directory
      overrideMountPath: /my-custom-path

Troubleshooting errors​

If one or more mounts are configured incorrectly, webup will not start.

The issue will present itself by showing the webup container in a init state. Using kubectl events will also show some errors coming from the CSI Driver SMB.

If you have access to the server, you can run sudo dmesg to watch Kernel logs and find clearer errors, such as BAD NETWORK NAME (indicating a wrong remote share name).