Epic Goal

"Tech Preview" release of Java/Quarks Operator plugin SDK to enable Java users/customers to leverage existing Operator UX and cloud-native tooling (Quarkus) to write Operators managed by OLM.

Why is this important?

• We want to bring Java talents to manage infrastructure challenges
• We want to support managed service teams to manage distributed Java apps in the same language + existing libraries w/o steep learning curve
• We want to provide a way to manage Java apps leveraging the “high container density” + “high computing throughput” with Quarkus extension
• We want to enable more upstream communities/partners to easily join to Operator Framework ecosystem and integrate with OLM

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

• OLM Integrations (java-operator-plugins)
  • make bundle
    • bundle validate
  • run bundle
  • run bundle-upgrade

• Expose Operator metrics (java-operator-sdk)
  • Out-of-the-box Operator metrics
  • Adding custom metrics

• Investigate supporting webhook creation + OLM integration (java-operator-sdk, java-operator-plugins)

• Investigate supporting scorecard (java-operator-plugins)

Previous Work (Optional):

1. OSDK-1480 - [UPSTREAM] Release beta of Quarkus plugin

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>