![]() ![]() You can find more info about what was actually added in below section.īack to table of contents Essential changes to rf-service Till now it was triggered as CronJob so there was schedule and possible repeatability, implemented changes allows taking advantage of running it within octopus. Now you only need container with your test suites to execute on demand, which is exactly what rf-service is supposed to provide. It was used in integration testing context, but could be easily used as recurring health checks. ![]() Basically, they turned 0/1 helm test approach into handling test as actual resource that can be retried, filtered and executed in parallel. Kyma-project Octopus took steps towards making this happen, you can find whole motivation in their blog post. The concept of encapsulating all the needed testing tools in container and running them against deployment is neat, the problem is that those tests are not treated as first class kubernetes citizens. This was noticed by helm team and implemented as helm test functionality. We assume that things defined in YAML files will be delivered as we expect but does it really differ from regular programming? It becomes even more crucial when the final YAML is templated as in helm case. Testing kubernetes deployments is for sure something that is not that evolved as other parts of kubernetes world. Testing on kubernetes - rf-service - this article describes Python service executed in a form of CronJob that actually runs the tests from KubeLibrary on kubernetes cluster.īack to table of contents Why octopus is such a good fit? Robot Framework library for testing Kubernetes - in this part I’m describing Robot Framework library (Python) that uses Kubernetes client for getting info about your cluster and turning it into actual test suites. ![]() You can find more info in following articles: This article is a part of series connected with testing on Kubernetes. ![]()
0 Comments
Leave a Reply. |