apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "122008" uid: 184b3773-741c-417d-8c5a-d1cba0e70a20 spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:51:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.353193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 1.546933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 1.217842ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 1.212381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:15Z" - latency: 1.194751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:15Z" - latency: 1.502275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:15Z" - latency: 1.100728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:15Z" - latency: 1.465307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:15Z" - latency: 1.378395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:15Z" - latency: 2.016526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "124484" uid: 0ce2e37d-6a5c-45bb-b6ae-99995ea73526 spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:50:15Z" message: 'load-balancer-api-external: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.974362ms message: 'load-balancer-api-external: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:15Z" - latency: 6.834616ms message: 'load-balancer-api-external: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:56:15Z" - latency: 55.797726ms message: 'load-balancer-api-external: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:15Z" - latency: 7.320968ms message: 'load-balancer-api-external: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:55:15Z" - latency: 56.098142ms message: 'load-balancer-api-external: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 8.727633ms message: 'load-balancer-api-external: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:15Z" - latency: 55.437459ms message: 'load-balancer-api-external: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 8.92103ms message: 'load-balancer-api-external: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:15Z" - latency: 53.073166ms message: 'load-balancer-api-external: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 7.06131ms message: 'load-balancer-api-external: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "124485" uid: 9232eb44-ede5-49b7-b4f9-e658ebcba67a spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:50:15Z" message: 'load-balancer-api-internal: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.959914ms message: 'load-balancer-api-internal: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:15Z" - latency: 6.86017ms message: 'load-balancer-api-internal: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:56:15Z" - latency: 54.115917ms message: 'load-balancer-api-internal: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:15Z" - latency: 7.364136ms message: 'load-balancer-api-internal: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:55:15Z" - latency: 53.677469ms message: 'load-balancer-api-internal: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 8.925713ms message: 'load-balancer-api-internal: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:15Z" - latency: 54.084853ms message: 'load-balancer-api-internal: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 9.005565ms message: 'load-balancer-api-internal: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:15Z" - latency: 52.581418ms message: 'load-balancer-api-internal: tcp connection to a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 7.228695ms message: 'load-balancer-api-internal: resolved host name a3ee7570faedf4a5ca3084ec2df71db2-8c14c679226562c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-128-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "122003" uid: 10bf8528-0feb-4726-a496-2d1e0cd5598e spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:15Z" message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.352874ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 2.354747ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 2.386078ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 3.182794ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:15Z" - latency: 2.444676ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:15Z" - latency: 2.064ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:15Z" - latency: 2.168912ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:15Z" - latency: 2.612207ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:15Z" - latency: 2.448867ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:15Z" - latency: 2.216602ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-133-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "122006" uid: ac6ee946-7d20-4dda-8b2a-193cd3aa1bb2 spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:15Z" message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.070156ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 2.751931ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 2.484863ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 3.570527ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:15Z" - latency: 2.533524ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:15Z" - latency: 2.189594ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:15Z" - latency: 2.600187ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:15Z" - latency: 2.448968ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:15Z" - latency: 2.644195ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:15Z" - latency: 2.694694ms message: 'network-check-target-ip-10-0-133-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-141-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "122002" uid: 06a2bcbd-c12a-4c59-a239-ff402e216559 spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:15Z" message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.351413ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 1.04511ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 1.836319ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 3.677339ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:15Z" - latency: 875.969µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:15Z" - latency: 1.076185ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:15Z" - latency: 1.589699ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:15Z" - latency: 2.22848ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:15Z" - latency: 1.747049ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:15Z" - latency: 1.553895ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.us-west-1.compute.internal uid: 64b6e104-9769-42a3-9b90-fe6d258f580e resourceVersion: "124482" uid: 022a98be-9985-4317-b8b9-a0ac759c98da spec: sourcePod: network-check-source-6f78d59f99-l2prc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:50:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.943µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:15Z" - latency: 2.655398ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:56:15Z" - latency: 796.008µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:15Z" - latency: 2.626044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:55:15Z" - latency: 885.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:15Z" - latency: 2.398226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:15Z" - latency: 873.392µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:15Z" - latency: 2.18104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:15Z" - latency: 918.462µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:15Z" - latency: 2.357292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:15Z" kind: List metadata: resourceVersion: ""