fix: make iterateTLSConfig only work for TLS config

[Ace-Tang]

Signed-off-by: Ace-Tang [email protected]

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[Ace-Tang]

iterateConfig want to solve TLS config at first, but ignore other map kind config like Runtime or something, it makes these types of config always be recognized as a unknow flag, to make it compatible, I wanna to make the funtion only work for TLS config, and recursive once.

[codecov-io]

Codecov Report

Merging #2057 into master will increase coverage by 5.06%.
The diff coverage is 25%.

@@            Coverage Diff             @@
##           master    #2057      +/-   ##
==========================================
+ Coverage   59.05%   64.11%   +5.06%     
==========================================
  Files         202      202              
  Lines       15494    15494              
==========================================
+ Hits         9150     9934     +784     
+ Misses       5233     4321     -912     
- Partials     1111     1239     +128

Flag	Coverage Δ
#criv1alpha1test	33.69% <0%> (-0.13%)	⬇️
#criv1alpha2test	34.31% <0%> (+3.01%)	⬆️
#integrationtest	38.58% <0%> (+0.01%)	⬆️
#unittest	22.72% <25%> (-0.04%)	⬇️

Impacted Files	Coverage Δ
daemon/config/config.go	40.74% <25%> (-6.18%)	⬇️
cri/v1alpha1/cri.go	65.18% <0%> (-0.18%)	⬇️
apis/server/utils.go	66.66% <0%> (+4.76%)	⬆️
cri/stream/httpstream/spdy/upgrade.go	60% <0%> (+5.71%)	⬆️
cri/v1alpha2/cri_utils.go	81.48% <0%> (+22.15%)	⬆️
cri/criservice.go	64.7% <0%> (+24.99%)	⬆️
cri/v1alpha2/cri_wrapper.go	53.87% <0%> (+53.87%)	⬆️
cri/v1alpha2/cri.go	66.2% <0%> (+66.2%)	⬆️
cri/v1alpha2/server.go	79.84% <0%> (+79.84%)	⬆️
cri/v1alpha2/cri_stream.go	80% <0%> (+80%)	⬆️
... and 2 more

[fuweid]

in your commit, the UnknownFlags is only for TLS?

[Ace-Tang]

iterateTLSConfig function is to make TLS value from map become a new key-value

{
   "TLS": {
       "a": "b"
    }
}  ->

{
   "a": "b"
}

as for other config, they will stay same, so do you got the point? @fuweid

[pouchrobot]

ping @Ace-Tang
We found that this PR is 42 commits, which is more than 10 commits, behind master.
Please rebase the branch against master and push it back again. Thanks a lot.

[allencloud]

Any update on this? @Ace-Tang @fuweid
Could we make this move on?

[fuweid]

LGTM