[
https://issues.apache.org/jira/browse/CAMEL-21710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudio Miranda reassigned CAMEL-21710:
---------------------------------------
Assignee: Claudio Miranda
> Set automatic parameter when running camel-jbang kubernetes run
> ---------------------------------------------------------------
>
> Key: CAMEL-21710
> URL: https://issues.apache.org/jira/browse/CAMEL-21710
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 4.9.0
> Reporter: Claudio Miranda
> Assignee: Claudio Miranda
> Priority: Major
> Fix For: 4.11.0
>
>
> When running "camel kubernetes run file.java" there may be many parameters to
> set accordingly to the cluster the user is currently connected to, so this
> enhancement request is to automatically detect the cluster and set the basic
> options to build and push the image and to deploy the kubernetes manifests.
> The goal is be able to use "camel kubernetes run file.java" and the automatic
> options take care of the correct configurations. There should be a new
> parameter to "camel kubernetes run --auto-disable" to disable this automation
> and let the user set the desired parameters. Also, if the user sets any
> parameter that is set by the automation, then the automation is disabled.
> As there could be many different ways to build and push the container images
> to the image registry we want to cover some basic scenarios to build and
> deploy to kubernetes.
> These are examples of building and deploying images and manifest that should
> be simplified with this proposal.
> 1. minikube with docker-env
> In this case when using minikube with "eval $(minikube docker-env)" these are
> the parameters to make it work
> {code}
> camel kubernetes run my.java \
> --cluster-type=minikube \
> --build-property=quarkus.kubernetes.image-pull-policy=Never \
> --image-builder=docker
> {code}
> 2. Openshift with S2I
> {code}
> camel kubernetes run mytest.java \
> --cluster-type=openshift
> {code}
> 3. Kind
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
