WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

OpenLiberty Operator - Day-2 Operations

  • 1.  OpenLiberty Operator - Day-2 Operations

    Posted Thu May 15, 2025 03:33 AM

    The IBM WebSphereLibertyOperator and the OpenLibertyOperator provide K8S customr-resource-definitions (CRDs) to collect Traces and Dumps namely:

    • OpenLibertyDump
    • OpenLibertyTrace

    These CRDs allow the generation of traces and dumps for the server the cloud native way. However bioh CRDs have the issue that a podName must be specified which becomes a usability limitation if the deployment scales up (either manually or automatically via the HPA) as we have generic pod names there and the number of required CRDs varies and can't be prepared / setup using DevOps approach.

    The OpenLibertyOperator issue Support Day 2 operation for gathering trace for app/server at startup · Issue #685 · OpenLiberty/open-liberty-operator lists another problem caused by this approach namely that we can't setup tracing covering the server startup.

    Therefore I'm wondering if there is a recommended way to setup Day2 CRDs based on the WebSphereLiberty- / OpenLibertyApplication name so that all pods are covered by the trace/dump CRD? 



    ------------------------------
    Hermann Huebler
    Cloud Architect
    Alpium IT Solutions GmbH
    Vienna
    Austria

    #IBMChampion
    ------------------------------


Related Content