Create definition for application spec

[wolf31o2]

This covers the "application spec" in all of its forms.

• [ ] Repository information

  • [ ] Type (github/gitlab)
  • [ ] Owner / Repo
  • [ ] Branch

• [ ] Build / Deploy information

  • [ ] Command / Target path / root path / Development Command
  • [ ] Commit Ref
  • [ ] Environment variables

Logic splits:

• API definition
• Build definition
• Runtime definition
• Kubernetes Operator CRD

[scarmuega]

as an extra data point, this is an example custom resource that we use right now for Demeter frontends:

apiVersion: demeter.run/v1alpha1
kind: Frontend
metadata:
  generation: 1
  labels:
    demeter.run/kind: workload.v0
    demeter.run/slug: frontends
  name: aquarian-category-o2366w
spec:
  annotations:
    cardano.demeter.run/network: preview
  args: ""
  command: ""
  computeClass: gp1.x86.nano
  config: []
  enabled: true
  envVars: []
  givenName: TXPipe Website
  image: mydapp:v1
  replicas: 2
status:
  availableReplicas: 2
  computeDCUPerMin: 308
  observedGeneration: 1
  runningStatus: running
  startTime: 1698074168307
  storageDCUPerMin: 0

[scarmuega]

think of how multiple subdomains will work in a single namespace

[scarmuega]

for long term, discuss how to enable taints / affinity by region / provider