IBM Support

STE Webinar - IBM Sterling OMS Operator Deep Dive Series: Session 2 - "Upgrades, Operations & Production Readiness"

Webcasts


Abstract

This session covers Day-2 operations for IBM OMS Operator deployments, including upgrades and compatibility considerations, scaling and configuration management, health monitoring, observability and troubleshooting, and production best practices for security, high availability and resilient multi-zone deployments.

Though this session mainly focuses on IBM Sterling OMS Container setup, it will be useful for others as well in understanding the baseline technical concepts around it.

Content

Webinar Session Details:


      Title: STE Webinar - IBM Sterling OMS Operator Deep Dive Series: Session 2 - "Upgrades, Operations & Production Readiness"
      Schedule: Tuesday, July 7th, 2026, 10:00 AM - 11:00 AM Eastern Time (US & Canada)
    
      Session Speakers:
           Chiranjeevi Dasegowda - Senior Support Engineer, IBM Sterling OMS Support
           Tin Vo - Senior Software Developer, IBM Sterling OMS Development
    

      Session hosts:
           Jitendra Buge - Technical Lead, IBM Sterling OMS Support
           Cathrin Christo Sagayarajan - Technical Support Engineer, IBM Sterling OMS Support

 

Questions and Answers:

Question #1: Is HPA available in lower/older versions or do we need to move to a recent release for the scaling features shown?
Answer: 
The question was asked in the context of the Scaling slide which covers two separate capabilities and they have different version requirements:
 
  • HPA (Horizontal Pod Autoscaling)— available since early operator versions. No version upgrade required. If you are already running the OMS Operator, you can usespec.horizontalPodAutoscalerstoday
  • spec.healthMonitor.replicaCount > 1 (multi-replica Health Monitor)— this is the newer addition, introduced in the July 2025 release (CASE 3.0.31, operator v1.1.0). If you want to run multiple Health Monitor replicas, you need to be on that release or later
  • spec.servers[].replicaCount and spec.restService.replicaCount— these have been available since earlier versions and do not require a recent release

In summary: For HPA, no upgrade needed. For running multiple Health Monitor replicas specifically, July 2025 release (v1.1.0) or later is required.

Question #2: What is the recommendation for custom RBAC roles when installing the OMS Operator in a very restrictive Kubernetes environment?
Answer:
  • The OMS Operator requires a fixed set of namespace-scoped permissions,  these cannot be reduced without breaking operator functionality
  • The minimum required permissions for the operator service account are:
    • Full CRUD on all OMS custom resources:OMEnvironment,OMServer,OrderService,OrderHub,CallCenter
    • Full CRUD on core Kubernetes resources:pods,secrets,configmaps,services,serviceaccounts,persistentvolumes,persistentvolumeclaims
    • Full CRUD on:deployments,statefulsets,replicasets,jobs,cronjobs
    • Full CRUD on:networkpolicies,ingresses,horizontalpodautoscalers
    • pods/exec(create) andpods/log(get)
  • All permissions are namespace-scoped i.e. the operator does not require cluster-admin or cluster-wide roles
  • For restrictive environments, the non-OLM (operator utility) installation is recommended,  it avoids the need for OLM-related cluster-level resources such as CatalogSources and Subscriptions and gives you direct control over the Role and RoleBinding you create

 

 

Presentation

https://ibm.biz/~N40e1JFme

Multimedia

https://ibm.biz/~xyBNGWenI

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management System Software"},"ARM Category":[{"code":"a8m0z000000cy0AAAQ","label":"Install and Deploy"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0;9.0.0;9.1.0;9.2.0;9.2.1;9.3.0;9.4.0;9.5.0"}]

Document Information

Modified date:
13 July 2026

UID

ibm17277892

Page Feedback