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.

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

Closed
taylor opened this issue Sep 5, 2018 · 9 comments

Comments

@taylor
Copy link
Collaborator

taylor commented Sep 5, 2018

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:

  1. User has a Packet API key
  2. User goes to a public github repo
  3. User clones repo
  4. User adds Packet API key to environment or some config file
  5. User runs script or copy and pastes commands to get a k8s cluster

Could start with SSH to a brand new packet instance, launched from Packet dashboard, and run everything else from command line

@taylor
Copy link
Collaborator Author

taylor commented Sep 5, 2018

@taylor
Copy link
Collaborator Author

taylor commented Sep 5, 2018

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

rackn/terraform-provider-drp#56

@taylor
Copy link
Collaborator Author

taylor commented Sep 5, 2018

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.

@taylor
Copy link
Collaborator Author

taylor commented Sep 5, 2018

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.

@taylor
Copy link
Collaborator Author

taylor commented Sep 5, 2018

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.

@dankohn
Copy link
Contributor

dankohn commented Sep 5, 2018

Cc @zehicle

@denverwilliams
Copy link
Collaborator

After to running the new steps below digitalrebar/provision-content#133 (comment)

  • Go to https://portal.rackn.io/#/e/147.75.196.129:8092/bulk

  • Select all machines to be used in new k8s cluster

  • Use profile drop down to choose the profile "myprofile"

  • Click the + symbol to add the profile to the machines

  • Use Workflows drop down to choose the krib-reset-cluster workflow

  • Click the Change Workflow button (play / skip button) - This will reset the certs

We were successfully able to deploy a K8s cluster on RackN/Packet with both the GUI and Terraform

@zehicle
Copy link

zehicle commented Sep 10, 2018

@denverwilliams since this was successful, can we close the ticket?

@lixuna
Copy link
Collaborator

lixuna commented Sep 12, 2018

What's left:

@denverwilliams to provide additional documentation to this ticket, then close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

5 participants