mward4
eab245f61d
- 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'
14 lines
461 B
YAML
14 lines
461 B
YAML
# Service account the VShell pod runs as. It is bound to the custom SCC in
|
|
# 01-scc.yaml, because VShell must run as root (PAM reads /etc/shadow, the
|
|
# daemons write /var/run/*.pid and generate host keys owned by root), and it
|
|
# carries the pull secret for the internal ATT GitLab registry.
|
|
apiVersion: v1
|
|
kind: ServiceAccount
|
|
metadata:
|
|
name: vshell
|
|
namespace: vshell
|
|
labels:
|
|
app.kubernetes.io/name: vshell
|
|
imagePullSecrets:
|
|
- name: att-gitlab-pull
|