CENM Deployment using Docker, Minikube and Helm charts


 

Hi All:
I am following https://docs.corda.net/docs/cenm/1.2/deployment-kubernetes.html link and trying to do a small PoC using Minikube instead of Kubernetes and in AWS Ubuntu box. But I am unable to create my pods up and running.
Currently, on executing the command - kubectl create deployment idman --image=corda/enterprise-identitymanager:1.2-zulu-openjdk8u242, I am getting below error-

NAME                     READY   STATUS             RESTARTS   AGE
idman-7dd94fb9b9-rdqgr   0/1     CrashLoopBackOff   8          17m

on executing command - kubectl describe pod idman-7dd94fb9b9-rdqgr, I am getting a detailed error as -

Name:         idman-7dd94fb9b9-rdqgr
Namespace:    cenm
Priority:     0
Node:         minikube/172.17.0.3
Start Time:   Wed, 05 Aug 2020 07:12:14 +0000
Labels:       app=idman
              pod-template-hash=7dd94fb9b9
Annotations:  <none>
Status:       Running
IP:           172.18.0.4
IPs:
  IP:           172.18.0.4
Controlled By:  ReplicaSet/idman-7dd94fb9b9
Containers:
  enterprise-identitymanager:
    Container ID:   docker://75accb8f967364e28d9e3dbf609a4f836e52ca7b7a403bf2571337b1d3dd2f88
    Image:          corda/enterprise-identitymanager:1.2-zulu-openjdk8u242
    Image ID:       docker-pullable://corda/enterprise-identitymanager@sha256:69846d36fd87a76a7da92cbb19ad7fd94ac2a94f0c01303efe4d2f0ab9265615
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 05 Aug 2020 07:18:10 +0000
      Finished:     Wed, 05 Aug 2020 07:18:10 +0000
    Ready:          False
    Restart Count:  6
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-cst7g (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-cst7g:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-cst7g
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                     From               Message
  ----     ------     ----                    ----               -------
  Normal   Scheduled  8m30s                   default-scheduler  Successfully assigned cenm/idman-7dd94fb9b9-rdqgr to minikube
  Normal   Pulling    8m30s                   kubelet, minikube  Pulling image "corda/enterprise-identitymanager:1.2-zulu-openjdk8u242"
  Normal   Pulled     8m18s                   kubelet, minikube  Successfully pulled image "corda/enterprise-identitymanager:1.2-zulu-openjdk8u242"
  Normal   Created    6m41s (x5 over 8m15s)   kubelet, minikube  Created container enterprise-identitymanager
  Normal   Started    6m41s (x5 over 8m15s)   kubelet, minikube  Started container enterprise-identitymanager
  Normal   Pulled     6m41s (x4 over 8m14s)   kubelet, minikube  Container image "corda/enterprise-identitymanager:1.2-zulu-openjdk8u242" already present on machine
  Warning  BackOff    3m22s (x24 over 8m13s)  kubelet, minikube  Back-off restarting failed container

Need your assistance please.

Thanks & Regards,
Chandrika


Przemyslaw Bak
 

Hello Chandrika,

you are using “kubectl create deployment …” – unfortunately it won’t work this way.
Each CENM service requires prerequisite steps (some of them a few …) which are then followed by the main process (container).
kubectl create deployment doesn’t run any prereq steps and creates just a pod which is simply not enough to make Identity Manager working (let alone the whole CENM …)

The order in which we spin up all CENM services is also important.

The URL you refer to has step by step manual how to deploy CENM on Kubernetes cluster and it doesn’t use any kubectl commands to create CENM services on k8s.
We haven’t tested nor used it on minikube so we cannot guarantee it will work though …

Kind regards
--
Przemyslaw Bak | R3 | DevOps Engineer
2 London Wall Place, 12th Floor
London, EC2Y 5AU
p.bak@r3.com<mailto:p.bak@r3.com> . www.r3.com<http://www.r3.com/>



From: <corda-dev@groups.io> on behalf of "Chandrika Basak via groups.io" <chandrika.chowdhury=gmail.com@groups.io>
Reply to: "corda-dev@groups.io" <corda-dev@groups.io>
Date: Wednesday, 5 August 2020 at 08:34
To: "corda-dev@groups.io" <corda-dev@groups.io>
Subject: [corda-dev] CENM Deployment using Docker, Minikube and Helm charts

Hi All:
I am following https://docs.corda.net/docs/cenm/1.2/deployment-kubernetes.html <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.corda.net%2Fdocs%2Fcenm%2F1.2%2Fdeployment-kubernetes.html&data=02%7C01%7C%7Ca4eed95fc92f4db7c1fa08d83911f6e4%7Ca4be1f2e2d10419587cd736aca9b672c%7C0%7C0%7C637322096600227691&sdata=QHUFfayal4Bb9xDHVzXDZtiFTDtUwVEgknpLkB2gc%2FA%3D&reserved=0> link and trying to do a small PoC using Minikube instead of Kubernetes and in AWS Ubuntu box. But I am unable to create my pods up and running.
Currently, on executing the command - kubectl create deployment idman --image=corda/enterprise-identitymanager:1.2-zulu-openjdk8u242, I am getting below error-
NAME READY STATUS RESTARTS AGE
idman-7dd94fb9b9-rdqgr 0/1 CrashLoopBackOff 8 17m

on executing command - kubectl describe pod idman-7dd94fb9b9-rdqgr, I am getting a detailed error as -
Name: idman-7dd94fb9b9-rdqgr
Namespace: cenm
Priority: 0
Node: minikube/172.17.0.3
Start Time: Wed, 05 Aug 2020 07:12:14 +0000
Labels: app=idman
pod-template-hash=7dd94fb9b9
Annotations: <none>
Status: Running
IP: 172.18.0.4
IPs:
IP: 172.18.0.4
Controlled By: ReplicaSet/idman-7dd94fb9b9
Containers:
enterprise-identitymanager:
Container ID: docker://75accb8f967364e28d9e3dbf609a4f836e52ca7b7a403bf2571337b1d3dd2f88
Image: corda/enterprise-identitymanager:1.2-zulu-openjdk8u242
Image ID: docker-pullable://corda/enterprise-identitymanager@sha256:69846d36fd87a76a7da92cbb19ad7fd94ac2a94f0c01303efe4d2f0ab9265615
Port: <none>
Host Port: <none>
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Wed, 05 Aug 2020 07:18:10 +0000
Finished: Wed, 05 Aug 2020 07:18:10 +0000
Ready: False
Restart Count: 6
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-cst7g (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-cst7g:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-cst7g
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 8m30s default-scheduler Successfully assigned cenm/idman-7dd94fb9b9-rdqgr to minikube
Normal Pulling 8m30s kubelet, minikube Pulling image "corda/enterprise-identitymanager:1.2-zulu-openjdk8u242"
Normal Pulled 8m18s kubelet, minikube Successfully pulled image "corda/enterprise-identitymanager:1.2-zulu-openjdk8u242"
Normal Created 6m41s (x5 over 8m15s) kubelet, minikube Created container enterprise-identitymanager
Normal Started 6m41s (x5 over 8m15s) kubelet, minikube Started container enterprise-identitymanager
Normal Pulled 6m41s (x4 over 8m14s) kubelet, minikube Container image "corda/enterprise-identitymanager:1.2-zulu-openjdk8u242" already present on machine
Warning BackOff 3m22s (x24 over 8m13s) kubelet, minikube Back-off restarting failed container

Need your assistance please.

Thanks & Regards,
Chandrika


 

Hey Thanks Przemyslaw Bak. Appreciate your response.

I also tried the step by step approach as given in the link -
https://docs.corda.net/docs/cenm/1.2/deployment-kubernetes.html
but I am facing the below error

Unable to decode an event from the watch stream: v1.WatchEvent: Object: readObjectFieldAsBytes: expect : after object field, parsing 1130 ...:{},"k:{\"... at {"type":"ADDED","object":{"kind":"Service","apiVersion":"v1","metadata":{"name":"idman-ip","namespace":"cenm","selfLink":"/api/v1/namespaces/cenm/services/idman-ip","uid":"310ed26c-cf0f-4717-ad95-d69d3a39b5a3","resourceVersion":"465","creationTimestamp":"2020-08-04T12:43:33Z","labels":{"app.kubernetes.io/instance":"idman-ip","app.kubernetes.io/managed-by":"Helm","app.kubernetes.io/name":"idman-ip","app.kubernetes.io/part-of":"cenm","app.kubernetes.io/version":"1.2","helm.sh/chart":"idman-ip-1.0.0"},"annotations":{"meta.helm.sh/release-name":"idman-ip","meta.helm.sh/release-namespace":"cenm"},"managedFields":[{"manager":"Go-http-client","operation":"Update","apiVersion":"v1","time":"2020-08-04T12:43:33Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:meta.helm.sh/release-name":{},"f:meta.helm.sh/release-namespace":{}},"f:labels":{".":{},"f:app.kubernetes.io/instance":{},"f:app.kubernetes.io/managed-by":{},"f:app.kubernetes.io/name":{},"f:app.kubernetes.io/part-of":{},"f:app.kubernetes.io/version":{},"f:helm.sh/chart":{}}},"f:spec":{"f:externalTrafficPolicy":{},"f:ports":{".":{},"k:{\"port\":2222,\"protocol\":\"TCP\"}":{".":{},"f:name":{},"f:port":{},"f:protocol":{},"f:targetPort":{}},"k:{\"port\":10000,\"protocol\":\"TCP\"}":{".":{},"f:name":{},"f:port":{},"f:protocol":{},"f:targetPort":{}}},"f:selector":{".":{},"f:app.kubernetes.io/instance":{},"f:app.kubernetes.io/name":{},"f:app.kubernetes.io/part-of":{},"f:app.kubernetes.io/version":{}},"f:sessionAffinity":{},"f:type":{}}}}]},"spec":{"ports":[{"name":"main","protocol":"TCP","port":10000,"targetPort":10000,"nodePort":31493},{"name":"ssh","protocol":"TCP","port":2222,"targetPort":2222,"nodePort":30203}],"selector":{"app.kubernetes.io/instance":"idman","app.kubernetes.io/name":"idman","app.kubernetes.io/part-of":"cenm","app.kubernetes.io/version":"1.2"},"clusterIP":"10.101.185.89","type":"LoadBalancer","sessionAffinity":"None","externalTrafficPolicy":"Local","healthCheckNodePort":31397},"status":{"loadBalancer":{}}}}


