stefanprodan / gitops-istio Goto Github PK

I was trying to deploy on minikube with 2 cpu and 4096MB memory and experienced this error on pod istio-telemetry:

Events:
  Type     Reason            Age                 From               Message
  ----     ------            ----                ----               -------
  Warning  FailedScheduling  11s (x23 over 21m)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu.

Then, I tried to use minikube with 4 cpu instead and everything's fine.

There is a doc on Istio stating that it is recommended to use 4 cpu to start with minikube. Maybe an update on README is needed?

diff --git a/README.md b/README.md
index f661cd4..bd33e8f 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ Components:
 
 You'll need a Kubernetes cluster **v1.11** or newer with `LoadBalancer` support, 
 `MutatingAdmissionWebhook` and `ValidatingAdmissionWebhook` admission controllers enabled. 
-For testing purposes you can use Minikube with two CPUs and 4GB of memory. 
+For testing purposes you can use Minikube with four CPUs and 4GB of memory. 
 
 Install Flux CLI, Helm and Tiller:

Helm v3 removed the Tiller component. It would be nice to have the guide updated to use Helm v3 instead of the previous version based on Tiller.

I think the reconciler needs to ignore my-cluster, but then I'm not sure where it gets the istio version?

Use Istio operator CRD instead of the deprecated Helm chart.

I have a fresh install Kubernetes cluster on AWS EKS.

The problem occured when installing using flux-init.sh:

Installing Flux for ${REPO_URL}
Error: flux namespace does not exists

I guessed the issue is flux is not created

So, I need to execute kubectl create namespace flux before ./scripts/flux-init.sh [email protected]:<YOUR-USERNAME>/gitops-istio

I think there is a typo in the readme, because the service for my minikube test is not istio-ingressgateway but

kubectl -n istio-system get svc istio-gateway -ojson | jq .status.loadBalancer.ingress

returning

[
  {
    "ip": "10.96.193.77"
  }
]

Aside from this irrelevant fix, I 've found very usefull your suggestion here and after

kubectl delete pod/istiod-7848cf56c8-t5fnw -n istio-system

all pods in istio-system started running. Good, however that comment is from 2019; is there any recent information on more automated management nowadays, without the need for manual pod deletion? If this is off-topic here due to being an issue related to Istio or something else, feel free to disregard.

My final question, how about changing the tag version in the frontend instead of the backend, so to make the effect more visible also from the UI?
Otherwise, the backend version appears to be non-discoverable from the user's perspective, doesn't it?

I was trying to install your project and stuck on the failing pod flagger-loadtester.

When I checked the logs, it shows:
Failed to pull image "weaveworks/flagger-loadtester:0.21.1": rpc error: code = Unknown desc = Error response from daemon: manifest for weaveworks/flagger-loadtester:0.21.1 not found

I fixed it by changing the version through:
fluxctl release --workload=prod:deployment/flagger-loadtester \ --update-image=weaveworks/flagger-loadtester:0.12.1 --k8s-fwd-ns flux

Line issue:

After following your instructions, I am not able to see any metrics on the 'Istio Canary' dashboard within grafana. I tried opening prometheus and running a query for istio_requests_total just to see the raw time series data, but there is nothing there. It appears that istio is not collecting any metrics? Or possibly that the load test is not actually sending any requests through the system?

Do I need to run any commands to initiate the load test?

Hi,

I have tried to install latest version on GKE (1.13.6), and get the following error :

ts=2019-06-26T14:01:26.541674009Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-06-26T14:01:26.633669856Z caller=images.go:24 component=sync-loop error="getting unlocked automated resources: duplicate definition of ':customresourcedefinition/sidecars.networking.istio.io' (in istio-system/crd-10.yaml and istio-system/crd-11.yaml)"

Could you please to take a look ? Thank you so much.

Best Regards,
VietNC

when running through your README, I can see the istio-system and the CRDs however istio isn't installed.

Ref: fluxcd/helm-operator-get-started#28

Hi,

I have tried to install latest version on GKE (1.13.6), component Flagger (0.16) and Istio (1.2.0) are up, but when I access dashboards, it cannot load information about namespace (but the namespace is existed on k8s) and some graphs is missing data as following attached images :

Hope you could help to take a look this issue. Thank you so much.

Best Regards,
VietNC