Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Add support for a "Manifest Directory" #182

Closed
luxas opened this issue Jul 15, 2019 · 1 comment
Closed

Add support for a "Manifest Directory" #182

luxas opened this issue Jul 15, 2019 · 1 comment
Assignees
Labels
area/UX Let's make Ignite's UX great! kind/design Categorizes issue or PR as related to the design of the project. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@luxas
Copy link
Contributor

luxas commented Jul 15, 2019

As suggested by (@)jbeda in the TGIK session -- in the same way as the kubelet can do "Static Pods" ref, Ignite should be able to do VMs. This is essentially what the GitOps code is about, but without the Git sync loop.

Let's target this for v0.5.0

@luxas luxas added area/UX Let's make Ignite's UX great! kind/design Categorizes issue or PR as related to the design of the project. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jul 15, 2019
@luxas luxas added this to the v0.5.0 milestone Jul 15, 2019
@luxas
Copy link
Contributor Author

luxas commented Jul 30, 2019

This was fixed in #226 #234 #241 💯

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/UX Let's make Ignite's UX great! kind/design Categorizes issue or PR as related to the design of the project. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

2 participants