Can you suggest something please?

Thanks & Regards,
Chandrika


Przemyslaw Bak
 

Hi Chandrika,

Can you send over the exact command(s) you had run and all the screen output ?


Kind regards
--
Przemyslaw Bak | R3 | DevOps Engineer
2 London Wall Place, 12th Floor
London, EC2Y 5AU
p.bak@r3.com<mailto:p.bak@r3.com> . www.r3.com<http://www.r3.com/>



From: <corda-dev@groups.io> on behalf of "Chandrika Basak via groups.io" <chandrika.chowdhury=gmail.com@groups.io>
Reply to: "corda-dev@groups.io" <corda-dev@groups.io>
Date: Wednesday, 5 August 2020 at 13:11
To: "corda-dev@groups.io" <corda-dev@groups.io>
Subject: Re: [corda-dev] CENM Deployment using Docker, Minikube and Helm charts

Hey Thanks Przemyslaw Bak. Appreciate your response.

I also tried the step by step approach as given in the link - https://docs.corda.net/docs/cenm/1.2/deployment-kubernetes.html<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.corda.net%2Fdocs%2Fcenm%2F1.2%2Fdeployment-kubernetes.html&data=02%7C01%7C%7C6830166db65f4a5c18cd08d83938b27b%7Ca4be1f2e2d10419587cd736aca9b672c%7C0%7C0%7C637322262976086564&sdata=qI2u2D%2BzIBnNvGgsx3wr4zFofKUd5GTagL7jE%2F5TCqs%3D&reserved=0>
but I am facing the below error

