fix(deps): update module github.com/kong/kubernetes-configuration to v1.5.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/kong/kubernetes-configuration	v1.4.2 → v1.5.3

---

Release Notes

kong/kubernetes-configuration (github.com/kong/kubernetes-configuration)

v1.5.3

Compare Source

Changes

See changelog for a complete list of changes.

Install CRDs from all channels

kustomize build github.com/Kong/kubernetes-configuration/config/crd/gateway-operator\?ref=v1.5.3 | kubectl apply -f -
kustomize build github.com/Kong/kubernetes-configuration/config/crd/ingress-controller\?ref=v1.5.3 | kubectl apply -f -
kustomize build github.com/Kong/kubernetes-configuration/config/crd/ingress-controller-incubator\?ref=v1.5.3 | kubectl apply -f -

v1.5.2

Compare Source

Fixes

• Fix KongUpstreamPolicy CRD CEL validation rules on hash_on.
  #​498

v1.5.1

Compare Source

Cleanups

• Update the CRDs metadata with up to date version.
  #​495

v1.5.0

Compare Source

Cleanups

• Marked KongIngress, TCPIngress, and UDPIngress as deprecated.
  You can use Gateway API resources instead.
  See the migration guides for KongIngress
  and TCPIngress/UDPIngress for more details.
  #​464

Added

• Added sticky sessions support for KongUpstreamPolicy.
  It corresponds to the sticky session feature of Kong Gateway.
  In KIC, we have added a drain support feature.
  When both are enabled, sticky session will continue to be bound to Kong Pod
  when it's marked as terminating.
  When sticky session is enabled but drain support is not, then sticky session
  will stop routing traffic to Kong Pods when they are marked as terminating.
  #​463

v1.4.3

Compare Source

Changes

See changelog for a complete list of changes.

Install CRDs from all channels

kustomize build github.com/Kong/kubernetes-configuration/config/crd/gateway-operator\?ref=v1.4.3 | kubectl apply -f -
kustomize build github.com/Kong/kubernetes-configuration/config/crd/ingress-controller\?ref=v1.4.3 | kubectl apply -f -
kustomize build github.com/Kong/kubernetes-configuration/config/crd/ingress-controller-incubator\?ref=v1.4.3 | kubectl apply -f -

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 2 additional dependencies were updated

Details:

Package	Change
github.com/Kong/sdk-konnect-go	v0.2.28 -> v0.3.1
sigs.k8s.io/controller-runtime	v0.20.4 -> v0.21.0

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 33.54%. Comparing base (9cce3c6) to head (872bf61).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1931   +/-   ##
=======================================
  Coverage   33.54%   33.54%           
=======================================
  Files          76       76           
  Lines        6711     6711           
=======================================
  Hits         2251     2251           
  Misses       4280     4280           
  Partials      180      180           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.