Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

In setting up kubernetes (1 master, 1 minion), I noticed that if you started with an all in one setup, the localhost, or local minion remained after switching to the second. 

Version-Release number of selected component (if applicable): 0.6

How reproducible: Very 

Steps to Reproduce:
1. Follow https://access.redhat.com/articles/1198103 
 - Set this up as an all in one, 
 - change the minion ip to an atomic host (complete instructions)
2. kubectl get minion

Actual results:

This will report 2 minions, 1 for the master and one for the atomic host. 

Expected results:

Due to serice restarts on the master and the minon's this should only report 1 minion (the atomic host). At lest that is what I would expect.  

Additional info:

I am removing the GA blocker. This is working as expected, even if that stinks. Once a minion is created in etcd it will never be removed. We hope to have better dynamic minion support in the future. As the minion is not running a kubelet, the health checks will fail, and no pods will be scheduled to the minion.

While this is a bug that needs fixed, it is not a GA blocker.

Re-purposing bug for RFE on dynamic clustering.

So upstream, you can now add/remove minions via the api.  I'd suggest we stop recommending people set anything in the --machines= option to the controller manager and start adding/removing minions via the api.  So this should be fixed in the next atomic update assuming we rebase...

I'm going to close this bug. It is working as expected. If a node joins the cluster (be it single node or not) it is 'part' of the cluster until the admin removes it. Restarting the apiserver/node is not relevant.