-
Notifications
You must be signed in to change notification settings - Fork 51
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
Test and review using Digital Rebar to deploy Kubernetes clusters on Packet.net #48
Comments
Videos and docs referenced:
|
Tried to use Terraform plan that builds the whole KRIB cluster from the command line following the video https://www.youtube.com/watch?v=5trB3_IFFX8 and documentation for building the terraform provider https://github.com/rackn/terraform-provider-drp#building-the-provider, but ran into validation errors. Opened a ticket on the provider repo |
As there were no all command line walk-throughs/demos for only using the rebar command line we refocused on using the Rebar web ui for now. |
TIP: Reset profile or create a new one to clear k8s API server IP Reusing a existing profile fails because the Kubernetes API server IP is already populated in the profile Creating a brand new profile or reseting the profile in rebar fixes the issue. |
While using the web-ui we ran into what looks like a certificate related issue when the KRIB workflow is running. Opened a upstream ticket, digitalrebar/provision-content#133, with the instructions to reproduce. |
Cc @zehicle |
After to running the new steps below digitalrebar/provision-content#133 (comment)
We were successfully able to deploy a K8s cluster on RackN/Packet with both the GUI and Terraform |
@denverwilliams since this was successful, can we close the ticket? |
What's left:@denverwilliams to provide additional documentation to this ticket, then close. |
Goal: Deploy a Kubernetes cluster to bare metal using a PXE boot install method on Packet.net
This should cover starting with no Packet nodes and all the way to a running Kubernetes cluster which supports deploying apps via helm charts.
A user should be able to start with nothing more than a Packet.net account.
The steps would look something like:
Could start with SSH to a brand new packet instance, launched from Packet dashboard, and run everything else from command line
The text was updated successfully, but these errors were encountered: