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

k8s cluster totally not work after helm uninstall volcano #2191

Closed
pengyuan opened this issue Apr 25, 2022 · 5 comments
Closed

k8s cluster totally not work after helm uninstall volcano #2191

pengyuan opened this issue Apr 25, 2022 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@pengyuan
Copy link

pengyuan commented Apr 25, 2022

What happened:
k8s cluster totally not work after helm uninstall volcano

when helm install any other charts, then error occurs.

kubectl get events -w -n volcano

Error creating: Internal error occurred: failed calling webhook "mutatepod.volcano.sh": Post "https://volcano-admission-service.volcano.svc:443/pods/mutate?timeout=10s": service "volcano-admission-service" not found

What you expected to happen:

k8s cluster should work as before.

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

(helm version: 1.5.1)
helm upgrade --install volcano ./volcano -f custom.yaml --namespace volcano

helm uninstall volcano -n volcano

Anything else we need to know?:

Environment:

  • Volcano Version: 0.1
  • Kubernetes version (use kubectl version): 1.20
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@pengyuan pengyuan added the kind/bug Categorizes issue or PR as related to a bug. label Apr 25, 2022
@pengyuan
Copy link
Author

#2079
#2102

it seems this problem does not resolved.

@hwdef
Copy link
Member

hwdef commented Apr 25, 2022

Yes, you have to clean webhook manually.

@stale
Copy link

stale bot commented Jul 30, 2022

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 30, 2022
@hwdef
Copy link
Member

hwdef commented Aug 12, 2022

fix in #2346
/close

@volcano-sh-bot
Copy link
Contributor

@hwdef: Closing this issue.

In response to this:

fix in #2346
/close

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/test-infra repository.

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants