Add PKO (Package Operator) deployment manifests#286
Open
anispate wants to merge 2 commits intoopenshift:mainfrom
Open
Add PKO (Package Operator) deployment manifests#286anispate wants to merge 2 commits intoopenshift:mainfrom
anispate wants to merge 2 commits intoopenshift:mainfrom
Conversation
This commit adds Package Operator (PKO) deployment configuration to migrate osd-metrics-exporter from OLM (Operator Lifecycle Manager) to PKO. PKO is a more lightweight deployment model that packages all operator manifests into a container image, deployed via a ClusterPackage custom resource. Added files: - .tekton/osd-metrics-exporter-pko-*.yaml: Konflux build pipelines for PKO image - build/Dockerfile.pko: Dockerfile to build PKO package image - deploy_pko/: PKO manifests (RBAC, Deployment, PackageManifest) - deploy_pko/Cleanup-OLM-Job.yaml: Job to clean up old OLM resources - hack/pko/clusterpackage.yaml: ClusterPackage template for deployment Related: SREP-3729
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anispate The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #286 +/- ##
=======================================
Coverage 45.36% 45.36%
=======================================
Files 13 13
Lines 690 690
=======================================
Hits 313 313
Misses 363 363
Partials 14 14 🚀 New features to boost your workflow:
|
Applied the same manual fixes that were needed for aws-vpce-operator (SREP-3729): 1. Add OPERATOR_IMAGE parameter to clusterpackage.yaml template - Required to pass operator image to PKO deployment - Added config.image field in ClusterPackage spec 2. Fix manifest.yaml schema - Move 'type: object' to correct level (was incorrectly nested inside properties) - Ensures proper OpenAPI v3 schema validation 3. Add Namespace resource - deploy_pko/Namespace-openshift-osd-metrics-exporter.yaml - Includes cluster-monitoring label and PKO phase annotation - Was not in original deploy/ directory, added manually like AVO These fixes ensure PKO deployment works correctly following the proven aws-vpce-operator migration pattern.
Contributor
|
@anispate: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds Package Operator (PKO) deployment configuration to migrate osd-metrics-exporter from OLM (Operator Lifecycle Manager) to PKO.
PKO is a more lightweight deployment model that packages all operator manifests into a container image, deployed via a ClusterPackage custom resource.
Changes
Generated via boilerplate PKO migration script:
.tekton/osd-metrics-exporter-pko-*.yaml- Konflux build pipelines for PKO imagebuild/Dockerfile.pko- Dockerfile to build PKO package imagedeploy_pko/- PKO manifests (RBAC, Deployment, PackageManifest)deploy_pko/Cleanup-OLM-Job.yaml- Job to clean up old OLM resourceshack/pko/clusterpackage.yaml- ClusterPackage template for deploymentManual fixes applied (same as aws-vpce-operator SREP-3729):
OPERATOR_IMAGEparameter andconfig.imageto ClusterPackage templatetype: objectwas incorrectly nested inside properties)Migration Path
Testing Plan
After this PR merges and subsequent MRs are deployed:
1. Verify Konflux PKO Image Build
2. Integration Deployment Validation (hivei01ue1)
3. Functional Validation
4. Compare PKO vs OLM
Related
Follow-up MRs
After this merges:
Generated with Claude Code