Skip to main content

Add components to your application

Deployable container in the cluster are components, so we should create them first. This can be done on the product detail page

https://odj.cloud/

Add Component

General Information

First of all it is necessary to enter a unique ID for the component which will be used in technical names. Next to that, a name and a description is mandatory.

https://odj.cloud/

Add Component

Component Type

On the next page you can select the component type. In most of the make applications, this will be "deployable".

https://odj.cloud/

Add Component

Deployable

Is intented to be deployed to the runtime. You will need to provide a Dockerfile.

Library

Contains code that might be shared between components but is not runnable on its own.

Supportive

Similar to a deployable component in that you will need to provide a Dockerfile. However, this component is not automatically deployed to the runtime. Instead, this component type can be used for debugging tools and other stuff that does not need to run all the time.

Deployable Type

On the next page you can select the deployable type. If it is a backend component this should be of type "REST API" and if you want to offer an UI choose type "Other".

https://odj.cloud/

Add Component

API Type

If you have selected a "REST API", you choose between Product API, Backend-For-Frontend and Legacy API. The only difference is currently the level of API-Linting, but just as warning for you, no build breaker or something like this.

https://odj.cloud/

Add Component

Capabilities

Lastly, it is possible to choose a capability you will implement with your component. You can choose an already existing one or create a new capability.

https://odj.cloud/

Add Component

warning

Any component which needs to be exposed outside of the cluster, needs to implement a capability.