Skip to content

Connectivity check is checking ipv4 features when injecting ipv6 #35125

@vincepri

Description

@vincepri

Is there an existing issue for this?

  • I have searched the existing issues

Version

equal or higher than v1.16.0 and lower than v1.17.0

What happened?

if ct.Features[features.IPv4].Enabled {
cmd := []string{"/bin/sh", "-c", fmt.Sprintf("ip -family inet6 -oneline address show dev %s scope global | awk '{print $4}' | cut -d/ -f1", iface)}
addr, err := client.ExecInPod(ctx, pod.Namespace, pod.Name, "", cmd)
if err != nil {
return fmt.Errorf("failed to fetch secondary network ip addr: %w", err)
}
ct.secondaryNetworkNodeIPv6[pod.Spec.NodeName] = strings.TrimSuffix(addr.String(), "\n")
}

How can we reproduce the issue?

The check for pod ipv6 is checking for ipv4 features

Cilium Version

N/A

Kernel Version

N/A

Kubernetes Version

N/A

Regression

No response

Sysdump

No response

Relevant log output

No response

Anything else?

No response

Cilium Users Document

  • Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

area/agentCilium agent related.cilium-cliThis PR contains changes related with cilium-clifeature/ipv6Relates to IPv6 protocol supportkind/bugThis is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.pinnedThese issues are not marked stale by our issue bot.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions