apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "44915" uid: 7367b436-50b7-48a6-829e-8ccfbff3ec81 spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T02:26:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.107103ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:47:45Z" - latency: 1.620265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:46:45Z" - latency: 976.226µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:45:45Z" - latency: 1.543682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:44:45Z" - latency: 1.092797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 928.734µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 950.486µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 1.025294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 1.077502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 1.094693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:38:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "40623" uid: 3997a9e8-6b3a-413f-87f9-0923aecd4c6d spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:25:45Z" message: 'load-balancer-api-external: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.895999ms message: 'load-balancer-api-external: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 9.714188ms message: 'load-balancer-api-external: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:43:45Z" - latency: 5.123537ms message: 'load-balancer-api-external: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 10.083553ms message: 'load-balancer-api-external: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:42:45Z" - latency: 3.676291ms message: 'load-balancer-api-external: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 9.142249ms message: 'load-balancer-api-external: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:41:45Z" - latency: 5.679521ms message: 'load-balancer-api-external: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 8.205585ms message: 'load-balancer-api-external: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:40:45Z" - latency: 6.026688ms message: 'load-balancer-api-external: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 6.689665ms message: 'load-balancer-api-external: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:39:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "40624" uid: ccd701ed-093c-4c3f-b0f5-99c14b792fa9 spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:25:45Z" message: 'load-balancer-api-internal: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.466431ms message: 'load-balancer-api-internal: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 9.683302ms message: 'load-balancer-api-internal: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:43:45Z" - latency: 5.11492ms message: 'load-balancer-api-internal: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 10.042528ms message: 'load-balancer-api-internal: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:42:45Z" - latency: 4.204518ms message: 'load-balancer-api-internal: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 9.114662ms message: 'load-balancer-api-internal: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:41:45Z" - latency: 5.773736ms message: 'load-balancer-api-internal: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 8.163819ms message: 'load-balancer-api-internal: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:40:45Z" - latency: 6.033238ms message: 'load-balancer-api-internal: tcp connection to a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 6.63756ms message: 'load-balancer-api-internal: resolved host name a99a5d4679ece4e9bbe04d46ea9fc180-184120c8f65d9f6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:39:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-network-check-target-ip-10-0-132-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "44914" uid: ff98e007-05ec-4053-858b-ba06768466ae spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:26:45Z" message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.424759ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:47:45Z" - latency: 2.377918ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:46:45Z" - latency: 2.451151ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:45:45Z" - latency: 2.521586ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:44:45Z" - latency: 2.20446ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 2.263329ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 2.569944ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 2.386097ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 2.105583ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 2.162751ms message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:38:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-network-check-target-ip-10-0-135-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "44912" uid: c75bf509-0c76-42b0-ad10-22582a5a8adf spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:26:45Z" message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.777µs message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:47:45Z" - latency: 1.252735ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:46:45Z" - latency: 989.233µs message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:45:45Z" - latency: 783.038µs message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:44:45Z" - latency: 1.430995ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 1.438945ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 1.236488ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 1.228913ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 1.248841ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 1.196723ms message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:38:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-network-check-target-ip-10-0-137-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "44911" uid: ad0b750d-6b5e-48d1-959c-5f6ef333e317 spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:26:45Z" message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.347096ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:47:45Z" - latency: 2.37807ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:46:45Z" - latency: 2.486234ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:45:45Z" - latency: 2.57686ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:44:45Z" - latency: 2.385335ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 2.380884ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 2.833569ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 2.291568ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 2.686416ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 2.334836ms message: 'network-check-target-ip-10-0-137-41: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:38:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-238-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-238.ec2.internal uid: f1d54952-d1fb-417a-bf1c-45892e3f00e2 resourceVersion: "40622" uid: 72e37c05-37e6-48f5-9c52-8a315ca95b05 spec: sourcePod: network-check-source-7bc5b6bf85-qpsrr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T02:25:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.676µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:43:45Z" - latency: 1.83294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:43:45Z" - latency: 1.072205ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:42:45Z" - latency: 2.180981ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:42:45Z" - latency: 1.497389ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:41:45Z" - latency: 1.814035ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:41:45Z" - latency: 800.338µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:40:45Z" - latency: 2.040778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:40:45Z" - latency: 828.912µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:39:45Z" - latency: 1.965425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:39:45Z" kind: List metadata: resourceVersion: ""