-
Notifications
You must be signed in to change notification settings - Fork 74
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
Watcher-to-API server insecure connection not working #616
Comments
@bilalbokharee I think you need to modify watcher deployment to use insecure mode. |
@khrm Thanks for the response I see this error in API server pod after removing volume and volumeMount from watcher deployment
|
You also need to remove |
You could create a kustomize overlay that adds the grpc |
Expected Behavior
After setting
-auth_mode
toinsecure
in watcher deployment, watcher communicates with API server with no auth required.Actual Behavior
After
insecure
is set, watcher pod stays inContainerCreating
state, with error messageMountVolume.SetUp failed for volume "tls" : secret "tekton-results-tls" not found
Once set to insecure, there is no need for container to get stuck in
ContainerCreating
, waiting for this volume to mount. It should be bypassed, allowing watcher to poll API server without auth required.This is based on results v0.8.0
The text was updated successfully, but these errors were encountered: