Daemonset RollingUpdate Max Surge support

[abby-gourlay]

Description

Currently the terraform provider doesn't support a max_surge argument in the rolling update configuration for a daemonset. However according to the Kubernetes documentation this should be possible

This attribute is in our existing daemonsets on our EKS 1.23 cluster

Potential Terraform Configuration

strategy {
      type = "RollingUpdate"
      rolling_update {
        max_unavailable = 0
        max_surge = "50%"
      }
    }

References

Terraform documentation: https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/daemonset#rolling_update

Kubernetes documentation: https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#:~:text=updateStrategy.rollingUpdate.-,maxSurge,-(IntOrString)

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[iamunni]

would like to work on this. can I take this up?

[github-actions[bot]]

Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you!

[abby-gourlay]

This has been implemented at some point, and I've used it successfully now