embed KubernetesClient.Models and KubernetesClient.Basic into client sdk #1407
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.
The old proposal that introduced
KubernetesClient.Models
andKubernetesClient.Basic
#793Why
In order to facilitate support
net48
.KubernetesClient.Models
andKubernetesClient.Basic
consistently maintained targetingnetstandard2.0
. However, the commitment to supporting netstandard2.0 has significantly constrained theKubernetesClient
in terms of adopting newer .NET features, such as record models.One of the core objectives behind introducing the
KubernetesClient.Models
andKubernetesClient.Basic
was to foster third-party engagement, encouraging developers to create custom clients. However, this approach may appear somewhat over-designed, seems no actual adoption of this functionality. Furthermore, even after embedding, third-party clients retain the ability to implement customized client solutions by overriding theAbstractKubernetes
.With the embedding completed, both
KubernetesClient
andKubernetesClient.Classic
can now follow their respective paths for independent development and enhancement.