-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
What happened?
While upgrading to v2.3.0 we have faced issue on Kyverno side due to attempts to create same ingress url multiple times.
Investigating more, we found that this issue happens intermittently while application is on submitted state, so wanted to ask about that as we have not faced that on the older version from Google or maybe we are missing some config on the new deployment
Sample effect of this, is about lifecycle transitions because this conflict is preventing SparkApplication from transitioning from Submitted state to Running state ending up being zombie and not being Garbage collected after timeToLiveSeconds
Below are screenshots of where we have faced that
Reproduction Code
No response
Expected behavior
No response
Actual behavior
No response
Environment & Versions
- Kubernetes Version:
- Spark Operator Version:
- Apache Spark Version:
Additional context
No response
Impacted by this bug?
Give it a 👍 We prioritize the issues with most 👍