fix(helm): update chart emqx-operator ( 2.2.25 → 2.2.26 ) #1417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.25
->2.2.26
Release Notes
emqx/emqx-operator (emqx-operator)
v2.2.26
: EMQX Operator 2.2.26 ReleasedCompare Source
Release Note 🍻
EMQX Operator 2.2.26 has been released.
Supported version
apps.emqx.io/v2beta1
apps.emqx.io/v1beta4
Enhancements 🚀
apps.emqx.io/v2beta1 EMQX
.minAvailable
ormaxUnavailable
inspec.coreTemplate.spec
orspec.replicantTemplate.spec
within the EMQX CRD. The default setting is {"minAvailable": 1}.EMQX operator can now be deployed in a single namespace scope, where it will only manage resources within that namespace. Just set
singleNamespace: true
in thevalues.yaml
file of Helm chart, and then the operator will only manage resources in the namespace where it is deployed.How to install/upgrade EMQX Operator 💡
Warning 🚨
apps.emqx.io/v1beta3
andapps.emqx.io/v2alpha1
will be dropped soonWhat's Changed
Full Changelog: emqx/emqx-operator@2.2.25...2.2.26
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.