Skip to content

✨ OPRUN-4850: Introduce the initial ClusterObjectSlice API - #3195

Draft
fao89 wants to merge 3 commits into
operator-framework:mainfrom
fao89:oprun-4850-clusterobjectslice-api
Draft

fao89 wants to merge 3 commits into
operator-framework:mainfrom
fao89:oprun-4850-clusterobjectslice-api

Conversation

@fao89

@fao89 fao89 commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Description

Start the OPRUN-4850 design discussion with documentation and an initial experimental ClusterObjectSlice API for storing rendered manifests independently of rollout intent. Existing inline and Secret-backed content paths continue to work as they do today.

  • Document the motivation, representation tradeoffs, responsibility boundaries, reviewer decisions, and admission scenarios.
  • Introduce an immutable, cluster-scoped API with explicit object identities and JSON/GzipJSON payloads. Schema and CEL validate the storage envelope; payload parsing, decompression, and identity comparison remain follow-up work.
  • Generate the CRD, apply configurations, and API reference, wire the CRD into experimental installations, and cover admission behavior with API tests.

This draft is a conversation starter. Readable manifests, deeper admission validation, COD/COS references, digests, and retention coordination remain open for incremental proposals. Creating a slice stores content without applying objects or reporting rollout readiness.

Documentation is in one commit, followed by separate commits for API source/tests and generated code/manifests.

Related issue: https://redhat.atlassian.net/browse/OPRUN-4850

Validation

  • make test-unit
  • API and object-controller manifest tests after the entry type rename
  • make lint lint-helm
  • make lint-api-diff — no new issues; 32 pre-existing issues
  • make verify
  • Commit hooks and whitespace checks

Reviewer Checklist

  • API Go Documentation
  • Tests: Unit Tests (and E2E Tests, if appropriate)
  • Comprehensive Commit Messages
  • Links to related GitHub Issue(s)

Always review AI generated responses prior to use.
AI-assisted response via openshift-developer plugin

Start the OPRUN-4850 discussion with a minimal content-storage contract,
validation boundaries, ownership expectations, and incremental follow-ups.
Include the generated API reference alongside the design document.

Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
Introduce experimental immutable manifest storage with ClusterObjectSliceEntry
values. Validate the envelope through schema and CEL rules and add API tests
and experimental chart wiring. Deep payload admission, consumer integration,
and retention remain separate follow-ups for OPRUN-4850.

Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
Generate the experimental CRD, deep-copy methods, apply configurations,
and experimental installation manifests from the initial ClusterObjectSlice
API definition. The generated API reference is in the documentation commit.

Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 19, 2026
@netlify

netlify Bot commented Nov 19, 2026

Copy link
Copy Markdown

👷 Deploy request for olmv1 pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 9d3bec8

@openshift-ci

openshift-ci Bot commented Nov 19, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign pedjak for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coderabbitai

coderabbitai Bot commented Nov 19, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant