apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72113" uid: db312314-b5c0-4bd5-b3d4-374a7f799729 spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T01:40:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.984002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 895.451µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 1.194739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 1.651253ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 1.240646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 1.372953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:10:19Z" - latency: 951.252µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:09:19Z" - latency: 1.13858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:08:19Z" - latency: 1.258738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:07:19Z" - latency: 1.015481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:06:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72115" uid: a467a98f-24ea-419c-9a2e-fb932f3a63c0 spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T01:39:19Z" message: 'load-balancer-api-external: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.023387ms message: 'load-balancer-api-external: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 8.243273ms message: 'load-balancer-api-external: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:15:19Z" - latency: 5.355196ms message: 'load-balancer-api-external: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 10.621314ms message: 'load-balancer-api-external: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:14:19Z" - latency: 4.240549ms message: 'load-balancer-api-external: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 6.978473ms message: 'load-balancer-api-external: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:13:19Z" - latency: 6.243922ms message: 'load-balancer-api-external: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 8.509601ms message: 'load-balancer-api-external: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:12:19Z" - latency: 3.699061ms message: 'load-balancer-api-external: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 7.720996ms message: 'load-balancer-api-external: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:11:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72114" uid: e96824f5-4d00-42d7-91b3-2b880445a867 spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T01:39:19Z" message: 'load-balancer-api-internal: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.890198ms message: 'load-balancer-api-internal: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 8.334553ms message: 'load-balancer-api-internal: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:15:19Z" - latency: 5.384257ms message: 'load-balancer-api-internal: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 10.577654ms message: 'load-balancer-api-internal: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:14:19Z" - latency: 4.23136ms message: 'load-balancer-api-internal: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 6.895954ms message: 'load-balancer-api-internal: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:13:19Z" - latency: 5.204698ms message: 'load-balancer-api-internal: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 8.31218ms message: 'load-balancer-api-internal: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:12:19Z" - latency: 3.734072ms message: 'load-balancer-api-internal: tcp connection to a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 7.580505ms message: 'load-balancer-api-internal: resolved host name a5358a4201ea042db83917a258d5ba6e-9eb88211d486f86d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T02:11:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-network-check-target-ip-10-0-129-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72108" uid: 886f7002-37fe-4bf8-93d1-e5412c48650d spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T01:40:19Z" message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.569µs message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 1.201875ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 1.165797ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 1.427447ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 1.51131ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 947.297µs message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:10:19Z" - latency: 1.043321ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:09:19Z" - latency: 1.14252ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:08:19Z" - latency: 970.747µs message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:07:19Z" - latency: 936.704µs message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:06:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-network-check-target-ip-10-0-138-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72110" uid: 775a7cba-d22f-48c0-8266-b1df03da6f19 spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T01:40:19Z" message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.126383ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 2.254373ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 2.312573ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 2.484833ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 2.286235ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 2.114664ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:10:19Z" - latency: 2.174528ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:09:19Z" - latency: 2.311727ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:08:19Z" - latency: 2.129355ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:07:19Z" - latency: 2.179621ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:06:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-network-check-target-ip-10-0-142-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72111" uid: 87f4f6cb-c04b-45bd-82c9-c8be462c7773 spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T01:40:19Z" message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.234489ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 1.779275ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 1.962457ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 2.419842ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 2.112276ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 2.214785ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:10:19Z" - latency: 2.123971ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:09:19Z" - latency: 2.277208ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:08:19Z" - latency: 1.960052ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:07:19Z" - latency: 2.004242ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:06:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T01:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-127-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-127.ec2.internal uid: 501df559-4e9e-487c-9ad6-c03553718627 resourceVersion: "72112" uid: 5d2cd9cf-d6aa-4ce3-b9e4-f53ba91582d7 spec: sourcePod: network-check-source-7d88cb55d8-25r79 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T01:39:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158387ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:15:19Z" - latency: 2.343831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T02:15:19Z" - latency: 875.035µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:14:19Z" - latency: 1.80151ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T02:14:19Z" - latency: 919.473µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:13:19Z" - latency: 2.072801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T02:13:19Z" - latency: 998.675µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:12:19Z" - latency: 2.12248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T02:12:19Z" - latency: 871.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T02:11:19Z" - latency: 1.95436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T02:11:19Z" kind: List metadata: resourceVersion: ""