Skip to content

Conversation

@devops-42
Copy link

Pull Request

What? (description)

  • fixed typo in parameter userdata for virtual machine deployment
  • changed IP address to use when accessing the talos API
  • added second loadbalancerrule to enable communication with the Talos API (needed for bootstrapping the cluster)

Why? (reasoning)

The current documentation contains a typo for the userdata CLI parameter. When trying to bootstrap the cluster, that talosctlcould not reach the Talos API on the VM.

Acceptance

Please use the following checklist:

  • you linked an issue (if applicable)
  • you included tests (if applicable)
  • you ran conformance (make conformance)
  • you formatted your code (make fmt)
  • you linted your code (make lint)
  • you generated documentation (make docs)
  • you ran unit-tests (make unit-tests)

See make help for a description of the available targets.

@github-project-automation github-project-automation bot moved this to To Do in Planning Mar 18, 2025
@talos-bot talos-bot moved this from To Do to In Review in Planning Mar 18, 2025
feat: improve cloudstack documentation

- Fixed typo in parameter `userdata` for virtual machine deployment
- Changed IP address to use when accessing the talos API
- Added second loadbalancer rule to enable communication with the Talos API (needed for bootstrapping the cluster)
}
```

> Note 2: For this example an additional "loadbalancerrule" is needed to enable the communication between `talosctl` and the VM.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks like something specific to your environment, that you can't access the VMs directly?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's maybe Cloudstack specific: When using the offering for isolated networks the VM resides in a SDN which is not routed to the public network. I needed to add this rule in order to connect to the VM on the API port of Talos.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if that should be split out into a separate optional section (?).

Also if you do LB with external IP, Talos doesn't know about it, so it should be patched into the machine config, .machine.certSANs

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be a possibility. I made a PoC consisting of 3 CP and 2 Worker nodes in Cloudstack using the setup and could easily update the Kubernetes from 1.31.x to 1.32.x. I'll look into the patching of the machine config.

@smira smira moved this from In Review to On Hold in Planning Mar 24, 2025
@github-actions
Copy link

github-actions bot commented May 4, 2025

This PR is stale because it has been open 45 days with no activity.

@github-actions github-actions bot added the Stale label May 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: On Hold

Development

Successfully merging this pull request may close these issues.

2 participants