Skip to content

[ENHANCE] Find a different way to release helm charts, instead of commits to master branch  #684

@MuneebAijaz

Description

@MuneebAijaz

Is your feature request related to a problem? Please describe.

Push workflow commits back to master branch which creates multiple issues:

Current need to write back to master branch:

  • this branch hosts latest helm charts, which gets updates on labels, image number and chart versions on every PR merged. Example commit: 8595b4a

Describe the solution you'd like
Find a different strategy to release helm charts and plain manifests instead of committing back to master branch.

Describe alternatives you've considered

  • Create versioned branches to host helm charts
  • Push to different repo to host helm charts for opensource repos, instead of code repos.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions