KongConsumer Secrets being required to exist before the KongConsumer still causes friction for deployments

[purvaldur]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When I attempt to deploy a KongConsumer at the same time as the Secret defined in its' credentials field, I get hit with the consumer referenced non-existent credentials secret error from the admission webhook. If I manually deploy the secret before the consumer it deploys properly.

Expected Behavior

deploying KongConsumer at the same time as its' associated Secret deploys both properly without complaint from the admission webhook.

Steps To Reproduce

No response

Kong Ingress Controller version

v3.3

Kubernetes version

v1.29.6

Anything else?

This was initially discussed by the Kong team in #2324 and continued in #2195 without a definite resolution.

The severity of the credentials issue was referred to as having been "greatly reduced with the events mechanism" and closed due to lacking scope in todays' context. However the issue still persists.