commit | f431d3f1a16a8ff78681353d9ffd0f385db8895d | [log] [tgz] |
---|---|---|
author | Tommy Hughes IV <tchughesiv@gmail.com> | Mon Jul 22 10:42:42 2019 -0400 |
committer | GitHub <noreply@github.com> | Mon Jul 22 10:42:42 2019 -0400 |
tree | cc9a180193c30c1b4efe73e898ff0b4bf1106097 | |
parent | 3194f1bf26cabe37e7109d5b6ddbf2cfb5b0e17e [diff] | |
parent | dfc1ef2288dd56f389dbf38690b8ccb8e5cbc7ff [diff] |
Merge pull request #19 from sutaakar/image-tag Adjust expected image stream tags to Kogito 0.2.0 images
make
e.g.
docker push quay.io/kiegroup/kogito-cloud-operator:<version>
To install this operator on OpenShift 4 for end-to-end testing, make sure you have access to a quay.io account to create an application repository. Follow the authentication instructions for Operator Courier to obtain an account token. This token is in the form of “basic XXXXXXXXX” and both words are required for the command.
Push the operator bundle to your quay application repository as follows:
operator-courier push deploy/catalog_resources/courier/0.1.0 kiegroup kogitocloud-operator 0.1.0 "basic XXXXXXXXX"
If pushing to another quay repository, replace kiegroup with your username or other namespace. Also note that the push command does not overwrite an existing repository, and it needs to be deleted before a new version can be built and uploaded. Once the bundle has been uploaded, create an Operator Source to load your operator bundle in OpenShift.
## kogito imagestreams should already be installed/available ... e.g. oc apply -f https://raw.githubusercontent.com/kiegroup/kogito-cloud/master/s2i/kogito-imagestream.yaml -n openshift oc create -f deploy/catalog_resources/courier/kiecloud-operatorsource.yaml
Remember to replace registryNamespace with your quay namespace. The name, display name and publisher of the operator are the only other attributes that may be modified.
It will take a few minutes for the operator to become visible under the OperatorHub section of the OpenShift console Catalog. It can be easily found by filtering the provider type to Custom.
## kogito imagestreams should already be installed/available ... e.g. oc apply -f https://raw.githubusercontent.com/kiegroup/kogito-cloud/master/s2i/kogito-imagestream.yaml -n openshift oc new-project <project-name> ./hack/3.11deploy.sh
Use the OLM console to subscribe to the kogito
Operator Catalog Source within your namespace. Once subscribed, use the console to Create KogitoApp
or create one manually as seen below.
$ oc create -f deploy/crs/app_v1alpha1_kogitoapp_cr.yaml kogitoapp.app.kiegroup.org/example-quarkus created
oc delete kogitoapp example-quarkus
Change log level at runtime w/ the DEBUG
environment variable. e.g. -
make dep make clean DEBUG="true" operator-sdk up local --namespace=<namespace>
Before submitting PR, please be sure to generate, vet, format, and test your code. This all can be done with one command.
make test