Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: delete default value of minAvailable #1096

Merged
merged 1 commit into from
Dec 24, 2024

Conversation

Rory-Z
Copy link
Member

@Rory-Z Rory-Z commented Dec 24, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new version v2beta1 for the EMQX CustomResourceDefinition (CRD) with enhanced properties.
    • Added support for secretRef in bootstrapAPIKeys for improved security.
    • New fields in the status section provide detailed insights into EMQX nodes.
  • Bug Fixes

    • Removed default value for MinAvailable, now requiring explicit definition.
  • Documentation

    • Updated API reference documentation for v2beta1, clarifying changes to the minAvailable field.

@Rory-Z Rory-Z requested a review from a team as a code owner December 24, 2024 07:49
Copy link

coderabbitai bot commented Dec 24, 2024

Walkthrough

This pull request introduces modifications to the EMQX Operator's CustomResourceDefinition (CRD) and associated documentation across multiple files. The primary change involves removing the default value annotation for the MinAvailable field in the EMQXReplicantTemplateSpec structure. The update spans configuration files, API type definitions, and reference documentation in both English and Chinese, reflecting a comprehensive approach to updating the EMQX Operator's specification.

Changes

File Change Summary
apis/apps/v2beta1/emqx_types.go Removed default value annotation // +kubebuilder:default:=1 for MinAvailable field
config/crd/bases/apps.emqx.io_emqxes.yaml Added v2beta1 version with new properties like secretRef, clusterDomain, config, and expanded status fields
deploy/charts/emqx-operator/templates/crd.emqxes.apps.emqx.io.yaml Introduced v2beta1 version with updated schema definitions and expanded template specifications
docs/en_US/reference/v2beta1-reference.md Updated minAvailable field documentation, removing default value
docs/zh_CN/reference/v2beta1-reference.md Updated minAvailable field documentation in Chinese, removing default value

Possibly related PRs

Poem

🐰 Hop, hop, through code's domain,
Default values now unchained!
MinAvailable sets us free,
Flexibility's the key, you see!
EMQX Operator's new refrain 🚀


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
🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@Rory-Z Rory-Z force-pushed the chore/delete-default-value branch from 3575640 to 583e921 Compare December 24, 2024 07:53
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/en_US/reference/v2beta1-reference.md (1)

111-111: LGTM! Consider enhancing the documentation.

The removal of the default value for minAvailable is appropriate since it's mutually exclusive with maxUnavailable. Consider adding an example to clarify the usage, such as "For example, setting '50%' ensures that at least half of the pods remain available during eviction."

🧰 Tools
🪛 LanguageTool

[uncategorized] ~111-~111: A comma might be missing here.
Context: ...n the
absence of the evicted pod. So for example you can prevent all volunta...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~111-~111: A comma might be missing here.
Context: ...r />absence of the evicted pod. So for example you can prevent all voluntary
evic...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06e45d3 and 583e921.

📒 Files selected for processing (5)
  • apis/apps/v2beta1/emqx_types.go (0 hunks)
  • config/crd/bases/apps.emqx.io_emqxes.yaml (0 hunks)
  • deploy/charts/emqx-operator/templates/crd.emqxes.apps.emqx.io.yaml (0 hunks)
  • docs/en_US/reference/v2beta1-reference.md (2 hunks)
  • docs/zh_CN/reference/v2beta1-reference.md (2 hunks)
💤 Files with no reviewable changes (3)
  • apis/apps/v2beta1/emqx_types.go
  • config/crd/bases/apps.emqx.io_emqxes.yaml
  • deploy/charts/emqx-operator/templates/crd.emqxes.apps.emqx.io.yaml
🧰 Additional context used
🪛 LanguageTool
docs/en_US/reference/v2beta1-reference.md

[uncategorized] ~111-~111: A comma might be missing here.
Context: ...n the
absence of the evicted pod. So for example you can prevent all volunta...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~111-~111: A comma might be missing here.
Context: ...r />absence of the evicted pod. So for example you can prevent all voluntary
evic...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~235-~235: A comma might be missing here.
Context: ...n the
absence of the evicted pod. So for example you can prevent all volunta...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~235-~235: A comma might be missing here.
Context: ...r />absence of the evicted pod. So for example you can prevent all voluntary
evic...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🔇 Additional comments (3)
docs/zh_CN/reference/v2beta1-reference.md (2)

111-111: LGTM! Documentation update for EMQXCoreTemplateSpec.minAvailable

The removal of the default value for minAvailable field is consistent with the PR objective and maintains the correct validation rule.


235-235: LGTM! Documentation update for EMQXReplicantTemplateSpec.minAvailable

The removal of the default value for minAvailable field is consistent with the PR objective and maintains the correct validation rule.

docs/en_US/reference/v2beta1-reference.md (1)

235-235: LGTM! Verify mutual exclusivity implementation.

The removal of the default value for minAvailable in EMQXReplicantTemplateSpec maintains consistency with EMQXCoreTemplateSpec.

Let's verify the mutual exclusivity implementation:

✅ Verification successful

Mutual exclusivity is properly implemented in the CRD validation

The CRD validation rules correctly enforce mutual exclusivity between minAvailable and maxUnavailable fields through:

  • A CEL validation rule: has(self.minAvailable) && has(self.maxUnavailable) ? false : true
  • A clear error message: "minAvailable cannot be set when maxUnavailable is specified. These fields are mutually exclusive in PodDisruptionBudget."
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that minAvailable and maxUnavailable are mutually exclusive in the CRD validation

# Search for the CRD validation rules
ast-grep --pattern 'oneOf {
  $$$
  properties {
    minAvailable: $$$
  }
  $$$
  properties {
    maxUnavailable: $$$
  }
  $$$
}'

Length of output: 134


Script:

#!/bin/bash
# Let's try a different approach to find the CRD validation rules
# Search for files containing both minAvailable and maxUnavailable
rg -l "minAvailable.*maxUnavailable|maxUnavailable.*minAvailable" --type yaml

# Then let's examine the content of these files to verify the validation rules
rg "minAvailable|maxUnavailable" -A 5 -B 5 --type yaml

Length of output: 11606

🧰 Tools
🪛 LanguageTool

[uncategorized] ~235-~235: A comma might be missing here.
Context: ...n the
absence of the evicted pod. So for example you can prevent all volunta...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~235-~235: A comma might be missing here.
Context: ...r />absence of the evicted pod. So for example you can prevent all voluntary
evic...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

@Rory-Z Rory-Z merged commit 70eeca7 into emqx:main Dec 24, 2024
42 checks passed
@Rory-Z Rory-Z deleted the chore/delete-default-value branch December 24, 2024 08:03
Copy link

codecov bot commented Dec 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.38%. Comparing base (06e45d3) to head (583e921).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1096      +/-   ##
==========================================
+ Coverage   76.16%   76.38%   +0.22%     
==========================================
  Files          69       69              
  Lines        6246     6246              
==========================================
+ Hits         4757     4771      +14     
+ Misses       1249     1240       -9     
+ Partials      240      235       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant