timtorchen / homelab Goto Github PK

Description

Nextcloud is a resource monster. It is easy to deplete a node resource while continuous upload or download.

Note

Reference:

• Nexcloud doc - memory caching

Describe the bug

Currently you have renovate upgrading Flux individual docker images, this way is not the proper way to upgrade Flux according to their docs. This is because their manifests include more than just image upgrades on version changes.

For me I found it useful to create a Github workflow to upgrade flux.

This issue contains a list of Renovate updates and their statuses.

Other Branches

These updates are pending. To force PRs open, check the box below.

• (bot) Update renovatebot/github-action action to v25.76.1
• (bot) Update actions/checkout action to v3
• (bot) Update peter-evans/create-pull-request action to v4
• (bot) Update renovatebot/github-action action to v32

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• (bot) Update Helm release drone-runner-kube to v0.1.8
• (bot) Update Helm release redis-operator to v0.10.3
• (bot) Update Helm release thanos to v0.4.6
• (bot) Update nextcloud Docker tag to v22.2.9
• (bot) Update precommit hook k8s-at-home/sops-pre-commit to v2.1.1
• (bot) Update precommit hook zricethezav/gitleaks to v8.8.8
• (bot) Update quay.io/ceph/ceph Docker tag to v16.2.9
• (bot) Update Helm release cert-manager to v1.8.2
• (bot) Update Helm release drone to v0.3.0
• (bot) Update Helm release external-dns to v1.9.0
• (bot) Update Helm release grafana to v6.31.1
• (bot) Update Helm release ingress-nginx to v4.1.4
• (bot) Update Helm release kube-prometheus-stack to v16.15.0
• (bot) Update Helm release kured to v2.15.0
• (bot) Update Helm release mealie to v4.2.2
• (bot) Update Helm release navidrome to v6.3.2
• (bot) Update Helm release nextcloud to v2.14.6
• (bot) Update Helm release qbittorrent to v13.4.3
• (bot) Update Helm release rook-ceph to v1.9.6
• (bot) Update Helm release vaultwarden to v4.2.3
• (bot) Update Helm release velero to v2.30.0
• (bot) Update Terraform cloudflare to ~> 3.17.0
• (bot) Update Terraform hashicorp/terraform to ~> 1.2.0
• (bot) Update Terraform sops to ~>0.7.0
• (bot) Update dependency kubernetes-csi/external-snapshotter to v4.2.1
• (bot) Update postgres Docker tag to v13.7
• (bot) Update raspbernetes/velero-csi-plugin Docker tag to v0.2.0
• (bot) Update velero/velero-plugin-for-aws Docker tag to v1.5.0
• (bot) Update Helm release kube-prometheus-stack to v36
• (bot) Update Helm release mealie to v5
• (bot) Update dependency kubernetes-csi/external-snapshotter to v6
• (bot) Update nextcloud Docker tag to v24
• (bot) Update postgres Docker tag to v14
• (bot) Update quay.io/ceph/ceph Docker tag to v17
• (bot) Update quay.io/opstree/redis-exporter Docker tag to v2
• Check this option to rebase all the above open PRs at once

Yea, timtorchen is toooooo long, just timtor.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: .github/renovate.json5
Error type: The renovate configuration file contains some invalid settings
Message: Regex Managers must contain depNameTemplate configuration or regex group named depName

This issue contains a list of Renovate updates and their statuses.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update Helm release bitwardenrs to v2.1.5
• Update Helm release cert-manager to v1.3.0
• Update Helm release external-dns to v4.10.0
• Update Helm release grafana to v6.7.3
• Update Helm release ingress-nginx to v3.29.0
• Update Helm release jellyfin to v5.2.1
• Update Helm release kube-prometheus-stack to v14.6.2
• Update Helm release kured to v2.4.2
• Update Helm release minio to v8.0.10
• Update Helm release nextcloud to v2.6.1
• Update Helm release jellyfin to v7
• Check this option to rebase all the above open PRs at once

Helmfile is a little bit messy while configuration growing big.
I find most of k8s-at-home community members choose flux2, just feel a little bit lonely (?).
I will do some test and consider if it is better change into flux2 or other tools 🤔

Description

Like https://github.com/timtorChen/lab-infra/issues/1, I think keep project in muti-repo and find a central place for k8s manifests would better reduce some copy and paste.

Packing list

• cluster manifests
• grafana dashboards
• github actions
• update README
• transfer issues

Description

Current renovate-bot cannot recognize GitRepository tag, and sometimes I may forget update the tag while update the helmrelease. It will be nice if GitRepository tag is included in renovate PR.