About kubeadm initialization problem

[StephenJose-Dai]

Describe the issue

I am going to deploy kubernets. I used kubeadm to generate a default configuration file and modified it, but when I was ready to initialize it told me that it could not find a node called master. I confirmed that there was nothing wrong with my network. I tried to ping the node name and it communicated normally. I also used nslookup to get the IP address corresponding to the master node. I don't know why it has this error. I can't seem to find any articles that can help me solve this problem!
I am not using docker, but containerd！

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Aaina26]

I don't think this issue should be reported here. If you think this is a bug then you can report it in kubernetes/kubernetes. If this is a support request which I think it is, you can ask in Kubernetes slack community: https://kubernetes.slack.com/archives/C09NXKJKA

[StephenJose-Dai]

It seems that this channel is full and I cannot join it

[Aaina26]

Here is the invite link: http://slack.k8s.io/
For future reference see: https://github.com/kubernetes/community/tree/master/communication#discussions-happen-here