Skip to content

Operators cloud-native framing and PostgreSQL Operator 3.0.0 messaging#156

Open
brianamarie wants to merge 4 commits into
mainfrom
ingest/pr-11-operators-cloud-native
Open

Operators cloud-native framing and PostgreSQL Operator 3.0.0 messaging#156
brianamarie wants to merge 4 commits into
mainfrom
ingest/pr-11-operators-cloud-native

Conversation

@brianamarie
Copy link
Copy Markdown
Collaborator

@brianamarie brianamarie commented May 26, 2026 •
edited
Loading

Summary

  • Integrates cloud native database operations framing into products/operators/messaging.md, including sales enablement (best-fit profiles, qualification signals, discovery questions, public resources).
  • Ingests Percona Operator for PostgreSQL 3.0.0 messaging: Crunchy PGO hard fork in Why Percona and PostgreSQL open source copy; operators hub covers migration coexistence, OLM namespace scope, Patroni 4.1.3, and major-upgrade workflow; refreshes stale PostgreSQL Operator doc links off 2.8.x.
  • Merges current main into this branch.

Sources

Closes #159

Test plan

  • npx markdownlint-cli2 "framework/why-percona.md" "products/postgresql/messaging.md" "products/operators/messaging.md"
  • Reviewer pass: cloud-native framing + 3.0 decomposition (fork in framework/postgresql; ops in operators)
  • Confirm no percona-operator-for-postgresql/2.8 links in changed files

@brianamarie @cursoragent
refine operators messaging with cloud native framing
a63ecd0 
Integrate cloud native database operations framing into the existing operator-first narrative and preserve the core value-pillar structure. Add a concise sales enablement section with fit signals, discovery questions, and public resources for field use.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie brianamarie requested a review from obiyduhata as a code owner May 26, 2026 11:15
@brianamarie brianamarie added Content & messaging Canonical copy, products, use cases, case studies, and narrative. Area: Kubernetes operators Kubernetes operators platform messaging (products/operators/). Inbound Inbound: ships, GTM, or external requests driving updates to canonical messaging in this repo. Needs: product or GTM Product, marketing, or GTM should confirm scope, naming, or positioning. labels May 27, 2026
brianamarie and others added 2 commits May 27, 2026 14:21
@brianamarie
Merge origin/main into ingest/pr-11-operators-cloud-native
d8a35a0
@brianamarie @cursoragent
Ingest Operator for PostgreSQL 3.0.0 with cloud-native operators mess…
19777b5 
…aging.

Merge main, add Percona-owned Crunchy PGO fork to Why Percona and PostgreSQL
open source copy, and operational 3.0 proof in operators hub (migration, OLM,
Patroni, doc links) alongside existing cloud-native framing and sales enablement.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie brianamarie changed the title PR-11: integrate cloud native framing into operators messaging Operators cloud-native framing and PostgreSQL Operator 3.0.0 messaging May 27, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 27, 2026 •
edited
Loading

Messaging Smart Suggestions

File Why impacted Claim Confidence
use-cases-value-pillars/cost-optimization.md PostgreSQL cost/TCO claims usually impact shared value proof messaging. cost 0.95
framework/core-positioning.md PostgreSQL cost/TCO claims usually impact shared value proof messaging. cost 0.95
products/postgresql/messaging.md PostgreSQL cost/TCO claims usually impact shared value proof messaging. cost 0.65
reference/canonical-naming.md License and open source positioning changes are cross-cutting. cost 0.95
reference/banned-terms.md License and open source positioning changes are cross-cutting. cost 0.95
framework/core-positioning.md License and open source positioning changes are cross-cutting. cost 0.95
framework/why-percona.md License and open source positioning changes are cross-cutting. cost 0.65
offerings/expert-support.md License and open source positioning changes are cross-cutting. cost 0.65
offerings/expertops.md License and open source positioning changes are cross-cutting. cost 0.65
offerings/expert-consulting.md License and open source positioning changes are cross-cutting. cost 0.95
offerings/expert-support.md Offering naming updates should stay aligned across offering pages. cost 0.65
offerings/expertops.md Offering naming updates should stay aligned across offering pages. cost 0.65
offerings/expert-consulting.md Offering naming updates should stay aligned across offering pages. cost 0.95
reference/canonical-naming.md Offering naming updates should stay aligned across offering pages. cost 0.95
framework/core-positioning.md Offering naming updates should stay aligned across offering pages. cost 0.95
framework/core-positioning.md Product messaging modules often need checks against company framing and shared pillars or offerings. cost 0.95
framework/why-percona.md Product messaging modules often need checks against company framing and shared pillars or offerings. cost 0.65
framework/core-positioning.md Core framework story files usually need mutual consistency and may warrant aligned product or offering language. cost 0.95
framework/why-percona.md Core framework story files usually need mutual consistency and may warrant aligned product or offering language. cost 0.65
framework/executive-summary.md Core framework story files usually need mutual consistency and may warrant aligned product or offering language. cost 0.95

