feat: add Knative integration for notifications

- Add CloudEvents sink deployment for eoapi-notifier integration
- Configure dynamic secret name for PostgreSQL connection
- Add local development configuration with reduced resources
- Support both CI and local test environments

Author: pantierra

.github/workflows/ci.yml

@@ -1,4 +1,4 @@
-name: CI
+name: CI tests
 
 on:
   push:
@@ -11,7 +11,7 @@ env:
   PGO_VERSION: 5.7.4
 
 jobs:
-  validate:
+  lint:
     name: Lint checks
     runs-on: ubuntu-latest
     steps:
@@ -37,3 +37,108 @@ jobs:
 
       - name: Validate Helm values schema
         run: make validate-schema
+
+  helm-unit-tests:
+    name: Helm Unit Tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Install Helm
+        uses: azure/setup-helm@v4
+        with:
+          version: ${{ env.HELM_VERSION }}
+
+      - name: Run Helm unit tests
+        run: make tests
+
+      - name: Run lint checks
+        run: make lint
+
+      - name: Validate Helm schemas
+        run: make validate-schema
+
+  integration-tests:
+    name: Integration Tests (K3s)
+    if: github.event.pull_request.head.repo.full_name == github.repository
+    permissions:
+      contents: 'read'
+      id-token: 'write'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Wait for Helm tests to pass
+        uses: lewagon/[email protected]
+        if: github.event_name == 'pull_request'
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+          check-name: 'Helm Unit Tests'
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          wait-interval: 30
+
+      - name: Start K3s cluster
+        uses: jupyterhub/action-k3s-helm@v4
+        with:
+          k3s-channel: latest
+          helm-version: ${{ env.HELM_VERSION }}
+          metrics-enabled: false
+          docker-enabled: true
+
+      - name: Set release name
+        run: echo "RELEASE_NAME=eoapi-$(echo "${{ github.sha }}" | cut -c1-8)" >> "$GITHUB_ENV"
+
+      - name: Wait for K3s readiness
+        run: |
+          echo "=== Waiting for K3s cluster to be ready ==="
+
+          # The action already sets up kubectl context, just verify it works
+          kubectl cluster-info
+          kubectl get nodes
+
+          # Wait for core components
+          kubectl wait --for=condition=Ready pod -l k8s-app=kube-dns -n kube-system --timeout=300s
+          kubectl wait --for=condition=Ready pod -l app.kubernetes.io/name=traefik -n kube-system --timeout=300s
+
+          # Verify Traefik CRDs
+          timeout=300; counter=0
+          for crd in "middlewares.traefik.io" "ingressroutes.traefik.io"; do
+            while [ $counter -lt $timeout ] && ! kubectl get crd "$crd" &>/dev/null; do
+              sleep 3; counter=$((counter + 3))
+            done
+            [ $counter -ge $timeout ] && { echo "❌ Timeout waiting for $crd"; exit 1; }
+          done
+
+          echo "✅ K3s cluster ready"
+
+      - name: Deploy eoAPI
+        id: deploy
+        run: |
+          echo "=== eoAPI Deployment ==="
+          export RELEASE_NAME="${RELEASE_NAME}"
+          export PGO_VERSION="${{ env.PGO_VERSION }}"
+          export CI_MODE=true
+
+          # Deploy using consolidated script with CI mode
+          ./scripts/deploy.sh --ci
+
+      - name: Validate deployment
+        run: |
+          echo "=== Post-deployment validation ==="
+          ./scripts/test.sh check-deployment
+
+      - name: Run integration tests
+        run: |
+          export RELEASE_NAME="$RELEASE_NAME"
+          ./scripts/test.sh integration --debug
+
+      - name: Debug failed deployment
+        if: failure()
+        run: |
+          ./scripts/debug-deployment.sh
+
+      - name: Cleanup
+        if: always()
+        run: |
+          helm uninstall "$RELEASE_NAME" -n eoapi || true
+          kubectl delete namespace eoapi || true

.github/workflows/helm-tests.yml

@@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Added local testing with k3s and minikube
 - Base local development values file (`local-base-values.yaml`)
 - Unified local cluster management with `CLUSTER_TYPE` variable
+- Added knative in CI to test eoapi-notifier.
 
 ## [0.7.12] - 2025-10-17
 

CHANGELOG.md

@@ -57,3 +57,7 @@ dependencies:
     version: 0.0.8
     repository: "oci://ghcr.io/developmentseed/charts"
     condition: eoapi-notifier.enabled
+  - name: knative-operator
+    version: 1.17.8
+    repository: https://knative.github.io/operator
+    condition: knative.enabled

charts/eoapi/Chart.yaml

@@ -7,3 +7,65 @@ ingress:
   className: "traefik"
   annotations:
     traefik.ingress.kubernetes.io/router.entrypoints: web
+
+# Knative components for CloudEvents
+knative:
+  enabled: true
+  cloudEventsSink:
+    enabled: true
+
+# eoapi-notifier configuration with CloudEvents output
+eoapi-notifier:
+  enabled: true
+  waitForKnativeCRDs: true
+  config:
+    logLevel: DEBUG
+    sources:
+      - type: pgstac
+        config:
+          channel: pgstac_items_change
+          connection:
+            existingSecret:
+              name: ""  # Set dynamically by deploy script
+              keys:
+                username: "user"
+                password: "password"
+                host: "host"
+                port: "port"
+                database: "dbname"
+    outputs:
+      - type: cloudevents
+        config:
+          source: /eoapi/pgstac
+          event_type: org.eoapi.stac.item
+          destination:
+            ref:
+              apiVersion: serving.knative.dev/v1
+              kind: Service
+              name: eoapi-cloudevents-sink
+  resources:
+    requests:
+      cpu: "50m"
+      memory: "64Mi"
+    limits:
+      cpu: "200m"
+      memory: "128Mi"
+
+# Reduce PostgreSQL resources for local development
+postgrescluster:
+  instances:
+    - name: "postgres"
+      replicas: 1
+      dataVolumeClaimSpec:
+        accessModes:
+          - "ReadWriteOnce"
+        resources:
+          requests:
+            storage: "1Gi"
+      resources:
+        requests:
+          cpu: "100m"
+          memory: "512Mi"
+        limits:
+          cpu: "500m"
+          memory: "1Gi"