The ConfigMap https://kubernetes.io/docs/tasks/configure-pod-container/configmap/ feature could be see as a configuration repository for the ODM container instance. This issue should see as an investigation to see how we can leverage this feature for the ODM container needs.

This issue was found on MiniKube (see #9). We should probably have the same issue on IBM Cloud Private.

Hi @lgrateau,
Hope you are having a good day ! I am trying to setup ODM on Amazon EKS and have couple of observations:

Followed the steps required to deploy ODM on EKS. I am receiving the below error message when executing kubectl describe pod:

Warning Failed 36s (x3 over 85s) kubelet Failed to pull image "cp.icr.io/cp/cp4a/odm/odm-decisionserverconsole:8.10.5.0-amd64": rpc error: code = Unknown desc = Error response from daemon: pull access denied for cp.icr.io/cp/cp4a/odm/odm-decisionserverconsole, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Also, documentation on EC2 instance used such as family, storage, memory etc would greatly benefit in spinning up an EKS using eksctl.

This issue was found on MiniKube (see #9). We should probably have the same issue with Helm.

I wanted to configure Kubernetes Liveness, Readiness probes for a ODM cluster topology setup.

Are there suitable HTTP endpoints that can be used for probes on all four docker containers?

1. ODM Decision Center
2. ODM Decision Server
   1. ODM Decision Server runtime
   2. ODM Decision Server console
   3. ODM Decision Runner

use this tool https://pages.github.ibm.com/IBMPrivateCloud/content-standards/content-verification-linter/ and check if the result raised no error

When instanciating a helm chart the dc / dr /ds should be optional if the replicas is set to 0.

#38

on EKS In the command to create the trust store we should add the argument "-storetype JKS".
If may happen that the truststore is created in PKCS12 format if using the default type.

https://github.com/ODMDev/odm-docker-kubernetes/blob/96980c2f593fdc95dcf338b8ea03d13b3edad2dc/eks/README.md?plain=1#L273

https://pages.github.ibm.com/IBMPrivateCloud/content-provider-playbook/10-standards-and-guidance/#helm-charts/

Reproduced on MiniKube.
If the decision runner is prefixed with "odm-", the URL of the decision runner (using decisionrunner) generated at built time in the database for Decision Center does not work.

NB: It is probably also not working on the other clouds.

Following the IBM Guidance the copyright should be :

###############################################################################

Licensed Materials - Property of IBM.

Copyright IBM Corporation 2017. All Rights Reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure

restricted by GSA ADP Schedule Contract with IBM Corp.

Contributors:

IBM Corporation - initial API and implementation

###############################################################################

This issue was found on MiniKube (see #9). We probably have the same issue on Google Cloud.

First deployment chart name "odm-dev" is OK in DC (teamserver/configure/manage server): RES server = odm-dev-odm-decisionserverconsole
Second deployment chart name "secondodm" is not OK in DC (teamserver/configure/manage server): RES server = odm-decisionserverconsole

chart name is missing

This issues was found on MiniKube (see #9). We probably have the same issue on Bluemix.

Hello,

I have been attempting to set this up on Azure Kubernetes Service using Azure PostreSQL as storage. However, my company mandates SSL communication to databases, and I do not see a way to specify that option on the helm chart.

Is PostgreSQL over SSL supported?

The https://github.com/IBM/charts contains the IBM helm chart. It will be better to host this charts in this repo.

https://pages.github.ibm.com/IBMPrivateCloud/content-provider-playbook/01-getting-started/#the-ibm-cloud-private-icp-content-squad

Hi,

I am trying to setup odm on kubernetes i m getting following error
Status: Downloaded newer image for postgres:9.6.6
---> 5579c7505b1b
Step 2/9 : LABEL maintainer="Rachel ORTI [email protected], ODMDev [email protected]"
---> Running in 8ec3816ee003
Removing intermediate container 8ec3816ee003
---> fbefe95f8fda
Step 3/9 : MAINTAINER "Rachel ORTI [email protected], ODMDev [email protected]"
---> Running in 8c1a3c0f85c4
Removing intermediate container 8c1a3c0f85c4
---> 2593f362afe7
Step 4/9 : ARG ODMDOCKERDIR
---> Running in 6d66629b6af4
Removing intermediate container 6d66629b6af4
---> 0c525767b5d3
Step 5/9 : ADD $ODMDOCKERDIR/databases/postgresql/data.tar.gz /upload
ERROR: Service 'dbserver' failed to build: ADD failed: stat /var/lib/docker/tmp/docker-builder829022242/odm-ondocker/databases/postgresql/data.tar.gz: no such file or directory

This is on windows 10 machine and verified that file exits in the location mentioned

Thanks in advance

Complete the Helm chart with report with all ODM URLs.

The helm charts support testing after install.

To have all the contribution related to ODM in an unique location, we need to transfert this repo to the ODMDev org.

The IBM HELM Chart validator raises warning beacause the ODM Helm chart does not contains LICENSES File.

The DB Server container instance store the data in their data in their local file system.
If we restart the container the data are lost.
The goal of this issue is to investigate how to map the data container to a Persistent Kubernetes volumes.

Once we know what we have to do we need to modify the different topology (minikube , bluemix and helm chart yml file ) to add this configuration

In the doc, it says to create the db server here, but the db server is not used.

aws ecr create-repository --repository-name dbserver --image-scanning-configuration scanOnPush=true --region $REGION