apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62832" uid: 6691f191-e41b-47a7-b8bf-30a36cae5a87 spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T09:26:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.077203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 1.003521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 1.080965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 1.053188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 1.27083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 1.635228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:56:57Z" - latency: 980.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:55:57Z" - latency: 1.252175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:54:57Z" - latency: 1.194997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:53:57Z" - latency: 871.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62833" uid: 46e53078-621e-40aa-9c07-b9afd2c81efb spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T09:25:57Z" message: 'load-balancer-api-external: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.60026ms message: 'load-balancer-api-external: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 8.155287ms message: 'load-balancer-api-external: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:01:57Z" - latency: 4.763426ms message: 'load-balancer-api-external: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 7.154719ms message: 'load-balancer-api-external: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:00:57Z" - latency: 5.922145ms message: 'load-balancer-api-external: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 7.48378ms message: 'load-balancer-api-external: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T09:59:57Z" - latency: 4.992282ms message: 'load-balancer-api-external: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 7.083916ms message: 'load-balancer-api-external: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T09:58:57Z" - latency: 5.082616ms message: 'load-balancer-api-external: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 8.565363ms message: 'load-balancer-api-external: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T09:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62834" uid: d0f750e5-9422-4254-a279-ead70e0b99a0 spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T09:25:57Z" message: 'load-balancer-api-internal: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.746857ms message: 'load-balancer-api-internal: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 8.069755ms message: 'load-balancer-api-internal: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:01:57Z" - latency: 3.206575ms message: 'load-balancer-api-internal: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 7.018184ms message: 'load-balancer-api-internal: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:00:57Z" - latency: 6.019635ms message: 'load-balancer-api-internal: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 7.397585ms message: 'load-balancer-api-internal: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T09:59:57Z" - latency: 4.951338ms message: 'load-balancer-api-internal: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 7.049811ms message: 'load-balancer-api-internal: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T09:58:57Z" - latency: 4.078453ms message: 'load-balancer-api-internal: tcp connection to aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 8.435605ms message: 'load-balancer-api-internal: resolved host name aef5afa0bc72343f59f8aa42777dda2d-126cc559e0729300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T09:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-network-check-target-ip-10-0-129-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62829" uid: a74b10ed-68e4-406e-99f6-a4c38524ea7a spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T09:26:57Z" message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.771753ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 1.808544ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 2.122549ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 1.89043ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 1.666848ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 2.255587ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:56:57Z" - latency: 2.140704ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:55:57Z" - latency: 2.186778ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:54:57Z" - latency: 2.12793ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:53:57Z" - latency: 1.819877ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-network-check-target-ip-10-0-132-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62831" uid: 0ba8a886-6742-4dc3-bdc3-41cd29f03290 spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T09:26:57Z" message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323569ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 2.13771ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 2.221788ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 2.194918ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 2.508571ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 2.374722ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:56:57Z" - latency: 2.055476ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:55:57Z" - latency: 2.228366ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:54:57Z" - latency: 2.09695ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:53:57Z" - latency: 2.150559ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-network-check-target-ip-10-0-135-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62828" uid: 0d3eff9b-8f13-4cb4-8cbc-bdf60bf8c721 spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T09:26:57Z" message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.328µs message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 1.044846ms message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 895.829µs message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 888.563µs message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 1.376002ms message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 1.169967ms message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:56:57Z" - latency: 1.156047ms message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:55:57Z" - latency: 1.046503ms message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:54:57Z" - latency: 855.181µs message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:53:57Z" - latency: 847.713µs message: 'network-check-target-ip-10-0-135-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:19:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-145-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-145.ec2.internal uid: dffe8b8e-4968-4ecd-9d27-46e7fc7841f6 resourceVersion: "62830" uid: 7529ce12-d45a-4118-9a72-31c6cdfb2345 spec: sourcePod: network-check-source-7bc5b6bf85-b5cz2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T09:25:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:01:57Z" - latency: 1.981161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:01:57Z" - latency: 1.077322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:00:57Z" - latency: 1.684062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:00:57Z" - latency: 1.196941ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:59:57Z" - latency: 2.006879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T09:59:57Z" - latency: 877.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:58:57Z" - latency: 2.031955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T09:58:57Z" - latency: 1.065272ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T09:57:57Z" - latency: 2.578845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T09:57:57Z" kind: List metadata: resourceVersion: ""