Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure Cache types.WatchKinds and proto.WatchEvents are in sync #11692

Merged
merged 7 commits into from
Apr 9, 2022

Conversation

rosstimothy
Copy link
Contributor

@rosstimothy rosstimothy commented Apr 4, 2022

This adds a test, TestCacheWatchKindExistsInEvents, that ensures
all types.WatchKind registered for all Cache components have a
corresponding proto.Event defined. By doing this we can ensure
that for a release there will be no resource type X is not suppported
errors causing the Cache to be unhealthy. Unfortunately this does not
prevent issues across releases which may have different resources being emitted.

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.
@github-actions github-actions bot requested review from r0mant and ravicious April 4, 2022 13:50
@rosstimothy
Copy link
Contributor Author

friendly ping @r0mant

@rosstimothy rosstimothy enabled auto-merge (squash) April 8, 2022 20:21
@rosstimothy rosstimothy merged commit f5d2542 into master Apr 9, 2022
@rosstimothy rosstimothy deleted the tross/cache_watchevents_sync branch April 9, 2022 14:34
rosstimothy added a commit that referenced this pull request Apr 13, 2022
…11692)

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.

(cherry picked from commit f5d2542)

# Conflicts:
#	api/client/streamwatcher.go
#	lib/auth/grpcserver.go
rosstimothy added a commit that referenced this pull request Apr 13, 2022
…11692)

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.

(cherry picked from commit f5d2542)

# Conflicts:
#	lib/auth/grpcserver.go
rosstimothy added a commit that referenced this pull request Apr 13, 2022
…11692)

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.

(cherry picked from commit f5d2542)
@rosstimothy
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
branch/v7
branch/v8
branch/v9

Questions ?

Please refer to the Backport tool documentation

rosstimothy added a commit that referenced this pull request Apr 15, 2022
…11692) (#11927)

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.

(cherry picked from commit f5d2542)
rosstimothy added a commit that referenced this pull request Apr 18, 2022
…11692) (#11926)

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.

(cherry picked from commit f5d2542)

# Conflicts:
#	lib/auth/grpcserver.go
rosstimothy added a commit that referenced this pull request Apr 19, 2022
…11692) (#11925)

This adds a test, `TestCacheWatchKindExistsInEvents`, that ensures
all `types.WatchKind` registered for all Cache components have a
corresponding `proto.Event` defined. By doing this we can ensure
that for a release there will be no `resource type X is not
suppported` errors causing the Cache to be unhealthy. Unfortunately
this does not prevent issues across releases which may have different
resources being emitted.

(cherry picked from commit f5d2542)

# Conflicts:
#	api/client/streamwatcher.go
#	lib/auth/grpcserver.go
@webvictim webvictim mentioned this pull request Apr 19, 2022
@webvictim webvictim mentioned this pull request Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants