Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6301

Allow Noobaa to configure a private storage endpoint on Azure

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • openshift-4.14
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request
      Allow Noobaa to configure a private storage endpoint on Azure

      2. What is the nature and description of the request?
      Support customers aspiring to follow Microsoft Azure security recommendations by allowing the Azure storage account hosting the object storage bucket for Noobaa to be configured as "private" vs. the default public.

      3. Why does the customer need this? (List the business requirements here)
      Several users noticed warnings in Azure Security advisor reporting the potentially dangerous exposure of the storage endpoint used by the Noobaa configured by its operator.

      4. List any affected packages or components.
      Check storage accounts created for Noobaa

            [RFE-6301] Allow Noobaa to configure a private storage endpoint on Azure

            valerioziaco

            In order to speed up the processing of RFEs please ensure that a component is added to the RFE. Not adding or removing a component from the component field may result in delays in processing the request.

            OpenShift Jira Automation Bot added a comment - valerioziaco In order to speed up the processing of RFEs please ensure that a component is added to the RFE. Not adding or removing a component from the component field may result in delays in processing the request.

              etamir@redhat.com Eran Tamir
              valerioziaco Valerio Ziaco
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: