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.

Sign up for GitHub

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

Jump to bottom

Add a documentation for "Add a node to the MKE 4 cluster" #292

Open
moshiurH opened this issue Jan 20, 2025 · 4 comments · May be fixed by #309
Open

Add a documentation for "Add a node to the MKE 4 cluster" #292

moshiurH opened this issue Jan 20, 2025 · 4 comments · May be fixed by #309
Assignees
@KoryKessel-Mirantis
Labels
Docs-A Must Do

Comments

@moshiurH
Copy link
Collaborator

moshiurH commented Jan 20, 2025 •
edited
Loading

See https://mirantis.github.io/mke-docs/docs/getting-started/

Image

Key points we should probably add

  • Use a tool like terraform to deploy additional AWS nodes
$ cat terraform.tfvars
manager_count        = 3
worker_count         = 3
username             = "moshiur"
task_name            = "mke4_more_ui_testing"
project              = "ORCA"
expire_duration      = "72h"

to

$ cat terraform.tfvars
manager_count        = 3
worker_count         = 4
username             = "moshiur"
task_name            = "mke4_more_ui_testing"
project              = "ORCA"
expire_duration      = "72h"
  • Update the mke4.yaml file containing the new nodes
$ grep -A 45 "hosts" mke4.yaml  hosts:
    - role: controller+worker
      ssh:
        address: 18.237.201.195
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
    - role: controller+worker
      ssh:
        address: 54.218.20.72
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
    - role: controller+worker
      ssh:
        address: 54.187.250.85
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
    - role: worker
      ssh:
        address: 44.245.17.0
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
    - role: worker
      ssh:
        address: 35.91.28.61
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
    - role: worker
      ssh:
        address: 34.219.25.139
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
    - role: worker
      ssh:
        address: 35.88.245.179
        keyPath: /home/moshiur/Documents/Github/mke/deployments/mke3/ssh_keys/mke3.pem
        port: 22
        user: ubuntu
  ingressController:
    affinity:
      nodeAffinity: {}
  • mkectl apply to add the new nodes

Before:
Image

After:
Image
@moshiurH
Copy link
Collaborator Author

Please note that the actions and new node buttons does not do anything.

@KoryKessel-Mirantis KoryKessel-Mirantis added the Docs-A Must Do label Feb 4, 2025
@nwneisen
Copy link
Collaborator

nwneisen commented Feb 10, 2025 •
edited
Loading

I would suggest we put this under it's own page for Adding a node since we have a section for removing a node. Or combine Interacting with a cluster, Removing a node, and Adding a node into the Interacting with a cluster page since they are all small an somewhat related.

I don't think we should suggest using terraform since most customers a bare metal and running different tech in general. but we should mention that users will need to have the the host information for the new node.

...
hosts:
    ...
    - role: worker
      ssh:
        address: <address>
        keyPath: <key location
        port: <ssh port>
        user: <username>
...

We may want to suggest they get the updated config, mkectl config get, from their cluster and then add their new host info before running mkectl apply.

@brianbancroft
Copy link
Collaborator

Please note that the actions and new node buttons does not do anything.

Yes. Intentionally disabled with tooltip messages to make clear that "nope, you can't do that in MKE4" in contrast with other resources

@KoryKessel-Mirantis KoryKessel-Mirantis linked a pull request Feb 11, 2025 that will close this issue
Addition of cluster node addition content (and removal of none). #309
Open
@KoryKessel-Mirantis
Copy link
Collaborator

Please note that the actions and new node buttons does not do anything.

Yes. Intentionally disabled with tooltip messages to make clear that "nope, you can't do that in MKE4" in contrast with other resources

Opting to just not mention the web UI in the content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KoryKessel-Mirantis KoryKessel-Mirantis

Labels
Docs-A Must Do
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Addition of cluster node addition content (and removal of none). Mirantis/mke-docs
5 participants
@nwneisen @brianbancroft @KoryKessel-Mirantis @moshiurH @MagdaDziadosz