Only auto-apply suggestions at high confidence with reviewer approval.

Triggered by pull_request. Workflow smart-suggestions.yml. Docs: AUTOMATION.md, automation/README.md.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 27, 2026 •
edited
Loading

Messaging Impact Check

  • Changed files: 5

postgres-cost-claim (BLOCKING)

PostgreSQL cost/TCO claims usually impact shared value proof messaging.

Required review files:

  • use-cases-value-pillars/cost-optimization.md
  • framework/core-positioning.md
  • products/postgresql/messaging.md

Suggested additional scan:

  • use-cases-value-pillars/*.md

licensing-or-open-source-claims (BLOCKING)

License and open source positioning changes are cross-cutting.

Required review files:

  • reference/canonical-naming.md
  • reference/banned-terms.md
  • framework/core-positioning.md
  • framework/why-percona.md
  • offerings/expert-support.md
  • offerings/expertops.md
  • offerings/expert-consulting.md

Suggested additional scan:

  • use-cases-value-pillars/*.md
  • products/**/messaging.md

offering-name-or-tier-change (WARN)

Offering naming updates should stay aligned across offering pages.

Required review files:

  • offerings/expert-support.md
  • offerings/expertops.md
  • offerings/expert-consulting.md
  • reference/canonical-naming.md
  • framework/core-positioning.md

Suggested additional scan:

  • products/**/messaging.md
  • use-cases-value-pillars/*.md

product-messaging-module-touch (WARN)

Product messaging modules often need checks against company framing and shared pillars or offerings.

Required review files:

  • framework/core-positioning.md
  • framework/why-percona.md

Suggested additional scan:

  • use-cases-value-pillars/*.md
  • offerings/*.md

framework-story-touch (WARN)

Core framework story files usually need mutual consistency and may warrant aligned product or offering language.

Required review files:

  • framework/core-positioning.md
  • framework/why-percona.md
  • framework/executive-summary.md

Suggested additional scan:

  • offerings/*.md
  • use-cases-value-pillars/*.md
  • products/**/messaging.md

Manual waiver commands (maintainers):

  • /impact-ok all (optional same-line note after all is ignored)
  • /impact-all (same as /impact-ok all)
  • /impact-ok <exact missing path>
  • /impact-reset all
  • /impact-reset <exact missing path>

Waiver state is stored in <!-- messaging-impact-waiver-data:v1 -->.

Triggered by pull_request. Workflow impact-check.yml. Docs: AUTOMATION.md, automation/README.md.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 27, 2026 •
edited
Loading

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Duplicate Detector

  • Changed markdown docs: 5

No significant overlap detected.

Manual waiver commands (maintainers)

  • /governance-ok all or /governance-all
  • /governance-ok new-file, /governance-ok doc-coverage, /governance-ok duplicate
  • /governance-reset all or /governance-reset with the same token

Waiver JSON is stored in a hidden PR comment (messaging-governance-waiver-data:v1), same pattern as Impact Check.

Triggered by pull_request. Workflow content-governance-checks.yml. Docs: AUTOMATION.md, automation/README.md.

@brianamarie @cursoragent
docs(offerings): add differentiated Kubernetes operator scenarios
2247a26 
Add Expert Support planning/escalation and ExpertOps hands-on operator
scenarios without duplicating migration or Day-2 language across offerings.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie brianamarie mentioned this pull request Jun 1, 2026
Open
@brianamarie brianamarie added the Area: PostgreSQL PostgreSQL ecosystem messaging (products/postgresql/). label Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@obiyduhata obiyduhata Awaiting requested review from obiyduhata obiyduhata is a code owner

@andrey-glazkov andrey-glazkov Awaiting requested review from andrey-glazkov

@ImTheKai ImTheKai Awaiting requested review from ImTheKai ImTheKai is a code owner

@janwieremjewicz janwieremjewicz Awaiting requested review from janwieremjewicz janwieremjewicz is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

@obiyduhata obiyduhata

Labels

Area: Kubernetes operators Kubernetes operators platform messaging (products/operators/). Area: PostgreSQL PostgreSQL ecosystem messaging (products/postgresql/). Content & messaging Canonical copy, products, use cases, case studies, and narrative. Inbound Inbound: ships, GTM, or external requests driving updates to canonical messaging in this repo. Needs: product or GTM Product, marketing, or GTM should confirm scope, naming, or positioning.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Release] Percona Operator for PostgreSQL 3.0.0 has been released

2 participants

@brianamarie @obiyduhata