Tim Hockin c8111709e5 Add an error matcher, convert 2 tests ...

I fixed up the TestValidateEndpointsCreate path to show the matcher
instead of manual origin checking.

I picked TestValidateTopologySpreadConstraints because it was the last
failing test on my screen when I changed on of the commonly hard-coded
error strings. I fixed exactly those validation errors that were needed
to make this test pass.  Some of the Origin values can be debated.

The `field/testing.Matcher` interface allows tests to configure the
criteria by which they want to match expected and actual errors.  The
hope is that everyone will use Origin for Invalid errors.

There's some collateral impact for tests which use exact-comparisons and
don't expect origins.  These are all candidates for using the matcher.

2025-02-28 08:36:26 -08:00

..

config

Add an error matcher, convert 2 tests

2025-02-28 08:36:26 -08:00

well_known_labels.go

Refactor service-proxy-name label

2019-01-29 11:28:35 -05:00