tadayosi commented on issue #3865:
URL: https://github.com/apache/camel-k/issues/3865#issuecomment-1333430388
> Do we have full feature parity if we adopt the Kustomize option?
Good point. Right now, only few `kamel install` flags are ported to the
Kustomize method, while users are free to manually patch the resources under
`install/` to achieve the same. So I agree that it's a bit too early to
deprecate `kamel install`. At the same time, unless we try to push the
Kustomize method as the primary method we won't fill the gap in the near term.
At least I think we can start promoting it as one of the primary methods.
```
$ make help
...
operator Install the operator deployment and related resources
Cluster-admin privileges are required.
NAMESPACE: Set the namespace to install the
operator into
PLATFORM: Override the discovered platform, if
required
GLOBAL: Sets the operator to watch all
namespaces for custom resources [true|false]
CUSTOM_IMAGE: Set a custom operator image name
CUSTOM_VERSION: Set a custom operator image version/tag
ALWAYS_PULL_IMAGES: Sets whether to always pull the operator
image [true|false]
MONITORING: Adds the prometheus monitoring resources
MONITORING_PORT: Set a custom monitoring port
HEALTH_PORT: Set a custom health port
LOGGING_LEVEL: Set the level of logging [info|debug]
DRY_RUN: Prints the resources to be applied
instead of applying them
...
```
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
