-
Notifications
You must be signed in to change notification settings - Fork 243
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
Clarification : purpose of the odo's application #691
Comments
Why don't you store the composition info within the odo's file ? How can we re-install or move the application to another cluster/namespace if we don't have this info ?
|
My guess composition is stored in labels Application name is used as a value of |
If you want to export component you could do something like this:
this will dump all resources related to But of course this is not ideal, as this is just reserves, the component has also data inside PVC, and those won't be exported. That is not easy to do. |
I think that current scope for Also, .kube/odo file will change when configuration proposal get implemented. And there are some things that in the long run will also affect this behavior:
I wouldn't get too much ahead of what should be done in the short run. |
stale discussion |
What is the purpose of the odo's application ? To group related components of an application deployed into a k8s namespace ?
If this is the correct definition, why are the components related to an application not added to the application definition created within
~/.kube/odo
fileScenario played
The text was updated successfully, but these errors were encountered: