[
https://issues.apache.org/jira/browse/MINIFICPP-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gábor Gyimesi resolved MINIFICPP-1765.
--------------------------------------
Fix Version/s: 0.12.0
Resolution: Fixed
> Speed up the kubernetes.feature
> -------------------------------
>
> Key: MINIFICPP-1765
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1765
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Ferenc Gerlits
> Assignee: Gábor Gyimesi
> Priority: Minor
> Labels: MiNiFi-CPP-Hygiene
> Fix For: 0.12.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently, each Scenario of the {{kubernetes.feature}} creates a new {{kind}}
> cluster during setup, and deletes it on teardown. Every time {{kind create
> cluster}} runs, it takes 20 to 30 seconds. Downloading the {{kind}} binary
> and loading the {{minifi}} docker image into the cluster each take around 5
> seconds, as well.
> Restructure the test setups to create and delete the kind cluster on feature
> level instead of test scenario level. We could set up a single kind cluster
> on feature level, do a cleanup after every scenario, and only delete the
> cluster after all the test scenarios in the feature are finished.
> One difficulty is that the volumes of the {{kind}} cluster are connected to
> the temporary test directories which are created for each Scenario. We would
> need to either reconnect the volumes (if that is possible), or create
> feature-level temporary directories, copy the minifi {{config.yml}} etc to
> these new directories, and clean them up after the Scenario is done.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
