-
Notifications
You must be signed in to change notification settings - Fork 117
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
The same resource is duplicated in eventing-kafka-post-install and so on. #3347
Comments
This issue is stale because it has been open for 90 days with no |
Keep |
This issue is stale because it has been open for 90 days with no |
Keep |
This issue is stale because it has been open for 90 days with no |
/reopen |
@kahirokunn: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This issue is stale because it has been open for 90 days with no |
/reopen |
@kahirokunn: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Describe the bug
The same resource is duplicated in eventing-kafka-post-install and so on.
eg.
https://github.com/knative/operator/blob/ad01c40e1691cebaf5952a74bee975d01e3407f8/cmd/operator/kodata/eventing-source/1.10/kafka/eventing-kafka-post-install.yaml#L694
https://github.com/knative/operator/blob/ad01c40e1691cebaf5952a74bee975d01e3407f8/cmd/operator/kodata/eventing-source/1.10/kafka/eventing-kafka-post-install.yaml#L214
There are a total of eight duplicates.
Expected behavior
Unduplicated condition.
To Reproduce
Steps to reproduce the behavior.
Knative release version
The Knative version, where you find this issue.
Additional context
Add any other context about the problem here such as proposed priority
The text was updated successfully, but these errors were encountered: