kubernetes – Kubectl error: memcache.go:265] couldn’t get current …

September 6, 2025

Everything was running smoothly with my Kubernetes clusters until today: after performing an update on my Ubuntu system, I’m now unable to establish a connection from my working environment to the

https://stackoverflow.com/questions/76841889/kubectl-error-memcache-go265-couldn-t-get-current-server-api-group-list-get

kubernetes – Kubectl error: memcache.go:265] couldn’t get current … <body> <h1> Array ( [0] => jubernetes – kubectl error: memcache.go:265] couldn’t get current … [1] => mubernetes – kubectl error: memcache.go:265] couldn’t get current … [2] => lubernetes – kubectl error: memcache.go:265] couldn’t get current … [3] => oubernetes – kubectl error: memcache.go:265] couldn’t get current … [4] => iubernetes – kubectl error: memcache.go:265] couldn’t get current … [5] => kybernetes – kubectl error: memcache.go:265] couldn’t get current … [6] => khbernetes – kubectl error: memcache.go:265] couldn’t get current … [7] => kjbernetes – kubectl error: memcache.go:265] couldn’t get current … [8] => kibernetes – kubectl error: memcache.go:265] couldn’t get current … [9] => k8bernetes – kubectl error: memcache.go:265] couldn’t get current … [10] => k7bernetes – kubectl error: memcache.go:265] couldn’t get current … [11] => kuvernetes – kubectl error: memcache.go:265] couldn’t get current … [12] => kunernetes – kubectl error: memcache.go:265] couldn’t get current … [13] => kuhernetes – kubectl error: memcache.go:265] couldn’t get current … [14] => kugernetes – kubectl error: memcache.go:265] couldn’t get current … [15] => kubwrnetes – kubectl error: memcache.go:265] couldn’t get current … [16] => kubsrnetes – kubectl error: memcache.go:265] couldn’t get current … [17] => kubdrnetes – kubectl error: memcache.go:265] couldn’t get current … [18] => kubrrnetes – kubectl error: memcache.go:265] couldn’t get current … [19] => kub4rnetes – kubectl error: memcache.go:265] couldn’t get current … [20] => kub3rnetes – kubectl error: memcache.go:265] couldn’t get current … [21] => kubeenetes – kubectl error: memcache.go:265] couldn’t get current … [22] => kubednetes – kubectl error: memcache.go:265] couldn’t get current … [23] => kubefnetes – kubectl error: memcache.go:265] couldn’t get current … [24] => kubetnetes – kubectl error: memcache.go:265] couldn’t get current … [25] => kube5netes – kubectl error: memcache.go:265] couldn’t get current … [26] => kube4netes – kubectl error: memcache.go:265] couldn’t get current … [27] => kuberbetes – kubectl error: memcache.go:265] couldn’t get current … [28] => kubermetes – kubectl error: memcache.go:265] couldn’t get current … [29] => kuberjetes – kubectl error: memcache.go:265] couldn’t get current … [30] => kuberhetes – kubectl error: memcache.go:265] couldn’t get current … [31] => kubernwtes – kubectl error: memcache.go:265] couldn’t get current … [32] => kubernstes – kubectl error: memcache.go:265] couldn’t get current … [33] => kuberndtes – kubectl error: memcache.go:265] couldn’t get current … [34] => kubernrtes – kubectl error: memcache.go:265] couldn’t get current … [35] => kubern4tes – kubectl error: memcache.go:265] couldn’t get current … [36] => kubern3tes – kubectl error: memcache.go:265] couldn’t get current … [37] => kuberneres – kubectl error: memcache.go:265] couldn’t get current … [38] => kubernefes – kubectl error: memcache.go:265] couldn’t get current … [39] => kuberneges – kubectl error: memcache.go:265] couldn’t get current … [40] => kuberneyes – kubectl error: memcache.go:265] couldn’t get current … [41] => kuberne6es – kubectl error: memcache.go:265] couldn’t get current … [42] => kuberne5es – kubectl error: memcache.go:265] couldn’t get current … [43] => kubernetws – kubectl error: memcache.go:265] couldn’t get current … [44] => kubernetss – kubectl error: memcache.go:265] couldn’t get current … [45] => kubernetds – kubectl error: memcache.go:265] couldn’t get current … [46] => kubernetrs – kubectl error: memcache.go:265] couldn’t get current … [47] => kubernet4s – kubectl error: memcache.go:265] couldn’t get current … [48] => kubernet3s – kubectl error: memcache.go:265] couldn’t get current … [49] => kubernetea – kubectl error: memcache.go:265] couldn’t get current … [50] => kubernetez – kubectl error: memcache.go:265] couldn’t get current … [51] => kubernetex – kubectl error: memcache.go:265] couldn’t get current … [52] => kuberneted – kubectl error: memcache.go:265] couldn’t get current … [53] => kubernetee – kubectl error: memcache.go:265] couldn’t get current … [54] => kubernetew – kubectl error: memcache.go:265] couldn’t get current … [55] => kubernetes ᰫ kubectl error: memcache.go:265] couldn’t get current … [56] => kubernetes &#u211; kubectl error: memcache.go:265] couldn’t get current … [57] => kubernetes &#i211; kubectl error: memcache.go:265] couldn’t get current … [58] => kubernetes ⏻ kubectl error: memcache.go:265] couldn’t get current … [59] => kubernetes ᾯ kubectl error: memcache.go:265] couldn’t get current … [60] => kubernetes &#8q11; kubectl error: memcache.go:265] couldn’t get current … [61] => kubernetes &#8w11; kubectl error: memcache.go:265] couldn’t get current … [62] => kubernetes ⁷ kubectl error: memcache.go:265] couldn’t get current … [63] => kubernetes ” kubectl error: memcache.go:265] couldn’t get current … [64] => kubernetes &#82q1; kubectl error: memcache.go:265] couldn’t get current … [65] => kubernetes — kubectl error: memcache.go:265] couldn’t get current … [66] => kubernetes &#821q; kubectl error: memcache.go:265] couldn’t get current … [67] => kubernetes – jubectl error: memcache.go:265] couldn’t get current … [68] => kubernetes – mubectl error: memcache.go:265] couldn’t get current … [69] => kubernetes – lubectl error: memcache.go:265] couldn’t get current … [70] => kubernetes – oubectl error: memcache.go:265] couldn’t get current … [71] => kubernetes – iubectl error: memcache.go:265] couldn’t get current … [72] => kubernetes – kybectl error: memcache.go:265] couldn’t get current … [73] => kubernetes – khbectl error: memcache.go:265] couldn’t get current … [74] => kubernetes – kjbectl error: memcache.go:265] couldn’t get current … [75] => kubernetes – kibectl error: memcache.go:265] couldn’t get current … [76] => kubernetes – k8bectl error: memcache.go:265] couldn’t get current … [77] => kubernetes – k7bectl error: memcache.go:265] couldn’t get current … [78] => kubernetes – kuvectl error: memcache.go:265] couldn’t get current … [79] => kubernetes – kunectl error: memcache.go:265] couldn’t get current … [80] => kubernetes – kuhectl error: memcache.go:265] couldn’t get current … [81] => kubernetes – kugectl error: memcache.go:265] couldn’t get current … [82] => kubernetes – kubwctl error: memcache.go:265] couldn’t get current … [83] => kubernetes – kubsctl error: memcache.go:265] couldn’t get current … [84] => kubernetes – kubdctl error: memcache.go:265] couldn’t get current … [85] => kubernetes – kubrctl error: memcache.go:265] couldn’t get current … [86] => kubernetes – kub4ctl error: memcache.go:265] couldn’t get current … [87] => kubernetes – kub3ctl error: memcache.go:265] couldn’t get current … [88] => kubernetes – kubextl error: memcache.go:265] couldn’t get current … [89] => kubernetes – kubevtl error: memcache.go:265] couldn’t get current … [90] => kubernetes – kubeftl error: memcache.go:265] couldn’t get current … [91] => kubernetes – kubedtl error: memcache.go:265] couldn’t get current … [92] => kubernetes – kubecrl error: memcache.go:265] couldn’t get current … [93] => kubernetes – kubecfl error: memcache.go:265] couldn’t get current … [94] => kubernetes – kubecgl error: memcache.go:265] couldn’t get current … [95] => kubernetes – kubecyl error: memcache.go:265] couldn’t get current … [96] => kubernetes – kubec6l error: memcache.go:265] couldn’t get current … [97] => kubernetes – kubec5l error: memcache.go:265] couldn’t get current … [98] => kubernetes – kubectk error: memcache.go:265] couldn’t get current … [99] => kubernetes – kubectp error: memcache.go:265] couldn’t get current … [100] => kubernetes – kubecto error: memcache.go:265] couldn’t get current … [101] => kubernetes – kubectl wrror: memcache.go:265] couldn’t get current … [102] => kubernetes – kubectl srror: memcache.go:265] couldn’t get current … [103] => kubernetes – kubectl drror: memcache.go:265] couldn’t get current … [104] => kubernetes – kubectl rrror: memcache.go:265] couldn’t get current … [105] => kubernetes – kubectl 4rror: memcache.go:265] couldn’t get current … [106] => kubernetes – kubectl 3rror: memcache.go:265] couldn’t get current … [107] => kubernetes – kubectl eeror: memcache.go:265] couldn’t get current … [108] => kubernetes – kubectl edror: memcache.go:265] couldn’t get current … [109] => kubernetes – kubectl efror: memcache.go:265] couldn’t get current … [110] => kubernetes – kubectl etror: memcache.go:265] couldn’t get current … [111] => kubernetes – kubectl e5ror: memcache.go:265] couldn’t get current … [112] => kubernetes – kubectl e4ror: memcache.go:265] couldn’t get current … [113] => kubernetes – kubectl ereor: memcache.go:265] couldn’t get current … [114] => kubernetes – kubectl erdor: memcache.go:265] couldn’t get current … [115] => kubernetes – kubectl erfor: memcache.go:265] couldn’t get current … [116] => kubernetes – kubectl ertor: memcache.go:265] couldn’t get current … [117] => kubernetes – kubectl er5or: memcache.go:265] couldn’t get current … [118] => kubernetes – kubectl er4or: memcache.go:265] couldn’t get current … [119] => kubernetes – kubectl errir: memcache.go:265] couldn’t get current … [120] => kubernetes – kubectl errkr: memcache.go:265] couldn’t get current … [121] => kubernetes – kubectl errlr: memcache.go:265] couldn’t get current … [122] => kubernetes – kubectl errpr: memcache.go:265] couldn’t get current … [123] => kubernetes – kubectl err0r: memcache.go:265] couldn’t get current … [124] => kubernetes – kubectl err9r: memcache.go:265] couldn’t get current … [125] => kubernetes – kubectl erroe: memcache.go:265] couldn’t get current … [126] => kubernetes – kubectl errod: memcache.go:265] couldn’t get current … [127] => kubernetes – kubectl errof: memcache.go:265] couldn’t get current … [128] => kubernetes – kubectl errot: memcache.go:265] couldn’t get current … [129] => kubernetes – kubectl erro5: memcache.go:265] couldn’t get current … [130] => kubernetes – kubectl erro4: memcache.go:265] couldn’t get current … [131] => kubernetes – kubectl error: nemcache.go:265] couldn’t get current … [132] => kubernetes – kubectl error: kemcache.go:265] couldn’t get current … [133] => kubernetes – kubectl error: jemcache.go:265] couldn’t get current … [134] => kubernetes – kubectl error: mwmcache.go:265] couldn’t get current … [135] => kubernetes – kubectl error: msmcache.go:265] couldn’t get current … [136] => kubernetes – kubectl error: mdmcache.go:265] couldn’t get current … [137] => kubernetes – kubectl error: mrmcache.go:265] couldn’t get current … [138] => kubernetes – kubectl error: m4mcache.go:265] couldn’t get current … [139] => kubernetes – kubectl error: m3mcache.go:265] couldn’t get current … [140] => kubernetes – kubectl error: mencache.go:265] couldn’t get current … [141] => kubernetes – kubectl error: mekcache.go:265] couldn’t get current … [142] => kubernetes – kubectl error: mejcache.go:265] couldn’t get current … [143] => kubernetes – kubectl error: memxache.go:265] couldn’t get current … [144] => kubernetes – kubectl error: memvache.go:265] couldn’t get current … [145] => kubernetes – kubectl error: memfache.go:265] couldn’t get current … [146] => kubernetes – kubectl error: memdache.go:265] couldn’t get current … [147] => kubernetes – kubectl error: memczche.go:265] couldn’t get current … [148] => kubernetes – kubectl error: memcsche.go:265] couldn’t get current … [149] => kubernetes – kubectl error: memcwche.go:265] couldn’t get current … [150] => kubernetes – kubectl error: memcqche.go:265] couldn’t get current … [151] => kubernetes – kubectl error: memcaxhe.go:265] couldn’t get current … [152] => kubernetes – kubectl error: memcavhe.go:265] couldn’t get current … [153] => kubernetes – kubectl error: memcafhe.go:265] couldn’t get current … [154] => kubernetes – kubectl error: memcadhe.go:265] couldn’t get current … [155] => kubernetes – kubectl error: memcacge.go:265] couldn’t get current … [156] => kubernetes – kubectl error: memcacbe.go:265] couldn’t get current … [157] => kubernetes – kubectl error: memcacne.go:265] couldn’t get current … [158] => kubernetes – kubectl error: memcacje.go:265] couldn’t get current … [159] => kubernetes – kubectl error: memcacue.go:265] couldn’t get current … [160] => kubernetes – kubectl error: memcacye.go:265] couldn’t get current … [161] => kubernetes – kubectl error: memcachw.go:265] couldn’t get current … [162] => kubernetes – kubectl error: memcachs.go:265] couldn’t get current … [163] => kubernetes – kubectl error: memcachd.go:265] couldn’t get current … [164] => kubernetes – kubectl error: memcachr.go:265] couldn’t get current … [165] => kubernetes – kubectl error: memcach4.go:265] couldn’t get current … [166] => kubernetes – kubectl error: memcach3.go:265] couldn’t get current … [167] => kubernetes – kubectl error: memcache,go:265] couldn’t get current … [168] => kubernetes – kubectl error: memcachelgo:265] couldn’t get current … [169] => kubernetes – kubectl error: memcache;go:265] couldn’t get current … [170] => kubernetes – kubectl error: memcache/go:265] couldn’t get current … [171] => kubernetes – kubectl error: memcache.fo:265] couldn’t get current … [172] => kubernetes – kubectl error: memcache.vo:265] couldn’t get current … [173] => kubernetes – kubectl error: memcache.bo:265] couldn’t get current … [174] => kubernetes – kubectl error: memcache.ho:265] couldn’t get current … [175] => kubernetes – kubectl error: memcache.yo:265] couldn’t get current … [176] => kubernetes – kubectl error: memcache.to:265] couldn’t get current … [177] => kubernetes – kubectl error: memcache.gi:265] couldn’t get current … [178] => kubernetes – kubectl error: memcache.gk:265] couldn’t get current … [179] => kubernetes – kubectl error: memcache.gl:265] couldn’t get current … [180] => kubernetes – kubectl error: memcache.gp:265] couldn’t get current … [181] => kubernetes – kubectl error: memcache.g0:265] couldn’t get current … [182] => kubernetes – kubectl error: memcache.g9:265] couldn’t get current … [183] => kubernetes – kubectl error: memcache.go:165] couldn’t get current … [184] => kubernetes – kubectl error: memcache.go:q65] couldn’t get current … [185] => kubernetes – kubectl error: memcache.go:w65] couldn’t get current … [186] => kubernetes – kubectl error: memcache.go:365] couldn’t get current … [187] => kubernetes – kubectl error: memcache.go:255] couldn’t get current … [188] => kubernetes – kubectl error: memcache.go:2t5] couldn’t get current … [189] => kubernetes – kubectl error: memcache.go:2y5] couldn’t get current … [190] => kubernetes – kubectl error: memcache.go:275] couldn’t get current … [191] => kubernetes – kubectl error: memcache.go:264] couldn’t get current … [192] => kubernetes – kubectl error: memcache.go:26r] couldn’t get current … [193] => kubernetes – kubectl error: memcache.go:26t] couldn’t get current … [194] => kubernetes – kubectl error: memcache.go:266] couldn’t get current … [195] => kubernetes – kubectl error: memcache.go:265] xouldn’t get current … [196] => kubernetes – kubectl error: memcache.go:265] vouldn’t get current … [197] => kubernetes – kubectl error: memcache.go:265] fouldn’t get current … [198] => kubernetes – kubectl error: memcache.go:265] douldn’t get current … [199] => kubernetes – kubectl error: memcache.go:265] ciuldn’t get current … [200] => kubernetes – kubectl error: memcache.go:265] ckuldn’t get current … [201] => kubernetes – kubectl error: memcache.go:265] cluldn’t get current … [202] => kubernetes – kubectl error: memcache.go:265] cpuldn’t get current … [203] => kubernetes – kubectl error: memcache.go:265] c0uldn’t get current … [204] => kubernetes – kubectl error: memcache.go:265] c9uldn’t get current … [205] => kubernetes – kubectl error: memcache.go:265] coyldn’t get current … [206] => kubernetes – kubectl error: memcache.go:265] cohldn’t get current … [207] => kubernetes – kubectl error: memcache.go:265] cojldn’t get current … [208] => kubernetes – kubectl error: memcache.go:265] coildn’t get current … [209] => kubernetes – kubectl error: memcache.go:265] co8ldn’t get current … [210] => kubernetes – kubectl error: memcache.go:265] co7ldn’t get current … [211] => kubernetes – kubectl error: memcache.go:265] coukdn’t get current … [212] => kubernetes – kubectl error: memcache.go:265] coupdn’t get current … [213] => kubernetes – kubectl error: memcache.go:265] couodn’t get current … [214] => kubernetes – kubectl error: memcache.go:265] coulsn’t get current … [215] => kubernetes – kubectl error: memcache.go:265] coulxn’t get current … [216] => kubernetes – kubectl error: memcache.go:265] coulcn’t get current … [217] => kubernetes – kubectl error: memcache.go:265] coulfn’t get current … [218] => kubernetes – kubectl error: memcache.go:265] coulrn’t get current … [219] => kubernetes – kubectl error: memcache.go:265] coulen’t get current … [220] => kubernetes – kubectl error: memcache.go:265] couldb’t get current … [221] => kubernetes – kubectl error: memcache.go:265] couldm’t get current … [222] => kubernetes – kubectl error: memcache.go:265] couldj’t get current … [223] => kubernetes – kubectl error: memcache.go:265] couldh’t get current … [224] => kubernetes – kubectl error: memcache.go:265] couldn’r get current … [225] => kubernetes – kubectl error: memcache.go:265] couldn’f get current … [226] => kubernetes – kubectl error: memcache.go:265] couldn’g get current … [227] => kubernetes – kubectl error: memcache.go:265] couldn’y get current … [228] => kubernetes – kubectl error: memcache.go:265] couldn’6 get current … [229] => kubernetes – kubectl error: memcache.go:265] couldn’5 get current … [230] => kubernetes – kubectl error: memcache.go:265] couldn’t fet current … [231] => kubernetes – kubectl error: memcache.go:265] couldn’t vet current … [232] => kubernetes – kubectl error: memcache.go:265] couldn’t bet current … [233] => kubernetes – kubectl error: memcache.go:265] couldn’t het current … [234] => kubernetes – kubectl error: memcache.go:265] couldn’t yet current … [235] => kubernetes – kubectl error: memcache.go:265] couldn’t tet current … [236] => kubernetes – kubectl error: memcache.go:265] couldn’t gwt current … [237] => kubernetes – kubectl error: memcache.go:265] couldn’t gst current … [238] => kubernetes – kubectl error: memcache.go:265] couldn’t gdt current … [239] => kubernetes – kubectl error: memcache.go:265] couldn’t grt current … [240] => kubernetes – kubectl error: memcache.go:265] couldn’t g4t current … [241] => kubernetes – kubectl error: memcache.go:265] couldn’t g3t current … [242] => kubernetes – kubectl error: memcache.go:265] couldn’t ger current … [243] => kubernetes – kubectl error: memcache.go:265] couldn’t gef current … [244] => kubernetes – kubectl error: memcache.go:265] couldn’t geg current … [245] => kubernetes – kubectl error: memcache.go:265] couldn’t gey current … [246] => kubernetes – kubectl error: memcache.go:265] couldn’t ge6 current … [247] => kubernetes – kubectl error: memcache.go:265] couldn’t ge5 current … [248] => kubernetes – kubectl error: memcache.go:265] couldn’t get xurrent … [249] => kubernetes – kubectl error: memcache.go:265] couldn’t get vurrent … [250] => kubernetes – kubectl error: memcache.go:265] couldn’t get furrent … [251] => kubernetes – kubectl error: memcache.go:265] couldn’t get durrent … [252] => kubernetes – kubectl error: memcache.go:265] couldn’t get cyrrent … [253] => kubernetes – kubectl error: memcache.go:265] couldn’t get chrrent … [254] => kubernetes – kubectl error: memcache.go:265] couldn’t get cjrrent … [255] => kubernetes – kubectl error: memcache.go:265] couldn’t get cirrent … [256] => kubernetes – kubectl error: memcache.go:265] couldn’t get c8rrent … [257] => kubernetes – kubectl error: memcache.go:265] couldn’t get c7rrent … [258] => kubernetes – kubectl error: memcache.go:265] couldn’t get cuerent … [259] => kubernetes – kubectl error: memcache.go:265] couldn’t get cudrent … [260] => kubernetes – kubectl error: memcache.go:265] couldn’t get cufrent … [261] => kubernetes – kubectl error: memcache.go:265] couldn’t get cutrent … [262] => kubernetes – kubectl error: memcache.go:265] couldn’t get cu5rent … [263] => kubernetes – kubectl error: memcache.go:265] couldn’t get cu4rent … [264] => kubernetes – kubectl error: memcache.go:265] couldn’t get cureent … [265] => kubernetes – kubectl error: memcache.go:265] couldn’t get curdent … [266] => kubernetes – kubectl error: memcache.go:265] couldn’t get curfent … [267] => kubernetes – kubectl error: memcache.go:265] couldn’t get curtent … [268] => kubernetes – kubectl error: memcache.go:265] couldn’t get cur5ent … [269] => kubernetes – kubectl error: memcache.go:265] couldn’t get cur4ent … [270] => kubernetes – kubectl error: memcache.go:265] couldn’t get currwnt … [271] => kubernetes – kubectl error: memcache.go:265] couldn’t get currsnt … [272] => kubernetes – kubectl error: memcache.go:265] couldn’t get currdnt … [273] => kubernetes – kubectl error: memcache.go:265] couldn’t get currrnt … [274] => kubernetes – kubectl error: memcache.go:265] couldn’t get curr4nt … [275] => kubernetes – kubectl error: memcache.go:265] couldn’t get curr3nt … [276] => kubernetes – kubectl error: memcache.go:265] couldn’t get currebt … [277] => kubernetes – kubectl error: memcache.go:265] couldn’t get curremt … [278] => kubernetes – kubectl error: memcache.go:265] couldn’t get currejt … [279] => kubernetes – kubectl error: memcache.go:265] couldn’t get curreht … [280] => kubernetes – kubectl error: memcache.go:265] couldn’t get currenr … [281] => kubernetes – kubectl error: memcache.go:265] couldn’t get currenf … [282] => kubernetes – kubectl error: memcache.go:265] couldn’t get curreng … [283] => kubernetes – kubectl error: memcache.go:265] couldn’t get curreny … [284] => kubernetes – kubectl error: memcache.go:265] couldn’t get curren6 … [285] => kubernetes – kubectl error: memcache.go:265] couldn’t get curren5 … [286] => kubernetes – kubectl error: memcache.go:265] couldn’t get current ᰾ [287] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#u230; [288] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#i230; [289] => kubernetes – kubectl error: memcache.go:265] couldn’t get current ␎ [290] => kubernetes – kubectl error: memcache.go:265] couldn’t get current ῂ [291] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#8q30; [292] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#8w30; [293] => kubernetes – kubectl error: memcache.go:265] couldn’t get current ₊ [294] => kubernetes – kubectl error: memcache.go:265] couldn’t get current “ [295] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#82w0; [296] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#82e0; [297] => kubernetes – kubectl error: memcache.go:265] couldn’t get current ‰ [298] => kubernetes – kubectl error: memcache.go:265] couldn’t get current   [299] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#823o; [300] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#823p; [301] => kubernetes – kubectl error: memcache.go:265] couldn’t get current &#823-; ) https://clipperroutesevere.com/kdjbw4ywu?key=a54852e5dee5f9fa314d768d692142d1 </h1> </body>