-
Feature Request
-
Resolution: Done
-
Major
-
0.9.1
-
2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)
Once we have KOGITO-128 implemented, we should handle all the build features in a separated PR that won't be available on Kubernetes.
- blocks
-
KOGITO-151 Implement deploy application in remote mode feature to Kogito CLI
- Closed
-
KOGITO-2344 Support for Kubernetes Builds on Operator
- Closed
-
KOGITO-2349 User have to define both env variable --image-s2i & --image-runtime to work
- Closed
-
KOGITO-2161 Implement CLI approach to redeploy a service
- Closed
- causes
-
KOGITO-2522 Webhooks seems not working when deploying a Kogito Build
- Closed
- is blocked by
-
KOGITO-128 Operator support on Kubernetes for deploying Kogito Runtimes
- Resolved
- is related to
-
KOGITO-2090 BDD Tests: Integrate KogitoBuild in tests
- Resolved
-
KOGITO-1998 Deprecate KogitoApp CR
- Resolved
-
KOGITO-2019 When a build is running and the configuration has changed, we should start a new build any way
- Resolved
- relates to
-
KOGITO-1771 Several Builds are triggered when deploying a Kogito Application using S2i
- Resolved
-
KOGITO-128 Operator support on Kubernetes for deploying Kogito Runtimes
- Resolved