chore(schema-migrator): separate job, include helm hooks

[prashant-shahi]

Summary

• New Features

  • Enhanced Job naming flexibility with conditional suffixes based on installation context.
  • Introduced lifecycle management for the schema migrator with additional Helm hook annotations.
  • Added a new wait init container to ensure ClickHouse readiness before migration.
  • Improved initialization logic for schemaMigrator and otel-collector based on installation or upgrade context.
  • Updated image versions for schemaMigrator and otelCollector to enhance deployment.

• Bug Fixes

  • Removed TTL setting for completed Jobs, streamlining job retention management.

• Documentation

  • Updated configuration details for the schema migrator in the values.yaml file to reflect new annotations and image version updates.

[coderabbitai[bot]]

Walkthrough

The pull request introduces changes to the Helm templates for Kubernetes Jobs associated with the schema migrator in the SigNoz application. A new variable, $schemaMigratorSuffix, is defined to conditionally modify the Job name based on the installation context. The ttlSecondsAfterFinished field is removed, affecting job retention. Additionally, annotations for Helm hooks are added to manage the lifecycle of the schema migrator during upgrades, ensuring it runs before the main upgrade and is deleted appropriately. The init containers are also renamed for clarity, and new containers are introduced to enhance functionality.

Changes

File Path	Change Summary
charts/signoz/templates/schema-migrator-async/migrations.yaml	- Updated Job name to include $schemaMigratorSuffix. - Modified command arguments to append the suffix. - Removed ttlSecondsAfterFinished. - Renamed init containers and added a new wait container.
charts/signoz/templates/schema-migrator/migrations.yaml	- Updated Job name to include $schemaMigratorSuffix. - Adjusted init container names for clarity. - Removed ttlSecondsAfterFinished. - Reformatted command for the first init container.
charts/signoz/values.yaml	- Added upgradeHelmHooks to enable lifecycle management. - Updated image tags for schemaMigrator and otelCollector. - Modified initContainers to include a new wait container.
charts/signoz/templates/otel-collector-metrics/deployment.yaml	- Added conditional logic for init container arguments based on installation or upgrade context.
charts/signoz/templates/otel-collector/deployment.yaml	- Introduced conditional logic for init container arguments depending on installation or upgrade context.

Possibly related PRs

• #526: The changes in this PR involve modifications to the schema migrator's job configuration, including renaming and restructuring, which directly relate to the updates made in the main PR regarding the init containers and job names.

Poem

🐇 In the garden of code, changes bloom,
A suffix to names, dispelling the gloom.
With hooks in the air, migrations take flight,
Jobs dance to the rhythm, all set for the night.
A sprinkle of YAML, a dash of delight,
In the world of SigNoz, everything's right! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.