* Add Virtual Kubelet provider for VIC Initial virtual kubelet provider for VMware VIC. This provider currently handles creating and starting of a pod VM via the VIC portlayer and persona server. Image store handling via the VIC persona server. This provider currently requires the feature/wolfpack branch of VIC. * Added pod stop and delete. Also added node capacity. Added the ability to stop and delete pod VMs via VIC. Also retrieve node capacity information from the VCH. * Cleanup and readme file Some file clean up and added a Readme.md markdown file for the VIC provider. * Cleaned up errors, added function comments, moved operation code 1. Cleaned up error handling. Set standard for creating errors. 2. Added method prototype comments for all interface functions. 3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder. * Add mocking code and unit tests for podcache, podcreator, and podstarter Used the unit test framework used in VIC to handle assertions in the provider's unit test. Mocking code generated using OSS project mockery, which is compatible with the testify assertion framework. * Vendored packages for the VIC provider Requires feature/wolfpack branch of VIC and a few specific commit sha of projects used within VIC. * Implementation of POD Stopper and Deleter unit tests (#4) * Updated files for initial PR
1.5 KiB
1.5 KiB
Kubernetes initial testing notes
Required HW setup:
- Ubuntu 16.04
- 4 CPU
- 16GB memory
- 80GB disk
- (might need 8CPU/32GB of memory, as the above recommended was quite slow still)
Initial install:
sudo apt-get updatesudo apt-add-repository ppa:juju/stablesudo apt-add-repository ppa:conjure-up/nextsudo apt updatesudo apt install conjure-up
Configure container hypervisor:
newgrp lxdsudo lxd init
Walkthrough the config (just hit enter) - select NO when asked to setup IPv6
Point juju at the new hypervisor:
juju bootstrap localhost lxd-test
Start the k8s cluster:
conjure-up canonical-kubernetes
Just hit enter a few times until you get to the summary and hit Q
watch -c juju status --color
Wait for quite a while until the cluster is completely up/active/idle. Can take upwards of an hour!
Finalize setup:
mkdir -p ~/.kubejuju scp kubernetes-master/0:config ~/.kube/configjuju scp kubernetes-master/0:kubectl ~/bin/kubectl
Verify it is working and the cluster is up:
kubectl cluster-info
Example commands:
kubectl run -i -t busybox --image=busybox --restart=Neverkubectl run nginx --image=nginx
Show the running pods:
kubectl get pods
To scale up the cluster:
juju add-unit kubernetes-worker
To show the controller:
juju switch
To destroy the cluster:
juju destroy-controller lxd-test --destroy-all-models