KubeAPIWarningLogger unknown field "xxxx.creationTimestamp"

[Jeffwan]

When I create an object, I notice it surface some KubeAPIWarningLogger messages, seems it doesn't affect anything but it's annoying. This should be something common to other cases, anyone have clues?

1. I double checked the objects I created, it doesn't have creationTimestamp there
2. I didn't use // +kubebuilder:pruning:PreserveUnknownFields yet.

./bin/controller-gen-v0.14.0 --version
Version: v0.14.0

Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.2

[alvaroaleman]

This means that the go type you have in your code has fields that do not exist in the CRD of the server. I recommend to fix that. If this is an expected state of affairs, you can change the config of the warning logger in the rest.Config

[andrewsykim]

Ran into this too, the problem is that our CRDs embed corev1.PodTemplateSpec, which includes a metav1.ObjectMeta. However, the generated CRD does not include all fields of metav1.ObjectMeta but the Go type still has it

[andrewsykim]

I think surpressing the warning is a fine workaround too, I just found #2887 which I'll look into

[nayihz]

I think surpressing the warning is a fine workaround too, I just found #2887 which I'll look into

hi @andrewsykim , I also encountered the same problem. May I ask if this pr solved your problem? Thanks.

[snorwin]

@andrewsykim, @nayihz I'm facing similar problems, for that reason I opened an issue (kubernetes-sigs/controller-tools#1168) to address the root cause.

[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