Customization Overview

Elastic Path does not intend or expect that CloudOps for Kubernetes will fulfill all requirements for every customer or meet the needs of all Self Managed Commerce customers. Self Managed Commerce customers can extend or customize the CloudOps for Kubernetes code, creating a fork of the CloudOps for Kubernetes code.

Customizing makes upgrading more difficult.

Regular CloudOps for Kubernetes upgrades are required to stay ahead of the Amazon Elastic Kubernetes Service (EKS) end of support cycle, as discussed in Support Lifecycle. When you customize the CloudOps for Kubernetes code base or architecture, it is very difficult to apply CloudOps for Kubernetes upgrades. Minimize CloudOps for Kubernetes customizations to simplify future upgrades.

Infrastructure Options

If you want to make significant customizations to meet your requirements, then CloudOps for Kubernetes may not be the most suitable long-term infrastructure solution for your Self Managed Commerce project. To learn about other infrastructure options, see Self Managed Commerce Deployment Solutions.

important

When you fork the CloudOps for Kubernetes code, you are responsible to:

• Ensure the proper design, implementation and functionality of modifications and extensions.
• Troubleshoot and resolve any issues with Self Managed Commerce or CloudOps for Kuberernetes resulting from the modifications and extensions.
• Maintain and update the fork of the CloudOps for Kubernetes code by implementing code fixes and merging CloudOps for Kubernetes updates provided by Elastic Path.