<p>We are looking for viable option to map external windows file share inside  <strong>kubernetes+AWS-EKS</strong> hosted docker containers and few of the options. Windows file share being in same VPN is accessible with IP address</p>

<p>In absence of anything natively supported by kubernetes esp on EKS, we are trying Flexvolumes along with persistant volume. But that would need installation of cifs drivers on nodes which as I understand EKS does't provide being manages nodes. </p>

<p>Any option which doesn't require node level installation of custom drives including cifs etc?</p>

AnilR
<p>You could modify the cloudformation stack to install the drivers after startup, see 
<a href="https://amazon-eks.s3-us-west-2.amazonaws.com/cloudformation/windows-public-preview/amazon-eks-cfn-quickstart-windows.yaml" rel="nofollow noreferrer">https://amazon-eks.s3-us-west-2.amazonaws.com/cloudformation/windows-public-preview/amazon-eks-cfn-quickstart-windows.yaml</a> </p>

<p>It references <a href="https://amazon-eks.s3-us-west-2.amazonaws.com/cloudformation/windows-public-preview/amazon-eks-windows-nodegroup.yaml" rel="nofollow noreferrer">https://amazon-eks.s3-us-west-2.amazonaws.com/cloudformation/windows-public-preview/amazon-eks-windows-nodegroup.yaml</a> which contains the following powershell startup lines</p>

<pre><code>&lt;powershell&gt;
[string]$EKSBinDir = "$env:ProgramFiles\Amazon\EKS"
[string]$EKSBootstrapScriptName = 'Start-EKSBootstrap.ps1'
[string]$EKSBootstrapScriptFile = "$EKSBinDir\$EKSBootstrapScriptName"
[string]$cfn_signal = "$env:ProgramFiles\Amazon\cfn-bootstrap\cfn-signal.exe"
&amp; $EKSBootstrapScriptFile -EKSClusterName ${ClusterName} ${BootstrapArguments} 3&gt;&amp;1 4&gt;&amp;1 5&gt;&amp;1 6&gt;&amp;1
$LastError = if ($?) { 0 } else { $Error[0].Exception.HResult }
&amp; $cfn_signal --exit-code=$LastError `
  --stack="${AWS::StackName}" `
  --resource="NodeGroup" `
  --region=${AWS::Region}
&lt;/powershell&gt;
</code></pre>

<p>Add your custom installation requirements and use this new stack when launching your nodes</p>
