Files
vshell/openshift/runtime/06-att-gitlab-pull-secret.yaml
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

25 lines
906 B
YAML

# Credentials for the internal ATT GitLab container registry.
#
# Create it with your own GitLab credentials (deploy token, PAT with read_registry,
# or a robot account) - do not commit them:
#
# oc create secret docker-registry att-gitlab-pull -n vshell \
# --docker-server=att-gitlab.apps.evd.geaerospace.net:5050 \
# --docker-username=<user> \
# --docker-password=<token>
#
# Already referenced by runtime/00-serviceaccount.yaml and runtime/03-deployment.yaml,
# so nothing else needs to be linked.
apiVersion: v1
kind: Secret
metadata:
name: att-gitlab-pull
namespace: vshell
labels:
app.kubernetes.io/name: vshell
app.kubernetes.io/component: registry-auth
type: kubernetes.io/dockerconfigjson
stringData:
.dockerconfigjson: |
{"auths":{"att-gitlab.apps.evd.geaerospace.net:5050":{"username":"REPLACE","password":"REPLACE","auth":"REPLACE_BASE64_USER_COLON_TOKEN"}}}