chore: API documentation sync

[github-actions]

Automated pull request to sync docs for:

• Console operator
• Deployment operator
• Liquid filters

[greptile-apps]

Greptile Summary

This automated sync PR adds POSTGRES as a new valid enum value for the VectorStore field in the management API reference documentation.

• Adds POSTGRES to the VectorStore enum alongside the existing ELASTIC and OPENSEARCH options in the AISettings section.

Confidence Score: 4/5

Safe to merge — the change is a single-line documentation update adding a new enum value.

The change is minimal and documentation-only. The only gap worth noting is that POSTGRES is listed as a valid enum value but, unlike elastic and opensearch, there is no corresponding postgres connection settings row in the table, leaving users without guidance on how to configure it.

pages/api-reference/kubernetes/management-api-reference.md — the VectorStore section around line 5317 lacks a postgres connection settings entry.

Important Files Changed

Filename	Overview
pages/api-reference/kubernetes/management-api-reference.md	Adds POSTGRES as a valid enum value for VectorStore; no corresponding postgres connection settings field is documented unlike the elastic/opensearch counterparts.

_{Reviews (1): Last reviewed commit: "sync docs" | Re-trigger Greptile}

[greptile-apps]

Missing postgres connection settings field

The POSTGRES enum value is added to VectorStore, but the table has no corresponding postgres configuration field — unlike elastic and opensearch, which each have a dedicated connection settings entry. If selecting POSTGRES requires any connection parameters, users will have no documentation on how to provide them. If PostgreSQL uses a built-in or shared secret, a note to that effect would prevent confusion.