Skip to content

[Backport release-1.4] fix(platform): add OpenSearch to PaaS bundle - #2757

Merged
myasnikovdaniil merged 1 commit into
release-1.4from
backport-2648-to-release-1.4
May 27, 2026
Merged

myasnikovdaniil merged 1 commit into
release-1.4from
backport-2648-to-release-1.4

Conversation

@myasnikovdaniil

Copy link
Copy Markdown
Contributor

What this PR does

Backport of #2648 to release-1.4.

OpenSearch ships as a complete package set in release-1.4
(packages/apps/opensearch/, packages/system/opensearch-operator/,
packages/system/opensearch-rd/, and the opensearch-operator /
opensearch-application PackageSources), but the PaaS bundle template
never referenced the two cozystack.opensearch-* PackageSources.

Result on any cluster with bundles.paas.enabled=true:

  • opensearch-operator is not deployed → no OpenSearchCluster CRD
  • opensearch-rd is not deployed → no ApplicationDefinition/opensearch,
    so the dashboard catalog has no OpenSearch entry and tenants cannot
    create opensearches.apps.cozystack.io

This adds the two missing includes to
packages/core/platform/templates/bundles/paas.yaml, matching #2648 exactly.

Release note

Fix: OpenSearch is now installed by the PaaS bundle (`bundles.paas.enabled=true`); previously the operator and ApplicationDefinition were defined but never referenced from the bundle, so OpenSearch did not appear in the dashboard catalog.

# Description
Backport of #2648 to `release-1.4`.

Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>
@coderabbitai

coderabbitai Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4d9e6c5a-0e18-403e-b1dd-994e88aec27d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport-2648-to-release-1.4

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request ensures that OpenSearch is correctly deployed when the PaaS bundle is enabled. By including the necessary package references in the bundle template, it resolves an issue where the operator and application definitions were present in the repository but not being utilized in the platform configuration.

Highlights

  • OpenSearch Integration: Added the missing OpenSearch operator and application references to the PaaS bundle template.
  • Backport: This PR serves as a backport of changes from the main branch to the release-1.4 branch.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment Gemini (@gemini-code-assist) Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@github-actions github-actions Bot added area/platform Issues or PRs related to platform infrastructure (bundle, flux, talos, installer) area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/bug Categorizes issue or PR as related to a bug size/XS This PR changes 0-9 lines, ignoring generated files labels May 27, 2026
@dosubot dosubot Bot added the kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line label May 27, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds the cozystack.opensearch-operator and cozystack.opensearch-application packages to the PaaS bundle template. The reviewer noted that modifying packages/core/platform/ is sensitive and may require updates to the migration flow or an explicit note regarding backward compatibility, as per the repository guidelines.

{{include "cozystack.platform.package.default" (list "cozystack.rabbitmq-operator" $) }}
{{include "cozystack.platform.package.default" (list "cozystack.redis-operator" $) }}
{{include "cozystack.platform.package.default" (list "cozystack.mongodb-operator" $) }}
{{include "cozystack.platform.package.default" (list "cozystack.opensearch-operator" $) }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This change modifies packages/core/platform/, which is a sensitive component. According to the repository guidelines, changes here can require updates to the migration flow (such as the Helm hook in packages/core/platform/templates/migration-hook.yaml and the runner image with scripts in packages/core/platform/images/migrations/). Since this PR lacks a corresponding migration update or an explicit note that backward compatibility is preserved, please provide an explicit note or update the migration flow.

References
  1. Changes to packages/core/platform/ can require updates to the migration flow. Flag any change to this package that lacks a corresponding migration update or an explicit note that backward compatibility is preserved. (link)

@myasnikovdaniil
myasnikovdaniil merged commit 67a89c2 into release-1.4 May 27, 2026
10 checks passed
@myasnikovdaniil
myasnikovdaniil deleted the backport-2648-to-release-1.4 branch May 27, 2026 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/platform Issues or PRs related to platform infrastructure (bundle, flux, talos, installer) area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line kind/bug Categorizes issue or PR as related to a bug size/XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant