Bug 1324785 - [RFE] Azure Blob Storage support for PVs
Summary: [RFE] Azure Blob Storage support for PVs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: hchen
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 09:49 UTC by Evgheni Dereveanchin
Modified: 2020-02-14 17:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-18 12:39:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Description Evgheni Dereveanchin 2016-04-07 09:49:12 UTC 
Description of request:
Azure provides Block Blob Storage which is not currently supported by OpenShift. As Azure is one of the supported platforms for OpenShift, it should be able to consume this kind of storage.

Additional info:
Currently the only way to consume Azure storage is use Azure File Storage by mounting the SMB share and expose the PV of HostPath type. This has lots of limitations (permission issues, no symlink support) which do not allow to use it fully and securely within pods.
Comment 3 hchen 2016-05-07 12:56:52 UTC 
upstream PR at https://github.com/kubernetes/kubernetes/pull/25195
Comment 4 Troy Dawson 2016-11-18 17:11:19 UTC 
upstream pull request replaced by #29836
https://github.com/kubernetes/kubernetes/pull/29836

This has been merged into ocp and is in OCP v3.4.0.28 or newer.
Comment 6 errata-xmlrpc 2017-01-18 12:39:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0066
Note You need to log in before you can comment on or make changes to this bug.