You may observe some strange behavior when running "kubectl log" commands in Konvoy 1.X, including (but not limited to) timeouts, unexpected outputs, and follow sessions being broken (kubectl logs -f).
Issues of this nature may be difficult to troubleshoot because there are no specific error outputs to refer to.
However, we have observed that some users have had success with upgrading their kube-oidc-proxy version to address this known issue:
https://github.com/jetstack/kube-oidc-proxy/issues/135
As of this writing, the kube-oidc-proxy version in Konvoy 1.X is 0.2.0. To upgrade to 0.3.0 you can edit the "kube-oidc-proxy" section of the "addons" block of your cluster.yaml:
- name: kube-oidc-proxy
enabled: true
values: |
---
image:
tag: v0.3.0
To apply this change, run "./konvoy deploy addons".
If you are experiencing similar symptoms, and upgrading your kube-oidc-proxy version does not resolve it, please feel free to submit a support ticket and we'll be happy to help:
https://support.d2iq.com/hc/en-us/articles/4408231804564