Storage plugins for Kubernetes
Switch branches/tags
Nothing to show
Clone or download
Latest commit b3f069f Aug 10, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
flexprovisioner remove specifing credential for iscsi provisioning Aug 9, 2018
flexvolume/windows Merge pull request #7 from KnicKnic/no_splat Aug 9, 2018
.gitignore move some code from flex to flexvolume Jun 18, 2018
LICENSE Initial commit Apr 23, 2018
README.md Update README.md (#2) Apr 25, 2018

README.md

FlexVolume

See flexvolume/windows for Kubernetes flexvolume plugins that can mount iSCSI and SMB on Windows.

FlexProvisioner

See flexprovisioner for an example Kubernetes storage provisioner that given a Windows Server can provision SMB and iSCSI volumes.

Contributing


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Report a Computer Security Vulnerability


If you are a security researcher and believe you have found a security vulnerability that meets the definition of a security vulnerability that is not resolved by the 10 Immutable Laws of Security, please send e-mail to us at secure@microsoft.com. To help us to better understand the nature and scope of the possible issue, please include as much of the below information as possible.

  • Type of issue (buffer overflow, SQL injection, cross-site scripting, etc.)
  • Product and version that contains the bug, or URL if for an online service
  • Service packs, security updates, or other updates for the product you have installed
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue on a fresh install
  • Proof-of-concept or exploit code
  • Impact of the issue, including how an attacker could exploit the issue

Microsoft follows Coordinated Vulnerability Disclosure (CVD) and, to protect the ecosystem, we request that those reporting to us do the same. To encrypt your message to our PGP key, please download it from the Microsoft Security Response Center PGP Key. You should receive a response within 24 hours. If for some reason you do not, please follow up with us to ensure we received your original message. For further information, please visit the Microsoft Security Response Policy and Practices page and read the Acknowledgment Policy for Microsoft Security Bulletins.

For additional details, see Report a Computer Security Vulnerability on Technet


Copyright (c) 2018 Microsoft Corp. All rights reserved.