Migrating components
This section describes how to migrate components to devfile v2. There ARE major changes in the components
section of the devfile. A component specified in a v1.0 devfile will NOT work as it is in a devfile v2.0.
-
Component is a polymophic type
For a better syntax validation component now is defined as a polymorphic type and can be implemented as
container
,kubernetes
,openshift
,plugin
orvolume
.v2.0 --- components: - container: image: maven ... - container: image: nodejs ... - kubernetes: reference: https://.../mongo.yaml
See corresponding issue.
-
Shared Volumes Across Components. See corresponding issue.
-
Out of Main Pod Compoenents. See corresponding issue.
-
Replace Alias with Name. See corresponding issue.
-
Renaming dockerimage component type. See corresponding issue.
-
Specify sources path for containers. See corresponding issue.
-
Specify size of volume for component. See corresponding issue.
-
Containers endpoints (routes/ingresses). See corresponding issue.
-
Component is a polymophic type. See corresponding issue.
-
Shared Volumes Across Components. See corresponding issue.
-
Out of Main Pod Compoenents. See corresponding issue.
-
Replace Alias with Name. See corresponding issue.
-
Renaming dockerimage component type. See corresponding issue.
-
Specify sources path for containers. See corresponding issue.
-
Specify size of volume for component. See corresponding issue.
-
Containers endpoints (routes/ingresses). See corresponding issue.