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
Describe the bug
Arguable a somewhat special edge case, but the introduction of DefaultOIDCDiscoveryBaseURL with its default value https://kubernetes.default.svc leads to a panic when trying to run the unit tests in a CI that runs in Kubernetes. I suspect that the initialization picks up that endpoint and can resolve it in-cluster and then tries to use it. Reason why I suspect this is that if you replace kubernetes.default.svc with something that cannot be resolved in-cluster, the test case does pass.
Describe the bug
Arguable a somewhat special edge case, but the introduction of
DefaultOIDCDiscoveryBaseURL
with its default valuehttps://kubernetes.default.svc
leads to a panic when trying to run the unit tests in a CI that runs in Kubernetes. I suspect that the initialization picks up that endpoint and can resolve it in-cluster and then tries to use it. Reason why I suspect this is that if you replacekubernetes.default.svc
with something that cannot be resolved in-cluster, the test case does pass.Expected behavior
Unit tests do run also in a Kubernetes provided containerized environment, if possible.
To Reproduce
Run unit tests inside a Kubernetes pod, e.g. Tekton setup.
Knative release version
v0.43.0
knative-v1.16.0
Additional context
n/a
The text was updated successfully, but these errors were encountered: