apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "54170" uid: 13297fae-32d6-4f4f-acb1-3dba883878b4 spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T14:23:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.173099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:16Z" - latency: 1.503ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:16Z" - latency: 1.09244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:16Z" - latency: 1.040188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:16Z" - latency: 932.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:47:16Z" - latency: 1.264078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:46:16Z" - latency: 1.047622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:45:16Z" - latency: 943.254µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:44:16Z" - latency: 1.133727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:43:16Z" - latency: 1.283301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:42:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "55237" uid: 05e614d3-b1bc-40c1-b59c-0a7bfa774cb9 spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T14:22:16Z" message: 'load-balancer-api-external: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.51357ms message: 'load-balancer-api-external: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:16Z" - latency: 6.964311ms message: 'load-balancer-api-external: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:52:16Z" - latency: 5.424119ms message: 'load-balancer-api-external: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:16Z" - latency: 9.217294ms message: 'load-balancer-api-external: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:51:16Z" - latency: 4.114267ms message: 'load-balancer-api-external: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:16Z" - latency: 9.198716ms message: 'load-balancer-api-external: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:50:16Z" - latency: 8.540103ms message: 'load-balancer-api-external: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:16Z" - latency: 10.354283ms message: 'load-balancer-api-external: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:49:16Z" - latency: 4.407548ms message: 'load-balancer-api-external: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:16Z" - latency: 8.464057ms message: 'load-balancer-api-external: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:48:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "55238" uid: 069c49ff-9974-4342-a7e8-f18a948447e6 spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T14:22:16Z" message: 'load-balancer-api-internal: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.804581ms message: 'load-balancer-api-internal: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:16Z" - latency: 6.986789ms message: 'load-balancer-api-internal: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:52:16Z" - latency: 4.992716ms message: 'load-balancer-api-internal: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:16Z" - latency: 9.185522ms message: 'load-balancer-api-internal: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:51:16Z" - latency: 4.753246ms message: 'load-balancer-api-internal: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:16Z" - latency: 9.2973ms message: 'load-balancer-api-internal: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:50:16Z" - latency: 12.300478ms message: 'load-balancer-api-internal: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:16Z" - latency: 10.391176ms message: 'load-balancer-api-internal: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:49:16Z" - latency: 4.400854ms message: 'load-balancer-api-internal: tcp connection to adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:16Z" - latency: 8.534781ms message: 'load-balancer-api-internal: resolved host name adfc7bb7b40ea47f8a0772099f814621-c9a68f8c5e4c1e35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:48:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-network-check-target-ip-10-0-141-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "54169" uid: 79a9567f-6ec0-4e38-b029-264ac930596f spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:23:16Z" message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.324278ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:16Z" - latency: 1.218735ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:16Z" - latency: 1.075678ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:16Z" - latency: 1.554961ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:16Z" - latency: 1.6754ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:47:16Z" - latency: 1.662973ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:46:16Z" - latency: 1.28125ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:45:16Z" - latency: 920.861µs message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:44:16Z" - latency: 1.414916ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:43:16Z" - latency: 1.441271ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:42:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-network-check-target-ip-10-0-142-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "54278" uid: 36f0bdc8-c170-4121-8709-25fd66439915 spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:23:22Z" message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.234565ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:22Z" - latency: 2.598369ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:22Z" - latency: 1.207121ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:22Z" - latency: 2.404536ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:22Z" - latency: 2.650376ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:47:22Z" - latency: 2.224162ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:46:22Z" - latency: 2.586345ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:45:22Z" - latency: 2.64005ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:44:22Z" - latency: 2.687724ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:43:22Z" - latency: 2.516544ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-network-check-target-ip-10-0-142-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "54350" uid: 950b877a-bcda-4fe6-943a-17450d74a2f2 spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:23:25Z" message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.080538ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:25Z" - latency: 848.268µs message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:25Z" - latency: 2.355642ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:25Z" - latency: 1.061465ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:25Z" - latency: 2.325694ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:47:25Z" - latency: 948.239µs message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:46:25Z" - latency: 1.067881ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:45:25Z" - latency: 871.372µs message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:44:25Z" - latency: 2.482202ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:43:25Z" - latency: 2.455901ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:42:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-45.ec2.internal uid: 09ca8fd0-2353-4c83-9865-3c18766290fd resourceVersion: "55236" uid: c91b5a7f-44b7-4f19-80a9-98c011ffb120 spec: sourcePod: network-check-source-869dcfcdcd-27tzm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T14:22:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.53µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:16Z" - latency: 1.697178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:52:16Z" - latency: 2.214033ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:16Z" - latency: 2.169456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:51:16Z" - latency: 1.886906ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:16Z" - latency: 1.82549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:50:16Z" - latency: 1.880632ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:49:16Z" - latency: 1.799565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:49:16Z" - latency: 2.198617ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:48:16Z" - latency: 1.789571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:48:16Z" kind: List metadata: resourceVersion: ""