Unable to decode an event from the watch stream: v1.WatchEvent: Object: readObjectFieldAsBytes: expect : after object field, parsing 1130 ...:{},"k:{\"... at {"type":"ADDED","object":{"kind":"Service","apiVersion":"v1","metadata":{"name":"idman-ip","namespace":"cenm","selfLink":"/api/v1/namespaces/cenm/services/idman-ip","uid":"310ed26c-cf0f-4717-ad95-d69d3a39b5a3","resourceVersion":"465","creationTimestamp":"2020-08-04T12:43:33Z","labels":{"app.kubernetes.io/instance":"idman-ip","app.kubernetes.io/managed-by":"Helm","app.kubernetes.io/name":"idman-ip","app.kubernetes.io/part-of":"cenm","app.kubernetes.io/version":"1.2","helm.sh/chart":"idman-ip-1.0.0"},"annotations":{"meta.helm.sh/release-name":"idman-ip","meta.helm.sh/release-namespace":"cenm"},"managedFields":[{"manager":"Go-http-client","operation":"Update","apiVersion":"v1","time":"2020-08-04T12:43:33Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:meta.helm.sh/release-name":{},"f:meta.helm.sh/release-namespace":{}},"f:labels":{".":{},"f:app.kubernetes.io/instance":{},"f:app.kubernetes.io/managed-by":{},"f:app.kubernetes.io/name":{},"f:app.kubernetes.io/part-of":{},"f:app.kubernetes.io/version":{},"f:helm.sh/chart":{}}},"f:spec":{"f:externalTrafficPolicy":{},"f:ports":{".":{},"k:{\"port\":2222,\"protocol\":\"TCP\"}":{".":{},"f:name":{},"f:port":{},"f:protocol":{},"f:targetPort":{}},"k:{\"port\":10000,\"protocol\":\"TCP\"}":{".":{},"f:name":{},"f:port":{},"f:protocol":{},"f:targetPort":{}}},"f:selector":{".":{},"f:app.kubernetes.io/instance":{},"f:app.kubernetes.io/name":{},"f:app.kubernetes.io/part-of":{},"f:app.kubernetes.io/version":{}},"f:sessionAffinity":{},"f:type":{}}}}]},"spec":{"ports":[{"name":"main","protocol":"TCP","port":10000,"targetPort":10000,"nodePort":31493},{"name":"ssh","protocol":"TCP","port":2222,"targetPort":2222,"nodePort":30203}],"selector":{"app.kubernetes.io/instance":"idman","app.kubernetes.io/name":"idman","app.kubernetes.io/part-of":"cenm","app.kubernetes.io/version":"1.2"},"clusterIP":"10.101.185.89","type":"LoadBalancer","sessionAffinity":"None","externalTrafficPolicy":"Local","healthCheckNodePort":31397},"status":{"loadBalancer":{}}}}


