apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "178917" uid: 57149566-2287-4252-b8aa-146376e6f3e5 spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T07:06:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191428ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:09:21Z" - latency: 932.474µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:08:21Z" - latency: 1.205771ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:07:21Z" - latency: 1.306353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:06:21Z" - latency: 2.158263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 1.026865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 1.515387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 1.016646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 1.154097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 3.210429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:00:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "169053" uid: 151cecbf-5678-4ffe-ac70-e04f4e07dd95 spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T07:05:21Z" message: 'load-balancer-api-external: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.465636ms message: 'load-balancer-api-external: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 9.23356ms message: 'load-balancer-api-external: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:05:21Z" - latency: 16.830008ms message: 'load-balancer-api-external: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 8.839107ms message: 'load-balancer-api-external: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:04:21Z" - latency: 23.42582ms message: 'load-balancer-api-external: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 9.294032ms message: 'load-balancer-api-external: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:03:21Z" - latency: 17.375252ms message: 'load-balancer-api-external: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 6.989536ms message: 'load-balancer-api-external: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:02:21Z" - latency: 16.484019ms message: 'load-balancer-api-external: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 7.390158ms message: 'load-balancer-api-external: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:01:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "169054" uid: 698cef03-e22b-4d4d-8570-bf14b3c0a18b spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T07:05:21Z" message: 'load-balancer-api-internal: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.48832ms message: 'load-balancer-api-internal: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 9.162962ms message: 'load-balancer-api-internal: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:05:21Z" - latency: 16.443304ms message: 'load-balancer-api-internal: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 8.758236ms message: 'load-balancer-api-internal: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:04:21Z" - latency: 15.288146ms message: 'load-balancer-api-internal: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 9.321452ms message: 'load-balancer-api-internal: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:03:21Z" - latency: 18.517768ms message: 'load-balancer-api-internal: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 6.911639ms message: 'load-balancer-api-internal: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:02:21Z" - latency: 16.579244ms message: 'load-balancer-api-internal: tcp connection to a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 7.326093ms message: 'load-balancer-api-internal: resolved host name a02b51741ab5b4ca5bc641472406905e-d58114832b2a1f72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T08:01:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-network-check-target-ip-10-0-131-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "178914" uid: c7c6c28a-3f15-43f9-8573-9839701d61a7 spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T07:06:21Z" message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.747393ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:09:21Z" - latency: 2.547523ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:08:21Z" - latency: 2.728732ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:07:21Z" - latency: 2.900503ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:06:21Z" - latency: 3.077077ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 2.789565ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 2.725753ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 2.680409ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 3.27013ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 4.24642ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:00:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-network-check-target-ip-10-0-132-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "178912" uid: 207890d6-d918-4c47-80d2-c239008b55c6 spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T07:06:21Z" message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.688076ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:09:21Z" - latency: 1.085355ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:08:21Z" - latency: 1.754357ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:07:21Z" - latency: 1.066652ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:06:21Z" - latency: 3.638933ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 2.061588ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 1.125558ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 1.742364ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 1.644288ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 1.962141ms message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:00:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-network-check-target-ip-10-0-143-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "178913" uid: 3c2dd772-24b6-4283-9cd4-e200afe9b580 spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T07:06:21Z" message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.795513ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:09:21Z" - latency: 2.509897ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:08:21Z" - latency: 3.089512ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:07:21Z" - latency: 2.291509ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:06:21Z" - latency: 2.756565ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 3.049821ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 2.945281ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 3.23755ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 2.483476ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 7.234879ms message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:00:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T06:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-173.ec2.internal uid: a4a81960-a39c-4928-a6a8-dbdb6dff1df4 resourceVersion: "169051" uid: d5ceae14-43b3-4ec2-83a9-b3641345d488 spec: sourcePod: network-check-source-6f78d59f99-fv48w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T07:05:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.130581ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:05:21Z" - latency: 3.478821ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T08:05:21Z" - latency: 1.21045ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:04:21Z" - latency: 2.715147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T08:04:21Z" - latency: 1.373399ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:03:21Z" - latency: 2.728144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T08:03:21Z" - latency: 1.004633ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:02:21Z" - latency: 1.856378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T08:02:21Z" - latency: 1.000489ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T08:01:21Z" - latency: 2.360043ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T08:01:21Z" kind: List metadata: resourceVersion: ""