Community updates for Crunchy Postgres for Kubernetes

[craigkerstiens]

In an effort to improve communication, we wanted to create this issue to consolidate information regarding the PGO community and Crunchy Postgres for Kubernetes from a few different threads in one place.

First, to better engage you, our community, we're centralizing on discord as a place to come and engage whether feature request, troubleshooting, or just to hang out and talk Postgres. We will continue to keep the mailing list for archival purposes, but for discussion of PGO, Crunchy Postgres for Kubernetes, or just Postgres we are hoping the discord group will be a useful place for the community. Of note, if you need production support with accompanying SLA we do recommend you reach out to us about becoming a Crunchy Data customer. If you believe you have discovered a bug in PGO, of course please continue to open a GitHub issue (though we hope you will use discord for community support questions).

Second, we're making our trusted build and packages of Crunchy Postgres for Kubernetes more available–explicitly allowing for production use for individuals and small businesses under our updated terms of use. We recommend you read the full terms of use, but here is a summary of what is permitted when consuming our containers for Crunchy Postgres for Kubernetes:

	Individuals and small organization (<50 Employees)	Large Organization (50+ Employees)
Personal or Internal Use of Crunchy Data Software for Development Purposes	Permitted	Permitted
Personal or Internal Use of Crunchy Data Software for Production Purposes	Permitted	Not Permitted
Resale or Redistribution of Crunchy Data Software to Third Parties	Not Permitted	Not Permitted
Use of Crunchy Data Software in Connection with Consulting or Support Services Delivered to Third Parties	Not permitted	Not permitted

This update for Crunchy Postgres for Kubernetes constitutes no changes to our upstream Postgres Operator (PGO) which remains available as open source under the Apache 2.0 license

Third, as we recently announced support for ARM builds for customers which provide some great cost savings relative to performance–those container images are now available for download from the Crunchy Data Developer Portal.

Finally, we have adapted our policy regarding retaining container images within our Developer Portal to provide for images to be retained for a longer period of time. Previously we provided for the latest two releases of Postgres to be available. At the time our intention was to encourage frequent upgrades of Crunchy Postgres for Kubernetes and prevent users from accessing out of date container images, as we believe an updated database is a healthy one. We've realized that this has caused pain and surprises to users who weren't in the process of regularly updating their database. While we will continue to update only the container images associated with the two most recent Crunchy Postgres for Kubernetes versions, we will now continue to provide the un-updated earlier versions of Crunchy Postgres for Kubernetes and Postgres container images through the Developer Portal in order to prevent surprises in user environments. To the extent you need updated versions of the older Crunchy Postgres for Kubernetes and Postgres container images, or are interested in monthly rebuilds of the Crunchy Postgres for Kubernetes and Postgres container images, please contact us learn more about the benefits of a commercial subscription.

We hope these changes will provide a better user experience for the PGO community and participants of the Crunchy Data Developer Program.

[rgherta]

Very disappointing