Using Helm's fullnameOverride param we can set a static name.
The reason for doing so is that a lot of additional operators and controllers work with appending suffixes.
If we would continue using the same name as the instance CRD, we could encounter too long names and things may break.
Static names avoid this by setting a short-enough name.
The result is that every postgresql Pod in a namespace is called postgresql-0 as an example (instead of something like sv-postgresql-s-old-fire-7894-0 along with other resources like Services or PVCs.)
This is technically a breaking change, but since we haven't released anything working yet, it's fine.
Checklist
For Code changes
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] PR contains the label area:operator
[x] I have not made any changes in the charts/ directory.
Summary
Using Helm's
fullnameOverrideparam we can set a static name. The reason for doing so is that a lot of additional operators and controllers work with appending suffixes. If we would continue using the same name as the instance CRD, we could encounter too long names and things may break. Static names avoid this by setting a short-enough name.The result is that every postgresql Pod in a namespace is called
postgresql-0as an example (instead of something likesv-postgresql-s-old-fire-7894-0along with other resources like Services or PVCs.)This is technically a breaking change, but since we haven't released anything working yet, it's fine.
Checklist
For Code changes
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelogarea:operatorcharts/directory.