[
https://issues.jboss.org/browse/ISPN-6675?page=com.atlassian.jira.plugin....
]
Sebastian Łaskawiec commented on ISPN-6675:
-------------------------------------------
Other options (less promising):
* [
S2I|https://github.com/openshift/source-to-image]
** Takes a Docker image and a Github repository and produces a final image.
** We could merge {{jboss/infinispan-server}} image together with a {{cloud.xml}} file
from Github repository and produce the final image in the OpenShift
** This also requires performing a Rolling Update (replacing all the Pods) procedure to
populate changes
* Extend the docker image and use Github repository
** All you need to do is to create a Dockerfile which extends {{jboss/infinispan-server}},
copy your custom {{cloud.xml}} file to
{{/opt/jboss/infinispan-server/standalone/configuration/cloud.xml}} and push it to the
Github repository
** Next, create a new application on the Openshift using this repository ({{oc new-app
https://github.com/foo/bar}}). Openshift will detect the building strategy automatically
(it will find a Dockerfile inside the repository).
* Extend the Docker image and use Docker hub
** Actually it's the easiest way...
** Build everything you need and push it to the Docker HUB
** Use {{oc new-app <your_image>}}
Better configuration management for Kubernetes
----------------------------------------------
Key: ISPN-6675
URL:
https://issues.jboss.org/browse/ISPN-6675
Project: Infinispan
Issue Type: Feature Request
Components: Cloud Integrations
Reporter: Sebastian Łaskawiec
Assignee: Sebastian Łaskawiec
Currently we either store the configuration in the Docker Image or use system properties
to turn the things on/off. Both approaches do not scale.
There are some other alternatives like [Kubernetes
ConfigMap|http://kubernetes.io/docs/user-guide/configmap] which are worth exploring
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)