Deliver ViNO CR in multi-tenant type Airship Phase #106
Labels
2-Manifests
Relates to manifest/document set related issues
enhancement
New feature or request
priority/critical
Items critical to be implemented, usually by the next release
size m
2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
type: multi-tenant
Milestone
Problem description
As an operator, I want to deliver a configured ViNO CR within an Airship phase of the multi-tenant site type delivery, so that I can define VMs based upon VM flavors/templates for use as nodes in Kubernetes sub-clusters.
Proposed change
The ViNO CR may be delivered as part of a target cluster workload phase. Applying one or more ViNO CRs will indicate to the ViNO operator the VMs to be created on target/management worker nodes and their associated infrastructure. Upon completion of this phase the VM infrastructure will be set up and virtual BareMetalHost (vBMH) resources will be defined with appropriate labels for use by SIP.
The text was updated successfully, but these errors were encountered: