mward4
eab245f61d
OpenShift: pull runtime image from the internal ATT GitLab registry
...
- runtime/03-deployment.yaml: image is now
att-gitlab.apps.evd.geaerospace.net:5050/att/infrastructure/vshell:latest with
imagePullSecrets; the internal ImageStream trigger is gone
- runtime/00-serviceaccount.yaml: carries att-gitlab-pull
- runtime/06-att-gitlab-pull-secret.yaml: registry credentials (placeholders)
- cluster/00-insecure-registry.yaml: Image/cluster insecureRegistries entry, the
cluster-side equivalent of 'podman pull -k'
- 02/03 build manifests marked optional, with the GitLab push-output variant
documented inline
- openshift/README.md split into run-from-registry and build-in-cluster paths
- all 14 manifests decode cleanly with 'oc create --dry-run=client'
2026-10-05 14:24:29 -04:00
mward4
9dbe3749ba
Add OpenShift manifests for in-cluster build and runtime
...
- build chain: project, Gitea basic-auth source secret, output ImageStream,
BuildConfig (Docker strategy, ubuntu:24.04 base), optional base-image
ImageStream and Docker Hub pull secret
- runtime: ServiceAccount + least-privilege SCC and its RoleBinding (VShell
needs UID 0), PVC for config/certificate, Deployment with ImageStream
trigger, ClusterIP Service, passthrough HTTPS Route
- all manifests verified with 'oc create --dry-run=client' against the
OpenShift 4.22 client scheme (12/12 decode cleanly)
2026-10-05 13:25:10 -04:00
mward4
a6f8e67976
VShell 5.0.1-3985 container image
...
Build the image from the vendor vshell-https .deb on ubuntu:24.04 (required:
GLIBC_2.38 / GLIBCXX_3.4.32). Contains the Dockerfile, the entrypoint that
starts and supervises the three VShell daemons without systemd, the
no-container-runtime build/validate/push tooling used to publish the image, and
the vendored .deb (sha256 pinned).
Published as gitea.milesward.dev/mward4/vshell:5.0.1-3985 and :latest.
Manifest digest sha256:8b0ff00be981fa05f1e4a4e4ff5307b6c7e5e61b487d4fbe7e02fefb2a04659f.
2026-10-05 12:15:20 -04:00
mward4