OperatorHub

Installing Crunchy Postgres for Kubernetes Using OperatorHub on OpenShift

Crunchy Postgres for Kubernetes can be installed on OpenShift through the OperatorHub point-and-click experience. Under Operators > OperatorHub, search for Crunchy and you’ll find Marketplace, Certified and Community installers. Choose the installer that fits your needs and consider installing in a specific namespace.

Registering your installation

OperatorHub installers come with a registration requirement. Users who register their installations will experience uninterrupted Crunchy Postgres for Kubernetes service during upgrades. Registration is achieved by visiting our token creation page with a Crunchy Data account.

If you already are a Crunchy Customer and have a Crunchy Account, use your Access Portal credentials to log in here. If you are not a customer, request an account.

Installing your Token

To obtain your token for Crunchy Postgres for Kubernetes, go to the token creation page.

Once you have your token, create a file called cpk_token and paste the token into it. Use the cpk_token file to create a Secret.

oc create secret generic cpk-registration --from-file=cpk_token -n $NAMESPACECopy

And that's it! Your installation is now fully enabled.

How Registration Affects Your Installation

OperatorHub installers require a registration token to upgrade from the installed version of Postgres. Once you apply a token to your installation, the token will be internally validated by the operator. Token validation does not require an internet connection.

Without a token, existing Postgres clusters will continue running uninterrupted. You will be able to create and destroy them, but you won’t be able to upgrade existing Postgres clusters until you complete the registration process.

Registration Events

If your Crunchy Postgres for Kubernetes installation is properly registered, you will not see any registration-related events. However, if you have not yet registered, certain events may be generated for each PostgresCluster.

For instance, an event such as the following will be generated for any PostgresCluster managed by an unregistered installation:

Crunchy Postgres for Kubernetes requires registration for upgrades. Register now to be ready for your next upgrade. See https://access.crunchydata.com/register-cpk for details.Copy

This warning event simply indicates that registration will be required when upgrading.

If you are seeing this event, please be sure to register your installation as soon as possible.

Additional events will then be generated indicating successful (or unsuccessful) registration. For instance, the following informational event will be generated once you have successfully registered your installation:

Thank you for registering your installation of Crunchy Postgres for Kubernetes.Copy

Red Hat Certification and Container Compliance for Crunchy Postgres for Kubernetes

Overview

Crunchy Postgres for Kubernetes is certified by Red Hat, ensuring it meets stringent security and compatibility standards. This certification encompasses our use of containers, specifically adhering to the "Container image requirements" set forth by Red Hat.

Container Image Requirements

According to Red Hat's guidelines, container images must use a Universal Base Image (UBI) provided by Red Hat. The version of the UBI base image must be supported on the RHEL version undergoing certification.

Compliance with UBI 8

Currently, our UBI 8 containers fully comply with Red Hat’s requirements. The Red Hat Enterprise Linux Container Compatibility Matrix confirms that UBI 8 containers are supported across all host types, including RHEL 7, RHEL 8, and RHEL 9. This means our containers are supported on both older RHEL hosts (e.g., RHEL 7 for older OpenShift versions) and newer RHEL hosts (e.g., RHEL 9 on OpenShift v4.13+).

Certification and Support

Customers can be assured that our containers are fully certified and supported on all available versions of OpenShift. Our robust testing across all supported OpenShift versions ensures any issues are identified and addressed, with Red Hat providing support as needed.

Cross-Platform Compatibility

One of the key advantages of containers is their cross-platform compatibility. Containers encapsulate applications and their dependencies into a consistent runtime environment, which can be executed on various underlying operating systems. This portability ensures that our containers can run seamlessly on different OS versions and environments, including different versions of RHEL, other Linux distributions, and even other operating systems that support container runtimes like Docker. This cross-platform capability ensures flexibility and broad compatibility for diverse deployment scenarios.

FAQ

Q: What OperatorHub installers require a registration token?

A: All OperatorHub installers currently require a registration token.

Q: What happens if I don't install a token?

A: A valid token is required to be able to perform any upgrades after Crunchy Postgres for Kubernetes is installed. Your running Postgres instances will remain unaffected. New installs are also unaffected.

Q: What if my Crunchy Postgres for Kubernetes clusters can't establish an internet connection?

A: The token's validation is processed internally within Crunchy Postgres for Kubernetes. An active internet connection isn't needed for this verification process.

Q: How do I get a token?

A: To obtain a token, head to the Crunchy Data Token Portal at https://tokens.crunchydata.com. You'll be prompted to either log in via your Access Portal credentials or initiate an account request. You can also manage and view your existing tokens at this site.

Q: Do I need a token to install from the Red Hat Marketplace?

A: The token is only required to upgrade a running instance of Crunchy Postgres. Installs do not currently require a token. However, obtaining one as part of the install process is advised, so you do not need to worry about it when it's time to upgrade.

Q: What kinds of upgrades require a token?

A: Postgres introduces new features in a new major version once each year. With Crunchy Postgres for Kubernetes, you choose when to apply these upgrades, and they do require a token. Bug fixes and minor version upgrades for Postgres happen automatically when upgrading the operator, which also requires a token.

Q: Will I need a new token for each upgrade?

A: No. A token simply unlocks the ability to upgrade, and is not tied to a specific version of Crunchy Postgres for Kubernetes.

Q: When does this take effect?

A: The token system and website have been launched alongside the release of Crunchy Postgres for Kubernetes version 5.5. It's important to note that to upgrade beyond version 5.5, you will require a token. For instance, if you have Crunchy Postgres for Kubernetes version 5.5 installed, you will need a token when upgrading to version 5.5.1 or version 5.6.