We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Sometimes the endpoint running in kubernetes will generate worker pods with the same name.
For example:
# minikube kubectl get pods NAME READY STATUS RESTARTS AGE funcx-1632329996841 1/1 Running 0 4m3s funcx-1632329998841 1/1 Running 0 4m2s funcx-1632330007842 1/1 Running 0 3m53s funcx-endpoint-86756c48c8-nc7r2 1/1 Running 2 (10m ago) 12m
This is because the pods are named after the current millisecond, which is not a unique ID.
This makes referring to those pods awkward on the commandline.
crossref this bug this is forked from: Parsl/parsl#1122
To Reproduce
Get the endpoint to launch two pods in the same millisecond.
Expected behavior Distinct pods should have distinct names.
Environment my own minikube on ubuntu
The text was updated successfully, but these errors were encountered:
The forked KubernetesProvider is now deprecated, and Parsl/parsl#3639 addresses this issue for Parsl's KubernetesProvider.
KubernetesProvider
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Sometimes the endpoint running in kubernetes will generate worker pods with the same name.
For example:
This is because the pods are named after the current millisecond, which is not a unique ID.
This makes referring to those pods awkward on the commandline.
crossref this bug this is forked from: Parsl/parsl#1122
To Reproduce
Get the endpoint to launch two pods in the same millisecond.
Expected behavior
Distinct pods should have distinct names.
Environment
my own minikube on ubuntu
The text was updated successfully, but these errors were encountered: