Skip to content
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.

Commit

Permalink
Specify how resource is cleaned up (#274)
Browse files Browse the repository at this point in the history
Specify how resource is cleaned up after successful execution of a k8s pod
[Issue](flyteorg/flyte#2650)
Signed-off-by: SmritiSatyanV [email protected]

Signed-off-by: SmritiSatyanV <[email protected]>
  • Loading branch information
SmritiSatyanV authored Jul 5, 2022
1 parent 4c4af21 commit 902b902
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion go/tasks/pluginmachinery/flytek8s/config/config.go
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ type K8sPluginConfig struct {
// DeleteResourceOnFinalize instructs the system to delete the resource on finalize. This ensures that no resources
// are kept around (potentially consuming cluster resources). This, however, will cause k8s log links to expire as
// soon as the resource is finalized.
DeleteResourceOnFinalize bool `json:"delete-resource-on-finalize" pflag:",Instructs the system to delete the resource on finalize. This ensures that no resources are kept around (potentially consuming cluster resources). This, however, will cause k8s log links to expire as soon as the resource is finalized."`
DeleteResourceOnFinalize bool `json:"delete-resource-on-finalize" pflag:",Instructs the system to delete the resource upon successful execution of a k8s pod rather than have the k8s garbage collector clean it up. This ensures that no resources are kept around (potentially consuming cluster resources). This, however, will cause k8s log links to expire as soon as the resource is finalized."`

// Time to wait for transient CreateContainerError errors to be resolved. If the
// error persists past this grace period, it will be inferred to be a permanent
Expand Down

0 comments on commit 902b902

Please sign in to comment.