fix: update kingress status logic

[shiyan2016]

Ⅰ. Describe what this PR did

In pkg/ingress/kube/kingress/status.go, the updateStatus method contained an inverted condition for determining whether to update the KIngress status.

if ingress.Status.PublicLoadBalancer == nil || len(ingress.Status.PublicLoadBalancer.Ingress) != len(KIngressStatus) || reflect.DeepEqual(ingress.Status.PublicLoadBalancer.Ingress, KIngressStatus) {

The condition incorrectly used reflect.DeepEqual without negation, meaning:

• Status updates were triggered when the current state and desired state were identical (no-op updates)
• Status updates were skipped when the state had actually changed, causing KIngress to report stale LoadBalancer addresses

Add the ! negation operator to reflect.DeepEqual so the update is triggered only when the current state differs from the desired state.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

Ⅵ. AI Coding Tool Usage Checklist (if applicable)

Please check all applicable items:

• For new standalone features (e.g., new wasm plugin or golang-filter plugin):

  • I have created a design/ directory in the plugin folder
  • I have added the design document to the design/ directory
  • I have included the AI Coding summary below

• For regular updates/changes (not new plugins):

  • I have provided the prompts/instructions I gave to the AI Coding tool below
  • I have included the AI Coding summary below

AI Coding Prompts (for regular updates)

AI Coding Summary

[CLAassistant]

All committers have signed the CLA.

[johnlanni]

cc @EndlessSeeker

[EndlessSeeker]

LGTM

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
pkg/ingress/kube/kingress/status.go	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!