microservices-demo | Demo application to go with Blog on spring.io | Learning library

Dear StackOverflow community!

I am trying to run the https://github.com/GoogleCloudPlatform/microservices-demo locally on minikube, so I am following their development guide: https://github.com/GoogleCloudPlatform/microservices-demo/blob/master/docs/development-guide.md

After I successfully set up minikube (using virtualbox driver, but I tried also hyperkit, however the results were the same) and execute skaffold run, after some time it will end up with following error:

I am trying to build and deploy microservices images to a single-node Kubernetes cluster running on my development machine using minikube. I am using the cloud-native microservices demo application Online Boutique by Google to understand the use of technologies like Kubernetes, Istio etc.

Link to github repo: microservices-demo

While following the installation process, and on running command skaffold run to build and deploy my application, I get some errors:

I have been working on extending the GCP Online Boutique microservices example, and I would like to add Istio AuthorizationPolicy resources to the system.

Concretely, I want an AuthorizationPolicy to block all not-whitelisted traffic to cartservice, and I want to whitelist traffic from frontend to cartservice.

Currently, I am able to block traffic with an AuthorizationPolicy, but I cannot whitelist traffic by principal or namespace.

For context, here is my system setup. (Anything not explicitly stated here is the default from the demo linked above)

Istio Version:

I am trying to build and deploy microservices images to a single-node Kubernetes cluster running on my development machine using minikube. I am using the cloud-native microservices demo application Online Boutique by Google to understand the use of technologies like Kubernetes, Istio etc.

Link to github repo: microservices-demo

I have followed all the installation process to locally build and deploy the microservices, and am able to access the web frontend through my browser. However, when I click on any of the product images say, I see this error page.

HTTP Status: 500 Internal Server Error

On doing a check using kubectl get pods I realize that one of my pods( Recommendation service) has status CrashLoopBackOff. Running kubectl describe pods recommendationservice-55b4d6c477-kxv8r:

I have two applications, nginx and redis, where nginx uses redis to cache some data so the redis address must be configured in nginx.

On the one hand, I could first apply the redis deployment and get its IP and then apply the nginx deployment to set up the two application in my minikube.

But on the other, to simplify installation in the Kubernetes Dashboard for QA, I want to create a single Kubernetes YAML file (like GoogleCloudPlatform/microservices-demo/kubernetes-manifests.yaml) to deploy these two applications on two diverse Pods. However, if I do it by means of Environment Variables, I cannot get the redis address.

So how do I achieve it?

I took this example https://github.com/paulc4/microservices-demo and I created 3 docker images from it, with the following Dockerfiles:

springdocker-registration:

When i deploy this Deployment for sock-shop Yaml for sock-shop

but it does not give me write permission in the container so i cannot even write in it

this is the error i'm getting:

Error: Reference to undeclared resource

on outputs.tf line 2, in output "api-gateway-codedeploy-app-name":
2: value = "${api-gateway-codedeploy.app-name}"

A managed resource "api-gateway-codedeploy" "app-name" has not been declared in the root module.

my terraform relevant folder structure is

Given a following scheme of services and their dependencies I would like to engineer a set of Helm charts.

• API Gateway calls Service A and Service C
• Service A calls Service B
• Service B calls Database
• Service C calls Service B and Service D

At the moment I see two alternatives:

1. Each of the 6 components in a diagram below is a single chart and each arrow in a diagram is a single dependency.
   

2. There's an Umbrella chart that has a dependency on all other charts. The Database chart is a dependency of Service B chart.
   

Helm documentation suggest going with option 2. I am however more keen towards option 1 due to an ease of local development and CI/CD pipeline.

Example scenario: developer is refactoring Service C and he wants to run the code he changed and test it.

• Option 1. Developer installs a Service C chart only.
• Option 2: Developer would have to either:
  • install an Umbrella chart which leads to waste of a CPU and memory resources because of running unneeded services like Service A or API Gateway, which doesn't scale well with the complexity of the system;
  • install Service C, then Service B and then Service D, which also doesn't scale well with the complexity of the system because it requires to perform many manual actions and also require from developer to be faimiliar with the architecture of the system in order to know what charts needs to be installed.

I would like to make an educated decision on which alternative to take. I am more keen towards option 1, but Helm docs and also few examples I was able to find on the Internet (link) are also going with option 2, so I think I might be missing something.