awesome-repositories.com
博客
MCP
awesome-repositories.com

通过 AI 驱动的搜索,发现最优秀的开源仓库。

探索精选搜索开源替代品自托管软件博客网站地图
项目MCP 服务器关于排名机制媒体报道
法律隐私政策服务条款
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

3 个仓库

Awesome GitHub RepositoriesHardware-Based Instance Selection

Selection of cloud instance types based on specified hardware resource requirements.

Distinct from Marketplace Instance Provisioning: Distinct from marketplace provisioning as it is based on hardware resource specs, not third-party marketplace catalogs.

Explore 3 awesome GitHub repositories matching devops & infrastructure · Hardware-Based Instance Selection. Refine with filters or upvote what's useful.

Awesome Hardware-Based Instance Selection GitHub Repositories

用 AI 发现最棒的仓库。我们将通过 AI 为您搜索最匹配的仓库。
  • kubernetes/kopskubernetes 的头像

    kubernetes/kops

    16,631在 GitHub 上查看↗

    kops is a Kubernetes cluster provisioner and lifecycle manager designed to automate the creation, maintenance, and destruction of production-grade clusters on cloud infrastructure. It functions as a declarative infrastructure manager, synchronizing the live state of a cluster with versioned manifests stored in remote object storage to ensure idempotent operations. The project distinguishes itself by offering comprehensive automation for the entire cluster lifecycle, including high-availability control plane deployment, incremental rolling updates, and automated version upgrades. It also serve

    Automatically selects the most appropriate cloud instance types based on required CPU and memory specifications.

    Gocncfcontainersgo
    在 GitHub 上查看↗16,631
  • aws/karpenter-provider-awsaws 的头像

    aws/karpenter-provider-aws

    7,661在 GitHub 上查看↗

    karpenter-provider-aws is a Kubernetes node autoscaler and infrastructure provider for AWS. It serves as a node lifecycle manager and cluster cost optimizer that automatically provisions and removes compute instances based on the resource requirements of pending pods. The project distinguishes itself through advanced AWS spot instance orchestration and price-capacity optimized selection to reduce cloud spend. It minimizes costs by consolidating underutilized nodes and prioritizing spot or reserved instances over on-demand capacity, while proactively migrating workloads before cloud provider i

    Models pod resource requirements against available instance types to select the most cost-effective compute options.

    Go
    在 GitHub 上查看↗7,661
  • lxc/lxdlxc 的头像

    lxc/lxd

    5,554在 GitHub 上查看↗

    LXD is a unified platform for managing both system containers and virtual machines through a single REST API and command-line interface. It provides a programmatic HTTP interface for controlling the full lifecycle of instances, enabling automation and integration with external tools. The system runs unprivileged containers with per-instance UID/GID mappings, seccomp filters, and AppArmor profiles for kernel-level isolation, while supporting multiple storage backends including directory, Btrfs, LVM, ZFS, Ceph, LINSTOR, and TrueNAS through a unified driver interface. The platform distinguishes

    Allows users to choose between system containers and virtual machines at launch time.

    Go
    在 GitHub 上查看↗5,554
  1. Home
  2. DevOps & Infrastructure
  3. Hardware-Based Instance Selection

探索子标签

  • Container vs Virtual Machine SelectorsChoosing between system containers for speed or virtual machines for OS flexibility based on workload requirements. **Distinct from Hardware-Based Instance Selection:** Distinct from Hardware-Based Instance Selection: selects between container and VM runtimes, not cloud hardware types.
  • Resource Simulation SelectionSelection of compute instances by modeling pod resource requirements against available hardware specifications. **Distinct from Hardware-Based Instance Selection:** Uses simulation and modeling of pod requirements rather than just static hardware constraint matching.