ManagedFieldsEntryApplyConfiguration Not Part of ObjectMetaApplyConfiguration

[brito-rafa]

Hi,

On applyconfigurations/meta/v1 I wonder why ManagedFieldsEntryApplyConfiguration is not nested on ObjectMetaApplyConfiguration.

Is this by design?

Asking because []ManagedFieldsEntry belong to .metadata .

The implementation of ManagedFieldsEntryApplyConfiguration would fit similarly what []OwnerReferenceApplyConfiguration and methods are currently performing on ObjectMetaApplyConfiguration.

Thanks,
Rafa

PS: Some may ask why I want to set ManagedFieldsEntry if K8s server side deals with this automatically. I want to build unit tests to parse a variation of ManagedFieldsEntry from a given object.

[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