Nvidia 9, 10-series support is quite poor. Your experience at best will still be worse than AMD, Intel, or more modern Nvidia cards running the nvidia-open kernel modules with the latest Nvidia drivers.
jrgd
joined 5 months ago
I recently dug through a sampled list of UE5 games released on Steam. It is shocking how many have such poor reviews (often for reasons not beholden to the engine). Sifting through stuff, I did find a handful of games that didn't seem to have major performance, graphical flaws based on reviews and forum posts, though to note some of them also didn't seem to leverage much of UE5 technologies to begin with (Lumen, Nanite, etc.). Some games did seem to leverage UE5 tech still and have minimal to no complaints.
Sadly, a large portion of the released games I pulled from this list had referenced performance issues or otherwise major issues that tanked the Steam review score. I unfortunately didn't note down my findings for the handful that didn't, but if you want to look for yourself the list I searched from is linked.
Haven't played it myself, but based on watching gameplay and seeing community sentiment on the Steam forums and reviews, as well as from friends, it doesn't seem that the performance is quite perfect. Definitely better than most UE5 games currently released, but still has some problems. From the footage I have watched of the game, it definitely still looks like there is some moderate TAA ghosting as well. Does this hold true from gameplay?
Probably either wait for some other provider to build helm charts, roll your own k8s YAML for Redis based on the helm chart and with standard Redis OCI images, or migrate to a different, but compatible service like DragonflyDB if you don't need modern Redis features (not suggesting Valkey because they are also entrenched in Bitnami and offer it as the official chart source).
You're likely looking for this docs section for Caddy. The failure is the automated request to populate Caddy's root CA cert to the host system, but obviously failed as it doesn't have root permissions. As the docs state, if you intend to use the local HTTPS functionality of Caddy, you can manually run caddy trust privileged in order to populate the Caddy root CA cert manually. If you intend to disable the local HTTPS functionality (such as if you're running Caddy behind a http reverse proxy), you can ignore the mail message.
The main idea on a device running something like Graphene OS is that you are already in a state of using minimal, if not at all using Google Cloud services, including data backups. It's intended in tandem with modifications like GMS, GPS (if optionally installed into a given user, work profile) running as an unprivileged, permission-based application. If someone is taking their data privacy and security seriously enough to consider using a duress PIN and flashed their phone with something along the lines of Graphene OS, would they be likely to have heavy reliance to Google's Cloud offerings?
Certainly glad I had my suspicions of Bitnami rugpulling when constructing my Kubernetes cluster and preemptively stripped out as much as possible from helm charts that relied on anything Bitnami. This is going to suck for a lot of people and organizations given that images like rabbitmq, postgres, oauth2-proxy, minio among many others are affected.
It's not a full rugpull yet, but not being able to pin versions for the newer security-hardened images is already a huge issue for many pieces of software. Especially for things like not being able to pin to a major version of postgres will cause major problems over time for cluster admins and helm chart developers alike if they don't migrate to other solutions.
Who knows if (when) Bitnami decides to go further in restricting their images, charts from being free and open. I do wish in the future that more helm chart developers would know the caution that should be taken when trusting anything touched by Broadcom of all companies. Maybe this is the necessary warning sign for many.
Realistically, any LTS distro from a netinstaller or minimal image that can use a kiosk compositor like cage. So, the usual suspects of Debian, OpenSUSE, AlmaLinux, RockyLinux (or a derivative of one if the native distro doesn't support Raspberry Pi). Then you just have cage open the browser of choice on startup (e.g.
chromium --kiosk <url>) and you have a lightweight and relatively secure web kiosk.