Open taltrums opened 3 months ago
Hello, I totally agree. If you have multiple platforms to manage, you need to connect to each one individually to schedule such a cleanup task. Therefore, it can be defined in the values.yaml file as a parameter.
IMO this should not be part of the core configuration but rater on the same level as the UI. We already have the capabilities to do that with TF, Pulumi providers. CLI is up next and Ideally some CRDs wouls be nice too.
im running into this issue, i want to use the api as shown in swagger, but garbage collection has csrf tokens... its a bit of a pain to work around
You should handle it externally using any method you prefer—automation scripts, operators, Terraform, etc.—but not within the application itself.
can you add some reasoning why? (i feel a bit left in the dark, its just a rest endpoint)
How can we help you?
Problem Statement
We are looking for a way to automate Harbor cleanup tasks, such as garbage collection, using configuration files. Our goal is to ensure that these cleanup tasks are performed automatically and periodically without requiring manual intervention through the Harbor UI.
Requirements
Automated Garbage Collection:
values.yaml
, which can be used by Harbor during startup.Configuration as Code:
Current Manual Process
Currently, we perform garbage collection manually through the Harbor UI. This process involves:
This manual process is not ideal for several reasons: