apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63473" uid: 64af100c-c94d-4c81-b2cd-6adaa085d929 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-19T14:50:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.450952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 895.91µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 1.164062ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 972.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 1.414378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 1.448949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:20:20Z" - latency: 1.327089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:19:20Z" - latency: 944.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:18:20Z" - latency: 987.283µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:17:20Z" - latency: 996.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:16:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63475" uid: fc41bbb4-c363-489a-b57b-da75e0de10f0 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-19T14:49:20Z" message: 'load-balancer-api-external: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.719035ms message: 'load-balancer-api-external: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 9.038404ms message: 'load-balancer-api-external: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:25:20Z" - latency: 4.351294ms message: 'load-balancer-api-external: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 7.468673ms message: 'load-balancer-api-external: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:24:20Z" - latency: 5.732497ms message: 'load-balancer-api-external: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 7.62961ms message: 'load-balancer-api-external: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:23:20Z" - latency: 4.738882ms message: 'load-balancer-api-external: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 7.127713ms message: 'load-balancer-api-external: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:22:20Z" - latency: 4.945275ms message: 'load-balancer-api-external: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 7.863174ms message: 'load-balancer-api-external: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:21:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63474" uid: 08e97fc5-d93b-4aec-a278-f5f512467595 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-19T14:49:20Z" message: 'load-balancer-api-internal: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.72117ms message: 'load-balancer-api-internal: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 9.146978ms message: 'load-balancer-api-internal: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:25:20Z" - latency: 4.372135ms message: 'load-balancer-api-internal: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 7.417951ms message: 'load-balancer-api-internal: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:24:20Z" - latency: 5.237412ms message: 'load-balancer-api-internal: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 7.701122ms message: 'load-balancer-api-internal: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:23:20Z" - latency: 4.978128ms message: 'load-balancer-api-internal: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 7.166605ms message: 'load-balancer-api-internal: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:22:20Z" - latency: 4.517053ms message: 'load-balancer-api-internal: tcp connection to a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 7.9419ms message: 'load-balancer-api-internal: resolved host name a86af5e78783f4d28a521acb103243ea-ae06242761caf802.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:21:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-network-check-target-ip-10-0-134-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63469" uid: dc64e60a-8c9b-4dfc-8826-8d4deea4fbc7 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-19T14:50:20Z" message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.747535ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 804.23µs message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 1.3241ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 797.222µs message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 1.439081ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 1.298711ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:20:20Z" - latency: 1.031408ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:19:20Z" - latency: 1.164095ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:18:20Z" - latency: 1.006616ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:17:20Z" - latency: 1.087181ms message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:16:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-network-check-target-ip-10-0-134-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63472" uid: 4725220d-37b5-4416-9193-1ddc595056e5 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-19T14:50:20Z" message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.49933ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 1.945109ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 2.12913ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 2.281181ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 2.400602ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 2.15143ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:20:20Z" - latency: 2.202744ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:19:20Z" - latency: 2.370434ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:18:20Z" - latency: 2.165936ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:17:20Z" - latency: 2.222636ms message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:16:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-network-check-target-ip-10-0-141-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63470" uid: 1c6b3d70-c3dc-4d1b-94f4-e95f297791d1 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-19T14:50:20Z" message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.700242ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 1.980511ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 2.241624ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 2.246488ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 1.804947ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 2.678597ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:20:20Z" - latency: 2.292755ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:19:20Z" - latency: 2.017102ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:18:20Z" - latency: 2.100419ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:17:20Z" - latency: 1.980308ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:16:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:43:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-156-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-156.ec2.internal uid: 1baa77aa-64ec-4e9c-ba4c-bc2360383091 resourceVersion: "63471" uid: 5b407170-7caf-416f-a37b-15a12ba9ad73 spec: sourcePod: network-check-source-7bc5b6bf85-ds74r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-19T14:49:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.010806ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:25:20Z" - latency: 1.90395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:25:20Z" - latency: 945.362µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:24:20Z" - latency: 2.429661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:24:20Z" - latency: 1.19705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:23:20Z" - latency: 1.84641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:23:20Z" - latency: 1.33959ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:22:20Z" - latency: 1.88022ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:22:20Z" - latency: 1.019448ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:21:20Z" - latency: 1.816369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:21:20Z" kind: List metadata: resourceVersion: ""