Can you suggest something please?

Thanks & Regards,
Chandrika


 

Hi Przemyslaw Bak:
Below are the set of commands and their results. Please suggest

kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:58:53Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
The connection to the server localhost:8080 was refused - did you specify the right host or port?
 
helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"clean", GoVersion:"go1.13.12"}
 
 
Install Minikube-------------------
curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 \
  && chmod +x minikube
sudo mkdir -p /usr/local/bin/
sudo install minikube /usr/local/bin/
 
Start Minikube-------------------
sudo sysctl fs.protected_regular=0
minikube start --vm-driver=none
* minikube v1.12.2 on Ubuntu 18.04
* Using the none driver based on user configuration
* Starting control plane node minikube in cluster minikube
* Running on localhost (CPUs=4, Memory=16011MB, Disk=248104MB) ...
* OS release is Ubuntu 18.04.4 LTS
* Preparing Kubernetes v1.18.3 on Docker 19.03.12 ...
  - kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
> kubeadm.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
> kubectl.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
> kubelet.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
> kubeadm: 37.97 MiB / 37.97 MiB [---------------] 100.00% 77.73 MiB p/s 0s
> kubectl: 41.99 MiB / 41.99 MiB [---------------] 100.00% 41.74 MiB p/s 1s
> kubelet: 108.04 MiB / 108.04 MiB [-------------] 100.00% 72.87 MiB p/s 1s
 
