Communishift: project deletion and notifcations SOP

Openshift: WIP best practices

Signed-off-by: David Kirwan <davidkirwanirl@gmail.com>
This commit is contained in:
David Kirwan 2024-12-11 13:20:33 +00:00
parent 25d3f58d7a
commit 5141624ed5
No known key found for this signature in database
GPG key ID: A5893AB6474AC37D
5 changed files with 265 additions and 0 deletions

View file

@ -16,6 +16,20 @@ If needed, resource quotas can be overriden from defaults in the same dictionary
Note: Projects *must* start with `communishift-` eg `communishift-dev-test`.
See the following example of the `communishift-eventbot` project and the `communishift-fedora-review-service` project being added:
----
communishift_projects:
communishift-eventbot:
name: communishift-eventbot
communishift-fedora-review-service:
name: communishift-fedora-review-service
do_not_delete: true # Marked do not delete 2024-10-21
...
----
NOTE: To mark a project as one which should _NOT_ be cleaned up as part of the Communishift clean up script, mark it with the boolean like so and it is helpful to include the date so we can see at a glance when projects were granted this special status: `do_not_delete: true # Marked do not delete YYYY-MM-DD`
=== Add new project group to IPA
A group must be created in IPA which matches the name of the group added to the playbook in the previous step. Please ensure that the community member requesting access to the cluster is also added to this group in IPA, and made a sponsor. This way they can administer members in their group in a self service fashion later.