fix(barman): Adjust slot-creation

[ggggut]

Description

Hello, creating a slot failed on our side because ERROR: Unknown server 'pg'.
I found it hardcoded in the cronjob.
Wouldn't it be better to use the postgres.host value for creating the db slot?
Let me know what you think!

Best

Issues

barman.server ERROR: Check 'replication slot' failed for server 'xxxxxxx'
	replication slot: FAILED (replication slot 'barman' doesn't exist. Please execute 'barman receive-wal --create-slot xxxxxxx')
	directories: OK
	retention policy settings: OK

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released

[hairmare]

postgres.host does feel much better than having a hardcoded pg string. It should probably also get surfaced in values.yaml.

For the barman.backups thing to work it would probably also need some if hasKey/$.Values stuff in the template (like what is already there for backupSchedule).

[ggggut]

thank you! i will look into it tomorrow

[ggggut]

The barman.backups key works now. But..

It should probably also get surfaced in values.yaml.

Can you elaborate?

[ggggut]

I also added the possibility to add annotations. This could be useful in a few cases.
In our case we would need it to annotate velero backups.

[hairmare]

It should probably also get surfaced in values.yaml.

Can you elaborate?

I didn't realise that .postgres.host is already defined in values.yaml 🤦

[hairmare]

LGTM