John Howard
John Howard
On mobile (android chrome, but probably just related to screen size) the "Trusted by" icons are all squished together. This is on preliminary cc @craigbox
This page doesn't mention you need to modify the ingress service to include a TCP port (or use demo profile)
I just went through all the docs in https://preliminary.istio.io/docs/ops/common-problems/ and I was never recommended to use `istioctl analyze`. This seems like a large gap, as this should be the first...
For example, diagram on https://preliminary.istio.io/latest/docs/ops/deployment/architecture/. These serve no purpose other than confusion at this point IMO. cc @craigbox
Opening this issue to track major changes in 1.22 we should call out, and track blogs we should write alongside the release Major changes in 1.22 * Ambient to beta...
``` panic: runtime error: integer divide by zero goroutine 1 [running]: github.com/felixge/fgprof.(*wallclockProfile).exportPprof(0xc000060780, 0x0, {0x4064a0?, 0xc000024480?, 0x793f40?}, {0x405ef7?, 0x0?, 0x793f40?}) /home/john/go/pkg/mod/github.com/felixge/[email protected]/fgprof.go:220 +0xca5 github.com/felixge/fgprof.(*wallclockProfile).Export(0xc1851b0ab68a5af0?, {0x64d2a0, 0xc000040118}, {0x5f0e8c?, 0x7b8353bcb108?}, 0x6?, {0xc0000addc8?, 0x40e1db?, 0x793f40?},...
Example: Flip EDS cluster to DNS, but make the new clsuter warming (like pointing to an invalid cert). Today, the EDS is wiped out and we instantly get 503 UH....
https://prow.istio.io/view/gs/istio-prow/logs/integ-assertion_istio_postsubmit/1774280229741662208. We get logs like `2024-03-31T03:48:39.160862Z WARN proxy{uid=7136ad06-c86c-4879-b89f-8eedd1377582}:outbound{id=c6448ce0a846e223caca1d2a903a4c2a}: ztunnel::proxy::outbound: failed dur=106.83µs err=unknown waypoint: unable to determine waypoint upstream`. Config dump seems ok, but not sure what the UID even is...
When a user runs `istioctl install --set compatibilityVersion` or `helm install --set compatibilityVersion`, we should display: "You set the compatibility version to . Please considering giving feedback on why at...