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

fix: update helm chart emqx to 5.0.11 #2617

Merged
merged 1 commit into from
Nov 30, 2022
Merged

fix: update helm chart emqx to 5.0.11 #2617

merged 1 commit into from
Nov 30, 2022

Conversation

bloopy-boi[bot]
Copy link
Contributor

@bloopy-boi bloopy-boi bot commented Nov 29, 2022

This PR contains the following updates:

Package Update Change
emqx patch 5.0.3 -> 5.0.11

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@bloopy-boi bloopy-boi bot requested a review from h3mmy as a code owner November 29, 2022 20:23
@bloopy-boi bloopy-boi bot added renovate/helm type/patch size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. area/cluster Changes made in the cluster directory labels Nov 29, 2022
@bloopy-boi
Copy link
Contributor Author

bloopy-boi bot commented Nov 29, 2022

Path: cluster/apps/home/emqx/helm-release.yaml
Version: 5.0.3 -> 5.0.11

@@ -39,10 +39,9 @@
 EMQX_AUTHENTICATION__SERVER: "emqx-db:5432"
 EMQX_AUTHENTICATION__USERNAME: "postgres"
 EMQX_CLUSTER__DISCOVERY_STRATEGY: "k8s"
+ EMQX_CLUSTER__DNS__NAME: "emqx-headless.default.svc.cluster.local"
+ EMQX_CLUSTER__DNS__RECORD_TYPE: "srv"
 EMQX_CLUSTER__K8S__ADDRESS_TYPE: "hostname"
- EMQX_CLUSTER__K8S__APISERVER: "https://kubernetes.default.svc:443"
- EMQX_CLUSTER__K8S__NAMESPACE: "default"
- EMQX_CLUSTER__K8S__SERVICE_NAME: "emqx-headless"
 EMQX_CLUSTER__K8S__SUFFIX: "svc.cluster.local"
 EMQX_DASHBOARD__DEFAULT_PASSWORD: "${EMQX_ADMIN_PASSWORD}"
 EMQX_DASHBOARD__DEFAULT_USERNAME: "admin"
@@ -190,11 +189,11 @@
 metadata:
 labels:
 app: emqx
- version: 5.0.3
+ version: 5.0.11
 app.kubernetes.io/name: emqx
 app.kubernetes.io/instance: emqx
 annotations:
- checksum/config: "c50a3db4470fc9702d83942db016cb8635c3bca048af18d7b15b18e508897c07"
+ checksum/config: "5c03d00c43c7a42d3eeb02d5dc52b56c429ed31c8b0d14bfb185e56240f981a5"
 spec:
 volumes:
 - name: emqx-data
@@ -208,7 +207,7 @@
 - 1000
 containers:
 - name: emqx
- image: "emqx/emqx:5.0.3"
+ image: "emqx/emqx:5.0.11"
 imagePullPolicy: IfNotPresent
 securityContext:
 runAsNonRoot: true
@@ -242,14 +241,14 @@
 mountPath: "/opt/emqx/data"
 readinessProbe:
 httpGet:
- path: /api/v5/status
+ path: /status
 port: 18083
 initialDelaySeconds: 10
 periodSeconds: 5
 failureThreshold: 30
 livenessProbe:
 httpGet:
- path: /api/v5/status
+ path: /status
 port: 18083
 initialDelaySeconds: 60
 periodSeconds: 30

@bloopy-boi
Copy link
Contributor Author

bloopy-boi bot commented Nov 29, 2022

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ COPYPASTE jscpd yes no 1.31s
✅ YAML prettier 1 0 0 0.54s
✅ YAML yamllint 1 0 0.23s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

@h3mmy h3mmy merged commit f938bb9 into main Nov 30, 2022
@h3mmy h3mmy deleted the renovate/emqx-5.0.x branch November 30, 2022 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster Changes made in the cluster directory renovate/helm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/patch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant