Felipe Cruz Martinez

I'm running out of ideas as well after +6h...

Thank you @bboreham I have run it as a Pod and it has picked up the `kubeconfig` file automatically:  At the same time, I'm running Jaeger with Docker: ```cli...

I have chosen the 2nd option - running Jaeger as a pod and adding the service.  I'll be doing some write-up about this tomorrow in case anyone wants to...

@staranto I haven't updated the README file yet, so in the meantime please refer to this [blog post](https://felipecruz.es/visualizing-kubernetes-events-with-kspan/).

@staranto Then it could be a communication issue between the `kspan` container and the Jaeger container. This communication happens through an internal service named `otlp-collector` in the `default` namespace. Have...

I see you're deploying the kspan related resources to a namespace named `monitoring`. Quoting @bboreham: > By default kspan will use otlp-collector.default:55680 Try instead applying the manifest in the default...

As a first approach, I see no harm grating `Pull (Read Only)` permissions to any registry bucket that belongs to the project: https://cloud.google.com/container-registry/docs/access-control#permissions_and_roles Nevertheless, perhaps you may find it interesting...

I'd be highly interested in knowing the reasoning behind why the need for the 3 extra empty commits. Humbly asking, what purpose do they serve?

FYI we have just seen this error when using Release Manager to deploy 2 components (Golang and Python) on the OCP4 cluster. At the end, we had to increase the...

Hi, Today I got a different user that made the mistake of including a whitespace just right before the 'c' character in the word `capabilities`: ```yaml # Uncomment (below) to...