Skip to content

OSDOCS-18910: Document OLM v1 deployment configuration API#111495

Open
cbippley wants to merge 2 commits into
openshift:mainfrom
cbippley:OSDOCS-18910
Open

OSDOCS-18910: Document OLM v1 deployment configuration API#111495
cbippley wants to merge 2 commits into
openshift:mainfrom
cbippley:OSDOCS-18910

Conversation

@cbippley
Copy link
Copy Markdown
Contributor

@cbippley cbippley commented May 11, 2026

Overview

Documents the deployment configuration API for OLM v1, providing feature parity with OLM v0's SubscriptionConfig.

Related Issues

Content Added

6 new documentation modules (21.9K):

  • olmv1-deployment-config-api.adoc (4.4K) - Core concepts
  • olmv1-clusterobjectsets-deployment-mechanism.adoc (2.7K) - Deployment mechanism
  • olmv1-customizing-operator-deployments.adoc (2.1K) - Procedures
  • olmv1-deployment-config-examples.adoc (4.7K) - Examples
  • olmv1-deployment-config-reference.adoc (5.8K) - Field reference
  • olmv1-deployment-config-troubleshooting.adoc (2.2K) - Troubleshooting

Quality Assurance

DITA compliant (0 errors)
Style guide compliant (0 errors, 0 warnings)
Validated against upstream documentation
Tested on live cluster (OpenShift 4.22 nightly)

  • All commands and jsonpaths verified working
  • Label selectors for finding operator deployments confirmed
  • Condition paths and status queries tested with cert-manager operator
  • Deployment specification paths validated

Technical Improvements

  • Fixed bundle status documentation to clarify output format and added command for retrieving full bundle annotations
  • All troubleshooting commands verified against running ClusterExtension resources

Target: OpenShift 4.22 (Tech Preview)

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 11, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 11, 2026

@cbippley: This pull request references OSDOCS-18910 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "5.0." or "openshift-5.0.", but it targets "openshift-4.22" instead.

Details

In response to this:

Overview

Documents the deployment configuration API for OLM v1, providing feature parity with OLM v0's SubscriptionConfig.

Related Issues

Content Added

6 new documentation modules (21.9K):

  • olmv1-deployment-config-api.adoc (4.4K) - Core concepts
  • olmv1-clusterobjectsets-deployment-mechanism.adoc (2.7K) - Deployment mechanism
  • olmv1-customizing-operator-deployments.adoc (2.1K) - Procedures
  • olmv1-deployment-config-examples.adoc (4.7K) - Examples
  • olmv1-deployment-config-reference.adoc (5.8K) - Field reference
  • olmv1-deployment-config-troubleshooting.adoc (2.2K) - Troubleshooting

Quality Assurance

✅ DITA compliant (0 errors)
✅ Style guide compliant (0 errors, 0 warnings)
✅ Validated against upstream documentation

SME Review Required

See inline comments for areas needing verification by Per Goncalves da Silva.

Target: OpenShift 4.22 (Tech Preview)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label May 11, 2026
@cbippley
Copy link
Copy Markdown
Contributor Author

cbippley commented May 11, 2026

✅ Validated Content Summary

The following content has been fully validated against upstream documentation and is accurate:

Merge Behaviors (8 fields)

  • env/envFrom: Merge, deployment config wins
  • resources: Complete replacement
  • nodeSelector: Complete replacement
  • tolerations: Append
  • affinity: Selective override (non-nil fields)
  • volumes/volumeMounts: Append
  • annotations: Merge, bundle wins

Schema Validation

  • ✅ Schema source: SubscriptionConfig type from operator-framework API
  • ✅ Validation error types: unknown field, type mismatch, required field
  • ✅ JSON schema from Kubernetes API definitions

Field Structures

  • ✅ Environment variable field structure (name, value, valueFrom)
  • ✅ Resource field structure (requests, limits, cpu, memory)
  • ✅ Toleration field structure (key, operator, value, effect)
  • ✅ All field descriptions match upstream documentation