* Configuring local host environment ...
*
! The 'none' driver is designed for experts who need to integrate with an existing VM
* Most users should use the newer 'docker' driver instead, which does not require root!
* For more information, see: https://minikube.sigs.k8s.io/docs/reference/drivers/none/
*
! kubectl and minikube configuration will be stored in /home/ubuntu
! To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:
*
  - sudo mv /home/ubuntu/.kube /home/ubuntu/.minikube $HOME
  - sudo chown -R $USER $HOME/.kube $HOME/.minikube
*
* This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true
* Verifying Kubernetes components...
* Enabled addons: default-storageclass, storage-provisioner
* Done! kubectl is now configured to use "minikube"
 
minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
 
Create storage class, namespace and RBAC --------------------------
kubectl apply -f k8s/cenm.yaml
namespace/cenm created
role.rbac.authorization.k8s.io/all-in-cenm-namespace created
rolebinding.rbac.authorization.k8s.io/everything-in-cenm created
 
export nameSpace=cenm
kubectl config set-context $(kubectl config current-context) --namespace=${nameSpace}
Context "minikube" modified.
 
 
Option 2: Bootstrapping by reusing already allocated external IP addresses #---------------------------------------
cd k8s/helm
kubectl config use-context minikube
Switched to context "minikube".
 
./bootstrap.cenm -i idman-ip -n notary-ip --ACCEPT_LICENSE Y
CORDA ENTERPRISE NETWORK MANAGER – SOFTWARE EVALUATION LICENSE AGREEMENT has been accepted, CORDA ENTERPRISE NETWORK MANAGER will now continue.
The Software Evaluation License Agreement for this product can be viewed from https://www.r3.com/corda-enterprise-network-manager-evaluation-license.
A copy of the Software Evaluation License Agreement also exists within the /license directory in the container."
 
Your current kubectl context:
 
kubectl config context: minikube
namespace: cenm
   Helm release prefix: cenm
 
Do you want to continue ? (y/n) y
 
~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~    Checking public IP allocated for Identity Manager
~~~~~~~~~~~~~~~~
Error from server (NotFound): services "idman-ip" not found
 
 
Option 1: Bootstrapping by allocating new external IP addresses #---------------------------------------
cd k8s/helm
./bootstrap.cenm --ACCEPT_LICENSE Y
CORDA ENTERPRISE NETWORK MANAGER – SOFTWARE EVALUATION LICENSE AGREEMENT has been accepted, CORDA ENTERPRISE NETWORK MANAGER will now continue.
The Software Evaluation License Agreement for this product can be viewed from https://www.r3.com/corda-enterprise-network-manager-evaluation-license.
A copy of the Software Evaluation License Agreement also exists within the /license directory in the container."
 
Your current kubectl context:
 
kubectl config context: minikube
namespace: cenm
   Helm release prefix: cenm
 
Do you want to continue ? (y/n) y
 
~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~    Checking public IP allocated for Identity Manager
~~~~~~~~~~~~~~~~
Error from server (NotFound): services "idman-ip" not found
root@ip-172-31-65-166:~/CENM_PoC/cenm-deployment/k8s/helm# ./bootstrap.cenm --ACCEPT_LICENSE Y
CORDA ENTERPRISE NETWORK MANAGER – SOFTWARE EVALUATION LICENSE AGREEMENT has been accepted, CORDA ENTERPRISE NETWORK MANAGER will now continue.
The Software Evaluation License Agreement for this product can be viewed from https://www.r3.com/corda-enterprise-network-manager-evaluation-license.
A copy of the Software Evaluation License Agreement also exists within the /license directory in the container."
 
