apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60972" uid: caae34ac-d4d9-4e3b-b33c-d6f234a3dd4c spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T15:45:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 1.130262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 1.399405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 817.525µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 855.118µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 981.41µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:15:27Z" - latency: 1.147803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:14:27Z" - latency: 709.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:13:27Z" - latency: 716.494µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:12:27Z" - latency: 990.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:11:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60974" uid: e810e066-701d-443e-a565-817372d215a7 spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T15:44:27Z" message: 'load-balancer-api-external: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.267001ms message: 'load-balancer-api-external: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 7.031666ms message: 'load-balancer-api-external: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:20:27Z" - latency: 5.346867ms message: 'load-balancer-api-external: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 6.104327ms message: 'load-balancer-api-external: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:19:27Z" - latency: 6.948011ms message: 'load-balancer-api-external: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 8.591417ms message: 'load-balancer-api-external: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:18:27Z" - latency: 4.744949ms message: 'load-balancer-api-external: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 6.823763ms message: 'load-balancer-api-external: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:17:27Z" - latency: 5.24383ms message: 'load-balancer-api-external: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 8.718029ms message: 'load-balancer-api-external: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:16:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60973" uid: ae7ce0ad-b6c2-4fab-9f1e-6472be62924c spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T15:44:27Z" message: 'load-balancer-api-internal: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.277306ms message: 'load-balancer-api-internal: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 6.975971ms message: 'load-balancer-api-internal: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:20:27Z" - latency: 3.881159ms message: 'load-balancer-api-internal: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 6.044812ms message: 'load-balancer-api-internal: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:19:27Z" - latency: 6.941804ms message: 'load-balancer-api-internal: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 8.538328ms message: 'load-balancer-api-internal: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:18:27Z" - latency: 3.960551ms message: 'load-balancer-api-internal: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 6.792763ms message: 'load-balancer-api-internal: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:17:27Z" - latency: 5.18325ms message: 'load-balancer-api-internal: tcp connection to a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 8.784744ms message: 'load-balancer-api-internal: resolved host name a38cf6e881c314c3eb881f9b47bfbf2f-8edcf9fb410eaa5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:16:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-network-check-target-ip-10-0-132-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60969" uid: 58b1d235-6fe7-4511-82fa-1766d7285e75 spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T15:45:27Z" message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.150812ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 2.143558ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 2.260633ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 2.135435ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 2.07509ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 2.174874ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:15:27Z" - latency: 1.998123ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:14:27Z" - latency: 1.973159ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:13:27Z" - latency: 1.705156ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:12:27Z" - latency: 2.381739ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:11:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-network-check-target-ip-10-0-135-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60970" uid: c7502553-06ae-44c8-be06-6bf94f568db7 spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T15:45:27Z" message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.040578ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 1.966869ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 2.067186ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 2.300997ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 1.49053ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 2.015241ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:15:27Z" - latency: 2.521413ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:14:27Z" - latency: 1.943823ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:13:27Z" - latency: 1.967958ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:12:27Z" - latency: 2.046769ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:11:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-network-check-target-ip-10-0-140-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60968" uid: 57b205ab-4396-472e-a30f-afd6e1b5aaa5 spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T15:45:27Z" message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.149µs message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 1.053519ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 1.6297ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 763.545µs message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 755.828µs message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 1.101461ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:15:27Z" - latency: 1.433159ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:14:27Z" - latency: 1.360984ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:13:27Z" - latency: 724.056µs message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:12:27Z" - latency: 1.602111ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:11:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-212-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-212.ec2.internal uid: 609a2079-9ac1-4dc0-81f7-1617aec86659 resourceVersion: "60971" uid: 3470989c-94b0-41c7-8f80-97e722620511 spec: sourcePod: network-check-source-869dcfcdcd-crgxn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T15:44:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.583µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:20:27Z" - latency: 1.750715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:20:27Z" - latency: 1.016875ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:19:27Z" - latency: 1.79709ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:19:27Z" - latency: 989.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:18:27Z" - latency: 1.680963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:18:27Z" - latency: 712.412µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:17:27Z" - latency: 1.674504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:17:27Z" - latency: 899.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:16:27Z" - latency: 1.86372ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:16:27Z" kind: List metadata: resourceVersion: ""