-
It looks like the deployment for Kubernetes doesn't work with Kubernetes clusters with RBAC enabled. The deploy_kubernetes.sh script takes care of the service accounts but doesn't create the roles / r…
-
This makes it easier to deploy EnMasse on public cloud providers that do not have an ingress controller.
-
The EnMasse community images need to be built using the 'latest' artifacts. To import these using sources, we need the latest md5sum. The md5sum might change after every build. Can we have an optio…
-
-
Traceback (most recent call last):
File "/opt/APPS/servicebus/tst/zato-3/code/bin/zato", line 197, in
sys.exit(zato.cli.zato_command.main())
File "/opt/APPS/servicebus/tst/zato-3/code/zato…
-
To allow EnMasse to work with kubernetes, routes needs to be replaced with ingress. OpenShift can be configured to create routes automatically based on ingress resources.
-
Our use of templates prevents EnMasse from being deployed on a pure kubernetes cluster. Replacing templates with a third party resource (TPR) with the same schema, and adding a substitution mechanism …
-
The step related to project creation:
oc new-project enmasse
seems to be useless if the line related to run the deployment script has -p "enmasse".
Of course the script works but provides this…
-
_From @lulf on September 16, 2016 13:13_
_Copied from original issue: EnMasseProject/openshift-configuration#13_
-
minishft version: minishift v1.14.0+1ec5877
OS: Ubuntu 17.10
Deploying Hono on top of minishift throws lots of Pods Crash Loop Back-offs
```
$oc project hono
Already on project "hono" on ser…