Skip to content

CHART: Add capability of always forcing roll of deployment #51

@diogopereira-fd

Description

@diogopereira-fd

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

Feature request

Hi Team,

I’d like to contribute to the Kafka-UI Helm chart but currently don’t have access to create a branch for review.

Proposed Implementation:

I’ve identified the need to a change to podAnnoations to include a field with random generated values. This is needed in order to always force a roll-out of the pods. https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments

templates/deployment.yaml:

template:
    metadata:
      annotations:
        {{- if .Values.forcePodRefresh }}
        rollme: {{ randAlphaNum 5 | quote }}
        {{- end }}

Expected behavior

forcePodRefresh: true

will allow users to always force a full refresh of the pods.

Your installation details
commit sha: 8b5494b67a1185fc334ee9fbb10e9acb51fa288a
chart version: 1.4.11
config: as default, nothing special

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