d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
513cebe7b7cf590cd53c02ea8da1a20b58dd8f18
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group6-VIC-Machine/6-17-Configure-TLS.md
Loc Nguyen 513cebe7b7 VMware vSphere Integrated Containers provider (#206) 
* 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
2018-06-04 15:41:32 -07:00

1.5 KiB
Raw Blame History

Test 6-17 - Verify vic-machine configure TLS function

Purpose:

Verify vic-machine configure certificates

References:

  • vic-machine-linux configure -h

Environment:

This test requires that a vSphere server is running and available. One VCH is created for the suite and used throughout by each test so that we don't have to call create & configure in each test (which would duplicate the work of 6-13-TLS).

Configure VCH w/ own CA

Performs a similar test to the one in create.

  1. Generates a CA, self-signed
  2. Runs vic-machine configure against the VCH set up in pre-test
  3. Makes sure the installed certificate is the correct one

Configure VCH w/ trusted CA

  1. Generates a CA, adds it to trust pool, just like the test in Create
  2. Runs vic-machine to replace the previous cert with this one
  3. Uses openssl tool to verify correct trusted certificate is in place

Configure VCH - Run Configure Without Cert Options & Ensure Certs are Unchanged

  1. Generates a CA, installs it, verifies it's installed, as in the last test
  2. Calls configure again with no TLS options
  3. Check to make sure the installed cert from 1) is still presented

Configure VCH - Replace certificates with self-signed certificate using --no-tlsverify

  1. Calls configure against the existing VCH with --no-tlsverify and an empty --tls-cert-path
  2. Checks that a self-signed certificate is generated
  3. Checks that the installed certificate is the self-signed one that we just generated