apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "174497" uid: 35066d00-7c51-42f4-91b5-1db2f19dac49 spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T22:34:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 983.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:22:34Z" - latency: 917.652µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:21:34Z" - latency: 1.045131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:20:34Z" - latency: 1.231178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:19:34Z" - latency: 919.33µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:18:34Z" - latency: 1.391936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:17:34Z" - latency: 1.508725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:16:34Z" - latency: 1.121639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:15:34Z" - latency: 825.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:14:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "181783" uid: 73030a6f-3011-4552-9ba2-a1c0266d2d4c spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T22:33:34Z" message: 'load-balancer-api-external: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.716214ms message: 'load-balancer-api-external: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:27:34Z" - latency: 6.831845ms message: 'load-balancer-api-external: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:27:34Z" - latency: 5.092728ms message: 'load-balancer-api-external: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:26:34Z" - latency: 8.022467ms message: 'load-balancer-api-external: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:26:34Z" - latency: 9.026807ms message: 'load-balancer-api-external: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:25:34Z" - latency: 7.101302ms message: 'load-balancer-api-external: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:25:34Z" - latency: 5.792455ms message: 'load-balancer-api-external: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:24:34Z" - latency: 7.763371ms message: 'load-balancer-api-external: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:24:34Z" - latency: 5.588587ms message: 'load-balancer-api-external: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 7.677763ms message: 'load-balancer-api-external: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:23:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "181782" uid: fd23c8f6-ec94-4d41-baf3-6b14bbc672cf spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T22:33:34Z" message: 'load-balancer-api-internal: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.535814ms message: 'load-balancer-api-internal: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:27:34Z" - latency: 6.907283ms message: 'load-balancer-api-internal: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:27:34Z" - latency: 5.167573ms message: 'load-balancer-api-internal: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:26:34Z" - latency: 7.895495ms message: 'load-balancer-api-internal: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:26:34Z" - latency: 9.031427ms message: 'load-balancer-api-internal: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:25:34Z" - latency: 7.057794ms message: 'load-balancer-api-internal: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:25:34Z" - latency: 5.788254ms message: 'load-balancer-api-internal: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:24:34Z" - latency: 7.690102ms message: 'load-balancer-api-internal: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:24:34Z" - latency: 5.709681ms message: 'load-balancer-api-internal: tcp connection to a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 7.579586ms message: 'load-balancer-api-internal: resolved host name a4b2c3b4c121d4dfd8e3a2eaca441619-09a864881a6b6db7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:23:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-network-check-target-ip-10-0-138-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "174495" uid: 62c941de-3d4b-4472-83ae-be77673b729b spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T22:34:34Z" message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.492336ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 1.511328ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:22:34Z" - latency: 1.651774ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:21:34Z" - latency: 2.126638ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:20:34Z" - latency: 1.783002ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:19:34Z" - latency: 1.790629ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:18:34Z" - latency: 2.141982ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:17:34Z" - latency: 2.317717ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:16:34Z" - latency: 2.304786ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:15:34Z" - latency: 1.727568ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:14:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-network-check-target-ip-10-0-141-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "174494" uid: 14745b5a-e0fb-4ead-80f2-e287f5111088 spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T22:34:34Z" message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.238095ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 1.72329ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:22:34Z" - latency: 800.152µs message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:21:34Z" - latency: 917.056µs message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:20:34Z" - latency: 1.588993ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:19:34Z" - latency: 1.393885ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:18:34Z" - latency: 1.117844ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:17:34Z" - latency: 1.783322ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:16:34Z" - latency: 966.543µs message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:15:34Z" - latency: 917.936µs message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:14:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-network-check-target-ip-10-0-142-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "174496" uid: d48bd992-942a-4326-9f27-a186e3ae3764 spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T22:34:34Z" message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.568001ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 2.507887ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:22:34Z" - latency: 2.326734ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:21:34Z" - latency: 2.389643ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:20:34Z" - latency: 3.308307ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:19:34Z" - latency: 2.055659ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:18:34Z" - latency: 2.244707ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:17:34Z" - latency: 2.66946ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:16:34Z" - latency: 2.456895ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:15:34Z" - latency: 2.190449ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:14:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:27:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-223-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-223.us-east-2.compute.internal uid: 49b45bbf-11e4-445f-9a6e-b170436d9be4 resourceVersion: "181781" uid: ce12eccd-6a4b-4919-b4a3-440d820291f9 spec: sourcePod: network-check-source-6f78d59f99-xqcfc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T22:33:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.371µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:27:34Z" - latency: 1.913779ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:27:34Z" - latency: 1.010983ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:26:34Z" - latency: 1.886356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:26:34Z" - latency: 1.159925ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:25:34Z" - latency: 2.362143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:25:34Z" - latency: 861.26µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:24:34Z" - latency: 2.717854ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:24:34Z" - latency: 1.237524ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:23:34Z" - latency: 2.390099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:23:34Z" kind: List metadata: resourceVersion: ""