You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's good to have an option to clean up the external resources such as the s3 bucket created for the Gatling object when the corresponding Gatling object is deleted from Kubernetes. Currently the external resources are not cleaned up.
For example, adding a new field named cleanupExternalResources in Gatling API type, if the field is set true, the controller deletes external resources for the Gatling object when the corresponding Gatling is deleted
apiVersion: gatling-operator.tech.zozo.com/v1alpha1kind: Gatlingmetadata:
name: gatling-sample01spec:
generateReport: falsenotifyReport: falsecleanupAfterJobDone: falsecleanupExternalResources: true <<<< new field
...omit...
The text was updated successfully, but these errors were encountered:
Feature request
It's good to have an option to clean up the external resources such as the s3 bucket created for the Gatling object when the corresponding Gatling object is deleted from Kubernetes. Currently the external resources are not cleaned up.
For example, adding a new field named
cleanupExternalResources
in Gatling API type, if the field is settrue
, the controller deletes external resources for the Gatling object when the corresponding Gatling is deletedThe text was updated successfully, but these errors were encountered: