- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 738
 
feat: improve cloudstack documentation #10565
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
base: main
Are you sure you want to change the base?
Conversation
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)
        
          
                website/content/v1.9/talos-guides/install/cloud-platforms/cloudstack.md
              
                Outdated
          
            Show resolved
            Hide resolved
        
      | } | ||
| ``` | ||
| 
               | 
          ||
| > Note 2: For this example an additional "loadbalancerrule" is needed to enable the communication between `talosctl` and the VM. | 
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
Signed-off-by: Matthias Dietz <[email protected]>
| 
           This PR is stale because it has been open 45 days with no activity.  | 
    
Pull Request
What? (description)
userdatafor virtual machine deploymentloadbalancerruleto enable communication with the Talos API (needed for bootstrapping the cluster)Why? (reasoning)
The current documentation contains a typo for the
userdataCLI parameter. When trying to bootstrap the cluster, thattalosctlcould not reach the Talos API on the VM.Acceptance
Please use the following checklist:
make conformance)make fmt)make lint)make docs)make unit-tests)