feat: add SkipIncompleteLateInitializeCheck

[michaelhtm]

Description of changes:
When a field is marked for lateInitialize, the controller tries to
ensure that field is never nil.
If by chance the field is nil, the controller will reconcile every 5
seconds until the field is no longer nil.

Although we want certain fields lateInitialized, we don't expect them to
be nonNil.

In the example of RDS DBInstance, DBInstance contains
PerformanceInsightsKMSID, that we want to lateInitialize only when
PerformanceInsights is Enabled.

For now this change only allows us the incomplete check, but moving
forward, we may want to add certain conditions, to skip or not to
skip...

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[a-hilaly]

Although we want certain fields lateInitialized, we don't expect them to
be nonNil.
In the example of RDS DBInstance, DBInstance contains
PerformanceInsightsKMSID, that we want to lateInitialize only when
PerformanceInsights is Enabled.

But why make an extra ReadOne API call if you could already get the info from the OG ReadOne call?

[michaelhtm]

But why make an extra ReadOne API call if you could already get the info from the OG ReadOne call?

I agree. LateInitialize can be improved in the future.

[knottnt]

/retest

[michaelhtm]

/retest-required

[michaelhtm]

/retest-required

[michaelhtm]

/retest

[michaelhtm]

/retest ec2-controller-test

[ack-prow]

@michaelhtm: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test acm-controller-test
• /test apigatewayv2-controller-test
• /test cloudfront-controller-test
• /test documentdb-controller-test
• /test dynamodb-controller-test
• /test ec2-controller-test
• /test ecr-controller-test
• /test efs-controller-test
• /test eks-controller-test
• /test eventbridge-controller-test
• /test iam-controller-test
• /test lambda-controller-test
• /test pipes-controller-test
• /test prometheusservice-controller-test
• /test s3-controller-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test s3-olm-test
• /test verify-attribution

Use /test all to run all jobs.

In response to this:

/retest ec2-controller-test

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/test-infra repository.

[knottnt]

/lgtm

[knottnt]

/retest

[ack-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knottnt, michaelhtm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [knottnt,michaelhtm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[michaelhtm]

/test ec2-controller-test

[michaelhtm]

/retest-required

[ack-prow]

@michaelhtm: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
verify-attribution	19b99ae	link	false	/test verify-attribution
s3-olm-test	19b99ae	link	false	/test s3-olm-test
ec2-controller-test	19b99ae	link	true	/test ec2-controller-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.