apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "20840" uid: cb30d45f-e21f-4f80-ad05-cb956b67b335 spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-06T05:22:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 1.021555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 956.656µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:34:25Z" - latency: 984.12µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:33:25Z" - latency: 980.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:32:25Z" - latency: 782.725µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:31:25Z" - latency: 1.258918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:30:25Z" - latency: 1.024309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:29:25Z" - latency: 1.085502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:28:25Z" - latency: 1.357982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "22228" uid: c079d01d-a41d-4601-a8a4-71eb333117b7 spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T05:21:25Z" message: 'load-balancer-api-external: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.24885ms message: 'load-balancer-api-external: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:39:25Z" - latency: 9.532887ms message: 'load-balancer-api-external: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:39:25Z" - latency: 4.231689ms message: 'load-balancer-api-external: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:38:25Z" - latency: 8.804221ms message: 'load-balancer-api-external: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:38:25Z" - latency: 4.827995ms message: 'load-balancer-api-external: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:37:25Z" - latency: 8.536658ms message: 'load-balancer-api-external: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:37:25Z" - latency: 5.374325ms message: 'load-balancer-api-external: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 8.256696ms message: 'load-balancer-api-external: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:36:25Z" - latency: 3.904902ms message: 'load-balancer-api-external: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 7.759042ms message: 'load-balancer-api-external: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:35:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "22227" uid: 66712cbe-8300-4274-8004-9ebe5d4c239e spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T05:21:25Z" message: 'load-balancer-api-internal: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.359715ms message: 'load-balancer-api-internal: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:39:25Z" - latency: 9.474118ms message: 'load-balancer-api-internal: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:39:25Z" - latency: 4.222337ms message: 'load-balancer-api-internal: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:38:25Z" - latency: 8.83414ms message: 'load-balancer-api-internal: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:38:25Z" - latency: 4.42332ms message: 'load-balancer-api-internal: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:37:25Z" - latency: 8.504694ms message: 'load-balancer-api-internal: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:37:25Z" - latency: 3.774123ms message: 'load-balancer-api-internal: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 8.197355ms message: 'load-balancer-api-internal: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:36:25Z" - latency: 3.91631ms message: 'load-balancer-api-internal: tcp connection to a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 7.771444ms message: 'load-balancer-api-internal: resolved host name a9baf3243371e4872bca44c4df753215-4659ac669bdcbc9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T05:35:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-network-check-target-ip-10-0-136-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "20838" uid: 3c57876c-078d-4735-8083-b3cf6c6561d7 spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-06T05:22:25Z" message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.823675ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 2.305717ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 2.024137ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:34:25Z" - latency: 2.067325ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:33:25Z" - latency: 1.832834ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:32:25Z" - latency: 1.899184ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:31:25Z" - latency: 1.905264ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:30:25Z" - latency: 1.876551ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:29:25Z" - latency: 1.944479ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:28:25Z" - latency: 1.945287ms message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-network-check-target-ip-10-0-139-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "20839" uid: f2aa402b-b0da-48ec-b6c1-7a397c5878d0 spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-06T05:22:25Z" message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.119868ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 2.688179ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 2.185894ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:34:25Z" - latency: 2.103326ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:33:25Z" - latency: 2.163658ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:32:25Z" - latency: 2.061388ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:31:25Z" - latency: 2.023427ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:30:25Z" - latency: 2.151255ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:29:25Z" - latency: 2.159452ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:28:25Z" - latency: 2.350872ms message: 'network-check-target-ip-10-0-139-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-network-check-target-ip-10-0-142-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "20837" uid: 68f03654-4e91-4e45-8eeb-9144115c5343 spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-06T05:22:25Z" message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.039µs message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 1.729328ms message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 853.737µs message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:34:25Z" - latency: 740.327µs message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:33:25Z" - latency: 887.749µs message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:32:25Z" - latency: 1.321826ms message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:31:25Z" - latency: 1.167082ms message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:30:25Z" - latency: 770.746µs message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:29:25Z" - latency: 1.555816ms message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:28:25Z" - latency: 943.416µs message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T05:15:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-193.ec2.internal uid: 601f56fd-6368-4c9c-aef3-12a045f37e9a resourceVersion: "22226" uid: 02af752d-7071-4743-9145-e80101b4ca48 spec: sourcePod: network-check-source-dbd9cf844-5m5s6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-06T05:21:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 749.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:39:25Z" - latency: 1.750624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T05:39:25Z" - latency: 851.63µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:38:25Z" - latency: 1.954174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T05:38:25Z" - latency: 1.151976ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:37:25Z" - latency: 1.778914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T05:37:25Z" - latency: 893.57µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:36:25Z" - latency: 1.528145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T05:36:25Z" - latency: 663.567µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T05:35:25Z" - latency: 1.777162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T05:35:25Z" kind: List metadata: resourceVersion: ""