Mastodon

Mike Williamson<a href="https://infosec.exchange/tags/Kiali" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kiali</a> 2.0 for <a href="https://infosec.exchange/tags/Istio" class="mention hashtag" rel="nofollow noopener" target="_blank">#Istio</a> Gateway API support, new graphs, ambient support and lots more.<a href="https://infosec.exchange/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://medium.com/kialiproject/kiali-2-0-for-istio-2087810f337e" rel="nofollow noopener" translate="no" target="_blank">https://medium.com/kialiproject/kiali-2-0-for-istio-2087810f337e</a>

Markus EiseleKiali setup in Red Hat Developer Hub <a href="https://medium.com/kialiproject/kiali-setup-in-red-hat-developer-hub-57502ea8b988" target="_blank" rel="nofollow noopener" translate="no">https://medium.com/kialiproject/kiali-setup-in-red-hat-developer-hub-57502ea8b988</a> <a href="https://mastodon.online/tags/rhdh" class="mention hashtag" rel="tag">#rhdh</a> <a href="https://mastodon.online/tags/Backstage" class="mention hashtag" rel="tag">#Backstage</a> <a href="https://mastodon.online/tags/kiali" class="mention hashtag" rel="tag">#kiali</a> <a href="https://mastodon.online/tags/redhat" class="mention hashtag" rel="tag">#redhat</a>

Luca De PandisSo things are getting bad, and <a href="https://bsd.network/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> is being considered more complex to manage and more costly. I have to admit that while I really believed in the cloud, the problems that my customers were facing started to break my beliefs. Ops costs increased, because they still hired the IT guy, but now a <a href="https://bsd.network/tags/SiteReliabilityEngineer" class="mention hashtag" rel="nofollow noopener" target="_blank">#SiteReliabilityEngineer</a> costs way more than a traditional <a href="https://bsd.network/tags/SystemAdministrator" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemAdministrator</a>, and often he has an <a href="https://bsd.network/tags/infra" class="mention hashtag" rel="nofollow noopener" target="_blank">#infra</a> knowledge way inferior, since everything is not in house anymore. Everything is hosted and you don't access to the technology internals anymore. Also, they are dealing with a level of complexity unheard of. Before the cloud there were only physical and virtualized layers of complexity. Now we also have then <a href="https://bsd.network/tags/containerorchestration" class="mention hashtag" rel="nofollow noopener" target="_blank">#containerorchestration</a> and <a href="https://bsd.network/tags/servicemesh" class="mention hashtag" rel="nofollow noopener" target="_blank">#servicemesh</a> layers. We moved from putting a stupid <a href="https://bsd.network/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a> class in classpath to run <a href="https://bsd.network/tags/JBoss" class="mention hashtag" rel="nofollow noopener" target="_blank">#JBoss</a> with the <a href="https://bsd.network/tags/APM" class="mention hashtag" rel="nofollow noopener" target="_blank">#APM</a> profiling to running <a href="https://bsd.network/tags/Prometheus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Prometheus</a>, <a href="https://bsd.network/tags/Grafana" class="mention hashtag" rel="nofollow noopener" target="_blank">#Grafana</a>, <a href="https://bsd.network/tags/Jaeger" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jaeger</a> and <a href="https://bsd.network/tags/Kiali" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kiali</a> to obtain the same level of informations.The only good thing is that now in Linux engineers are using <a href="https://bsd.network/tags/eBPF" class="mention hashtag" rel="nofollow noopener" target="_blank">#eBPF</a> to profiling network and software execution. But this is NOT innovation at all. You could do that already with <a href="https://bsd.network/tags/DTrace" class="mention hashtag" rel="nofollow noopener" target="_blank">#DTrace</a> in <a href="https://bsd.network/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solaris</a> and <a href="https://bsd.network/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> with way less complexity, and the same level of profiling since <a href="https://bsd.network/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a>, <a href="https://bsd.network/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ruby</a> and lot of frameworks included its probes to support advanced tracing. Apple's <a href="https://bsd.network/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> used to provide a good <a href="https://bsd.network/tags/DTrace" class="mention hashtag" rel="nofollow noopener" target="_blank">#DTrace</a> frontend called <a href="https://bsd.network/tags/Instruments" class="mention hashtag" rel="nofollow noopener" target="_blank">#Instruments</a> that was really cool to work with.<a href="https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0" rel="nofollow noopener" target="_blank">https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0</a>

Recent searches

Search options

Administered by:

Server stats:

#kiali