Skip to main content

Platform Repository Anatomy

The .platform repository contains Kustomize references for your application per environment, it has this structure:

kubernetes
├── demo-http-echo
│   └── dev
│       └── kustomization.yaml
└── example-service
    ├── dev
    │   └── kustomization.yaml
    └── stg
        └── kustomization.yaml

The .platform repository is managed by automation, and you will not need to manually edit it.

The kustomization.yaml files reference the corresponding overlays in the application repository's .platform folder. There are two variations depending on how you manage your container images with Ybor.

Self-Managed Image​

If you are empowering your Kubernetes deployments with Ybor, but building and storing your container images yourself, the .platform kustomization will look like this:

# kubernetes/demo-http-echo/dev/kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- https://github.com/ybor-studio/demo-http-echo/.platform/kubernetes/dev
commonAnnotations:
  meta.p6m.dev/github-repository: demo/demo-http-echo
  meta.p6m.dev/last-updated: "1769539829"

Ybor Hosted Image​

If you have integrated your application's build and publish process with Ybor, the .platform kustomization will include the image details:

# kubernetes/example-service/dev/kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- https://github.com/ybor-studio/example-service/.platform/kubernetes/dev
images:
- digest: sha256:38cd15c7712185dcffdd8665c517f4c0d8b0713f008b5434f9e8f2b3eec70f98
  name: example-service-server
  newName: ybor-private-registry.io/applications/example-service-server
commonAnnotations:
  meta.p6m.dev/github-repository: ybor-studio/example-service
  meta.p6m.dev/last-updated: "1769541701"

What's Next​

For more information on how ArgoCD deploys from the .platform repository, check out the ArgoCD Deployments Overview.