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(deps): update helm release seaweedfs to v4.0.379 #1331

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2024

This PR contains the following updates:

Package Update Change
seaweedfs patch 4.0.377 -> 4.0.379
seaweedfs major 3.68.0 -> 4.0.379

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


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 these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from jessebot and cloudymax as code owners October 28, 2024 01:58
@renovate renovate bot force-pushed the renovate/seaweedfs-4.x branch from 87d5c19 to af42861 Compare October 29, 2024 04:47
@renovate renovate bot changed the title chore(deps): update helm release seaweedfs to v4.0.378 chore(deps): update helm release seaweedfs to v4.0.379 Oct 29, 2024
@cloudymax
Copy link
Contributor

cloudymax commented Nov 18, 2024

Progress

  • Filer, Master, and Volumes boot on new version
  • CSI driver
  • External Filer
  • FUSE mounts
  • Replication
  • Ingress options
  • Monitoring + Dashboards
  • Backups with k8up
  • Restoration from backups

Issues:

Replication not ready for use.

  1. While options for specifying Datacenter and Rack now exist in main helm-chart the creation and management of PVCs is immature and unpredictable. Will require more work to ingrate with our backup strategy

  2. CSI Driver data locality options not documented thoroughly enough to get a POC functional. Without this option we are forced to go over the network for all lookups.

  3. Network speed is critical limiting factor if data-locality isn't working. Our lab is limited to 1 & 2.5 Gbit. Until we upgrade to 10Gbit or data-locality can be fixed speeds are limited to 100-200MBps in replicated mode

Ingress non-functional

  1. Ingresses are a mess and presume a basic-auth + path-based routing setup. Will have to submit a PR to allow changing the PATH options etc...

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