Working with custom objects from CRDs about dotnet-kube-client HOT 3 CLOSED

This is fantastic. Thank you very much :)

from dotnet-kube-client.

Hi - this is fairly easy to do if you've already defined your resource type. There's an additional package called KubeClient.Extensions.CustomResources that defines a base class for your resource type.

Once you have defined your specification model (the bit that goes under spec in the JSON), you can define your resource model:

public enum ThingState
{
  Draft,
  Final
}

public class MyResourceSpecV1
{
  [JsonProperty("thingState")]
  [YamlMember(Name="thingState")]
  public ThingState ThingState { get; set; }

  [YamlMember(Name="thingSizes")]
  [JsonProperty("thingSizes", DefaultValueHandling = DefaultValueHandling.IgnoreAndPopulate)]
  public List<string> ThingSizes { get; set; }
}

[KubeObject("Pod", "things.example.com/v1")]
public class MyResourceV1
  : KubeCustomResourceV1<MyResourceSpecV1>
{
}

You can then follow the steps under Extensibility to create a client for working with your resources.

Note that your code can live in its own library - the client is designed so you can layer additional models and clients on top of the existing ones regardless of where they live.

from dotnet-kube-client.

Oh, and the DefaultValueHandling stuff is mainly to do with whether or not you want to send default (usually null) values when calling your API. If you use DefaultValueHandling.IgnoreAndPopulate, then the field is omitted from the JSON when serialising. If you use DefaultValueHandling.Include, then the field is included in the JSON with a null value.

from dotnet-kube-client.