Profiles describe demand. Platforms decide fulfillment.

Demand in a complete profile

apiVersion: runtimeconditions.io/v1alpha1
kind: RuntimeConditionsProfile

metadata:
  name: request-logger-http

workload:
  uri: github.com/example/request-logger-http
  version: v0.1.0

extensions:
  - https://runtimeconditions.io/extensions/common-integrations:v1alpha1
  - https://runtimeconditions.io/extensions/env-configuration:v1alpha1

conditions:
  - name: request-cache
    kind: cache
    interface:
      type: key_value
      engine: redis
    configuration:
      alternatives:
        - env:
            - property: url
              name: REDIS_URL
        - env:
            - property: hostname
              name: REDIS_HOST
            - property: port
              name: REDIS_PORT

Fulfillment outside the profile

The previous profile only says the workload needs a Redis-compatible cache and can consume it through REDIS_URL or REDIS_HOST plus REDIS_PORT. Before Kubernetes can inject REDIS_URL, an adapter has to satisfy that Condition by provisioning Redis or granting access to an existing Redis cache.

1. 1
   Profile Declares kind: cache, engine: redis, and acceptable env vars.
2. 2
   Adapter Chooses how this platform can satisfy the cache Condition.
3. 3
   Provider Creates Redis or grants access to an existing Redis instance.
4. 4
   Connection Output Publishes url, hostname, and port through platform artifacts.
5. 5
   Deployment Receives the env var names declared by the workload profile.

In the Kratix demo, the Redis Promise is the provider interface. It publishes a concrete connection ConfigMap. The adapter then binds the profile's REDIS_URL request to that ConfigMap in the generated Deployment.

apiVersion: v1
kind: ConfigMap
metadata:
  name: request-logger-cache-connection
  namespace: demo
data:
  url: redis://request-logger-cache.demo.svc.cluster.local:6379
  hostname: request-logger-cache.demo.svc.cluster.local
  port: "6379"

apiVersion: apps/v1
kind: Deployment
metadata:
  name: request-logger-http
  namespace: demo
spec:
  # ...
  template:
    spec:
      containers:
        - name: request-logger-http
          # ...
          env:
            - name: REDIS_URL
              valueFrom:
                configMapKeyRef:
                  name: request-logger-cache-connection
                  key: url

This snippet belongs in the generated Kubernetes Deployment. It is not part of the Runtime Conditions Profile. It is the result of the adapter satisfying the profile against a concrete platform.

Vocabulary

What never belongs in the profile

• Secret valuesAccess keys, tokens, passwords, and private material stay out.
• Target choicesBucket names, service names, cloud accounts, and cluster topology stay out.
• Provisioning instructionsThe profile declares requirements. Adapters and platforms provision or bind resources.