Your current kubectl context:
 
kubectl config context: minikube
namespace: cenm
   Helm release prefix: cenm
 
Do you want to continue ? (y/n) y
 
~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~    Triggering public IP allocation for Identity Manager
~~~~~~~~~~~~~~~~
COMMAND: helm install cenm-idman-ip idman-ip --set prefix=cenm
 
NAME: cenm-idman-ip
LAST DEPLOYED: Wed Aug  5 16:31:33 2020
NAMESPACE: cenm
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
It may take a few minutes for the public IP to be available. You can watch the status of by running this command (and watching column 'EXTERNAL-IP'):
 
kubectl get --namespace cenm svc -w cenm-idman-ip
 
You can later get public IP address again by running this command:
 
kubectl get svc --namespace cenm cenm-idman-ip --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}"
 
~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~    Triggering public IP allocation for Notary
~~~~~~~~~~~~~~~~
COMMAND: helm install cenm-notary-ip notary-ip --set prefix=cenm
 
NAME: cenm-notary-ip
LAST DEPLOYED: Wed Aug  5 16:31:33 2020
NAMESPACE: cenm
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
It may take a few minutes for the public IP to be available. You can watch the status of by running this command (and watching column 'EXTERNAL-IP'):
 
kubectl get --namespace cenm svc -w cenm-notary-ip
 
You can later get public IP address again by running this command:
 
kubectl get svc --namespace cenm cenm-notary-ip --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}"
 
~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~    Waiting until cloud provider has allocated public IP for Identity Manager (it may take a few minutes)
~~~~~~~~~~~~~~~~
.........
 
 
minikube kubectl get services
NAME             TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                          AGE
cenm-idman-ip    LoadBalancer   10.109.44.108   <pending>     10000:30726/TCP,2222:30774/TCP   13m
cenm-notary-ip   LoadBalancer   10.100.28.135   <pending>     10002:31614/TCP,2222:31787/TCP   13m
 
kubectl get pods -o wide
No resources found in cenm namespace.
 
minikube kubectl get events
No resources found in cenm namespace.
 
minikube kubectl -- get pods
No resources found in cenm namespace.
 
kubectl get ns
NAME              STATUS   AGE
cenm              Active   13m
default           Active   21m
kube-node-lease   Active   21m
kube-public       Active   21m
kube-system       Active   21m
 
minikube tunnel
Status:
machine: minikube
pid: 330836
route: 10.96.0.0/12 -> 172.31.65.166
minikube: Running
services: [cenm-idman-ip, cenm-notary-ip]
errors:
minikube: no errors
router: no errors
loadbalancer emulator: no errors
 
Thanks & Regards,
Chandrika


 

Hi:
The issue is External IP is not getting created for services and no pod or container is getting created.
can someone please help ?

Thanks & Regards,
Chandrika


Przemyslaw Bak
 

Hi,

You can try to skip the very first two steps (external IP allocation) and go straight to creating CENM services on your local laptop.
But as I said before we had never run nor tested this configuration so we cannot guarantee it will work.


Kind regards
--
Przemyslaw Bak | R3 | DevOps Engineer
2 London Wall Place, 12th Floor
London, EC2Y 5AU
p.bak@r3.com<mailto:p.bak@r3.com> . www.r3.com<http://www.r3.com/>



From: <corda-dev@groups.io> on behalf of "Chandrika Basak via groups.io" <chandrika.chowdhury=gmail.com@groups.io>
Reply to: "corda-dev@groups.io" <corda-dev@groups.io>
Date: Thursday, 6 August 2020 at 14:34
To: "corda-dev@groups.io" <corda-dev@groups.io>
Subject: Re: [corda-dev] CENM Deployment using Docker, Minikube and Helm charts

Hi:
The issue is External IP is not getting created for services and no pod or container is getting created.
can someone please help ?

Thanks & Regards,
Chandrika