Bug 1769739

Summary:	defaultProjectTemplate not evaluated
Product:	OpenShift Container Platform	Reporter:	Samuel <smoro>
Component:	openshift-apiserver	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED NOTABUG	QA Contact:	Xingxing Xia <xxia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, ccoleman, fshaikh, mfojtik, pweil, sttts
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-11 10:36:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Samuel 2019-11-07 10:46:16 UTC

Description of problem:

defaultProjectTemplate would not be applied if I create a Namespace, instead of a Project.

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

OCP 4.2.2

How reproducible:

Always

Steps to Reproduce:
1. Create a defaultProjectTemplate (https://docs.openshift.com/container-platform/4.1/applications/projects/configuring-project-creation.html#modifying-template-for-new-projects_configuring-project-creation)
2. Create Namespace

Actual results:

defaultProjectTemplate assets not added to new Project.

Expected results:

Custom assets should be created in new Projects.

Additional info:

Comment 2 Samuel 2019-11-11 11:06:34 UTC

@sttts : could you clarify how would we enforce defaultProjectTemplate custom configurations being applied to self-provisioned namespaces?

Why aren't custom objects installed on Projects, when end-user requested a Namespace instead of a Project?

Should customer open a RFE?

Comment 3 Clayton Coleman 2019-11-11 14:26:16 UTC

Customer should open a RFE - we have discussed a design that would move all project template behavior to allow this, but for now to get project templates customers have to let their users create projects.

Comment 4 Samuel 2019-11-13 15:37:24 UTC

Sure, though there's nothing preventing users from creating Projects. They can. They do.

Now, when a user deploys Helm charts, copy/pastes commands, an operator creates a namspace, ...
Eventually, I'ld still end up with Namespaces that would not comply with customer internal policies.

This is an issue in 3.X as well, and defeats the purpose of setting a defaultProjectTemplate.

Comment 5 Fatima 2020-02-12 08:52:46 UTC

Hi team,

I have created a RFE for this one, as suggested by Clayton.

https://issues.redhat.com/browse/RFE-444

Could anyone PTAL?

Thanks a ton!

Comment 6 Red Hat Bugzilla 2023-09-14 05:45:44 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days