You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a subject in a SinkBinding that refers to either a non-podspecable resource (e.g. CronJob:batch/v1beta1) or a faulty resource describption (like Job:batch/v1beta1 instead of Job:batch/v1), then no error is returned, but the status of this binding remains:
Furthermore, this resource can not be deleted anymore, because the delete operation hangs forever. In addition, a namespace with this faulty sink binding can also not delete (the namespace sticks in "Terminating" status)
Expected behavior
I would expect:
A clear error indication describing that the subject specification is wrong. Either as part of the status conditions or, if possible, already by an admission controller when verifying the source.
It should be possible to delete such resource again.
To Reproduce
Steps to reproduce the behavior.
Just apply
apiVersion: sources.knative.dev/v1alpha1kind: SinkBindingmetadata:
name: bind-heartbeat-2spec:
subject:
apiVersion: batch/v1# This is wrong, should be Jobkind: CronJobselector:
matchLabels:
app: heartbeat-cronsink:
ref:
apiVersion: serving.knative.dev/v1kind: Servicename: edisplay
Knative release version
Eventing 0.12.0
Additional context
Tried on minikube
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
Describe the bug
When using a subject in a
SinkBinding
that refers to either a non-podspecable resource (e.g. CronJob:batch/v1beta1) or a faulty resource describption (like Job:batch/v1beta1 instead of Job:batch/v1), then no error is returned, but the status of this binding remains:Furthermore, this resource can not be deleted anymore, because the delete operation hangs forever. In addition, a namespace with this faulty sink binding can also not delete (the namespace sticks in "Terminating" status)
Expected behavior
I would expect:
To Reproduce
Steps to reproduce the behavior.
Just apply
Knative release version
Eventing 0.12.0
Additional context
Tried on minikube
The text was updated successfully, but these errors were encountered: