docs: expand customer datasheet with Kubernetes architecture
This commit is contained in:
1 parent
6459109bcb
commit
da07d46341
3 files changed
+28
-2
No files matched your search
@@ -27,6 +27,33 @@ through a logical gateway to an approved local or customer-selected compatible
|
||||
inference provider. Kubernetes isolates services, applications and extensions.
|
||||
Prometheus, Alertmanager, Grafana, Loki and Alloy provide operational visibility.
|
||||
|
||||
## Kubernetes and background platform
|
||||
|
||||
Nexus One AI is packaged as a Kubernetes application platform. K3s provides the
|
||||
compact Kubernetes distribution for appliance and single-node deployments,
|
||||
while customer-specific enterprise designs can use an approved multi-node
|
||||
topology. Namespaces separate platform services, data, observability, developer
|
||||
workspaces, application previews and capability packs.
|
||||
|
||||
Stateless platform services run as Deployments. PostgreSQL, RabbitMQ and MinIO
|
||||
provide durable state, background-job transport and object storage. Services
|
||||
provide stable internal addresses; Ingress exposes only approved browser and API
|
||||
routes. ConfigMaps hold non-sensitive configuration and Secrets hold protected
|
||||
credentials. Jobs, CronJobs and persistent volumes support maintenance,
|
||||
scheduling, evidence and retained data.
|
||||
|
||||
Interactive requests enter through TLS ingress, pass identity and role policy,
|
||||
and reach the portal or Core API. Long-running work is recorded in PostgreSQL,
|
||||
queued through RabbitMQ, executed by workers, and stored as durable status and
|
||||
artifacts. Prometheus, Alertmanager and Grafana provide metrics and alerting;
|
||||
Alloy and Loki provide logs. Backup services protect databases, objects,
|
||||
configuration and approved workspace data and support restore verification.
|
||||
|
||||
App Studio applications execute in isolated Kubernetes preview namespaces before
|
||||
independent review and release through the application gateway. Capability packs
|
||||
also follow signed import, validation, enable, upgrade, rollback and removal
|
||||
lifecycles.
|
||||
|
||||
## Capability domains
|
||||
|
||||
### Work with AI
|
||||
@@ -109,4 +136,3 @@ Specific capability availability depends on the licensed edition, purchased
|
||||
packs, customer infrastructure and approved integration scope. Final architecture,
|
||||
sizing, security configuration and acceptance criteria are confirmed during the
|
||||
solution-design process.
|
||||
|
||||
Binary file not shown.
+1
-1
@@ -11,7 +11,7 @@ technical handoff point.
|
||||
| `Nexus_One_AI_Datasheet.docx` | Editable technical buyer datasheet. |
|
||||
| `Nexus_One_AI_Datasheet.pdf` | Shareable PDF export of the technical buyer datasheet. |
|
||||
| `Nexus_One_AI_Live_Features_and_Architecture_155.pdf` | Verified technical feature and architecture reference for the current `.155` Enterprise Pilot environment. |
|
||||
| `Nexus_One_AI_Enterprise_Platform_Datasheet.pdf` | Customer-facing enterprise datasheet covering value, architecture, capabilities, security, operations, deployment and evaluation. |
|
||||
| `Nexus_One_AI_Enterprise_Platform_Datasheet.pdf` | Customer-facing architecture and technical datasheet covering Kubernetes, services, data flows, capabilities, security, operations, deployment and evaluation. |
|
||||
| `NEXUS_ONE_AI_ENTERPRISE_DATASHEET_SOURCE.md` | Editable customer-facing content source for the enterprise platform datasheet. |
|
||||
| `NEXUS_ONE_AI_LIVE_TECHNICAL_REFERENCE_155.md` | Editable source reference covering live topology, capabilities, evidence, limitations and next actions. |
|
||||
| `CURRENT_CAPABILITIES.md` | Concise live capability/status matrix, updated against `.155`. |
|
||||
|
||||
Reference in new issue
Block a user