Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge pull request #942 from neiljerram/fix-node-name-var #943

Merged

Conversation

nelljerram
Copy link
Member

@nelljerram nelljerram commented Sep 1, 2020

Revert accidental change from KUBERNETES_NODE_NAME to NODENAME

Description

Todos

  • Tests
  • Documentation
  • Release note

Release Note

Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname

Revert accidental change from KUBERNETES_NODE_NAME to NODENAME
@jhughes2112
Copy link

Question, was this the reason why (on AWS, for example) if the $HOSTNAME would return "ip-x-y-z-w" but the node name was joined as "ip-x-y-z-w.ec2.internal", nodes would fail partway through joining? I had to work around this by forcing the short-name of AWS boxes to be the FQDN. Can I revert that if I update?

@bootc
Copy link

bootc commented Sep 15, 2020

Yes, that sounds like the issue I ran into: not on AWS but the symptoms are similar. You'll find that pods are created and scheduled on the node but can't actually start. This only affects Calico 3.16.0 though; 3.15 and lower were not affected, and fixed in 3.16.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants