-
Notifications
You must be signed in to change notification settings - Fork 218
improve: blocklist of problematic resources for previous version annotation #2774
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
Conversation
...ramework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java
Outdated
Show resolved
Hide resolved
* | ||
* @return blocklist of resource classes where the previous version annotation won't be used. | ||
*/ | ||
default List<Class<? extends HasMetadata>> previousAnnotationUsageBlocklist() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest also documenting the default implementation in the javadoc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure that is needed / that helpful since users can just open the code and see the defaults, also we don't do it for other configs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would make more sense, though, is to explain what is the consequence for a resource type to be in the block list because this isn't clear at all and people might be hesitant adding a resource to the block list without more details of what happens when they do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, this should probably be a set rather than a list as the order is meaningless whereas we only want one instance of a given resource type in this collection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Explained the consequence and changed it to set, thank you!
* | ||
* @return blocklist of resource classes where the previous version annotation won't be used. | ||
*/ | ||
default List<Class<? extends HasMetadata>> previousAnnotationUsageBlocklist() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would make more sense, though, is to explain what is the consequence for a resource type to be in the block list because this isn't clear at all and people might be hesitant adding a resource to the block list without more details of what happens when they do.
* @return blocklist of resource classes where the previous version annotation won't be used. | ||
*/ | ||
default List<Class<? extends HasMetadata>> previousAnnotationUsageBlocklist() { | ||
return List.of(Deployment.class, StatefulSet.class); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another aspect is whether or not these 2 classes should always be added to the block list regardless of what the user might set this list to (i.e. what is returned by this method should be added to the default list, not replace it completely).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those should not be always added, if the user is sure that the matcher is right those can be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I understand. From what I understand, Deployment and StatefulSet are always problematic for the matcher, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, only if it uses fields that are normalized later by the API, (and maybe if some defaults filled in, not sure about that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the light of this, it is debatable if those resource should be opt-in or opt-out. WDYT?
* | ||
* @return blocklist of resource classes where the previous version annotation won't be used. | ||
*/ | ||
default List<Class<? extends HasMetadata>> previousAnnotationUsageBlocklist() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, this should probably be a set rather than a list as the order is meaningless whereas we only want one instance of a given resource type in this collection.
@@ -188,6 +190,12 @@ public ConfigurationServiceOverrider withCloneSecondaryResourcesWhenGettingFromC | |||
return this; | |||
} | |||
|
|||
public ConfigurationServiceOverrider previousAnnotationUsageBlocklist( | |||
List<Class<? extends HasMetadata>> previousAnnotationUsageBlacklist) { | |||
this.previousAnnotationUsageBlocklist = previousAnnotationUsageBlacklist; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the previous comment on how this should probably be adding to the default set rather than completely replace it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Responded above.
.build(); | ||
} | ||
|
||
// for testing purposes replicating the matching logic but with the special matcher |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should use the configuration option from #2760 instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If that is merged, can change it (might be a new PR). thx!
LocallyRunOperatorExtension.builder() | ||
// Removing resource from blocklist List would result in test failure | ||
// .withConfigurationService( | ||
// o -> o.previousAnnotationUsageBlocklist(Collections.emptyList())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a new test then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It could be an additional test, I did not add that since I did not find it important to show that something is not working.
@metacosm are there any other concerns or we can merge this? |
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros <[email protected]>
228f8d2
to
7a1902b
Compare
Signed-off-by: Chris Laprun <[email protected]>
Signed-off-by: Chris Laprun <[email protected]>
@@ -474,7 +474,8 @@ default boolean previousAnnotationForDependentResourcesEventFiltering() { | |||
* | |||
* @return a Set of resource classes where the previous version annotation won't be used. | |||
*/ | |||
default Set<Class<? extends HasMetadata>> previousAnnotationUsageBlocklist() { | |||
default Set<Class<? extends HasMetadata>> | |||
previousAnnotationForDependentResourcesEventFilteringBlocklist() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine to have also with shorter form and keep it consistent. (withPreviousAnnotationForDependentResourcesBlocklist)
Signed-off-by: Attila Mészáros <[email protected]>
Signed-off-by: Attila Mészáros [email protected]