Skip to content

Conversation

@dandax123
Copy link

@dandax123 dandax123 commented Jul 24, 2025

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Documentation update
  • Refactoring (no functional changes)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • My code follows the style guidelines of this project
  • [x ] I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • [x ] I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective
    -->

@dandax123 dandax123 changed the title Feat: add helm charts Feat: add helm chart Jul 24, 2025
@dandax123 dandax123 force-pushed the daniel/add_helm_charts branch from 095c494 to 502ee81 Compare July 24, 2025 23:06
@remyoudemans
Copy link
Collaborator

Thanks for the PR @dandax123!
This seems helpful, but quite out of scope for this project.
We wouldn't want this repository to get filled up with code that isn't needed to run it, because that would come with its own maintenance overhead.

I still think this is valuable work though. If you put all the helm files in a public gist, then we could just link to them in this project's README and keep this repo lean.

@dandax123
Copy link
Author

dandax123 commented Aug 9, 2025

@remyoudemans I think you could create a repo in this same xavia-io organization called xavia-ota-helm and then we can move this there, and add a link in the docs to reference the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants