chore: upgrade kratos image to v1.2.0

[meysam81]

Related Issue or Design Document

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[Demonsthere]

Please correct the versions in chart.yaml and run make helm-docs :)

[Demonsthere]

this is the version of the chart, that is autogenerated on release, please don't touch ;)

[Demonsthere]

You can update appVersion: "v1.1.0" to reflect the new version

[meysam81]

@Demonsthere

While I'm gonna go ahead and apply your suggestion, I think this is a good moment for me to ask, why would you upgrade all the charts at the same version, even if others have not had change?

Wouldn't you say it is more appropriate to have per-chart Chart-version? based on the changes of specific chart.

[Demonsthere]

I agree it can be confusing, it's a pattern that we created when all of the charts were in a active development model. We are unsure if we want to keep the charts in this repo, or move them to the corresponding application repos, so for now we just release them as a bunch

[meysam81]

If it helps in any way, I think the code structure of Helm charts is better on its own repository. That's usually more maintainable in terms of the frequency of code changes for application code as compared to infra/platform/IaC code.

Having one helm chart per repository is not feasible IMO, but I believe the current repository can be structured in a better way so that Chart versions are not bumped at the same time, each having their own pace.

It can result into confusion otherwise when one of the charts need a bump and others don't, and yet all get a bump anyway!