apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "23497" uid: 6eacb5de-cbc9-4d02-9ffe-3ef5309ef673 spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T03:50:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.162143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:50:02Z" - latency: 994.086µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 1.180488ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 1.053353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 940.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 890.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 1.504742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:44:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "22296" uid: f2dd651b-f0b8-4dd1-83c6-da9534d939fb spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T03:49:02Z" message: 'load-balancer-api-external: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.566602ms message: 'load-balancer-api-external: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 7.320654ms message: 'load-balancer-api-external: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:49:02Z" - latency: 4.477337ms message: 'load-balancer-api-external: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 7.780889ms message: 'load-balancer-api-external: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:48:02Z" - latency: 4.570668ms message: 'load-balancer-api-external: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 7.353574ms message: 'load-balancer-api-external: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:47:02Z" - latency: 4.568425ms message: 'load-balancer-api-external: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 7.426312ms message: 'load-balancer-api-external: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:46:02Z" - latency: 5.662277ms message: 'load-balancer-api-external: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 8.206601ms message: 'load-balancer-api-external: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:45:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "22295" uid: 02f8b813-e8aa-4bc0-af9c-51e9bd01392b spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T03:49:02Z" message: 'load-balancer-api-internal: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.643475ms message: 'load-balancer-api-internal: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 7.423951ms message: 'load-balancer-api-internal: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:49:02Z" - latency: 4.474027ms message: 'load-balancer-api-internal: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 7.8337ms message: 'load-balancer-api-internal: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:48:02Z" - latency: 4.560499ms message: 'load-balancer-api-internal: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 7.423012ms message: 'load-balancer-api-internal: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:47:02Z" - latency: 4.529402ms message: 'load-balancer-api-internal: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 7.478031ms message: 'load-balancer-api-internal: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:46:02Z" - latency: 4.610935ms message: 'load-balancer-api-internal: tcp connection to a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 8.270448ms message: 'load-balancer-api-internal: resolved host name a5768778ff7c34f5cbfd55a83adb2b23-8522ab15edefda46.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T03:45:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-ip-10-0-130-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "23496" uid: 2d583353-c437-4740-ba48-d5c74c643bce spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T03:50:02Z" message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.095773ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:50:02Z" - latency: 2.479938ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 2.259592ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 2.422194ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 2.264619ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 2.507781ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 3.097444ms message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:44:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-ip-10-0-130-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "23494" uid: a93ddbc4-9e54-464a-b8fd-b7b89fc23c1b spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T03:50:02Z" message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.026738ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:50:02Z" - latency: 1.048504ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 1.276265ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 1.24914ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 1.084532ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 1.03544ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 1.196649ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:44:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-ip-10-0-132-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "23495" uid: 9418052d-41ad-463a-9859-c4b19be6a8e5 spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T03:50:02Z" message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.327673ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:50:02Z" - latency: 2.061687ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 2.385992ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 2.332513ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 2.564904ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 2.978417ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 2.526511ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:44:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T03:43:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: fbdd846c-36b0-4915-ba5b-be8a0722cc8c resourceVersion: "22294" uid: a389fa08-21d8-4cf7-b7ad-1395c8f74819 spec: sourcePod: network-check-source-685456655f-245ck targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T03:49:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:49:02Z" - latency: 1.811471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T03:49:02Z" - latency: 904.196µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:48:02Z" - latency: 2.085978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T03:48:02Z" - latency: 1.347527ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:47:02Z" - latency: 1.797502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T03:47:02Z" - latency: 1.233111ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:46:02Z" - latency: 1.842431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T03:46:02Z" - latency: 830.372µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T03:45:02Z" - latency: 3.277691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T03:45:02Z" kind: List metadata: resourceVersion: ""