-
Notifications
You must be signed in to change notification settings - Fork 219
Support Standard Kuberentes Resources not just CustomResource #678
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
# Conflicts: # operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/event/internal/CustomResourceEventSource.java
additinal fixes , renamings
# Conflicts: # operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/Cloner.java # operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java
...ework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ControllerConfiguration.java
Outdated
Show resolved
Hide resolved
…erator-sdk into support-non-cr
@@ -30,15 +30,14 @@ | |||
@Test | |||
public void testReconciliationOfNonCustomResourceAndStatusUpdate() { | |||
var deployment = operator.create(Deployment.class, testDeployment()); | |||
await().atMost(10, TimeUnit.SECONDS).untilAsserted(() -> { | |||
await().atMost(15, TimeUnit.SECONDS).untilAsserted(() -> { |
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.
Why is it taking longer now, though?
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.
trying something, just on one kubernetes version in tests sometimes fails. And it looks like for a timeout for retry after a conflict. But still working on it to figure it out
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 seems that the problem is with namespace deletion, not with the actual test logic.
No description provided.