Oliver Gould

Results 53 issues of Oliver Gould

We hit a panic in CI. It seems spurious, as re-running the workflow did not encounter the error: ```sh # shellcheck disable=SC2016 actionlint \ -format '{{range $err := .}}::error file={{$err.Filepath}},line={{$err.Line}},col={{$err.Column}}::{{$err.Message}}%0A```%0A{{replace...

bug

## Feature Request ### Motivation Tracing's default output is colorized. But when a program is not connected to a terminal, for instance because its output is redirected to a file...

kind/feature
crate/subscriber

policy-controller container builds frequently take 9+ minutes in CI (i.e. for integration tests, etc). This isn't so much a problem when doing a proper release, but it is an extremely...

area/build
priority/P1

The default Linkerd installation should be able to include authorization and authentication resources. The authentications would be useful to reuse in other installations inluding Linkerd extensions and application probe policies....

We have dozens (hundreds?) of "golden" files that we use in tests to compare against CLI-generated output. Any time our generated code changes, we simply regenerate all of these files....

priority/triage
area/test
rfc

The tracing test frequently fails with spurious errors like: ``` --- FAIL: TestTracing (179.94s) --- FAIL: TestTracing/expect_full_trace (120.03s) tracing_test.go:224: No trace found with processes: [nginx web emoji voting linkerd-proxy] FAIL...

help wanted
area/test
area/tracing

#8666 includes [logs] that show the destination controller serving redundant discovery updates roughly every 10 seconds (though sometimes up to 60s apart): ```logs [ 390.340324s] DEBUG ThreadId(01) outbound:accept{client.addr=10.244.7.14:50170}:proxy{addr=10.0.115.236:5432}:tcp: linkerd_proxy_discover::from_resolve: Changed...

area/controller
priority/triage

Hyper is planning a major 1.0 milestone that will impact many of their public APIs and, therefore, the proxy. We should get a better understanding of the planned changes so...

area/proxy
pinned

The various Linkerd subcommands that operate on kubernetes resources all work somewhat differently, and none of them support Kubernetes label selection. Anywhere where the `linkerd` CLI operates on a list...

help wanted
good first issue
area/cli
priority/P2

The name `steer` is pretty unintuitive. Personally, it makes me think of cattle. Perhaps we can rename it to something more concrete/descriptive in the next breaking release?