-
Environmental Info: Node(s) CPU architecture, OS, and Version: Cluster Configuration: Describe the bug: Steps To Reproduce:
Expected behavior: Actual behavior: }, Additional context / logs: Aug 11 17:21:51 ubunto8 k3s[2361]: time="2021-08-11T17:21:51.848879233Z" level=info msg="Cluster-Http-Server 2021/08/11 17:21:51 http: TLS handshake error from 50.64.28.166:56311: remote error: tls: unknown certificate authority" ============================ correct senario on v1.17.0+k3s.1 ============================ Aug 11 17:57:04 -ubunto8 k3s[11412]: I0811 17:57:04.292617 11412 reconciler.go:209] operationExecutor.VerifyControllerAttachedVolume started for volume "config" (UniqueName: "kubernetes.io/configmap/81ed8ccd-ccae-40c3-868d-b51a8e36eafa-config") pod "traefik-6787cddb4b-t6d4s" (UID: "81ed8ccd-ccae-40c3-868d-b51a8e36eafa") Backporting
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Support for Basic authentication (the thing that you're using with 1.17) has been removed from upstream Kubernetes since the 1.19 release. Note that this is not just deprecated or disabled, but deleted from the codebase: kubernetes/kubernetes#89069 |
Beta Was this translation helpful? Give feedback.
Support for Basic authentication (the thing that you're using with 1.17) has been removed from upstream Kubernetes since the 1.19 release. Note that this is not just deprecated or disabled, but deleted from the codebase: kubernetes/kubernetes#89069