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

Docker is installed on the etcd nodes. even though I set etcd_deployment_type: host #7987

Closed
scila1996 opened this issue Sep 18, 2021 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@scila1996
Copy link
Contributor

scila1996 commented Sep 18, 2021

Hi kubespray team

I was deployed my Kubernetes cluster with three etcd node seperate to store key-value database for kubernetes, it's only used for etcd cluster and not using same for kubernetes workload. Everything is ok, but in etcd.yaml, I was set config of etcd_deployment_type to host. But my server still install docker ? It's not necessary and Docker installed with default subnet is 172.17.0.0 and 172.18.0.0 subnet, it is overlap with my company network infrastructure system and I must be removed them manual after run playbook. Please disable automatic install docker if etcd_deployment_type is set to host.

Many thank !

@scila1996 scila1996 added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 18, 2021
@scila1996 scila1996 changed the title the Docker is installed on the etcd nodes. even though I set etcd_deployment_type: host Docker is installed on the etcd nodes. even though I set etcd_deployment_type: host Sep 18, 2021
@liupeng0518
Copy link
Member

That's a real problem.

@ahmadalli
Copy link

is this kind/feature or a bug?

@scila1996
Copy link
Contributor Author

is this kind/feature or a bug?

I don't know, but I think this issue is both !

@VannTen
Copy link
Contributor

VannTen commented Oct 20, 2021

This is adressed in #7532

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Jan 18, 2022
@rtsp
Copy link
Member

rtsp commented Jan 18, 2022

Fixed in #7532 #8386

/close

@k8s-ci-robot
Copy link
Contributor

@rtsp: Closing this issue.

In response to this:

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

7 participants