Description of problem: When using the console to instantiate a Template via the console a secret gets created which holds all of the parameters in the template. This secret is not owned by the TemplateInstance and when you delete the TemplateInstance it is not cleaned up. Persistent volume claims created by the template are cleaned up on deletion Mailing list discussion : https://mailman-int.corp.redhat.com/archives/openshift-sme/2021-June/msg00313.html Version-Release number of selected component (if applicable): 4.8.13 and earlier How reproducible: Every time Steps to Reproduce: 1. Add a service from the developer catalog that is from a template such as the Postgresql template 2. A TemplateInstance gets created and a secret named something like: TemplateInstance: postgresql-persistent-cx4rb Secret: postgresql-persistent-parameters-pvspn 3. Delete the TemplateInstance 4. Check the secret to see that the secret holding the parameters still exist. Actual results: Secret holding the parameters is not deleted Expected results: As the TemplateInstance creates the parameters secret it should own and delete it. Additional info: Using the CLI to achieve to deploy the template doesn't create a TemplateInstance e.g. oc process openshift//postgresql-persistent | oc create -f - or oc new-app --template postgresql-persistent Customer who raised the issue quotas secrets so every time a user creates a template via the console they get an "unexpected" secret.
verified on build version: 4.11.0-0.nightly-2022-06-23-153912 verified on browser version: chrome 102
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069