apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53900" uid: 24de35f5-a76a-4764-9e01-9f4bfd5a7555 spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T20:08:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.042708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 1.133145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 977.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 1.302725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 942.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 1.048935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:59Z" - latency: 982.766µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:59Z" - latency: 949.829µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:59Z" - latency: 1.116316ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:59Z" - latency: 959.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53902" uid: 9a0c70f2-f628-4e9a-8ee9-6b6693dae6ec spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T20:07:59Z" message: 'load-balancer-api-external: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.52406ms message: 'load-balancer-api-external: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 8.498434ms message: 'load-balancer-api-external: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:43:59Z" - latency: 4.892604ms message: 'load-balancer-api-external: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 8.418248ms message: 'load-balancer-api-external: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:42:59Z" - latency: 3.828603ms message: 'load-balancer-api-external: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 8.73754ms message: 'load-balancer-api-external: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:41:59Z" - latency: 4.524508ms message: 'load-balancer-api-external: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 9.049574ms message: 'load-balancer-api-external: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:40:59Z" - latency: 5.190074ms message: 'load-balancer-api-external: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 8.900678ms message: 'load-balancer-api-external: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53901" uid: a90c54d7-8f82-4927-a3a2-8a0e88e11512 spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T20:07:59Z" message: 'load-balancer-api-internal: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.536026ms message: 'load-balancer-api-internal: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 8.379645ms message: 'load-balancer-api-internal: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:43:59Z" - latency: 4.718919ms message: 'load-balancer-api-internal: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 8.503784ms message: 'load-balancer-api-internal: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:42:59Z" - latency: 3.848238ms message: 'load-balancer-api-internal: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 8.74762ms message: 'load-balancer-api-internal: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:41:59Z" - latency: 4.961631ms message: 'load-balancer-api-internal: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 8.998277ms message: 'load-balancer-api-internal: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:40:59Z" - latency: 5.173969ms message: 'load-balancer-api-internal: tcp connection to a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 8.77924ms message: 'load-balancer-api-internal: resolved host name a92aa028a1c2943eb80d0694bde8d3ee-774ccc6e87fb6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-network-check-target-ip-10-0-130-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53897" uid: d551cd67-2fa1-46ae-92eb-0efaffebb37b spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:08:59Z" message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.451257ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 2.481656ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 1.980383ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 2.382239ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 2.427371ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 2.091644ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:59Z" - latency: 2.297488ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:59Z" - latency: 2.247108ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:59Z" - latency: 2.472597ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:59Z" - latency: 2.631013ms message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-network-check-target-ip-10-0-135-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53896" uid: d25d9623-5c6d-4a8b-9ff8-6a0250f40a6e spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:08:59Z" message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.390271ms message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 929.336µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 866.006µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 867.5µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 1.415501ms message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 942.919µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:59Z" - latency: 945.372µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:59Z" - latency: 840.39µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:59Z" - latency: 882.691µs message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:59Z" - latency: 1.055192ms message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-network-check-target-ip-10-0-141-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53898" uid: 894a5500-0b2b-4f10-9942-9e2e6e9e7c48 spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:08:59Z" message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426844ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 2.514893ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 2.50349ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 2.548626ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 2.489426ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 2.238659ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:59Z" - latency: 2.672098ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:59Z" - latency: 2.54646ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:59Z" - latency: 2.363574ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:59Z" - latency: 2.473289ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:01:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-159-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-159.ec2.internal uid: 981fd951-a0fd-4ac7-9e5d-60a0312e7a8b resourceVersion: "53899" uid: 7339793a-73f4-4548-b066-bafad21b1a4e spec: sourcePod: network-check-source-869dcfcdcd-fxvmp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T20:07:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.328µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:43:59Z" - latency: 1.72641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:43:59Z" - latency: 784.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:42:59Z" - latency: 1.809871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:42:59Z" - latency: 1.123685ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:59Z" - latency: 1.824656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:41:59Z" - latency: 860.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:59Z" - latency: 1.790192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:40:59Z" - latency: 1.054393ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:59Z" - latency: 2.141522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:39:59Z" kind: List metadata: resourceVersion: ""