phantomjinx opened a new pull request #2464:
URL: https://github.com/apache/camel-k/pull/2464
* When installing on a non-openshift cluster, allow for possibility of
installing without a registry being present.
* Implies that no building of components can happen but running of
existing integrations and kits can
* e2e tests for installation and running
* Extend API to include constants for Disabled states
* install.go
* If --registry none is specified then setting the registry address to
disabled
* operator.go
* If regsitry Address is disabled then seting both Publish and Build
strategies to disabled (if not on openshift)
* defaults.go
* Avoid configuring registry is disabled
* Controllers and Actions
* Integration controller checks on integration kit and if latter is in
state "Cannot Build" then Error
* Integration kit controller executtes build action but if platform is
disabled then returns early in state "Cannot Build"
* "Cannot Build" differentiates from "Error" since error action can
put the integration kit back to initialization phase to try and build
again. This makes no sense for "Cannot Build" cannot build
* Makefile
* Allow the image to be overridden on the command line using an Env Var.
<!-- Description -->
<!--
Enter your extended release note in the below block. If the PR requires
additional action from users switching to the new release, include the string
"action required". If no release note is required, write "NONE".
You can (optionally) mark this PR with labels "kind/bug" or "kind/feature"
to make sure
the text is added to the right section of the release notes.
-->
**Release Note**
```release-note
NONE
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
