unrip/deploy/k8s/base/bootstrap-job.yaml
philipp 41b9ec680b
Some checks failed
deploy / deploy (push) Failing after 1m35s
Implement funded NEAR Intents trade loop
Proof: first non-mocked tradeable loop for one pair using funded NEAR Intents inventory, Kafka, and PostgreSQL.

Assumptions: solver-side execution is performed by signed token_diff quote responses over the Solver Relay; EURe is treated as 1:1 with EUR; k3s runtime uses unrip-dev.near as the named signer account.

Still fake: signer key is not yet registered on intents.near, strategy and executor remain disarmed by default, and no live mainnet quote response has been submitted from this repo yet.
2026-04-02 10:01:15 +02:00

42 lines
1.6 KiB
YAML

apiVersion: batch/v1
kind: Job
metadata:
name: redpanda-topic-bootstrap
namespace: unrip
spec:
backoffLimit: 6
template:
spec:
restartPolicy: OnFailure
containers:
- name: bootstrap-topics
image: docker.redpanda.com/redpandadata/redpanda:v24.3.9
command: ["/bin/sh", "-lc"]
args:
- |
set -eu
BROKERS="redpanda.unrip.svc.cluster.local:9092"
TOPICS="raw.near_intents.quote norm.swap_demand ref.market_price state.intent_inventory ops.liquidity_action decision.trade_decision cmd.execute_trade exec.trade_result"
RETENTION_MS="172800000"
RETENTION_BYTES="268435456"
echo "waiting for Redpanda at ${BROKERS}"
until rpk cluster info --brokers "$BROKERS" >/dev/null 2>&1; do
sleep 2
done
for topic in $TOPICS; do
if rpk topic describe "$topic" --brokers "$BROKERS" >/dev/null 2>&1; then
echo "ensuring retention config for existing topic: $topic"
rpk topic alter-config "$topic" --brokers "$BROKERS" \
--set retention.ms="$RETENTION_MS" \
--set retention.bytes="$RETENTION_BYTES"
continue
fi
echo "creating topic with bounded retention: $topic"
rpk topic create --brokers "$BROKERS" --partitions 1 --replicas 1 \
-c retention.ms="$RETENTION_MS" \
-c retention.bytes="$RETENTION_BYTES" \
"$topic"
done