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

[BUG] warning of hostname in mount pod creating #1137

Open
zwwhdls opened this issue Oct 10, 2024 · 2 comments
Open

[BUG] warning of hostname in mount pod creating #1137

zwwhdls opened this issue Oct 10, 2024 · 2 comments
Labels
kind/bug Something isn't working

Comments

@zwwhdls
Copy link
Member

zwwhdls commented Oct 10, 2024

What happened:
W1010 07:28:19.409275 7 warnings.go:70] metadata.name: this is used in the Pod's hostname, which can result in surprising behavior; a DNS label is recommended: [must be no more than 63 characters]

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?

Environment:

  • JuiceFS CSI Driver version (which image tag did your CSI Driver use):
  • Kubernetes version (e.g. kubectl version):
  • Object storage (cloud provider and region):
  • Metadata engine info (version, cloud provider managed or self maintained):
  • Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
  • Others:
@zwwhdls zwwhdls added the kind/bug Something isn't working label Oct 10, 2024
@zxh326
Copy link
Member

zxh326 commented Oct 10, 2024

fixed by #1043 ?

@zwwhdls
Copy link
Member Author

zwwhdls commented Oct 10, 2024

issue is still here

@zwwhdls zwwhdls changed the title [BUG] warning if using metadata.name to be hostname [BUG] warning in mount pod creating Oct 10, 2024
@zwwhdls zwwhdls changed the title [BUG] warning in mount pod creating [BUG] warning of hostname in mount pod creating Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants