steeling
steeling
From #4863 collapse all of the k8s input/output methods/funcs onto the k8s.Client object. This includes any function that accepts a controller/client object as a parameter, as well as all of...
Using a workflow pipeline (like azure devops), we'd be able to automate the release pipeline, removing both manual toil, and potential error from human involvement. This is not an all...
"Interfaces should be defined by where they are consumed, not by where they are instantiated" ["The bigger the interface, the weaker the abstraction."](https://www.youtube.com/watch?v=PAAkCSZUG1c&t=5m17s) A k8s.Controller, doesn't need to know how...
Ok, not quite all, but a good start would be in the `pkg/` subdirectory. We can omit anything for `cmd/`, and `pkg/cli`. There's a lot of functions that take in...
Subtask of #4862 This isn't quite needed for *every* object type, but for some of the more complex objects it makes sense. The mesh catalog currently has 2 responsibilities: 1....
Subtask of #4862. Currently traffic policy objects are coupled with envoy configs in that they contain denormalized data, to more closely represent the envoy config. However, do to domain separation,...
[See motivation here](https://docs.google.com/document/d/1L_u-XlVU8Fog-uFS3Uf0O2nz8IArQy82cd6Npxm038Y/edit#) This issue will serve as the master issue for translating all Envoy config generation code to builders. There are 2 additional caveats to using builders: - [...
Right now the code is sort of in this mid-way state between allowing multiple meshes in a cluster, and having one mesh per cluster. Do we have a stance on...
With the pubsub used in the message broker, we allow for many publishers and many subscribers. In the current implementation, if a subscriber fails to read from its subscribed channel...
Phase 1 could simply be a boolean on egress that applies mTLS with the existing mesh certificate. The onus would be on users to distribute the root certs appropriately. Phase...