Operations & Deploy
FQDNs
Container Images
| App | Image |
|---|---|
| Backend | registry.digiwedge.com/digiwedge/access-control-backend:<tag> |
| Admin SPA | registry.digiwedge.com/digiwedge/access-control-admin:<tag> |
| Docs Public | registry.digiwedge.com/digiwedge/access-control-docs-public:<tag> |
| Docs Internal | registry.digiwedge.com/digiwedge/access-control-docs-internal:<tag> |
Tags: use both :latest and :<git-sha>; Argo Image Updater can track digests and bump manifests automatically.
Kubernetes Manifests
- Docs:
kubernetes/access-control/docs/*(deployment, service, certificates) - Admin SPA:
kubernetes/access-control/frontend/*(deployment, service, env Secret) - Backend:
kubernetes/access-control/backend/*
Argo CD
- Docs Application:
kubernetes/access-control/docs/access-control-docs-argo.yaml(GitOps; Image Updater annotations included) - Admin Application:
kubernetes/access-control/frontend/access-control-admin-argo.yaml(configured for commit-sha tags)
Rollouts & Secret Rotation
Rollout restart after image push:
kubectl -n access-control rollout restart deploy/access-control-docs-public
kubectl -n access-control rollout status deploy/access-control-docs-public
kubectl -n access-control rollout restart deploy/access-control-docs-internal
kubectl -n access-control rollout status deploy/access-control-docs-internal
Legacy ingress basic-auth (if still used): Secret access-control-docs-basicauth (key users with htpasswd entries).