[sarankumar1325]

Problem description

The operator parameter reference (docs/reference/operator_parameters.md) disagrees with what the operator actually reads in pkg/util/config/config.go and config.NewFromMap:

• secret_name_template is documented as {username}.{cluster}.credentials.{namespace}.{tprkind}.{tprgroup}, and {namespace} is listed as a default placeholder. The operator does not substitute {namespace} (or {tprkind} / {tprgroup} as documented). Using {namespace} produces a secret name that is never found.
• Several keys are shown in CamelCase (MaxUnavailability, IgnoreUserSecretPath, Novolumepath) or as the typo connection_pooler_default_meomry_request. NewFromMap lower-cases keys and only fills struct fields that match, so those documented names are ignored.
• Patroni configuration keys are documented as PgHba / TTL / LoopWait / RetryTimeout / MaximumLagOnFailover. The map keys the operator applies are snake_case: pg_hba, ttl, loop_wait, retry_timeout, maximum_lag_on_failover.
• ready_wait_interval is documented as 5s; the default in config.NewFromMap is 4s.
• team_api_role_configuration is described but has no example of the name:value list the parser expects.

This is a documentation-only fix.

Linked issues

Fixes #3226.

Related but not overlapping: #3225 (infrastructure roles docs).

Checklist

Thanks for submitting a pull request to the Postgres Operator project.
Please, ensure your contribution matches the following items:

• Your go code is formatted. Your IDE should do it automatically for you. (No Go code in this PR.)
• You have updated generated code when introducing new fields to the acid.zalan.do api package. (No API changes.)
• New configuration options are reflected in CRD validation, helm charts and sample manifests. (No new options; the reference is aligned with existing parser keys and defaults.)
• New functionality is covered by unit and/or e2e tests. (Documentation only.)
• You have checked existing open PRs for possible overlay and referenced them.