Skip to content

fix: guard nil ConfigMap.Data before assignment in two controllers - #2773

Open
AruneshDwivedi wants to merge 1 commit into
openyurtio:masterfrom
AruneshDwivedi:fix/2709-dns-nil-data
Open

fix: guard nil ConfigMap.Data before assignment in two controllers#2773
AruneshDwivedi wants to merge 1 commit into
openyurtio:masterfrom
AruneshDwivedi:fix/2709-dns-nil-data

Conversation

@AruneshDwivedi

Copy link
Copy Markdown

Fixes #2709, #2707

  • gateway_dns_controller: initialize cm.Data when nil before writing
    DNS records, preventing a panic on ConfigMaps with no data field
  • platform_admin_controller: initialize cm.Data when nil in the
    writeFramework CreateOrUpdate callback

ConfigMap.Data is optional in the Kubernetes API, so existing
ConfigMaps may have a nil Data map.

Fixes openyurtio#2709, openyurtio#2707

- gateway_dns_controller: initialize cm.Data when nil before writing
  DNS records, preventing a panic on ConfigMaps with no data field
- platform_admin_controller: initialize cm.Data when nil in the
  writeFramework CreateOrUpdate callback

ConfigMap.Data is optional in the Kubernetes API, so existing
ConfigMaps may have a nil Data map.

Signed-off-by: Arunesh Dwivedi <arunesh.devops@gmail.com>
@AruneshDwivedi
AruneshDwivedi requested a review from a team as a code owner August 27, 2026 14:43
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(raven): prevent DNS controller panic when edge-tunnel-nodes ConfigMap has nil data

1 participant