Default influxdb2 pod disruption budget blocks node draining

[JamesHarrison]

Hi,

The default influxdb2 deployment as configured by this chart blocks node draining/eviction:

    "requestObject": {
        "kind": "Eviction",
        "apiVersion": "policy/v1beta1",
        "metadata": {
            "name": "flagsmith-influxdb2-0",
            "namespace": "production",
            "creationTimestamp": null
        }
    },
    "responseObject": {
        "kind": "Status",
        "apiVersion": "v1",
        "metadata": {},
        "status": "Failure",
        "message": "Cannot evict pod as it would violate the pod's disruption budget.",
        "reason": "TooManyRequests",
        "details": {
            "causes": [
                {
                    "reason": "DisruptionBudget",
                    "message": "The disruption budget flagsmith-influxdb2 needs 1 healthy pods and has 1 currently"
                }
            ]
        },
        "code": 429
    }

No disruptions are allowed, so k8s will block node draining. This has knock-on effects, such as stopping Amazon EKS and others from performing rolling cluster upgrades gracefully. This shouldn't be default behaviour.