apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "71061" uid: bdf3f478-2a13-44e5-847e-c01ea9033135 spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T20:52:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 995.061µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:34:39Z" - latency: 1.499583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:33:39Z" - latency: 1.008787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:32:39Z" - latency: 998.654µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:31:39Z" - latency: 1.114038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:30:39Z" - latency: 1.097085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:29:39Z" - latency: 1.235733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:28:39Z" - latency: 919.962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:27:39Z" - latency: 1.472852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:26:39Z" - latency: 943.275µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:25:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "80437" uid: e45e647e-53a7-4c11-a3c1-0f15ad0d7e9d spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T20:51:39Z" message: 'load-balancer-api-external: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.015013ms message: 'load-balancer-api-external: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:39:39Z" - latency: 9.074752ms message: 'load-balancer-api-external: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:39:39Z" - latency: 4.709591ms message: 'load-balancer-api-external: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:38:39Z" - latency: 8.197473ms message: 'load-balancer-api-external: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:38:39Z" - latency: 4.802292ms message: 'load-balancer-api-external: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:37:39Z" - latency: 9.498482ms message: 'load-balancer-api-external: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:37:39Z" - latency: 6.054357ms message: 'load-balancer-api-external: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:36:39Z" - latency: 8.612918ms message: 'load-balancer-api-external: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:36:39Z" - latency: 5.421053ms message: 'load-balancer-api-external: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:35:39Z" - latency: 8.689574ms message: 'load-balancer-api-external: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:35:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "80436" uid: 5dbb89f4-53c2-4658-87ce-9fbfcb34ccdb spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T20:51:39Z" message: 'load-balancer-api-internal: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.009648ms message: 'load-balancer-api-internal: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:39:39Z" - latency: 9.009191ms message: 'load-balancer-api-internal: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:39:39Z" - latency: 5.481537ms message: 'load-balancer-api-internal: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:38:39Z" - latency: 8.154498ms message: 'load-balancer-api-internal: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:38:39Z" - latency: 4.80201ms message: 'load-balancer-api-internal: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:37:39Z" - latency: 9.397082ms message: 'load-balancer-api-internal: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:37:39Z" - latency: 6.033449ms message: 'load-balancer-api-internal: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:36:39Z" - latency: 8.421912ms message: 'load-balancer-api-internal: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:36:39Z" - latency: 5.4401ms message: 'load-balancer-api-internal: tcp connection to aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:35:39Z" - latency: 8.629449ms message: 'load-balancer-api-internal: resolved host name aeaaa1f5268a34e04a7917fdf7053e4d-609eaa9286ab76f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T21:35:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-129-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "71059" uid: 40b6f7a8-5ecd-4504-9925-c86c3efed27a spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T20:52:39Z" message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.615463ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:34:39Z" - latency: 2.141918ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:33:39Z" - latency: 2.563628ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:32:39Z" - latency: 2.394877ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:31:39Z" - latency: 2.487399ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:30:39Z" - latency: 2.823441ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:29:39Z" - latency: 2.449282ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:28:39Z" - latency: 2.257503ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:27:39Z" - latency: 2.325449ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:26:39Z" - latency: 2.665105ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:25:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-139-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "71060" uid: fa6079b6-d9f9-4b1a-8f2d-ab70e6f9f538 spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T20:52:39Z" message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.429652ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:34:39Z" - latency: 2.02127ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:33:39Z" - latency: 2.651017ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:32:39Z" - latency: 2.593365ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:31:39Z" - latency: 2.515428ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:30:39Z" - latency: 2.871481ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:29:39Z" - latency: 2.446206ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:28:39Z" - latency: 2.239278ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:27:39Z" - latency: 2.323329ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:26:39Z" - latency: 2.227576ms message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:25:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-140-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "71058" uid: 1359db74-1379-4ba0-8ea2-934bcd9d21df spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T20:52:39Z" message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02156ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:34:39Z" - latency: 913.622µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:33:39Z" - latency: 1.544747ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:32:39Z" - latency: 1.100839ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:31:39Z" - latency: 1.011971ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:30:39Z" - latency: 2.076812ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:29:39Z" - latency: 1.100851ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:28:39Z" - latency: 957.389µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:27:39Z" - latency: 1.429563ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:26:39Z" - latency: 1.234019ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:25:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T20:45:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: 438f467f-fac5-4542-a6dd-5e95fe77c5a3 resourceVersion: "80435" uid: 5d8b73bf-e95d-4f3a-96fe-6fc1dcd3a5c9 spec: sourcePod: network-check-source-65bdbbff45-8ctcg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T20:51:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.325µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:39:39Z" - latency: 2.362632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T21:39:39Z" - latency: 818.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:38:39Z" - latency: 1.820832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T21:38:39Z" - latency: 1.141161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:37:39Z" - latency: 1.970537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T21:37:39Z" - latency: 895.776µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:36:39Z" - latency: 1.854772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T21:36:39Z" - latency: 1.06675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T21:35:39Z" - latency: 1.759145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T21:35:39Z" kind: List metadata: resourceVersion: ""