apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "53989" uid: e9f1fa60-a63a-467d-b132-90122693fd71 spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T19:18:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 1.161057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 1.022214ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 1.133363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 960.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:15Z" - latency: 967.784µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:15Z" - latency: 1.394023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:15Z" - latency: 1.049062ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:15Z" - latency: 1.300091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:15Z" - latency: 1.251932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "55092" uid: 99881601-65f4-4af4-9437-e56ef1dcac12 spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:17:15Z" message: 'load-balancer-api-external: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.802719ms message: 'load-balancer-api-external: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:15Z" - latency: 8.100927ms message: 'load-balancer-api-external: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:47:15Z" - latency: 4.712418ms message: 'load-balancer-api-external: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 8.199278ms message: 'load-balancer-api-external: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:46:15Z" - latency: 3.757387ms message: 'load-balancer-api-external: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 6.622344ms message: 'load-balancer-api-external: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:45:15Z" - latency: 5.230829ms message: 'load-balancer-api-external: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 6.925857ms message: 'load-balancer-api-external: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:44:15Z" - latency: 5.905801ms message: 'load-balancer-api-external: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 6.44018ms message: 'load-balancer-api-external: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "55093" uid: eaf8119b-e185-4935-b39c-768e02ec4798 spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:17:15Z" message: 'load-balancer-api-internal: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.825447ms message: 'load-balancer-api-internal: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:15Z" - latency: 8.155526ms message: 'load-balancer-api-internal: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:47:15Z" - latency: 4.721189ms message: 'load-balancer-api-internal: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 8.267338ms message: 'load-balancer-api-internal: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:46:15Z" - latency: 3.742567ms message: 'load-balancer-api-internal: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 6.712276ms message: 'load-balancer-api-internal: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:45:15Z" - latency: 5.29421ms message: 'load-balancer-api-internal: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 7.052602ms message: 'load-balancer-api-internal: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:44:15Z" - latency: 5.845156ms message: 'load-balancer-api-internal: tcp connection to a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 6.409197ms message: 'load-balancer-api-internal: resolved host name a7916f01690964288a3be8f3f027e4dd-316c8c9cada439ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-network-check-target-ip-10-0-133-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "53987" uid: 5a766b0f-0d95-43b9-b311-3c81c6c921a4 spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:18:15Z" message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.959996ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 2.17688ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 1.836736ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 1.609323ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 2.023161ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:15Z" - latency: 2.175221ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:15Z" - latency: 2.122821ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:15Z" - latency: 2.037896ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:15Z" - latency: 1.601793ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:15Z" - latency: 1.522603ms message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-network-check-target-ip-10-0-133-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "53988" uid: 05fd4288-afb7-4426-a1c4-4b07da13af7f spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:18:15Z" message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.494409ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 2.443684ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 2.26819ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 1.949055ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 2.603593ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:15Z" - latency: 2.59946ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:15Z" - latency: 2.285574ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:15Z" - latency: 2.385827ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:15Z" - latency: 2.176232ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:15Z" - latency: 2.14164ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-network-check-target-ip-10-0-142-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "53986" uid: 6acf220c-79c9-456f-9024-439f41dad070 spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:18:15Z" message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.066654ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 905.466µs message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 831.524µs message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 905.22µs message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 1.033358ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:15Z" - latency: 788.253µs message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:15Z" - latency: 1.604529ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:15Z" - latency: 845.578µs message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:15Z" - latency: 1.54662ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:15Z" - latency: 874.159µs message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:11:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-165-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-165.ec2.internal uid: e4263a43-f41f-47ee-a516-03c16d127062 resourceVersion: "55091" uid: 1d23ab1a-48f3-4ae1-9887-2e1f1b2a1aad spec: sourcePod: network-check-source-989f8b8dc-p4wp2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T19:17:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.082µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:15Z" - latency: 1.848796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:47:15Z" - latency: 1.121962ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:15Z" - latency: 1.930287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:46:15Z" - latency: 852.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:15Z" - latency: 1.651621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:45:15Z" - latency: 1.027908ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:15Z" - latency: 1.774781ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:44:15Z" - latency: 1.137851ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:15Z" - latency: 1.543691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:15Z" kind: List metadata: resourceVersion: ""