registry.k8s.io VS systemd

If you stop to think about, what AWS is selling here, it's quite funny. Most of the infrastructure behind registry.k8s.io is hosted on AWS (and also GCP). So AWS essentially tells you: Don't trust the upstream registry, it might go down, cache it on your own registry, hosted also by us.

For example: if you only allow cluster autoscaler and metrics server from registry.k8s.io you can pull those images through the cache as someone who has create repo IAM privileges. If someone without create repo privileges tries to pull a new image it will fail because they can't create the initial repo.

https://registry.k8s.io (the root url at /) redirects you to https://github.com/kubernetes/registry.k8s.io where we have an issue tracker.

❗ This container is having trouble accessing https://registry.k8s.io

Hosting a forwarding / redirect server instead of actually hosting images is probably a decent idea.

The K8s proxy is redirecting from only hosting on GCR to community-owned registries - https://kubernetes.io/blog/2023/03/10/image-registry-redirec...

You can view the code here - https://github.com/kubernetes/registry.k8s.io

But because everyone is already pointing at gcr.io (just like many openfaas users point at docker.io/) - they're having to do a huge campaign to announce the new URL - the same would apply with the author's solution here.

I wrote some automation for hosting (not redirects) in arkade with the OSS registry - Get a TLS-enabled Docker registry in 5 minutes - https://blog.alexellis.io/get-a-tls-enabled-docker-registry-...

The registry is also something you can run on a VM if you so wish, and have act as a pull through cache.

Apart from reliability - GitHub's container registry is the current next best option - but we have to ask ourselves, what happens when they start charging or the outages start to last longer or are more frequent than 1-2 times per week as we've seen in Q1 2023.

One annoyance with how docker images are specified is they include the location where they are stored. So if you want to change where you store you image you break everyone.

I wonder if what regsitry.k8s.io does could be generalized:

https://github.com/kubernetes/registry.k8s.io/blob/main/cmd/...

The idea is the depending on which cloud you are pulling the image from, they will use the closest blob store to service the request. This also has the effect that you could change the source of truth for the registry without breaking all Dockerfiles.

If you are using updated helm charts then most of them have already replaced with registry.k8s.io, for example nginx ingress so not really breaking change.

Retrieve the archive containing the JBoss Web Server from the Red Hat Customer Portal and install the files on the system. Configure the Red Hat Enterprise Linux (RHEL) operating system including the users, groups, and the required setup files to enable JBoss Web Server as a systemd service. Ensure the required Java Virtual Machine is installed Fine-tune the configuration of the JBoss Web Server server, such as binding it to the appropriate interface and port. Deploy web applications along with enabling and starting the JBoss Web Server as a [systemd](https://www.freedesktop.org/wiki/Software/systemd/) service. Perform a health check to ensure that the deployed application is accessible.

A systemd-free fork from Debian Linux+GNU

Devuan is a fork of Debian GNU+Linux without systemd.

This post shows how to install and run Docker on Devuan, a systemd-free fork of Debian.

I built the dev env on Devuan GNU+Linux, a fork of Debian without systemd. It resembles my past trial on Artix Linux.

Devuan GNU+Linux is a fork of Debian without systemd and hence Snaps (Snapd). Even on it, it's easy to install Android Studio and start to develop Android mobile apps.

[root@rocky-8-lxc ~]# rpm -qf /etc/rc.d/rc.local systemd-239-68.el8_7.4.x86_64 [root@rocky-8-lxc ~]# rpm -qi systemd Name : systemd Version : 239 Release : 68.el8_7.4 Architecture: x86_64 Install Date: Fri 07 Apr 2023 02:11:42 AM UTC Group : Unspecified Size : 11306123 License : LGPLv2+ and MIT and GPLv2+ Signature : RSA/SHA256, Tue 21 Feb 2023 05:04:34 PM UTC, Key ID 15af5dac6d745a60 Source RPM : systemd-239-68.el8_7.4.src.rpm Build Date : Tue 21 Feb 2023 04:52:49 PM UTC Build Host : ord1-prod-x86build004.svc.aws.rockylinux.org Relocations : (not relocatable) Packager : [email protected] Vendor : Rocky URL : http://www.freedesktop.org/wiki/Software/systemd Summary : System and Service Manager Description : systemd is a system and service manager that runs as PID 1 and starts the rest of the system. It provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux control groups, maintains mount and automount points, and implements an elaborate transactional dependency-based service control logic. systemd supports SysV and LSB init scripts and works as a replacement for sysvinit. Other parts of this package are a logging daemon, utilities to control basic system configuration like the hostname, date, locale, maintain a list of logged-in users, system accounts, runtime directories and settings, and daemons to manage simple network configuration, network time synchronization, log forwarding, and name resolution.