apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "22403" uid: 6e328f3d-3bba-4455-8bf3-bc8c891b4762 spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T07:39:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:00:30Z" - latency: 1.30517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:30Z" - latency: 1.096661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:30Z" - latency: 893.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:30Z" - latency: 1.365368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:30Z" - latency: 1.106444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:30Z" - latency: 917.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:30Z" - latency: 1.158177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:30Z" - latency: 1.291891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:30Z" - latency: 1.044849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "20647" uid: 198730b5-487c-4ced-ab9d-d27bc923e0e9 spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T07:38:31Z" message: 'load-balancer-api-external: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.831878ms message: 'load-balancer-api-external: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:31Z" - latency: 5.715837ms message: 'load-balancer-api-external: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:56:31Z" - latency: 5.119179ms message: 'load-balancer-api-external: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:31Z" - latency: 6.755782ms message: 'load-balancer-api-external: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:55:31Z" - latency: 5.614827ms message: 'load-balancer-api-external: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:31Z" - latency: 7.154752ms message: 'load-balancer-api-external: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:54:31Z" - latency: 3.686642ms message: 'load-balancer-api-external: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:31Z" - latency: 7.984203ms message: 'load-balancer-api-external: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:53:31Z" - latency: 5.497247ms message: 'load-balancer-api-external: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:31Z" - latency: 7.305656ms message: 'load-balancer-api-external: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:52:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "20648" uid: 2112867f-3cef-4872-a249-dda075eb024c spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T07:38:31Z" message: 'load-balancer-api-internal: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.875849ms message: 'load-balancer-api-internal: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:31Z" - latency: 2.571763ms message: 'load-balancer-api-internal: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:56:31Z" - latency: 5.568949ms message: 'load-balancer-api-internal: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:31Z" - latency: 6.294199ms message: 'load-balancer-api-internal: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:55:31Z" - latency: 4.633607ms message: 'load-balancer-api-internal: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:31Z" - latency: 2.498645ms message: 'load-balancer-api-internal: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:54:31Z" - latency: 4.469256ms message: 'load-balancer-api-internal: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:31Z" - latency: 3.020022ms message: 'load-balancer-api-internal: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:53:31Z" - latency: 4.705084ms message: 'load-balancer-api-internal: tcp connection to acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:31Z" - latency: 4.558947ms message: 'load-balancer-api-internal: resolved host name acd2c9dfd096346149664c29861c205b-d73b07730df18667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:52:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-128-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "22402" uid: ed673be7-009e-4e18-b881-1bffecb9dc21 spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T07:39:30Z" message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.84175ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:00:30Z" - latency: 1.736874ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:30Z" - latency: 1.448006ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:30Z" - latency: 1.860833ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:30Z" - latency: 1.692827ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:30Z" - latency: 1.739624ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:30Z" - latency: 1.729628ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:30Z" - latency: 1.666029ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:30Z" - latency: 1.997889ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:30Z" - latency: 2.045583ms message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-132-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "22400" uid: 803078ca-75c9-4437-a962-23448a46eb17 spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T07:39:30Z" message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.266371ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:00:30Z" - latency: 2.178408ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:30Z" - latency: 1.674813ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:30Z" - latency: 2.096842ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:30Z" - latency: 2.08804ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:30Z" - latency: 1.83802ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:30Z" - latency: 2.158975ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:30Z" - latency: 2.462544ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:30Z" - latency: 1.828794ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:30Z" - latency: 2.311529ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-139-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "22401" uid: 16fd9700-aa49-4e8d-9786-6a8f337450af spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T07:39:30Z" message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.277µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:00:30Z" - latency: 1.049837ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:30Z" - latency: 732.164µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:30Z" - latency: 844.226µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:30Z" - latency: 858.988µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:30Z" - latency: 1.301165ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:30Z" - latency: 1.278169ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:30Z" - latency: 905.102µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:30Z" - latency: 1.058617ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:30Z" - latency: 732.572µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:32:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: c8505306-2650-4f59-ade4-3e63e819951c resourceVersion: "20644" uid: 29e51f03-1619-4d62-b34c-2ac9de8ba369 spec: sourcePod: network-check-source-6f8b768455-bjh22 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T07:38:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.18214ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:30Z" - latency: 1.646525ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:56:30Z" - latency: 845.742µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:30Z" - latency: 1.593084ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:55:30Z" - latency: 862.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:30Z" - latency: 1.777914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:54:30Z" - latency: 843.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:30Z" - latency: 2.426541ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:53:30Z" - latency: 615.676µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:30Z" - latency: 2.092134ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:52:30Z" kind: List metadata: resourceVersion: ""