Comments on: Microservices With Spring Cloud Kubernetes

By: amit4sun

amit4sun — Sun, 25 Apr 2021 11:35:22 +0000

You created your Roles and Bindings for serviceaccount for each namespace (a,b,c,d) but you didn;t actually assign application resources to this namespace.

By: piotr.minkowski

piotr.minkowski — Tue, 09 Mar 2021 08:28:38 +0000

In reply to amit4sun. Which "gateway" do you mean?

By: amit4sun

amit4sun — Sun, 07 Mar 2021 00:36:20 +0000

Any reason why Ingress is configured to route the traffic directly to the microservices than to the gateway? I understand with MiniKube deployment just the gateway service on NodePort would have been enough but Since you provided the Ingress example, I was curious to know how traffic would have been routed via Ingress.

By: piotr.minkowski

piotr.minkowski — Wed, 20 Jan 2021 09:52:36 +0000

In reply to Nina H.. Hello, thanks. Yes, you can use it only with Java.

By: Nina H.

Nina H. — Wed, 20 Jan 2021 02:27:41 +0000

Hello, nice and informative Tutorial.
I have a question, should we use Spring Cloud Kubernetes on Polyglot Microservices (e.g. when we have one service with Java, another with Python, another with Go, etc.)?
Or it’s recommended only for a group of JVM based Microservices?

By: Piotr Mińkowski

Piotr Mińkowski — Fri, 07 Aug 2020 14:07:40 +0000

In reply to Ajit. Hi, It looks like you have problem with your instance of Minikube. Were you succesfull in running there anything else?

By: Ajit

Ajit — Fri, 07 Aug 2020 14:05:45 +0000

Hi,
I am getting below exception for department module .
I cloned your code from master branch.

> kubectl get pods
department-69f69cb4d5-2kkch 0/1 ImagePullBackOff

> describe pod department-79d6d487bb-mzs2m

Warning Failed 9s (x3 over 58s) kubelet, minikube Failed to pull image “piomin/department:1.0”: rpc error: code = Unknown desc = Error response from daemon: pull access denied for piomin/department, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied
Warning Failed 9s (x3 over 58s) kubelet, minikube Error: ErrImagePull

Same error also getting for organization module too. But employee module is working fine.

Any Idea?

Thanks in advance.

By: Piotr Mińkowski

Piotr Mińkowski — Sun, 12 Jul 2020 10:34:58 +0000

In reply to Jasgeet Singh.

Hi. You should add additional privileges for application since it has to access Kubernetes API. Something like that:

kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: service-discoverer
namespace: default
rules:
– apiGroups: [“”]
resources: [“services”, “endpoints”, “configmaps”, “secrets”, “pods”]
verbs: [“get”, “watch”, “list”]
—
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: default-service-discoverer
namespace: default
subjects:
– kind: ServiceAccount
name: default
namespace: default
roleRef:
kind: Role
name: service-discoverer
apiGroup: rbac.authorization.k8s.io

By: Jasgeet Singh

Jasgeet Singh — Sat, 11 Jul 2020 17:43:56 +0000

main] o.s.c.k.config.ConfigMapPropertySource : Can’t read configMap with name: [employee] in namespace:[default]. Ignoring.
io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [ConfigMap] with name: [employee] in namespace: [default] failed.

By: Jasgeet Singh

Jasgeet Singh — Sat, 11 Jul 2020 17:33:42 +0000

I am getting this error , please help

main] o.s.c.k.config.ConfigMapPropertySource : Can’t read configMap with name: [employee] in namespace:[default]. Ignoring.

io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [ConfigMap] with name: [employee] in namespace: [default] failed.