Using Kubernetes operators with SAP BTP Kyma runtime
Disclaimer: This blog post focuses on SAP BTP, Kyma runtimes running on Kyma open source version 2.0. For existing SAP BTP Kyma runtimes which are on Kyma open source 1.0, they will need to wait until their Kyma runtimes are upgraded to Kyma open source 2.0.
- Updates and upgrades
- Scaling / Sharding
- among others.
A Kubernetes operator abstracts all these concerns by implementing the above-mentioned operations as a control loop.
As mentioned above, operators are built on top of custom resources, so you declare your intent to deploy a component as a custom resource and the operator will take care of installing it in your Kubernetes / Kyma cluster. Of course, you will first need to have the operator installed. This is normally a simpler operation as compared to operating a stateful component.
You can checkout operatorhub.io for a list of various operators provided by established organizations as well as the community.
The usefulness of operators is not limited to just deploying components in Kubernetes.
The basic logic of declaring a specification/state and letting the operator take care of ensuring the actual state matches with the declared state can be extended for numerous scenarios.
One interesting use case is to provision and managed Hyperscaler resources using the operators.
Check out this Kyma open source link for operator options for Hyperscalers.
Please check out this SAP sample to provision Azure Redis Cache instance using Azure Service Operator and then use it with an application deployed in Kyma runtime.
- Use operators to manage complex stateful applications
- Use operators to manage and provision Hyperscaler services.
Looking forward to your feedback and comments here.
If you have further questions about Kyma, feel free to post them in the answers area of the SAP Community, here is a link.
To stay up to date with everything in Kyma, make sure to visit our Kyma topic page.