Is there a list of Areas of Impact while moving the Pega application from on-premise installation to containerization deployment?
@DeboliPaul could you check if the documentation mentioned in this post helps you?
@MarijeSchillern Thanks! It talks about only handling Kafka for stream services. However, there could be other areas apart from steam services that could be impacted. Is it not the case?
File services file path, BIX file path, Stream nodes, Authentication, All API call In-gress, Out-gress call will have to be allow-listed , container ports will need to be remapped to new load balancers, you need to move to clustering service for hazel cast, as embedded mode has issues, Kafka externalization, logs movement to a NAS directory as containers will be auto-refreshed/recycled any data needs to be hosted handled into persistence volumes on the cloud like S3 in AWS. Your deployment methodology would change of-course. you can deploy image every time vs deploy only rules it’s client choice. both has it’s own pros and cons.
@DeboliPaul I have not found any summary document about ‘areas of impact’ .
For Hazelcast, which is provided out-of-the-box with Pega, Pega Global Client Support is providing standard support: they will investigate if there is a problem with Hazelcast, and work with Hazelcast if necessary.
For Elasticsearch, Kafka, and Cassandra (for Pega Customer Decision Hub deployments), it is your responsibility to install and configure the third-party externalized services, and upgrade them when necessary. If you need support for these actions, you can reach out to that product’s open-source community to get help. You could also buy a licensed version of the third-party product, along with a support contract, from a third-party provider, and reach out to the provider for support.
Once you have your externalized services up and running, if you encounter an issue in production, you can call Pega Global Client Support for support.
The support model for externalized services is the same as the Pega Global Client Support process for supporting other vendor platform integrations, such as databases and application servers: provide basic troubleshooting to determine the cause of the issue. If Pega Global Client Support determines that the issue is not with Pega software, Pega Global Client Support will let you know that you must continue troubleshooting the issue with your third-party provider.
Hopefully the below articles may help:
Installing, patching, or updating Pega software in Kubernetes deployments
See the details for each service in Externalization of services in your deployment. For additional information about each third-party product, see the following documentation:
- Cassandra Overview (for Pega Customer Decision Hub deployments) - Cassandra overview
- Configuring External Kafka as a Stream service - Configuring External Kafka as a Stream service
- Using full-text search based in Elasticsearch - Using full-text search based in Elasticsearch
- Hazelcast: For Pega Platform™ version 8.6 and later, Pega supports a client-server deployment model using a cluster of nodes running Hazelcast as a server, to which the Pega nodes connect as a client. See Pega-provided Docker images.