Bug 1559728 - Add storage class support to templates shipped with OCP
Summary: Add storage class support to templates shipped with OCP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: Xiaoli Tian
URL:
Whiteboard: aos-scalability-39
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-23 07:03 UTC by Elvir Kuric
Modified: 2019-06-12 11:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-12 11:56:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Elvir Kuric 2018-03-23 07:03:19 UTC
Description of problem:
in v3.9 default installation in "openshift" namespace there will be many templates one can use for starting application. 

In every of these project PVCclaim is defined as ( below is from postgresql-persistant template ) 

--- 

{
            "apiVersion": "v1",
            "kind": "PersistentVolumeClaim",
            "metadata": {
                "name": "${DATABASE_SERVICE_NAME}"
            },
            "spec": {
                "accessModes": [
                    "ReadWriteOnce"
                ],
                "resources": {
                    "requests": {
                        "storage": "${VOLUME_CAPACITY}"
                    }
                }
            }
        },


so once this is started, it expect PVC to be created in advance and prepared prior oc new-app --template=<template> is executed. 

I am failing to understand why we do not have something like 

{
            "apiVersion": "v1",
            "kind": "PersistentVolumeClaim",
            "metadata": {
                "annotations":{
                        "volume.beta.kubernetes.io/storage-class": "${STORAGE_CLASS_NAME}"
                },
                "name": "${DATABASE_SERVICE_NAME}"
            },
            "spec": {
                "accessModes": [
                    "ReadWriteOnce"
                ],
                "resources": {
                    "requests": {
                        "storage": "${VOLUME_CAPACITY}"
                    }
                }
            }
        },


and also as parameter 

{
	"description" : "Storage class name to use",
	"displayName" : "Storage classs name",
	"name": "STORAGE_CLASS_NAME",
	"required": true

} 

this will enable to use 

# oc new-app --template=<template> -p STORAGE_CLASS_NAME=mystorage_class

and storage will be created dynamically and bound. 


Version-Release number of selected component (if applicable):

v3.9 and below packages 

atomic-openshift-sdn-ovs-3.9.11-1.git.0.0eb8959.el7.x86_64
atomic-openshift-clients-3.9.11-1.git.0.0eb8959.el7.x86_64
atomic-openshift-3.9.11-1.git.0.0eb8959.el7.x86_64
atomic-openshift-docker-excluder-3.9.11-1.git.0.0eb8959.el7.noarch
atomic-openshift-node-3.9.11-1.git.0.0eb8959.el7.x86_64
atomic-registries-1.22.1-1.gitd36c015.el7.x86_64
atomic-openshift-excluder-3.9.11-1.git.0.0eb8959.el7.noarch
atomic-openshift-tests-3.9.11-1.git.0.0eb8959.el7.x86_64


How reproducible:

always 

Steps to Reproduce:
1. check templates in -n openshift 

Actual results:

templates does not support storage class 

Expected results:

templates to support storage class 


Additional info:
NA

Comment 6 Kirsten Newcomer 2019-06-12 11:56:33 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.


Note You need to log in before you can comment on or make changes to this bug.