Comments for

Comment on Kubernetes Observability Using Loki, Cortex, Tempo and Grafana by gkr

gkr — Tue, 07 Nov 2023 22:24:04 +0000

Thanks for the wonderful writeup, there are few changes needed for the HotRod app, those env variables are no more valid. It has been replaced or updated.

env:
– name: OTEL_EXPORTER_JAEGER_AGENT_HOST
value: tempo.observability
– name: OTEL_EXPORTER_JAEGER_AGENT_PORT
value: ‘6831’
– name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://tempo.observability:4318

This is what worked for me!

Comment on Kubernetes Observability Using Loki, Cortex, Tempo and Grafana by Tanmay Saha

Tanmay Saha — Tue, 16 Aug 2022 06:15:45 +0000

Excellent and well done! Please help me to understand how Loki and Tempo data going into s3 without any configuration mentioned here. Cortex I get it.

Comment on Secure your Microservices Ingress in Istio with Let’s Encrypt by Sumit

Sumit — Tue, 03 May 2022 21:14:00 +0000

In reply to invisiblcloud.

Here is the output :-
% kubectl -n istio-system get pods
NAME READY STATUS RESTARTS AGE
istio-egressgateway-6f9d4548b-lbn95 1/1 Running 0 2m6s
istio-ingressgateway-5dc645f586-htq7z 1/1 Running 0 2m6s
istiod-79b65d448f-482xk 1/1 Running 0 2m19s
%

Do I need to mention “istio-ingressgateway-5dc645f586-htq7z” instead of “istio-gateway” ?

And also what about “–set sources[1]=istio-virtualservice” in helm command, shall I leave it as it is ?

I am available at [email protected] and +61405155584 (whatsapp). Please contact to help me sort this out.

Comment on Secure your Microservices Ingress in Istio with Let’s Encrypt by invisiblcloud

invisiblcloud — Tue, 03 May 2022 15:43:21 +0000

It looks like external-dns is not able to find istio-gateway. can you check if your istio installation went through successfully as part of step 3? when you run “kubectl -n istio-system get pods” do you see istio-gateway listed?

Comment on Secure your Microservices Ingress in Istio with Let’s Encrypt by Sumit

Sumit — Tue, 03 May 2022 12:42:14 +0000

I tried following this article…but the following command is failing with error “zsh: no matches found: sources[0]=istio-gateway”. Could you please suggest ?

% helm install external-dns bitnami/external-dns -n external-dns \
–set serviceAccount.create=false \
–set serviceAccount.name=sa-external-dns \
–set provider=aws \
–set txtOwnerId=istio-demo \
–set aws.zoneType=public \
–set sources[0]=istio-gateway \
–set sources[1]=istio-virtualservice
zsh: no matches found: sources[0]=istio-gateway
%

Comment on Part 2 – The need for developer focused Kubernetes Platforms by Building Internal Kubernetes Platforms – Invisibl Cloud

Building Internal Kubernetes Platforms – Invisibl Cloud — Wed, 05 Jan 2022 05:52:52 +0000

[…] Building internal Kubernetes platforms with the right set of components helps in answering these questions, drive successful Kubernetes adoption across teams and derive the benefits Kubernetes provides. […]