apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "55151" uid: 7da17447-2f38-4f52-89f3-76ae87079d03 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T20:12: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.284732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 902.216µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 929.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 833.589µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 1.658798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:36:20Z" - latency: 1.207093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:35:20Z" - latency: 1.046127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:34:20Z" - latency: 1.079214ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:33:20Z" - latency: 892.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:32:20Z" - latency: 929.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:31:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "56154" uid: f6c40214-5b73-4a3d-8c6d-496b0f66e708 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T20:11:20Z" message: 'load-balancer-api-external: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.886707ms message: 'load-balancer-api-external: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:41:20Z" - latency: 9.450481ms message: 'load-balancer-api-external: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:41:20Z" - latency: 3.522646ms message: 'load-balancer-api-external: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 13.881948ms message: 'load-balancer-api-external: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:40:20Z" - latency: 5.121716ms message: 'load-balancer-api-external: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 9.223552ms message: 'load-balancer-api-external: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:39:20Z" - latency: 4.208331ms message: 'load-balancer-api-external: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 11.531842ms message: 'load-balancer-api-external: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:38:20Z" - latency: 3.406241ms message: 'load-balancer-api-external: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 9.27972ms message: 'load-balancer-api-external: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:37:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "56155" uid: f1258253-5264-4fb5-bfe2-5bd809a95890 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T20:11:20Z" message: 'load-balancer-api-internal: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.859797ms message: 'load-balancer-api-internal: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:41:20Z" - latency: 9.498168ms message: 'load-balancer-api-internal: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:41:20Z" - latency: 3.54983ms message: 'load-balancer-api-internal: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 13.958624ms message: 'load-balancer-api-internal: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:40:20Z" - latency: 5.106409ms message: 'load-balancer-api-internal: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 9.273032ms message: 'load-balancer-api-internal: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:39:20Z" - latency: 4.191633ms message: 'load-balancer-api-internal: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 11.590691ms message: 'load-balancer-api-internal: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:38:20Z" - latency: 4.600104ms message: 'load-balancer-api-internal: tcp connection to ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 9.265472ms message: 'load-balancer-api-internal: resolved host name ae0d76204c64b42df8a756026aa6e3ce-ece6b46386d0d4ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T20:37:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-ip-10-0-133-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "55149" uid: 51268517-3566-4cc8-88de-8b9909e5ebe2 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T20:12:20Z" message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.401057ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 2.387975ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 2.09737ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 2.257918ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 2.161833ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:36:20Z" - latency: 2.790437ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:35:20Z" - latency: 2.392194ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:34:20Z" - latency: 2.420975ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:33:20Z" - latency: 2.100482ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:32:20Z" - latency: 2.654442ms message: 'network-check-target-ip-10-0-133-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:31:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-ip-10-0-133-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "55148" uid: fb555b2a-d899-48a8-9680-bf55941827c2 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T20:12:20Z" message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.213225ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 852.361µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 980.261µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 1.065426ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 754.102µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:36:20Z" - latency: 1.366454ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:35:20Z" - latency: 1.306574ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:34:20Z" - latency: 1.331656ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:33:20Z" - latency: 877.122µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:32:20Z" - latency: 1.115546ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:31:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-ip-10-0-134-113 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "55150" uid: 56d0e74f-ff95-492b-b525-1863a613ab40 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T20:12:20Z" message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.562667ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 2.726768ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 2.6048ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 2.265245ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 2.995402ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:36:20Z" - latency: 2.844834ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:35:20Z" - latency: 2.295151ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:34:20Z" - latency: 2.330678ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:33:20Z" - latency: 2.205388ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:32:20Z" - latency: 2.349632ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:31:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T20:05:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e3dfbf69-5873-4708-83bf-dc8adb981185 resourceVersion: "56153" uid: 5ef655f0-6607-4256-bfc2-d674770eea61 spec: sourcePod: network-check-source-989f8b8dc-skstg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T20:11:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.201µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:41:20Z" - latency: 2.116318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T20:41:20Z" - latency: 988.98µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:40:20Z" - latency: 1.6962ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T20:40:20Z" - latency: 750.077µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:39:20Z" - latency: 1.618435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T20:39:20Z" - latency: 1.171531ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:38:20Z" - latency: 1.813542ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T20:38:20Z" - latency: 871.771µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T20:37:20Z" - latency: 1.676405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T20:37:20Z" kind: List metadata: resourceVersion: ""