apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "100355" uid: 5c274947-56d9-4455-9a4a-ec23505b90f3 spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T10:18:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.240699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 1.613027ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:18Z" - latency: 883.734µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:18Z" - latency: 1.617877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:18Z" - latency: 1.629072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:18Z" - latency: 1.0646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:18Z" - latency: 1.350157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:43:18Z" - latency: 1.07495ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:42:18Z" - latency: 1.128433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:41:18Z" - latency: 1.064081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:40:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "104106" uid: 357e7676-bc71-45ed-9906-5834fd5a75b7 spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:17:18Z" message: 'load-balancer-api-external: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.48137ms message: 'load-balancer-api-external: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:18Z" - latency: 8.83733ms message: 'load-balancer-api-external: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:53:18Z" - latency: 5.325456ms message: 'load-balancer-api-external: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:18Z" - latency: 8.649795ms message: 'load-balancer-api-external: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:52:18Z" - latency: 5.747928ms message: 'load-balancer-api-external: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:18Z" - latency: 19.015038ms message: 'load-balancer-api-external: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:51:18Z" - latency: 5.142245ms message: 'load-balancer-api-external: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:18Z" - latency: 9.00116ms message: 'load-balancer-api-external: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:50:18Z" - latency: 5.999003ms message: 'load-balancer-api-external: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 9.051725ms message: 'load-balancer-api-external: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:49:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "104105" uid: 306e1e05-7ad7-41d4-8fe3-0f358293775b spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:17:18Z" message: 'load-balancer-api-internal: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.754503ms message: 'load-balancer-api-internal: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:18Z" - latency: 8.88874ms message: 'load-balancer-api-internal: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:53:18Z" - latency: 5.317977ms message: 'load-balancer-api-internal: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:18Z" - latency: 8.717689ms message: 'load-balancer-api-internal: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:52:18Z" - latency: 5.400964ms message: 'load-balancer-api-internal: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:18Z" - latency: 19.107346ms message: 'load-balancer-api-internal: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:51:18Z" - latency: 5.106391ms message: 'load-balancer-api-internal: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:18Z" - latency: 9.050028ms message: 'load-balancer-api-internal: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:50:18Z" - latency: 5.549752ms message: 'load-balancer-api-internal: tcp connection to a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 9.128993ms message: 'load-balancer-api-internal: resolved host name a594ea6a0475f44dc85157d7be9b2269-4d6af399b31c8a77.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:49:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-network-check-target-ip-10-0-130-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "100352" uid: 53017e4d-3b80-4ce3-a3b0-cfac825a82a1 spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:18:18Z" message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 783.393µs message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 1.415638ms message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:18Z" - latency: 1.156181ms message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:18Z" - latency: 930.543µs message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:18Z" - latency: 913.998µs message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:18Z" - latency: 1.552453ms message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:18Z" - latency: 1.028001ms message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:43:18Z" - latency: 1.402056ms message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:42:18Z" - latency: 1.050161ms message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:41:18Z" - latency: 825.966µs message: 'network-check-target-ip-10-0-130-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:40:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-network-check-target-ip-10-0-131-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "100353" uid: b8a76662-38d3-49d3-a521-e17398e17850 spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:18:18Z" message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.037004ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 2.13336ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:18Z" - latency: 2.025266ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:18Z" - latency: 1.983548ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:18Z" - latency: 2.017589ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:18Z" - latency: 1.58414ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:18Z" - latency: 2.253423ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:43:18Z" - latency: 1.976949ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:42:18Z" - latency: 1.915229ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:41:18Z" - latency: 1.963222ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:40:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-network-check-target-ip-10-0-141-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "100354" uid: a27050f0-fdda-4af8-929c-5149a4c04d28 spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:18:18Z" message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.119868ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 2.298193ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:18Z" - latency: 2.400937ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:18Z" - latency: 2.531423ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:18Z" - latency: 2.174847ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:18Z" - latency: 2.426537ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:18Z" - latency: 2.59981ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:43:18Z" - latency: 2.490545ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:42:18Z" - latency: 2.549477ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:41:18Z" - latency: 2.216222ms message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:40:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-235-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-235.ec2.internal uid: 7e4b7cc7-bc52-440c-837f-9c986e266cd5 resourceVersion: "104104" uid: 2c11b2ca-cf1f-44a1-a7af-1fb776382304 spec: sourcePod: network-check-source-7d88cb55d8-vf6dm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T10:17:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002542ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:18Z" - latency: 1.879094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:53:18Z" - latency: 1.118074ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:18Z" - latency: 1.954313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:52:18Z" - latency: 1.090326ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:18Z" - latency: 11.869537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:51:18Z" - latency: 961.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:18Z" - latency: 1.959241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:50:18Z" - latency: 931.477µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:18Z" - latency: 1.754769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:49:18Z" kind: List metadata: resourceVersion: ""