Goal:
Provides libraries/toolings for onboarding Operator/partner ecosystems to OLM 1.0's permissions management so customers get benefits and rely on OLM 1.0 to deliver a wide variety of add-ons/extensions to their clusters.

Why is this important:
As the Operator Framework is moving toward the ultimate "descoped Operator" concept (see more in Descoping Plan), it's important that SDK (and/or other client-side libraries/toolings) helps Operator authors to understand OLM 1.0's permission management patterns, adopt them in their Operator projects, and embrace the mindset of an Operator being an extension as a cluster singleton.

Use cases

• SDK provides helper libraries to help Operator author

• SDK acts as a catalyst to enable the "descoped Operator" pattern.

• SDK helps set Operator authors up to the recommended/best practice design on Day 1 so less ongoing management issues on the OLM side on Day 2.

• SDK provides a strong incentive to drive the adoption of the SDK both internally and externally.

• The generated codes follow the best practices/recommendations so Operator authors stay more focused on app lifecycle/business logic.

Desired Outcome:

• set the Operator authors up with the recommended designs to bridge the supporting feature gap from the OLM side between the "scoped Operator" vs the "descoped Operator" world.

• SDK and OLM jointly contribute to driving the paradigm shift of the descoped Operator concept within the community.

• Operator authors to stay more focused on app lifecycle/business logic rather than dealing with infrastructure/configuration challenges.