Issue-4087: Increase MaxItems for CACertificateRefs validation

[root30]

What type of PR is this?
kind feature

What this PR does / why we need it:
Increase the number of allowed Certificate Authority references

Which issue(s) this PR fixes:

Fixes #4087

Does this PR introduce a user-facing change?:

Increase the number of allowed Certificate Authority references from `8` to `32`

[k8s-ci-robot]

Hi @root30. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: root30
Once this PR has been reviewed and has the lgtm label, please assign shaneutt for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[snorwin]

/remove-lifecycle stale

[snorwin]

/cc @rikatz @kl52752

[snorwin]

/ok-to-test

[snorwin]

Thanks @root30!

It sounds reasonable to give administrators a bit more flexibility in how they choose to split their trusted CA bundles across resources.

[kl52752]

One think that worries me is the size of Gateway object and I'm fine with increasing the number but I'm worried that 32 is too much.
Frontend validation is set on gateway as Default value and per port overrides. We allows to set 64 per port overrides which equals Listeners max number. In worst case scenario will have 65 * 32 references which seams a lot.

[snorwin]

@kl52752 how about increasing it to 16 as a compromise? 😉

[kl52752]

yeah we can meet half way :)

@youngnick @robscott do you have any concerns about increasing this limitation?