-
Sub-task
-
Resolution: Done
-
Critical
-
None
-
fuse-next-TP1-GA
-
None
-
ENTESB-13408 - Cleanup installation and usage instructions
-
%
We should establish a common format for all quickstarts README.didact.md
OperatorHub installation
Unify OperatorHub installation steps. We introduced two different approaches to our quickstarts.
#1 Manually - camel-k-example-vdb
Now, go to your OpenShift 4.x WebConsole page, and find the OperatorHub menu item on left hand side menu and find and install "Data Virtualization Operator". This may take couple minutes to install.
#2 Didact steps - camel-k-example-event-streaming
That creates a secluded space where AMQ Streams can run. To deploy it, we subscribe to the AMQ Streams channel by using the following command: oc apply -f infra/kafka/amq-streams-subscription.yaml
– https://github.com/openshift-integration/camel-k-example-event-streaming/blob/master/infra/kafka/amq-streams-subscription.yaml#L19
– https://github.com/openshift-integration/camel-k-example-event-streaming/blob/master/infra/messaging/broker/amq-broker-subscription.yaml#L19
Personally I would prefer #2 - we can easily specify dependency version (see ENTESB-13255)
redhat.io secret
We need a secret in order to download images from redhat.io. We should add a check for the secret to the #Requirements section and provide steps to install it to the cluster.
kamel install needs cluster-admin role
Add check to #Requirements section for cluster-admin privileges
uninstalling steps
Quickstarts are missing uninstalling steps.
- is related to
-
ENTESB-13381 Quickstarts should have OperatorHub based instructions to install required products
- Resolved
-
ENTESB-13380 Quickstarts should have OperatorHub based instructions to install camel-k
- Closed
-
ENTESB-13499 Add uninstalling steps to Camel-K quickstarts
- Closed