-/usr/sbin/initnone-
As I do not want a complex sed query to check for systemd or not, let's
solve it in init_pod.sh and express it in CI_CONTEXT variable.

/shared/rc.local in case I loose my devbox.

out if we are using systemd or not. We just need to check
/proc/1/cmdline to get the command that started the container.
Now to chose between systemd and no systemd we just need to set
`command` key in the pod yaml definition for nosystemd or remove the
line to use systemd.
Much more straightforward...

If CI passes...

This reverts commit 421c6d14.

This version of EOS appears to work on my local dev box but not
in the CI.

Now copies keytab between pods and changes ownership/permissions atomically

CTA_StorageClass was hard coded. In this version it is read from the
extended attribute.

The workflow now includes the endpoint, which includes the Kubernetes namespace that the pod is
running in.

cta-cli.sss.keytab is deprecated. CTA Frontend now uses
/etc/cta/eos.sss.keytab, which should contain one SSS key per EOS
instance (only one in the case of CI).

This version of eos-server includes the WFE implementation for CLOSEW
(default and CTA_Archived), ARCHIVED, PREPARE and DELETE. The bash
scripts are no longer necessary.

removing replace-str option as -L just concatenates args after the replace-str place holder. toto is not a valid rados object which prevents the objectstore cleanup.