ZeroDownTime
/
kubezero
3
0
Fork 0
Code Issues 1 Pull Requests 23 Releases Wiki Activity

chore(deps): update kubezero-sql-dependencies #141

Open
renovate wants to merge 1 commits from renovate/kubezero-sql-kubezero-sql-dependencies into master
pull from: renovate/kubezero-sql-kubezero-sql-dependencies
merge into: ZeroDownTime:master
Conversation 0 Commits 1 Files Changed 1 +3 -3
renovate commented 2023-11-22 18:39:21 +00:00
Member
Copy Link

This PR contains the following updates:

Package Update Change
mariadb-galera (source) minor 7.4.7 -> 7.5.5
pxc-operator (source) minor 1.12.1 -> 1.14.1

Release Notes

percona/percona-helm-charts (pxc-operator)

v1.14.1

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:
K8SPXC-1365 - Fix watchNamespace and add createNamespace option

v1.14.0

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

v1.13.5

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:
CLOUD-838 - Allow setting env vars on the pxc-operator deployment (thanks @​2ZZ)

v1.13.4

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Fixes:
K8SPXC-1351 - Add pod annotations for pxc-operator helm chart (thanks @​pauvos)

v1.13.3

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:
CLOUD-767 - Include Release.Namespace in metadata objects

v1.13.2

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:
K8SPXC-1291 - Add automatic /tmp mount when readOnlyRootFileSystem is set (Thanks @​MarcThe for contribution)

v1.13.1

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:
K8SPXC-1279 - Add optional securityContext for operator container (Thanks for contributing @​MarcThe)

v1.13.0

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:
K8SPXC-1165 - Update for operator release 1.13.0

Full release notes

v1.12.2

Compare Source

A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster)

Changes:

  • K8SPXC-1188 - put annotation resource-policy: keep on cluster namespace when operator is set to watch namespace (this namespace.yaml will be removed sometime later)

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [mariadb-galera](https://bitnami.com) ([source](https://github.com/bitnami/charts/tree/HEAD/bitnami/mariadb-galera)) | minor | `7.4.7` -> `7.5.5` | | [pxc-operator](https://docs.percona.com/percona-operator-for-mysql/pxc/) ([source](https://github.com/percona/percona-helm-charts)) | minor | `1.12.1` -> `1.14.1` | --- ### Release Notes <details> <summary>percona/percona-helm-charts (pxc-operator)</summary> ### [`v1.14.1`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.14.1) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.14.0...pxc-operator-1.14.1) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: [K8SPXC-1365](https://perconadev.atlassian.net/browse/K8SPXC-1365) - Fix watchNamespace and add createNamespace option ### [`v1.14.0`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.14.0) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.13.5...pxc-operator-1.14.0) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) ### [`v1.13.5`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.13.5) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.13.4...pxc-operator-1.13.5) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: [CLOUD-838](https://perconadev.atlassian.net/browse/CLOUD-838) - Allow setting env vars on the pxc-operator deployment (thanks [@&#8203;2ZZ](https://github.com/2ZZ)) ### [`v1.13.4`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.13.4) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.13.3...pxc-operator-1.13.4) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Fixes: [K8SPXC-1351](https://perconadev.atlassian.net/browse/K8SPXC-1351) - Add pod annotations for pxc-operator helm chart (thanks [@&#8203;pauvos](https://github.com/pauvos)) ### [`v1.13.3`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.13.3) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.13.2...pxc-operator-1.13.3) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: [CLOUD-767](https://jira.percona.com/browse/CLOUD-767) - Include Release.Namespace in metadata objects ### [`v1.13.2`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.13.2) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.13.1...pxc-operator-1.13.2) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: [K8SPXC-1291](https://jira.percona.com/browse/K8SPXC-1291) - Add automatic /tmp mount when readOnlyRootFileSystem is set (Thanks [@&#8203;MarcThe](https://github.com/MarcThe) for contribution) ### [`v1.13.1`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.13.1) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.13.0...pxc-operator-1.13.1) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: [K8SPXC-1279](https://jira.percona.com/browse/K8SPXC-1279) - Add optional securityContext for operator container (Thanks for contributing [@&#8203;MarcThe](https://github.com/MarcThe)) ### [`v1.13.0`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.13.0) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.12.2...pxc-operator-1.13.0) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: [K8SPXC-1165](https://jira.percona.com/browse/K8SPXC-1165) - Update for operator release 1.13.0 [Full release notes](https://docs.percona.com/percona-operator-for-mysql/pxc/ReleaseNotes/Kubernetes-Operator-for-PXC-RN1.13.0.html) ### [`v1.12.2`](https://github.com/percona/percona-helm-charts/releases/tag/pxc-operator-1.12.2) [Compare Source](https://github.com/percona/percona-helm-charts/compare/pxc-operator-1.12.1...pxc-operator-1.12.2) A Helm chart for deploying the Percona Operator for MySQL (based on Percona XtraDB Cluster) Changes: - [K8SPXC-1188](https://jira.percona.com/browse/K8SPXC-1188) - put annotation `resource-policy: keep` on cluster namespace when operator is set to watch namespace (this namespace.yaml will be removed sometime later) </details> --- ### 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy42NC4zIiwidXBkYXRlZEluVmVyIjoiMzcuMjY3LjEiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIifQ==-->
renovate added the
renovate
 label 2023-11-22 18:39:21 +00:00
renovate force-pushed renovate/kubezero-sql-kubezero-sql-dependencies from b0aa45c12e to 3d77aa9475 2024-01-31 03:09:36 +00:00 Compare
renovate force-pushed renovate/kubezero-sql-kubezero-sql-dependencies from 3d77aa9475 to 65352291f6 2024-02-02 03:09:54 +00:00 Compare
renovate force-pushed renovate/kubezero-sql-kubezero-sql-dependencies from 65352291f6 to a8d984ecd6 2024-03-05 03:21:30 +00:00 Compare
renovate force-pushed renovate/kubezero-sql-kubezero-sql-dependencies from a8d984ecd6 to a494106c01 2024-04-06 03:07:30 +00:00 Compare
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b renovate/kubezero-sql-kubezero-sql-dependencies master
git pull origin renovate/kubezero-sql-kubezero-sql-dependencies

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff renovate/kubezero-sql-kubezero-sql-dependencies
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
renovate

Dependency via Renovate

No Label
renovate
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ZeroDownTime/kubezero#141
No description provided.
Delete Branch "renovate/kubezero-sql-kubezero-sql-dependencies"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?