Examples

  • ✅ All YAML examples are syntactically correct
  • ✅ Examples cover common use cases from upstream docs
  • ✅ KMM operator environment variable example
  • ✅ CA certificate volume mount example

Documentation Quality Assurance

DITA Compliance: 0 errors, 0 warnings
Vale Linting: 0 errors, 0 warnings (Red Hat + IBM style guides)
Module Types: Proper CONCEPT, PROCEDURE, REFERENCE structure
No Callouts: All code explanations use DITA-compliant definition lists
Concise Writing: ~30-40% reduction in prose while maintaining accuracy
Cross-references: All internal links valid
Technical Accuracy: Commands and jsonpaths verified on live cluster

@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented May 11, 2026

🤖 Mon May 11 19:15:21 - Prow CI generated the docs preview:

https://111495--ocpdocs-pr.netlify.app/openshift-enterprise/latest/extensions/ce/olmv1-configuring-extensions.html

Comment thread modules/olmv1-clusterobjectsets-deployment-mechanism.adoc Outdated
Comment thread modules/olmv1-clusterobjectsets-deployment-mechanism.adoc Outdated
Comment thread modules/olmv1-customizing-operator-deployments.adoc Outdated
Comment thread modules/olmv1-deployment-config-api.adoc Outdated
Comment thread modules/olmv1-deployment-config-api.adoc Outdated
Comment thread modules/olmv1-deployment-config-api.adoc Outdated
Comment thread modules/olmv1-deployment-config-api.adoc Outdated
Comment thread modules/olmv1-deployment-config-api.adoc Outdated
Comment thread modules/olmv1-deployment-config-api.adoc Outdated
Comment thread modules/olmv1-deployment-config-examples.adoc Outdated
Comment thread modules/olmv1-deployment-config-examples.adoc Outdated
Comment thread modules/olmv1-deployment-config-reference.adoc Outdated
Comment thread modules/olmv1-deployment-config-reference.adoc Outdated
Comment thread modules/olmv1-deployment-config-reference.adoc Outdated
Comment thread modules/olmv1-deployment-config-reference.adoc Outdated
Comment thread modules/olmv1-deployment-config-reference.adoc Outdated
Comment thread modules/olmv1-deployment-config-troubleshooting.adoc Outdated
Comment thread modules/olmv1-deployment-config-troubleshooting.adoc Outdated
Comment thread modules/olmv1-deployment-config-troubleshooting.adoc Outdated
Add comprehensive documentation for the deployment configuration API
in OLM v1, which provides feature parity with OLM v0 SubscriptionConfig.

New modules:
- olmv1-deployment-config-api.adoc: Core concepts and validation
- olmv1-clusterobjectsets-deployment-mechanism.adoc: Underlying deployment mechanism
- olmv1-customizing-operator-deployments.adoc: Step-by-step procedure
- olmv1-deployment-config-examples.adoc: Common configuration examples
- olmv1-deployment-config-reference.adoc: Complete field reference with merge behaviors
- olmv1-deployment-config-troubleshooting.adoc: Troubleshooting guide

Key features documented:
- Environment variables, resources, node placement (nodeSelector, tolerations, affinity)
- Volumes and volume mounts, annotations
- Explicit merge/override behavior for each field
- Schema validation and error handling
- OLM v0 to v1 migration guidance

All content is DITA-compliant and follows Red Hat/IBM style guidelines.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 11, 2026

@cbippley: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

- Reduce assembly short description from 355 to 183 chars
- Change procedure title from gerund to imperative form
- Improve short descriptions to include WHAT + WHY
- Remove "you can" patterns and add clear benefits
- All changes maintain Vale compliance (0 errors, 0 warnings)

Achieves CQA P8-P11 score of 4 for titles and descriptions.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants