apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "29062" uid: 2fd9edd3-e93c-442a-850e-9c42afd49ded spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-07T19:13:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:20:20Z" - latency: 959.589µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:19:20Z" - latency: 1.119895ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 1.462132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 920.131µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 942.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 1.218241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 865.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:13:20Z" - latency: 1.052565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:12:20Z" - latency: 993.755µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:11:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "27795" uid: 3a9eb2a0-0bed-4d8b-9ea7-0d4f531edf37 spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T19:12:20Z" message: 'load-balancer-api-external: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.583576ms message: 'load-balancer-api-external: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 7.8622ms message: 'load-balancer-api-external: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:18:20Z" - latency: 4.971939ms message: 'load-balancer-api-external: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 7.894787ms message: 'load-balancer-api-external: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:17:20Z" - latency: 5.224657ms message: 'load-balancer-api-external: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 12.904543ms message: 'load-balancer-api-external: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:16:20Z" - latency: 4.234157ms message: 'load-balancer-api-external: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 7.460382ms message: 'load-balancer-api-external: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:15:20Z" - latency: 5.277572ms message: 'load-balancer-api-external: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 7.112439ms message: 'load-balancer-api-external: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:14:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "27794" uid: 3fa64ec8-c668-4924-818d-2763abe15a4c spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T19:12:20Z" message: 'load-balancer-api-internal: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.580252ms message: 'load-balancer-api-internal: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 7.859226ms message: 'load-balancer-api-internal: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:18:20Z" - latency: 4.970298ms message: 'load-balancer-api-internal: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 7.986081ms message: 'load-balancer-api-internal: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:17:20Z" - latency: 5.19166ms message: 'load-balancer-api-internal: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 12.928421ms message: 'load-balancer-api-internal: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:16:20Z" - latency: 4.194988ms message: 'load-balancer-api-internal: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 7.514285ms message: 'load-balancer-api-internal: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:15:20Z" - latency: 5.247726ms message: 'load-balancer-api-internal: tcp connection to a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 7.190163ms message: 'load-balancer-api-internal: resolved host name a707a0d40608949fb8a1aad16900ca6a-deed470a35dee24b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:14:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-network-check-target-ip-10-0-136-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "29059" uid: 2570dc62-bd45-4e01-9963-2341ecbbaf20 spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-07T19:13:20Z" message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.992µs message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:20:20Z" - latency: 1.432059ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:19:20Z" - latency: 1.172522ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 1.350339ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 1.247968ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 809.355µs message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 1.153579ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 1.218488ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:13:20Z" - latency: 848.902µs message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:12:20Z" - latency: 805.365µs message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:11:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-network-check-target-ip-10-0-142-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "29061" uid: 1329e905-5766-4446-8986-bc75ef3d7512 spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-07T19:13:20Z" message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.25619ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:20:20Z" - latency: 2.29734ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:19:20Z" - latency: 2.377536ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 2.200302ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 2.053288ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 2.330292ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 2.42238ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 2.281019ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:13:20Z" - latency: 2.329626ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:12:20Z" - latency: 1.977256ms message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:11:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-network-check-target-ip-10-0-142-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "29060" uid: 1b3a463e-470c-4f60-a70f-afdb91f60921 spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-07T19:13:20Z" message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.861364ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:20:20Z" - latency: 1.952494ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:19:20Z" - latency: 1.525651ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 1.730379ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 1.947445ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 1.706163ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 2.134302ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 2.042261ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:13:20Z" - latency: 2.042804ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:12:20Z" - latency: 1.725563ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:11:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:06:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-1-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-1.ec2.internal uid: cf243de0-04a2-4386-83d2-0f804de572df resourceVersion: "27793" uid: 3e367347-b639-433a-98be-8f6cb13a6bc0 spec: sourcePod: network-check-source-dbd9cf844-xt7r7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-07T19:12:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.35µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:18:20Z" - latency: 1.587271ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:18:20Z" - latency: 963.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:17:20Z" - latency: 1.857999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:17:20Z" - latency: 962.142µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:16:20Z" - latency: 1.632871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:16:20Z" - latency: 1.040562ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:15:20Z" - latency: 1.782628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:15:20Z" - latency: 1.056809ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:14:20Z" - latency: 1.617231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:14:20Z" kind: List metadata: resourceVersion: ""