KubernetesClientConfiguration.JsonSerializerOptions always returns null.

[davidivkovic]

Describe the bug
KubernetesClientConfiguration.JsonSerializerOptions always returns null.

The getter for this property calls the KubernetesJson.AddJsonOptions method which is empty.

csharp/src/KubernetesClient/KubernetesClientConfiguration.cs

Lines 122 to 139 in 61e6b13

	public JsonSerializerOptions JsonSerializerOptions
	{
	get
	{
	// If not yet set, use defaults from KubernetesJson.
	if (jsonSerializerOptions is null)
	{
	KubernetesJson.AddJsonOptions(options =>
	{
	jsonSerializerOptions = new JsonSerializerOptions(options);
	});
	}
	return jsonSerializerOptions;
	}
	private set => jsonSerializerOptions = value;
	}

csharp/src/KubernetesClient.Aot/KubernetesJson.cs

Lines 76 to 78 in 61e6b13

	public static void AddJsonOptions(Action<JsonSerializerOptions> configure)
	{
	}

Kubernetes C# SDK Client Version
KubernetesClient.Aot 15.0.1

Server Kubernetes Version
1.30.2

Dotnet Runtime Version
.net9

To Reproduce
Create a KubernetesClientConfiguration and call the JsonSerializerOptions property.

Expected behavior
A System.Text.Json.JsonSerializerOptions instance to be returned.

Where do you run your app with Kubernetes SDK (please complete the following information):
Linux

[tg123]

aot should not expose this prop as you can't config it

[davidivkovic]

Is it possible to register a serializer context for custom types used with client.CustomObjects.CreateNamespacedCustomObjectWithHttpMessagesAsync(customObject)?

[tg123]

it is not possible in aot
everything is compiled ahead of time, no dynamic code allowed in this mode

if the main sdk good for you, aot is for performance scenarios only

[davidivkovic]

So it's currently not possible to use the CreateNamespacedCustomObject method in AOT?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.