Once successfully onboarded, click
Configure to configure the deployment of
joker.
This will bring you to Config Builder, which will scan the directory structure of the application's source code repository and provide a best-guess at what its deployment configuration file (its
f8.yaml file) should look like.
Further modify its configuration to expose the
joker component externally by selecting it in the "components" section.
Under its "expose" section, select Properties, and "external". Change its value to "true", which should also update the raw configuration shown on the right.
You may also further modify the configuration as needed, e.g. multiple instances, resource constraints, health checks, autoscaling parameters, and more.
If you are using DockerHub or Elastic Container Registry (ECR) as your container registry, you must
create the following repositories:
-
DockerHub:
- [dockerhub-org]/joker-joker
- [dockerhub-org]/joker-writer
- [dockerhub-org]/joker-func
- [dockerhub-org]/joker-load
- ECR:
- [ecr-registry]/joker/joker
- [ecr-registry]/joker/writer
- [ecr-registry]/joker/func
- [ecr-registry]/joker/load
Finally, click the
cloud_upload icon to upload the configuration to the application's source code repository.