Fix Kubernetes duplication in version command #953
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
I fixed the duplication on Kubernetes section when a server already exposes a Kubernetes component.
- How I did it
I simplified the code, removing the Kubernetes section in the versionTemplate, and instead I forge a Kubernetes component if the server does not expose one.
- How to verify it
Using a docker server exposing a kubernetes:
Before:
With the fix:
- Description for the changelog
Fix Kubernetes section duplication in version command
- A picture of a cute animal (not mandatory but encouraged)
![image](https://user-images.githubusercontent.com/31478878/37665666-0f0b7150-2c5e-11e8-83ae-4af6af1b2b7c.png)