feat: Flux integration

[Slygecko]

Flux Integration With Medulla Chart

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Summary of the changes

Integrated flux into the medulla chart.

Description

helm install will launch medulla chart along with the following dependancies:

• flux
• Istio
• tidb
• dapr
• gitea

Fixes #99

[andrewbabbittdev]

Almost there

[Slygecko]

PR is ready for review.

[andrewbabbittdev]

Looks like were missing the registry values here, meaning this is pulling from docker hub correct? This wont work if we plan on releasing Iron Bank images / GHCR.

Containers are broken down into a few sections:

Registry: ghcr.io
Repository: recro/medulla
Image: documentation
Tag: 0.1.0

Full URL: ghcr.io/recro/medulla/documentation:0.1.0

[Slygecko]

Thank you for the input. I will work on adding this.

[andrewbabbittdev]

Dont believe we need this if were using the istio ingress class no? You can either use Virtual Services + Gateways or the Istio Ingress Class but not both.

[Slygecko]

If the VS and gateway are not needed then that will allow us to use only one helm chart. Do you want me to move forward with that?

[andrewbabbittdev]

VS and Gateways have more features than an Ingress, so I would prefer we just use the Istio Gateway and VS's but there does need to be a VS for all services that are to be exposed.

You will still need two charts to support other dependencies being deploy (ex. TiDB cluster)