-
Enhancement
-
Resolution: Done
-
Major
-
0.10.0
-
None
After KOGITO-128 we probably should have an option to deploy the `KogitoRuntime` as well. This need further discussions, that's why I hadn't implemented it in KOGITO-128.
Ideally the command should be something like:
kogito deploy example-quarkus --image: quay.io/ricardozanini/example-quarkus:latest
But with the other options we currently have, this could be a problem in the UX perspective. Since we are also planning to deprecate KogitoApp (KOGITO-1998), much of those options won't make much sense in this same command either:
Usage: kogito deploy-service NAME [SOURCE] [flags] Aliases: deploy-service, deploy Flags: -b, --branch string Git branch to use in the git repository --build-env stringArray Key/pair value environment variables that will be set during the build. For example 'MY_CUSTOM_ENV=my_custom_value'. Can be set more than once. --build-limits strings Resource limits for the s2i build pod. Valid values are 'cpu' and 'memory'. For example 'cpu=1'. Can be set more than once. --build-requests strings Resource requests for the s2i build pod. Valid values are 'cpu' and 'memory'. For example 'cpu=1'. Can be set more than once. -c, --context-dir string Context/subdirectory where the code is located, relatively to repository root --enable-events If set to true will install a Kafka cluster via the Strimzi Operator. The environment variable 'KAFKA_BOOTSTRAP_SERVERS' will be available for the service during runtime. --enable-istio Enable Istio integration by annotating the Kogito service pods with the right value for Istio controller to inject sidecars on it. Defaults to false --enable-persistence If set to true will install Infinispan in the same namespace and inject the environment variables to configure the service connection to the Infinispan server. -e, --env stringArray Key/Pair value environment variables that will be set to the service runtime. For example 'MY_VAR=my_value'. Can be set more than once. -h, --help help for deploy-service --image-runtime string Custom image tag for the s2i build, e.g: quay.io/mynamespace/myimage:latest --image-s2i string Custom image tag for the s2i build to build the application binaries, e.g: quay.io/mynamespace/myimage:latest --image-version string Image version for standard Kogito build images. Ignored if a custom image is set for image-s2i or image-runtime. --incremental-build Build should be incremental? (default true) --limits strings Resource limits for the Service pod. Valid values are 'cpu' and 'memory'. For example 'cpu=1'. Can be set more than once. --maven-mirror-url string Internal Maven Mirror to be used during source-to-image builds to considerably increase build speed, e.g: https://my.internal.nexus/content/group/public --native Use native builds? Be aware that native builds takes more time and consume much more resources from the cluster. Defaults to false -p, --project string The project name where the service will be deployed --replicas int32 Number of pod replicas that should be deployed. (default 1) --requests strings Resource requests for the Service pod. Valid values are 'cpu' and 'memory'. For example 'cpu=1'. Can be set more than once. -r, --runtime string The runtime which should be used to build the Service. Valid values are 'quarkus' or 'springboot'. Default to 'quarkus'. (default "quarkus") --svc-labels strings Labels that should be applied to the internal endpoint of the Kogito Service. Used by the service discovery engine. Example: 'label=value'. Can be set more than once.
I recommend reviewing the CLI with KOGITO-1998 implementation using this JIRA.
- blocks
-
KOGITO-2521 Missing Webhooks option in CLI for deploy-service
- Closed
-
KOGITO-1998 Deprecate KogitoApp CR
- Resolved
- is blocked by
-
KOGITO-128 Operator support on Kubernetes for deploying Kogito Runtimes
- Resolved
- is related to
-
KOGITO-2739 BDD tests: Add CLI support for KogitoRuntime and KogitoBuild
- Resolved