Kubernetes YAML Generator

Generate Kubernetes YAML for Argo Workflows: executor ServiceAccount and RBAC, artifact repository ConfigMaps, namespaces with quotas, Deployments, Jobs, Secrets and PVCs.. Free, no sign-up, and everything runs privately in your browser.

How to use the Kubernetes YAML generator

  1. Choose a resource bundle — for example the Argo executor ServiceAccount and RBAC.
  2. Fill in the fields; names are converted to valid Kubernetes names automatically.
  3. Review the generated multi-document YAML on the right.
  4. Copy or download it and apply with kubectl apply -f.

Resource

Generated YAML

Resources Argo Workflows actually needs

Most Argo Workflows problems in the first week are Kubernetes problems: a missing role, a missing bucket configuration or a namespace without limits. This generator focuses on the objects that surround a working installation rather than generic boilerplate. The ServiceAccount + RBAC bundle creates the minimal executor permission — create and patch on workflowtaskresults — that workflow pods need to report outputs, with optional extras for resource templates that launch Jobs.

Artifact repositories

The artifact repository bundle generates an artifact-repositories ConfigMap with a default key for S3, MinIO, Google Cloud Storage or Azure Blob Storage. With workload identity selected, no static keys are referenced; otherwise the ConfigMap points at a Secret you create separately. Reference a non-default key from a workflow with artifactRepositoryRef.

Secure defaults

  • Deployments include resource requests, a memory limit, probes and a restricted security context.
  • Namespaces can enforce the restricted Pod Security Standard and get a ResourceQuota.
  • Secrets use stringData so values are readable before Kubernetes encodes them — never commit real secrets to Git.

Frequently asked questions

How do I apply several documents at once?

Save the output to one file and run kubectl apply -f file.yaml; Kubernetes processes each document separated by ---.

Do I need cluster-admin?

Creating Roles and RoleBindings requires permission to manage RBAC in the namespace. Namespaces and quotas usually need cluster-level rights.

Can I use these with Helm?

Yes. Paste the output into a chart’s templates/ folder and replace values with Helm expressions.

More free tools