[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #16: [DISCUSS] Work on next release

[GitBox <gi...@apache.org>]

onitake commented on issue #16:
URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-628783822


   Thank you, @rhtyd !
   
   IMHO, testing should largely be done through unit tests.
   At the moment, there are only a few of them, and they depend on a working CloudStack environment, or a mockup thereof.
   So, I would suggest that we construct a test environment with a mocked ACS management server, then run a `go test -v` inside, with environment vars set so it can connect to the mock.
   These tests can then be further extended through checks against the server, if all requested resources were deployed correctly.
   
   As for the documentation, the README should be sufficient to get the provider running, but it's not very extensive.
   
   The other questions are a bit more on the management side, but I would suggest we adopt best practices from the container world. Frequent, independent releases, the `latest` tag should always point to the latest stable release, example deployments should point to a particular version and only use features therein, etc.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org