apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "80151" uid: 2c51a9b5-d84e-400c-a256-46ea50ee655b spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T10:49:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.278µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:38:21Z" - latency: 1.622649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:37:21Z" - latency: 1.392769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 913.504µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 1.469586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 1.119308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 1.481518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 1.02996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:31:21Z" - latency: 1.05408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:30:21Z" - latency: 1.13331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "75657" uid: 29d799c1-0a0f-418a-ab54-4a9fceb0da50 spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T10:48:21Z" message: 'load-balancer-api-external: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.738633ms message: 'load-balancer-api-external: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 6.674237ms message: 'load-balancer-api-external: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:36:21Z" - latency: 4.242632ms message: 'load-balancer-api-external: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 6.122319ms message: 'load-balancer-api-external: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:35:21Z" - latency: 4.544228ms message: 'load-balancer-api-external: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 7.094892ms message: 'load-balancer-api-external: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:34:21Z" - latency: 4.77577ms message: 'load-balancer-api-external: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 6.380168ms message: 'load-balancer-api-external: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:33:21Z" - latency: 3.398514ms message: 'load-balancer-api-external: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 7.226826ms message: 'load-balancer-api-external: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "75656" uid: dd74a3a3-2415-4772-a9f0-a497a5fde565 spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T10:48:21Z" message: 'load-balancer-api-internal: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.501612ms message: 'load-balancer-api-internal: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 6.603235ms message: 'load-balancer-api-internal: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:36:21Z" - latency: 4.244727ms message: 'load-balancer-api-internal: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 6.080095ms message: 'load-balancer-api-internal: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:35:21Z" - latency: 4.553824ms message: 'load-balancer-api-internal: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 7.00434ms message: 'load-balancer-api-internal: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:34:21Z" - latency: 4.658384ms message: 'load-balancer-api-internal: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 6.316128ms message: 'load-balancer-api-internal: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:33:21Z" - latency: 4.597026ms message: 'load-balancer-api-internal: tcp connection to a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 7.154292ms message: 'load-balancer-api-internal: resolved host name a02122b2258254b298a6106e2133c24f-0899867d1bd7930a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T11:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-131-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "80148" uid: 9d9f2cca-dc49-4297-a8b1-f00e7a3c4fd1 spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T10:49:21Z" message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.246µs message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:38:21Z" - latency: 845.193µs message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:37:21Z" - latency: 835.377µs message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 1.209107ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 1.596642ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 838.744µs message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 1.930691ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 1.503548ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:31:21Z" - latency: 883.599µs message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:30:21Z" - latency: 1.057236ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-136-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "80150" uid: 0a989695-313c-401d-ac9f-fa875f3664e6 spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T10:49:21Z" message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.977078ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:38:21Z" - latency: 2.250834ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:37:21Z" - latency: 2.244004ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 2.053174ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 2.056711ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 2.148796ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 2.14043ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 2.163004ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:31:21Z" - latency: 2.225289ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:30:21Z" - latency: 2.116634ms message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-142-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "80149" uid: 8a775dcb-8472-456b-98b6-000199d6fcf5 spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T10:49:21Z" message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.917756ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:38:21Z" - latency: 2.347152ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:37:21Z" - latency: 2.144976ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 2.042232ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 2.081934ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 1.772982ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 1.969024ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 2.142981ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:31:21Z" - latency: 2.019496ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:30:21Z" - latency: 2.173743ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:29:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T10:42:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-159-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-159.ec2.internal uid: fa1115d9-0fd7-46fa-96f8-432ae418ab54 resourceVersion: "75654" uid: 88bbaf02-1120-4541-b692-6dd83859a040 spec: sourcePod: network-check-source-65bdbbff45-7pnrz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T10:48:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.105µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:36:21Z" - latency: 1.748848ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T11:36:21Z" - latency: 1.330281ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:35:21Z" - latency: 1.598258ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T11:35:21Z" - latency: 919.296µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:34:21Z" - latency: 1.821857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T11:34:21Z" - latency: 916.713µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:33:21Z" - latency: 1.806785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T11:33:21Z" - latency: 924.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T11:32:21Z" - latency: 2.099064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T11:32:21Z" kind: List metadata: resourceVersion: ""