The source project of this merge request has been removed.
Backport EE changes to the Kubernetes service
What does this MR do?
Backport a number of changes made in the EE KubernetesService to CE.
Are there points in the code the reviewer needs to double check?
I didn't backport helper methods unused in CE (like kube_deployments). If they get changed again in EE, that would lead to unnecessary conflicts.
Why was this MR needed?
Resolving conflicts in the CE->EE merge is difficult as things stand.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Edited by Nick Thomas