apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "55275" uid: f89b45bf-18c3-419d-ac51-94b207d3b507 spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T04:49:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.105047ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:17:41Z" - latency: 1.0083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:16:41Z" - latency: 1.050974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:15:41Z" - latency: 1.001359ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:14:41Z" - latency: 937.644µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:13:41Z" - latency: 1.01905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 914.329µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 1.014563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 1.137485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 910.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "50329" uid: aa6db9e5-1d82-44f3-8a20-c0c2ea75d3df spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T04:48:41Z" message: 'load-balancer-api-external: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.114174ms message: 'load-balancer-api-external: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 7.213668ms message: 'load-balancer-api-external: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:12:41Z" - latency: 5.441756ms message: 'load-balancer-api-external: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 6.698259ms message: 'load-balancer-api-external: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:11:41Z" - latency: 5.231903ms message: 'load-balancer-api-external: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 7.215569ms message: 'load-balancer-api-external: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:10:41Z" - latency: 3.955263ms message: 'load-balancer-api-external: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 6.668119ms message: 'load-balancer-api-external: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:09:41Z" - latency: 3.259464ms message: 'load-balancer-api-external: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - latency: 6.66812ms message: 'load-balancer-api-external: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:08:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "50328" uid: 08267174-736c-4072-ae06-06e9d8200915 spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T04:48:41Z" message: 'load-balancer-api-internal: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.072641ms message: 'load-balancer-api-internal: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 7.150691ms message: 'load-balancer-api-internal: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:12:41Z" - latency: 4.544821ms message: 'load-balancer-api-internal: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 6.728938ms message: 'load-balancer-api-internal: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:11:41Z" - latency: 5.240908ms message: 'load-balancer-api-internal: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 7.196098ms message: 'load-balancer-api-internal: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:10:41Z" - latency: 4.312793ms message: 'load-balancer-api-internal: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 6.832268ms message: 'load-balancer-api-internal: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:09:41Z" - latency: 3.322465ms message: 'load-balancer-api-internal: tcp connection to a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - latency: 6.612559ms message: 'load-balancer-api-internal: resolved host name a162f57d183f648a0847f28e16979aed-4f7be0ade2dab6eb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:08:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-network-check-target-ip-10-0-132-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "55273" uid: 4f8a8c39-79a0-4747-a029-798a51c63567 spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T04:49:41Z" message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.36855ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:17:41Z" - latency: 2.357349ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:16:41Z" - latency: 2.292372ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:15:41Z" - latency: 2.166942ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:14:41Z" - latency: 2.033113ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:13:41Z" - latency: 2.552168ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 2.181854ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 2.648093ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 2.553671ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 2.337817ms message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-network-check-target-ip-10-0-137-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "55274" uid: 2edcaa5b-1c33-48d9-b648-2523f41329c0 spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T04:49:41Z" message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.151477ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:17:41Z" - latency: 2.44115ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:16:41Z" - latency: 2.391827ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:15:41Z" - latency: 2.373554ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:14:41Z" - latency: 1.720116ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:13:41Z" - latency: 2.485479ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 2.211583ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 2.687378ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 2.490761ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 2.029629ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-network-check-target-ip-10-0-140-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "55272" uid: b2c7ef6f-41f7-4fa8-833f-ffa8a4b56dc9 spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T04:49:41Z" message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.639µs message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:17:41Z" - latency: 1.060863ms message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:16:41Z" - latency: 1.254799ms message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:15:41Z" - latency: 907.826µs message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:14:41Z" - latency: 1.098101ms message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:13:41Z" - latency: 1.352644ms message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 869.613µs message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 1.442257ms message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 1.095231ms message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 779.164µs message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-3-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-3.ec2.internal uid: 323811be-020d-476f-a2f8-2e8fe2a11ff9 resourceVersion: "50327" uid: c01429f5-fac7-4009-b5a2-8679d31f9edb spec: sourcePod: network-check-source-869dcfcdcd-g9vq4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T04:48:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.007µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:12:41Z" - latency: 1.736517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:12:41Z" - latency: 748.999µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:11:41Z" - latency: 1.606934ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:11:41Z" - latency: 872.719µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:10:41Z" - latency: 2.308451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:10:41Z" - latency: 864.442µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:09:41Z" - latency: 1.943318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:09:41Z" - latency: 976.771µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:08:41Z" - latency: 1.588833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:08:41Z" kind: List metadata: resourceVersion: ""