Configuration matérielle de Kubernetes : RAM, processeur, stockage, périmètre d’analyse et workers d’exécution

Planifiez les ressources RAM, CPU, le stockage persistant et les dépendances des services pour Kubernetes, avec un dimensionnement de ZimaOS adapté aux charges de travail, des sauvegardes et des choix de matériel pratiques.

Configuration matérielle de Kubernetes : RAM, processeur, stockage, périmètre d’analyse et workers d’exécution

Tokenetes hardware requirements at a glance

Tokenetes implements Transaction Tokens (TraTs) for microservices call chains. It's a Kubernetes-native framework providing immutable identity and context in service-to-service communication to prevent attacks like software supply chain or privileged user compromise. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

RAM
No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Size the full stack during the busy operation described below.
CPU
No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Measure CPU use during realistic activity.
Storage
Persist policies, scanner databases, result history, configured credentials and persistent service state.
Required services
Follow the current upstream runtime and complete Tokenetes topology for the selected release. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.
Main sizing variable
scan target size, image layers, repository count, policy evaluation and concurrent scans
Practical Zima starting point
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

From official requirements to the right setup

Plan the complete Tokenetes workload before selecting a server.

  1. Official requirements

    Choose the exact edition, stable release and supported container/runtime. Follow the current upstream runtime and complete Tokenetes topology for the selected release. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

  2. Confirm your needs

    Test a representative busy operation: scan target size, image layers, repository count, policy evaluation and concurrent scans Record peak resident memory, CPU, disk latency and completion time, including other containers.

  3. Leave room to grow

    Place active state on reliable persistent storage. Persist policies, scanner databases, result history, configured credentials and persistent service state. Budget working space for an upgrade or import and test recovery before relying on the deployment.

  4. Run it on ZimaOS

    Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

Check every playback client

  • Exact edition and stable release
  • Supported upstream runtime and architecture
  • All required companion services
  • Realistic peak activity
  • Persistent data and file ownership
  • Free host ports and reachable URLs
  • Working space and backup retention
  • Successful database/file restore

Official minimum requirements

Reviewed November 11, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.

Review Tokenetes official requirements

This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration. Numerical examples above retain their stated deployment scope; co-hosted services and independent backups need additional capacity.

RequirementOfficial minimumWhat this supports
RAM guidanceNo fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Size the full stack during the busy operation described below.Official guidance keeps its original test, recommendation or example scope.
CPU guidanceNo fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Measure CPU use during realistic activity.Core counts do not predict a fixed user, device or document capacity.
Storage planningPersist policies, scanner databases, result history, configured credentials and persistent service state.Installation space is separate from retained content, working files and backups.
Service topologyFollow the current upstream runtime and complete Tokenetes topology for the selected release. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.Include every stateful companion service in the host budget.
Persistent statePersist policies, scanner databases, result history, configured credentials and persistent service state.An image rebuild or container replacement is not a backup.
Deployment boundaryThis integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.Check the linked project instructions for the selected edition and release.

When to upgrade your hardware

Use observed Tokenetes workload pressure to decide when an upgrade is warranted.

Busy operations exceed the available window

The complete stack runs short of memory

Persistent data approaches available capacity

scan target size, image layers, repository count, policy evaluation and concurrent scans Time the job and identify CPU, storage or external-service waits before replacing hardware.

Imports, processing and simultaneous users.

Inspect the application and each required service for OOM events, sustained swap or growing queues. Reduce unnecessary concurrency before adding capacity.

Shared hosts and background work.

Persist policies, scanner databases, result history, configured credentials and persistent service state. Track primary state and backup retention separately.

Long-lived installations and growing collections.

Plan hardware growth with confidence

Address storage, memory, compute and deployment limits separately.

Use suitable active storage

Put latency-sensitive application/database state on durable local SSD storage and keep recoverable copies.

SATA or PCIe SSD according to measured data growth.

Add memory for the complete stack

Choose a higher-RAM host when peak application and companion-service usage leaves inadequate OS headroom.

