4 Commits

Include renames

Author	SHA1	Message	Date
Peter Razumovsky	516eab4d8a	core: define empty securityContext for pods to fix CIS 5.7.3 ... Resolves CIS benchmark rule 5.7.3, Pods part. SecurityContext should be explicitly defined in pod level of Pod spec section. It is sufficient to specify empty securityContext to satisfy CIS 5.7.3 rule. 5.7.3 Apply Security Context to Your Pods and Containers When designing your containers and pods, make sure that you configure the security context for your pods, containers, and volumes. Signed-off-by: Peter Razumovsky <prazumovsky@mirantis.com>	2024-10-09 16:10:03 +04:00
sp98	c98fc86918	core: remove owner refs in resource cleanup jobs ... Removed owner reference from Radosnamespace and subVolumeGroup cleanup resources. Signed-off-by: sp98 <sapillai@redhat.com>	2024-05-17 18:39:34 +05:30
sp98	f6b1449faa	core: cephblockpoolRadosNamespace cleanup ... Clean up pool images and snapshots in the radosnamespace Signed-off-by: sp98 <sapillai@redhat.com>	2024-04-12 21:49:49 +05:30
sp98	ef00fdac53	core: subvolumegroup clean up ... Cleanup the resources created by subvolumegroup when its deleted. Following resources will be cleaned up: - OMAP value - OMAP keys - Clones - Snapshots - Subvolumes Signed-off-by: sp98 <sapillai@redhat.com>	2024-04-10 17:34:45 +05:30