Skip to content

Expose deployment Strategy in values.yamlΒ #47

@woile

Description

@woile

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here (legacy) and here
  • I've tried installing latest charts and the issue still persists there
  • I'm running a supported version of the application & chart which is listed here

Describe the bug (actual behavior)

It's not a bug per se, but I'd like to ask if it's possible to expose the strategy.

https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy

Expected behavior

I'd like to run a single instance, but be able to tell kubernetes that on a new deployment.
I'd like to strictly enforce that zero old pods can be unavailable while new ones are coming up (Set maxUnavailable: 0 and maxSurge: 1).

Steps to reproduce

Look at deployment, it's not possible to modify the strategy:
https://github.com/kafbat/helm-charts/blob/main/charts/kafka-ui/templates/deployment.yaml

Additional context

I can submit a PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/triageIssues pending maintainers triage

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions