apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65238" uid: 7f856908-9cb2-457e-96b3-99e05f82bfb2 spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T22:57:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.551054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 1.079108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 1.151203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 1.288665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 1.005545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 1.24751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:27:40Z" - latency: 943.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:26:40Z" - latency: 1.374309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:25:40Z" - latency: 1.214141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:24:40Z" - latency: 1.149086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65240" uid: b21d6475-ba8d-4ffe-aa6a-77bc9a196101 spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T22:56:40Z" message: 'load-balancer-api-external: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.895432ms message: 'load-balancer-api-external: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 8.996845ms message: 'load-balancer-api-external: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:32:40Z" - latency: 3.926786ms message: 'load-balancer-api-external: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 7.097185ms message: 'load-balancer-api-external: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:31:40Z" - latency: 4.827773ms message: 'load-balancer-api-external: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 9.910284ms message: 'load-balancer-api-external: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:30:40Z" - latency: 5.367722ms message: 'load-balancer-api-external: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 8.796014ms message: 'load-balancer-api-external: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:29:40Z" - latency: 4.215496ms message: 'load-balancer-api-external: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 14.949049ms message: 'load-balancer-api-external: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:28:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65239" uid: b9fc600f-f5a5-42ba-97fc-3c208edf40df spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T22:56:40Z" message: 'load-balancer-api-internal: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.610499ms message: 'load-balancer-api-internal: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 9.04856ms message: 'load-balancer-api-internal: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:32:40Z" - latency: 4.257604ms message: 'load-balancer-api-internal: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 7.038475ms message: 'load-balancer-api-internal: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:31:40Z" - latency: 3.935973ms message: 'load-balancer-api-internal: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 9.936607ms message: 'load-balancer-api-internal: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:30:40Z" - latency: 5.613808ms message: 'load-balancer-api-internal: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 8.76306ms message: 'load-balancer-api-internal: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:29:40Z" - latency: 4.943109ms message: 'load-balancer-api-internal: tcp connection to a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 14.920746ms message: 'load-balancer-api-internal: resolved host name a6bb81629bfd048a5b63d12ed61962fa-d35f145222583786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T23:28:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-132-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65237" uid: 617f15a9-996c-4a08-9ec7-79173d7a4aaf spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T22:57:40Z" message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.724739ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 2.402156ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 2.479323ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 2.055535ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 2.324235ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 2.01755ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:27:40Z" - latency: 2.357157ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:26:40Z" - latency: 2.392134ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:25:40Z" - latency: 2.743785ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:24:40Z" - latency: 2.565685ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-136-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65234" uid: dcaca644-343b-435a-a8a8-b7bf21ba3937 spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T22:57:40Z" message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.848889ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 984.569µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 1.443978ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 1.217814ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 995.604µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 933.001µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:27:40Z" - latency: 1.13379ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:26:40Z" - latency: 975.717µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:25:40Z" - latency: 1.019418ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:24:40Z" - latency: 1.123061ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-136-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65235" uid: 58550e07-6ab4-4438-89d4-cefbed26e2ff spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T22:57:40Z" message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.685069ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 2.558628ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 2.607307ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 2.53948ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 2.464957ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 2.254474ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:27:40Z" - latency: 2.250308ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:26:40Z" - latency: 2.513806ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:25:40Z" - latency: 2.497294ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:24:40Z" - latency: 2.741823ms message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T22:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: 089e8a91-cf9d-4c76-a901-c68f981bca69 resourceVersion: "65236" uid: 6d78c1e9-4b54-43e3-bd70-0d4ca4565b78 spec: sourcePod: network-check-source-7d88cb55d8-pwg5s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T22:56:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.21476ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:32:40Z" - latency: 1.910365ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T23:32:40Z" - latency: 1.077487ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:31:40Z" - latency: 1.909056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T23:31:40Z" - latency: 1.067761ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:30:40Z" - latency: 1.875372ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T23:30:40Z" - latency: 1.217613ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:29:40Z" - latency: 1.952861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T23:29:40Z" - latency: 1.187165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T23:28:40Z" - latency: 1.824048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T23:28:40Z" kind: List metadata: resourceVersion: ""