3897bcbf24
Some checks failed
CLI Tests / test-cli (push) Failing after 4s
Deploy to Testnet / deploy-testnet (push) Successful in 1m40s
Documentation Validation / validate-docs (push) Failing after 12s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Integration Tests / test-service-integration (push) Successful in 2m42s
Package Tests / Python package - aitbc-agent-sdk (push) Failing after 34s
Package Tests / Python package - aitbc-core (push) Successful in 27s
Package Tests / Python package - aitbc-crypto (push) Successful in 13s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 8s
Package Tests / JavaScript package - aitbc-token (push) Successful in 18s
Python Tests / test-python (push) Failing after 50s
Security Scanning / security-scan (push) Failing after 43s
Multi-Node Stress Testing / stress-test (push) Successful in 12s
Cross-Node Transaction Testing / transaction-test (push) Successful in 9s
- Created aitbc/_version.py with centralized version definition - Updated aitbc/__init__.py to import __version__ from _version module - Updated constants.py to use __version__ for PACKAGE_VERSION - Replaced print() calls with logger in decorators.py, events.py, queue_manager.py, and state.py - Added logger initialization using get_logger(__name__) in config.py, decorators.py, events.py, queue_manager.py, and state.py - Added cli/commands
Kubernetes Example Manifests
This directory contains reference Kubernetes manifests for AITBC infrastructure components.
Purpose
These manifests are provided as reference implementations and examples for Kubernetes deployment. They are not production-ready deployment specifications for the core AITBC services.
Current Manifests
backup-configmap.yaml- Configuration for backup operationsbackup-cronjob.yaml- CronJob for automated backupscert-manager.yaml- Cert-manager configuration for TLS certificatesdefault-deny-netpol.yaml- Default deny network policy for securitysealed-secrets.yaml- Sealed Secrets configuration for secret management
Production Deployment
AITBC currently uses systemd-based orchestration for production deployments. See docs/testing/e2e-test-plan.md for systemd-based service orchestration details.
Usage
To use these examples in a Kubernetes environment:
- Review and customize the manifests for your environment
- Apply the manifests:
kubectl apply -f <manifest>.yaml - Modify as needed for your specific Kubernetes setup
Future Work
These manifests may be expanded to include full deployment specifications for core services (blockchain-node, coordinator-api, exchange) if Kubernetes deployment becomes a priority.