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

Kube-proxy removal is ignored #5552

Closed
MrFreezeex opened this issue Jan 17, 2020 · 3 comments · Fixed by #5554
Closed

Kube-proxy removal is ignored #5552

MrFreezeex opened this issue Jan 17, 2020 · 3 comments · Fixed by #5554
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@MrFreezeex
Copy link
Member

MrFreezeex commented Jan 17, 2020

Environment:

  • Cloud provider or hardware configuration:
    virtual machines
  • OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
    ubuntu 18
  • Version of Ansible (ansible --version):
    2.7.12

Kubespray version (commit) (git rev-parse --short HEAD):
master

Network plugin used:
kube-router

Anything else do we need to know:

kube-proxy is not removed post-deployment. There is several bugs in the playbook, like setting kube_proxy_remove to false in kubeadm role (

) while kubespray-default should sets it, a bad when condition in the task (
- kubeadm_discovery_address != kube_apiserver_endpoint | replace("https://", "")
).

@MrFreezeex MrFreezeex added the kind/bug Categorizes issue or PR as related to a bug. label Jan 17, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 16, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 16, 2020
@MrFreezeex
Copy link
Member Author

/remove-lifecycle rotten
This is still problematic an has a PR attached...

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 16, 2020
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