chore(greptimedb-operator): release greptimedb-operator

[zyy17]

Summary by CodeRabbit

• New Features

  • Updated application version to 0.1.3-alpha.6 and chart version to 0.2.11.
  • Enhanced security context definitions for various components of the GreptimeDB cluster, improving deployment security.

• Bug Fixes

  • Adjusted image tag to reflect the new version v0.1.3-alpha.6.

• Documentation

  • Updated README to reflect the new application and chart versions.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the greptimedb-operator Helm chart, specifically modifying the Chart.yaml, README.md, and configuration files. The appVersion and chart version have been incremented, reflecting a new release. Additionally, security context properties have been added to the custom resource definitions (CRDs) for enhanced security configurations across various components of the GreptimeDB cluster.

Changes

File Path	Change Summary
charts/greptimedb-operator/Chart.yaml	Updated appVersion from 0.1.3-alpha.3 to 0.1.3-alpha.6 and version from 0.2.10 to 0.2.11.
charts/greptimedb-operator/README.md	Updated version number from 0.2.10 to 0.2.11, appVersion from 0.1.3-alpha.3 to 0.1.3-alpha.6, and image.tag from v0.1.3-alpha.3 to v0.1.3-alpha.6.
charts/greptimedb-operator/templates/crds/crd-greptimedbcluster.yaml	Added security context properties for datanode, flownode, frontend, and main components.
charts/greptimedb-operator/templates/crds/crd-greptimedbstandalone.yaml	Added securityContext section under main and spec for GreptimeDBStandalone.
charts/greptimedb-operator/values.yaml	Updated image.tag from v0.1.3-alpha.3 to v0.1.3-alpha.6.

Possibly related PRs

• chore: bump greptimedb version from v0.9.0 to v0.9.1 #151: Updates the Chart.yaml for the greptimedb-cluster, including changes to appVersion and version.
• chore: bump greptimedb-operator to v0.1.0 #166: Updates the Chart.yaml for the greptimedb-operator, reflecting changes similar to the main PR.
• chore: bump greptimedb-operator version to v0.1.1 and add operator service configs #170: Similar updates to the Chart.yaml for the greptimedb-operator, focusing on appVersion and version.
• chore: bump greptimedb version to v0.9.5 #175: Changes in the Chart.yaml for the greptimedb-cluster with updates to appVersion and version.
• chore: bump operator version to v0.1.3-alpha.1 #180: Updates to the Chart.yaml for the greptimedb-operator, including appVersion and version changes.
• refactor: bump operator version to v0.1.3-alpha.3 #192: Reflects changes in the Chart.yaml for the greptimedb-operator, similar to the main PR.

Suggested reviewers

• daviderli614

Poem

🐰 In the garden where the changes bloom,
New versions hop, dispelling gloom.
Security's tight in every layer,
With tags updated, we dance with flair.
For GreptimeDB, a leap we take,
In every chart, new paths we make! 🌼

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

charts/greptimedb-operator/templates/crds/crd-greptimedbstandalone.yaml (1)

2218-2281: LGTM: Comprehensive pod-level security context implementation.

The pod-level security context implementation is thorough and provides essential security controls:

• File system group controls (fsGroup, fsGroupChangePolicy)
• Supplemental groups configuration
• System-level controls (sysctls)
• Security profiles at pod level

Consider documenting recommended security context values in the chart's README.md or values.yaml to guide users in securing their GreptimeDB deployments effectively.

charts/greptimedb-operator/templates/crds/crd-greptimedbcluster.yaml (1)

Line range hint 2060-17469: Consider adding default values for critical security settings.

While the schema is well-defined, consider adding default values for critical security settings to ensure secure-by-default behavior:

• runAsNonRoot: true
• allowPrivilegeEscalation: false
• readOnlyRootFilesystem: true

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1eddc82 and 47511f5.

📒 Files selected for processing (5)

• charts/greptimedb-operator/Chart.yaml (1 hunks)
• charts/greptimedb-operator/README.md (2 hunks)
• charts/greptimedb-operator/templates/crds/crd-greptimedbcluster.yaml (12 hunks)
• charts/greptimedb-operator/templates/crds/crd-greptimedbstandalone.yaml (2 hunks)
• charts/greptimedb-operator/values.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (3)

• charts/greptimedb-operator/Chart.yaml
• charts/greptimedb-operator/README.md
• charts/greptimedb-operator/values.yaml

🔇 Additional comments (4)

charts/greptimedb-operator/templates/crds/crd-greptimedbstandalone.yaml (1)

2048-2108: LGTM: Well-structured container security context implementation.

The addition of container-level security context is comprehensive and follows Kubernetes best practices, including:

• Privilege control (allowPrivilegeEscalation, privileged)
• User/group settings (runAsUser, runAsGroup, runAsNonRoot)
• Root filesystem protection (readOnlyRootFilesystem)
• Security profiles (seccompProfile, seLinuxOptions)
• Container capabilities management

charts/greptimedb-operator/templates/crds/crd-greptimedbcluster.yaml (3)

2060-2120: LGTM: Main container security context configuration is comprehensive.

The security context configuration for the main container includes all essential security settings:

• Process execution controls (allowPrivilegeEscalation, privileged)
• User/group controls (runAsUser, runAsGroup, runAsNonRoot)
• Filesystem controls (readOnlyRootFilesystem)
• Linux security modules (capabilities, seLinuxOptions, seccompProfile)

---

2230-2293: LGTM: Pod-level security contexts are consistently defined across components.

The pod-level security contexts are consistently defined across all components (base, datanode, flownode, frontend, monitoring) with comprehensive settings:

• Group management (fsGroup, supplementalGroups)
• User context (runAsUser, runAsGroup, runAsNonRoot)
• Linux security modules (seLinuxOptions, seccompProfile)
• Windows support (windowsOptions)

Also applies to: 5273-5336, 8290-8353, 11337-11400, 14424-14487, 17406-17469

---

11167-11227: LGTM: Container-level security contexts for frontend and monitoring components.

The security contexts for frontend and monitoring containers mirror the main container configuration, ensuring consistent security policies across all containers.

Also applies to: 17236-17296