Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment for OpenShift differs from other targets #1071

Open
b-abel opened this issue Feb 28, 2019 · 1 comment
Open

Deployment for OpenShift differs from other targets #1071

b-abel opened this issue Feb 28, 2019 · 1 comment

Comments

@b-abel
Copy link
Contributor

b-abel commented Feb 28, 2019

The deployment configuration for OpenShift (deploy/src/main/deploy/openshift/hono-template.yml) contains copies of the content of deploy/src/main/deploy/example-credentials.json and deploy/src/main/deploy/example-tenants.json which are not up to date.
It would be great if there were a solution that works without copying of configuration.

@ctron
Copy link
Contributor

ctron commented Feb 28, 2019

I agree that it would nice that would be synched automatically.

Then again it would make much sense in the current case. The additions are a coap secret (where coap isn't being deployed) and the X509 certs, which the user has to set up manually, as they certs won't get generated by the S2I template.

The whole idea of the S2I approach is that the user doesn't need to have maven installed, and simply can deploy the single YAML file. If you have an idea how we can achieve this, I would be glad to hear it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants