Add authenticationConfiguration to Ingress Class Params

[kellyyan]

Issue

#3858

Description

• Add authenticationConfiguration to IngressClassParams, allowing users to configure the authentication for all Ingresses in the IngressGroup associated with the IngressClass
• Add error handling to ensure authentication configuration is set properly
• Added tests
  • pkg/ingress/auth_config_builder_test.go
  • pkg/ingress/enhanced_backend_builder_test.go
  • pkg/ingress/reference_indexer_test.go
• Added documentation to ingress_class.md
• Minor formating fixes
• Manually tested using Ingress manifests
  • Test: create ALB with OIDC authentication configuration
  • Test: create ALB with Amazon Cognito authentication configuration
  • Test: create ALB with no authentication configuration

Checklist

• Added tests that cover your change (if possible)
• Added/modified documentation as required (such as the README.md, or the docs directory)
• Manually tested
• Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

• Backfilled missing tests for code in same general area 🎉
• Refactored something and made the world a better place 🌟

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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-ci-robot]

Hi @kellyyan. 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.

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.

[shraddhabang]

/ok-to-test

[shraddhabang]

/retest

[shraddhabang]

Update the CRDs for helm as well by running make crds.

[kellyyan]

Added in revision

[zac-nixon]

Instead of repeating the same index field statement twice can you do something like this:

var ingClassParams *elbv2api.IngressClassParams
if ingressClassParamsAvailable {
  ingClassParams = &elbv2api.IngressClassParams{}
}

Then you can set up the indexers ->

	if err := fieldIndexer.IndexField(ctx, &networking.Ingress{}, ingress.IndexKeySecretRefName,
			func(obj client.Object) []string {
				return r.referenceIndexer.BuildSecretRefIndexes(context.Background(), ingClassParams, obj.(*networking.Ingress))
			},
		); err != nil {
			return err
		}
		if err := fieldIndexer.IndexField(ctx, &corev1.Service{}, ingress.IndexKeySecretRefName,
			func(obj client.Object) []string {
				return r.referenceIndexer.BuildSecretRefIndexes(context.Background(), ingClassParams, obj.(*corev1.Service))
			},
		); err != nil {
			return err
		}

[kellyyan]

/retest

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
pull-aws-load-balancer-controller-e2e-test	885756c	link	true	/test pull-aws-load-balancer-controller-e2e-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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