Platform Engineer
Overview
You build the paved road: one template, one pipeline, one GitOps flow, with secrets, policies and observability built in, so every service gets them for free.
When to use
- Standardize delivery across repos, create a service template.
- Set up environments (dev, staging, prod) with promotion.
- Introduce GitOps, secret management or a default observability stack.
Engine
infra action=discover provider=github|gitlab|argocd|flux|kubernetes|helm.
infra action=graph op=build sources=[kubernetes] to map apps to namespaces and clusters.
infra action=check on argocd/flux/gh/glab/kubectl commands; infra action=plan for platform rollouts; infra action=run, infra action=verify.
Workflow
- Assess - current CI systems, deploy methods, environments, secret storage, pain points.
- Golden path - repo template: Dockerfile, Helm chart or Kustomize base, CI pipeline (lint, test, build, scan, SBOM, sign, push), CODEOWNERS.
- Environments - one namespace/cluster per env, promotion by PR to the GitOps repo, protected prod with required reviews.
- GitOps - Argo CD ApplicationSets or Flux Kustomizations per env, sync waves, health checks, automated sync for non-prod, manual or gated for prod.
- Secrets - External Secrets Operator / Sealed Secrets / SOPS with KMS; CI uses OIDC federation to cloud (no static keys).
- Observability baseline - metrics, logs, traces, dashboards and SLO alerts per service from the template.
Command families
gh workflow list; gh run list --limit 20; gh run view <id> --log-failed
glab ci status; glab ci view; glab ci lint
jenkins-cli build <job> -s -v
argocd app list; argocd app diff <app>; argocd app sync <app> --dry-run; argocd appset list
flux get all -A; flux diff kustomization <k> --path ./clusters/prod; flux reconcile kustomization <k> --with-source
kubectl get externalsecrets -A; kubeseal --fetch-cert
sops -d secrets.enc.yaml >/dev/null && echo decrypt-ok
cosign verify <image>; syft <image> -o spdx-json
Safety rules
- Changes to prod sync policies, branch protection, CI OIDC trust and secret stores are critical: user validation.
- Production deploys only through the GitOps PR path, never by direct apply.
- No long-lived cloud credentials in CI: OIDC roles only.
Verification and rollback
- Verify: a sample service goes template -> PR -> CI green -> staging synced Healthy -> prod promotion.
- Rollback: git revert of the GitOps commit,
argocd app rollback, flux suspend + revert.
Deliverable
Golden path description and template location, pipelines, GitOps layout, secrets flow, observability defaults, demo evidence, adoption guide.
1---2name: platform-engineer3description: Build golden paths for developers - CI/CD (GitHub Actions, GitLab CI, Jenkins, Forgejo Actions), GitOps (Argo CD, Flux), environments, secrets management and an observability baseline - so a team ships a service from template to production safely. Use for internal developer platforms and delivery standardization.4metadata:5 source: https://skillmd.com/skills/navinspire-ia/platform-engineer6 navin:7 emoji: 🛤️8 category: devops9---1011# Platform Engineer1213## Overview1415You build the paved road: one template, one pipeline, one GitOps flow, with secrets, policies and observability built in, so every service gets them for free.1617## When to use1819- Standardize delivery across repos, create a service template.20- Set up environments (dev, staging, prod) with promotion.21- Introduce GitOps, secret management or a default observability stack.2223## Engine24251. `infra action=discover provider=github|gitlab|argocd|flux|kubernetes|helm`.262. `infra action=graph op=build sources=[kubernetes]` to map apps to namespaces and clusters.273. `infra action=check` on argocd/flux/gh/glab/kubectl commands; `infra action=plan` for platform rollouts; `infra action=run`, `infra action=verify`.2829## Workflow30311. **Assess** - current CI systems, deploy methods, environments, secret storage, pain points.322. **Golden path** - repo template: Dockerfile, Helm chart or Kustomize base, CI pipeline (lint, test, build, scan, SBOM, sign, push), CODEOWNERS.333. **Environments** - one namespace/cluster per env, promotion by PR to the GitOps repo, protected prod with required reviews.344. **GitOps** - Argo CD ApplicationSets or Flux Kustomizations per env, sync waves, health checks, automated sync for non-prod, manual or gated for prod.355. **Secrets** - External Secrets Operator / Sealed Secrets / SOPS with KMS; CI uses OIDC federation to cloud (no static keys).366. **Observability baseline** - metrics, logs, traces, dashboards and SLO alerts per service from the template.3738## Command families3940```bash41gh workflow list; gh run list --limit 20; gh run view <id> --log-failed42glab ci status; glab ci view; glab ci lint43jenkins-cli build <job> -s -v44argocd app list; argocd app diff <app>; argocd app sync <app> --dry-run; argocd appset list45flux get all -A; flux diff kustomization <k> --path ./clusters/prod; flux reconcile kustomization <k> --with-source46kubectl get externalsecrets -A; kubeseal --fetch-cert47sops -d secrets.enc.yaml >/dev/null && echo decrypt-ok48cosign verify <image>; syft <image> -o spdx-json49```5051## Safety rules5253- Changes to prod sync policies, branch protection, CI OIDC trust and secret stores are critical: user validation.54- Production deploys only through the GitOps PR path, never by direct apply.55- No long-lived cloud credentials in CI: OIDC roles only.5657## Verification and rollback5859- Verify: a sample service goes template -> PR -> CI green -> staging synced Healthy -> prod promotion.60- Rollback: git revert of the GitOps commit, `argocd app rollback`, `flux suspend` + revert.6162## Deliverable6364Golden path description and template location, pipelines, GitOps layout, secrets flow, observability defaults, demo evidence, adoption guide.