8000 Define the Margo Standalone Cluster device role · Issue #94 · margo/specification · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Define the Margo Standalone Cluster device role #94
@ajcraig

Description

@ajcraig

Provide feature description below:

Goal: Define the required features and configuration needed for device owners to build a Margo conforming device that enables kubernetes functionality.

This feature describes a particular role "Standalone cluster" that also should enable the "Cluster leader" role outlined in a separate feature.

Provide adequate technical acceptance criteria(s) associated with this feature below:

  • Described features / functionality the device must comply with to enable workload user functionality. These features must be auto discoverable via workloads deployed on device if applicable.
    • Current set of features include but are not limited to:
    • OTEL Collector + End point auto discovery
    • OCI Container runtime
    • Kubernetes core components
    • Helm Client to enable local rendering and deployments
    • Margo Management interface (Workloads)
    • Margo Management Interface (Device configuration / may be private and not applicable)
  • Describe security requirements associated with multi-vendor applications residing on the same device.
  • Define the minimum set of Kubernetes API functions Margo wants to support with this role
  • Reference implementation that enables a user to recreate a Standalone cluster device role with open source components and margo specific components(once completed).

Although not required, it is highly encouraged to provide feature use-cases below:

  • Enable workloads that utilize kubernetes runtime environments to be compliant within the Margo ecosystem
    • Scalable applications
    • Enhanced automation over running services / applications.
  • Enable helm application deployments
  • Enable Kubernetes operator deployments
  • Enable Kubernetes deployment file deployments

Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0