Add DevWorkspace Pruner (operator-lib/prune package)

[akurinnoy]

What does this PR do?

This pull request adds a new controller that prunes (removes) DevWorkspaces based on these rules:

• DevWorkspaces that haven't been started for a specific period are considered inactive. This period is configurable.
• The pruning behavior (enable/disable, retention time, cron schedule, dry-run mode) is configured via the DevWorkspaceOperatorConfig (DWOC) resource.
• The pruning process is scheduled using a cron library, allowing for flexible configuration of the pruning frequency.
• A dry-run mode is supported, allowing administrators to preview the pruning actions without actually deleting any resources.

What issues does this PR fix or reference?

resolves #1376

Is it tested? How?

1. Deploy the operator with this new code.
2. Ensure that the DevWorksapceOperatorConfig initially does not have pruning enabled by default
   • there is no CleanupCronJob section in the config.workspace section of the DWOC.
   • or, if there is the CleanupCronJob section, ensure that enable: false.
3. Patch the DevWorkspaceOperatorConfig to enable pruning and set parameters:

kubectl patch DevWorkspaceOperatorConfig devworkspace-operator-config \
-n devworkspace-controller \
--type=merge \
-p '{"config": {"workspace": {"cleanupCronJob": {"enable": true, "dryRun": true, "retainTime": 60, "schedule": "* * * * *"}}}}'

4. Create several DevWorkspaces. Some should be started, and some should not be started.
5. Wait for the cron schedule to trigger the pruning - at least 1 minute.
6. Check logs and verify that the correct DevWorkspaces are identified but not deleted in dry-run mode.
7. Disable dry-run mode and verify that all eligible DevWorkspaces are actually deleted:

kubectl patch DevWorkspaceOperatorConfig devworkspace-operator-config \
-n devworkspace-controller \
--type=merge \
-p '{"config": {"workspace": {"cleanupCronJob": {"dryRun": false }}}}'

PR Checklist

• E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)
  • v8-devworkspace-operator-e2e: DevWorkspace e2e test
  • v8-che-happy-path: Happy path for verification integration with Che

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[dkwon17]

/retest

[openshift-ci]

@akurinnoy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v14-devworkspace-operator-e2e	0decf40	link	true	/test v14-devworkspace-operator-e2e
ci/prow/v14-images	0decf40	link	true	/test v14-images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[ibuziuk]

@akurinnoy great job, could you please provide a separate PR with the docs to https://github.com/devfile/devworkspace-operator/blob/main/docs/dwo-configuration.md

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: akurinnoy, ibuziuk
Once this PR has been reviewed and has the lgtm label, please assign dkwon17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment