The installation instructions for the WildFly Operator on OpenShift in the ejb-txn-remote-call quickstart should be revised. Currently, users are expected to build the WildFly Operator, which is unnecessarily complex. It requires installing Go language and dealing with builiding problems like having all neededs deps in correct versions.

Problem is that WildFly operator is not part of OpenShift OperatorHub by default so it could be added there and describe just steps how to install using Web UI or oc CLI commands.

Or update the documentation to guide users on adding the WildFly Operator from the community catalog instead of building it manually. The process is follwoing:

• Creating a community-catalog-source.yaml file:
   

  apiVersion: operators.coreos.com/v1alpha1
  kind: CatalogSource
  metadata:
    name: operatorhubio-catalog
    namespace: openshift-marketplace
  spec:
    displayName: Community Operators
    grpcPodConfig:
      securityContextConfig: restricted
    image: quay.io/operatorhubio/catalog:latest
    publisher: OperatorHub.io
    sourceType: grpc
    updateStrategy:
      registryPoll:
        interval: 60m

• Applying it with:
   

  oc apply -f community-catalog-source.yaml

• Installing the WildFly Operator via wildfly-operator.yml:
   

  apiVersion: operators.coreos.com/v1alpha1
  kind: Subscription
  metadata:
    name: wildfly
  spec:
    channel: alpha
    installPlanApproval: Automatic
    name: wildfly
    source: operatorhubio-catalog
    sourceNamespace: openshift-marketplace

• Applying it with:
   

  oc apply -f wildfly-operator.yml

cc-ing yborgess1@redhat.com