M. Mert Yildiran
M. Mert Yildiran
@remover thank you for reporting this issue. What's your Kubernetes server version? (`kubectl version`)
> > @remover thank you for reporting this issue. What's your Kubernetes server version? (`kubectl version`) > > ``` > ╰─$ kubectl version > Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e",...
> it does if i pass a context: `kubectl --context=dt version` > > ``` > Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"darwin/amd64"} > Server Version: version.Info{Major:"1",...
@remover in the mean time, you might want to try to set the kubeconfig context to your desired name: ``` kubectl config set-context NAME [--cluster=cluster_nickname] [--user=user_nickname] [--namespace=namespace] ``` and see...
@ittaigilat-cx thank you so much for reporting the issue! When I look at the logs, I see the error below in `default.mizu-api-server.basenine.log` file: ``` 2022/08/02 11:22:37 Basenine Community (Version: 0.8.3)...
@ittaigilat-cx how many users simultaneously use Mizu? Because each ongoing query stream maintains an open file in Basenine. Although the error happens in the very beginning of the program: https://github.com/up9inc/basenine/blob/main/server/server.go#L61...
@funwillis by looking at the logs, I see that the tapper DaemonSets were unable to establish the WebSocket connection to the API Server pod at `ws://mizu-api-server.mizu.svc.cluster.local/wsTapper` address. Since the API...
> @funwillis by looking at the logs, I see that the tapper DaemonSets were unable to establish the WebSocket connection to the API Server pod at `ws://mizu-api-server.mizu.svc.cluster.local/wsTapper` address. Since the...
@funwillis I think @gadotroee asked you to try on K8s instead of Rancher and asked for sharing the logs from the K8s deployment of the same configuration.
@funwillis OK we made sure that it's not a name resolution error. Is the HTTP request that you make encrypted using Transport Layer Security (TLS) for example? or through service...