Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy Virtual Node Operator (ViNO) via Airship Phase in multi-tenant type #104

Closed
lb4368 opened this issue Mar 2, 2021 · 4 comments
Closed
Assignees
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

Comments

@lb4368
Copy link

lb4368 commented Mar 2, 2021

Problem description
As an operator, I want to deploy the Virtual Node Operator (ViNO) as part of a multi-tenant site during an airshipctl phase, so that there is support for defining sub-clusters in later phase(s).

Proposed change
This involves delivering ViNO CRD/operator to the target/management cluster as part of an airshipctl phase (possibly initinfra). Upon completion of this phase the operator is deployed and ready for use. These CRDs/Operators are the critical components in deploying the sub-clusters to their desired state.

  1. Integrate the delivery of the ViNO CRD/operator (https://opendev.org/airship/vino) into an Airship phase defined in the multi-tenant type manifests.
  2. Verify capability to run phase applying ViNO CRD/operator via Airship as part of a Cloud Harbor site deployment leveraging the Cloud Harbor type manifests.
@lb4368 lb4368 added enhancement New feature or request triage 2-Manifests Relates to manifest/document set related issues type: multi-tenant priority/critical Items critical to be implemented, usually by the next release and removed triage labels Mar 2, 2021
@lb4368 lb4368 added this to the postV2.0 milestone Mar 3, 2021
@digambar15
Copy link
Contributor

Please assign this issue to me.

@eak13
Copy link

eak13 commented Mar 5, 2021

@digambar15 all yours, please let us know t-shirt size so we can add. Thanks.

@lb4368 lb4368 added the size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] label Mar 8, 2021
@lb4368 lb4368 modified the milestones: Future, v2.1 Mar 11, 2021
@digambar15
Copy link
Contributor

PS Created https://review.opendev.org/c/airship/treasuremap/+/781228. Got +2 from matt and +1 from Ian.

@lb4368
Copy link
Author

lb4368 commented Apr 28, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

3 participants