ZimaBoard 2 1664 or ZimaCube 2 Pro according to the measured constraint.

Separate capacity from compute

A multi-drive system helps when retained content and backup storage are the problem; it is not automatically a faster application.

ZimaCube 2 when a broader multi-drive workload justifies it.

Fix the observed bottleneck

This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

Check service configuration, I/O and network behavior before selecting a stronger CPU.

Can it run on ZimaOS?

Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.

Verify the supported upstream deployment

This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration. Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.

Review upstream deployment guidance ↗

Check workload-specific deployment details

This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

Review Tokenetes deployment details ↗

Which Zima hardware fits Tokenetes?

Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements.

Which workload best matches your Tokenetes deployment?

Conditional lab or supporting storage use only

Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

  • Supporting hardware onlyZimaBoard 2 1664

These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.

Zima hardware Best for Example workload Core configuration Recommended boundary Next step
ZimaBoard 2 1664 Conditional lab or supporting-service role scan target size, image layers, repository count, policy evaluation and concurrent scans
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
16 GB LPDDR5
Storage
64 GB eMMC; add SATA/PCIe SSD storage for persistent application data
Network
Dual 2.5GbE
Acceleration
No dedicated GPU required for this workload.
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration. Get Now
ZimaCube 2 Pro Conditional lab or supporting-service role Follow the current upstream runtime and complete Tokenetes topology for the selected release. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.
CPU
Intel Core i5-1235U, 10 cores / 12 threads
Memory
16 GB
Storage
256 GB system storage; six HDD bays and SSD expansion
Network
10GbE plus 2.5GbE
Acceleration
No dedicated GPU required for this workload.
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration. Get Now

What the Press Says

Highlights from trusted reviewers worldwide.

La Razón
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”
Read full review
GameRevolution
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”
Read full review
TechRadar Pro
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”
Read full review
FOX 8
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”
Read full review

Loved by the Community

Stories and reviews from people who build with Zima every day.

ZimaBlade single-board server
★★★★★

Zima Blade Little yet Powerful

Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.

ZimaCube Pro personal cloud
★★★★★

Very good!!

I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.

ZimaBlade single-board server
★★★★★

Great innovation for mini server!

It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.

ZimaBoard 2 single-board server
★★★★★

Avaliação ZimaBoard 2

Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.

Frequently asked questions

Answers to Tokenetes RAM, CPU, storage, Docker, database and ZimaOS sizing questions.

How much RAM should I plan for Tokenetes?

No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Size the full stack during the busy operation described below. Include ZimaOS, the application and its companion services rather than reserving the entire machine for one container.

What drives the CPU requirement?

No fixed numerical whole-host figure is inferred here; follow the selected release and deployment requirements. Measure CPU use during realistic activity. The workload to test is: scan target size, image layers, repository count, policy evaluation and concurrent scans

Which data must survive a container update?

Persist policies, scanner databases, result history, configured credentials and persistent service state. Preserve a consistent database/file set and verify that your recovery procedure restores a working application.

What other services belong in the budget?

Follow the current upstream runtime and complete Tokenetes topology for the selected release. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

Does this workload need a dedicated GPU?

A dedicated GPU is not assumed for the core workflow described here. Optional AI, acceleration or media-processing integrations must be evaluated separately against the selected backend.

Can I deploy it on ZimaOS?

Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

What should I check before upgrading hardware?

This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration. Measure the same representative operation before and after a configuration or hardware change.

Which Zima device is a practical starting point?

Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This integrates policy, admission or permissions into a supported Kubernetes environment. Controller/webhook availability, policy count, admission traffic and external verification backends need separate sizing and correct RBAC; container availability does not validate the cluster integration.

What sources informed this Tokenetes hardware guide?

This guide was reviewed against the linked project deployment documentation on November 11, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.

  1. Tokenetes official setup / requirements
  2. Tokenetes configuration / deployment
  3. Tokenetes official repository and releases
  4. ZimaBoard 2 specifications
  5. Tokenetes image source: public project material