Applying config/all.yaml problem

[huasiy]

When I try to apply config.all.yaml, I get following error:
Error from server (Invalid): error when creating "config/all.yaml": Deployment.apps "manager" is invalid: spec.template.spec.containers[0].volumeMounts[2].name: Not found: "config-etcd"
I read all.yaml and find no volumes named config-etcd. How can I fix it?

k8s: v1.23
docker: v20.10.12

[lynnleelhl]

Try to remove the "config-etcd" part and see if it works

…

On Tue, Feb 1, 2022 at 14:59 huaway ***@***.***> wrote: When I try to apply config.all.yaml, I get following error: Error from server (Invalid): error when creating "config/all.yaml": Deployment.apps "manager" is invalid: spec.template.spec.containers[0].volumeMounts[2].name: Not found: "config-etcd" I read all.yaml and find no volumes named config-etcd. How can I fix it? k8s: v1.23 docker: v20.10.12 — Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOL2QKI3FYXHU2RINXWWVTUY6AGLANCNFSM5NIJZEHQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[huasiy]

I can apply all.yaml now. But I can't get pod manager work correctly. Here is what I get from kubectl get po -A:

kube-system   manager-79b44dc889-qczpl                   0/1     CrashLoopBackOff   7 (4m32s ago)   21m
kube-system   manager-79b44dc889-tf98d                   0/1     CrashLoopBackOff   8 (83s ago)     21m
kube-system   manager-79b44dc889-xkvts                   0/1     Pending            0               21m

I check one pod's log and get:

E0201 15:34:59.915878       1 manager.go:241] controller-runtime/manager "msg"="Failed to get API Group-Resources" "error"="Get \"https://10.0.0.77:6443/api?timeout=32s\": dial tcp 10.0.0.77:6443: connect: connection refused"
E0201 15:34:59.916116       1 main.go:119] setup "msg"="unable to set up overall controller manager" "error"="Get \"https://10.0.0.77:6443/api?timeout=32s\": dial tcp 10.0.0.77:6443: connect: connection refused"

[lynnleelhl]

The ip and port should point to your kubernetes api server, please follow the install manual.

…

On Tue, Feb 1, 2022 at 16:01 huaway ***@***.***> wrote: I can apply all.yaml now. But I can't get pod managet work correctly. Here is what I get from kubectl get po -A: kube-system manager-79b44dc889-qczpl 0/1 CrashLoopBackOff 7 (4m32s ago) 21m kube-system manager-79b44dc889-tf98d 0/1 CrashLoopBackOff 8 (83s ago) 21m kube-system manager-79b44dc889-xkvts 0/1 Pending 0 21m I check one pod's log and get: E0201 15:34:59.915878 1 manager.go:241] controller-runtime/manager "msg"="Failed to get API Group-Resources" "error"="Get \"https://10.0.0.77:6443/api?timeout=32s\": dial tcp 10.0.0.77:6443: connect: connection refused" E0201 15:34:59.916116 1 main.go:119] setup "msg"="unable to set up overall controller manager" "error"="Get \"https://10.0.0.77:6443/api?timeout=32s\": dial tcp 10.0.0.77:6443: connect: connection refused" — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOL2QP6IYETZYDIFYX5RBDUY6HOBANCNFSM5NIJZEHQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[huasiy]

Actually I modify all.yaml to fit version 1.23 of k8s. I put field subresorces, validation, additionalPrinterColumns of crd into field versions. Here is the file: all.txt.
When I apply it, it seems to create some resources correctly. But I get error. Here is the result after I run k apply -f all.yaml

Should I just ignore the error?