apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32528" uid: d4eeecef-2e5f-4214-8573-a70196e343fa spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:21:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.15448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 1.427238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 1.924698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 1.083977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 1.152051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 930.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:30Z" - latency: 1.180363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:30Z" - latency: 1.212758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:30Z" - latency: 1.360915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:30Z" - latency: 1.79737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:47:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32530" uid: 0b417a55-1075-4483-8c73-464c702f121c spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:20:30Z" message: 'load-balancer-api-external: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.630977ms message: 'load-balancer-api-external: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 8.836341ms message: 'load-balancer-api-external: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:56:30Z" - latency: 5.473794ms message: 'load-balancer-api-external: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 9.168492ms message: 'load-balancer-api-external: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:55:30Z" - latency: 7.047948ms message: 'load-balancer-api-external: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 8.885718ms message: 'load-balancer-api-external: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:54:30Z" - latency: 4.465037ms message: 'load-balancer-api-external: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 7.847754ms message: 'load-balancer-api-external: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:53:30Z" - latency: 4.277612ms message: 'load-balancer-api-external: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 7.031063ms message: 'load-balancer-api-external: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:52:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32529" uid: 1984abcc-73d7-4ae4-8be9-d5f0e991136b spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:20:30Z" message: 'load-balancer-api-internal: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.683436ms message: 'load-balancer-api-internal: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 8.94676ms message: 'load-balancer-api-internal: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:56:30Z" - latency: 5.482791ms message: 'load-balancer-api-internal: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 9.186238ms message: 'load-balancer-api-internal: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:55:30Z" - latency: 7.054208ms message: 'load-balancer-api-internal: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 8.96633ms message: 'load-balancer-api-internal: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:54:30Z" - latency: 4.458696ms message: 'load-balancer-api-internal: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 7.836747ms message: 'load-balancer-api-internal: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:53:30Z" - latency: 5.398657ms message: 'load-balancer-api-internal: tcp connection to a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 7.065578ms message: 'load-balancer-api-internal: resolved host name a7a7e4541a572499d8459b42f1b49b85-570823774f58758a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:52:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-network-check-target-ip-10-0-134-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32524" uid: 5f9f1ee3-548d-4147-8527-5a50a007cfa9 spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:21:30Z" message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 995.379µs message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 1.064369ms message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 1.31581ms message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 1.497456ms message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 1.28864ms message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 1.528134ms message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:30Z" - latency: 836.292µs message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:30Z" - latency: 855.661µs message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:30Z" - latency: 1.633253ms message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:30Z" - latency: 890.686µs message: 'network-check-target-ip-10-0-134-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:47:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-network-check-target-ip-10-0-136-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32527" uid: 9af8d8cc-eb06-4d21-af2b-7ddd9a5d2a0f spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:21:30Z" message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.34852ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 2.587158ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 3.018532ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 2.123849ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 1.983109ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 2.335143ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:30Z" - latency: 2.580093ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:30Z" - latency: 2.195623ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:30Z" - latency: 2.387895ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:30Z" - latency: 2.230818ms message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:47:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-network-check-target-ip-10-0-139-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32525" uid: 6c7e0f13-d638-4df4-9e93-1a4a755bc088 spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:21:30Z" message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.135173ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 2.209414ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 2.140118ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 2.229287ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 2.416911ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 2.148978ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:30Z" - latency: 2.420571ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:30Z" - latency: 2.189137ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:30Z" - latency: 2.390591ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:30Z" - latency: 2.246278ms message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:47:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-14-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-14.ec2.internal uid: 78d5fb58-0c25-4d81-a179-37a40ac37a41 resourceVersion: "32526" uid: 5d98e820-e20b-4431-80ac-d6de2c159cda spec: sourcePod: network-check-source-7d88cb55d8-xv5f2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:20:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.665µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:30Z" - latency: 1.864751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:56:30Z" - latency: 1.01234ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:30Z" - latency: 1.791071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:55:30Z" - latency: 924.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:30Z" - latency: 2.082317ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:54:30Z" - latency: 1.327996ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:30Z" - latency: 1.807561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:53:30Z" - latency: 879.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:30Z" - latency: 2.273572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:52:30Z" kind: List metadata: resourceVersion: ""