apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26597" uid: 92bc8de5-6692-4d2b-97dd-fb205e8ead60 spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T03:47: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.157519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:29:02Z" - latency: 759.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 1.686546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 1.063309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 1.426131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 1.028042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 992.095µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:23:02Z" - latency: 1.125845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:22:02Z" - latency: 1.006455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:21:02Z" - latency: 1.398441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:20:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26383" uid: 0cd5ce40-b312-4b0d-be28-e8b5412854da spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T03:46:02Z" message: 'load-balancer-api-external: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.979952ms message: 'load-balancer-api-external: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 7.414848ms message: 'load-balancer-api-external: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:28:02Z" - latency: 50.574455ms message: 'load-balancer-api-external: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 6.63845ms message: 'load-balancer-api-external: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:27:02Z" - latency: 50.723783ms message: 'load-balancer-api-external: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 7.333435ms message: 'load-balancer-api-external: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:26:02Z" - latency: 54.536522ms message: 'load-balancer-api-external: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 7.786123ms message: 'load-balancer-api-external: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:25:02Z" - latency: 50.962152ms message: 'load-balancer-api-external: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 6.83516ms message: 'load-balancer-api-external: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:24:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26382" uid: 5e863311-0882-40a4-b659-bb386a7c64a1 spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T03:46:02Z" message: 'load-balancer-api-internal: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.365298ms message: 'load-balancer-api-internal: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 7.388761ms message: 'load-balancer-api-internal: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:28:02Z" - latency: 50.564426ms message: 'load-balancer-api-internal: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 6.710073ms message: 'load-balancer-api-internal: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:27:02Z" - latency: 55.183999ms message: 'load-balancer-api-internal: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 7.362195ms message: 'load-balancer-api-internal: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:26:02Z" - latency: 57.758906ms message: 'load-balancer-api-internal: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 8.026784ms message: 'load-balancer-api-internal: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:25:02Z" - latency: 55.266872ms message: 'load-balancer-api-internal: tcp connection to a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 6.822175ms message: 'load-balancer-api-internal: resolved host name a95d53b49f229424e99485fc26e575f5-a56771d31ca32175.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:24:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-network-check-target-ip-10-0-128-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26594" uid: 6bb08f36-657c-4d7c-a693-ea3cbcd7b8ed spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:47:02Z" message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.99691ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:29:02Z" - latency: 1.669876ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 1.94382ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 1.908737ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 2.035047ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 2.217617ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 2.130595ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:23:02Z" - latency: 2.026429ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:22:02Z" - latency: 1.75111ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:21:02Z" - latency: 2.235362ms message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:20:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-network-check-target-ip-10-0-128-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26596" uid: 66410a64-213d-4dfd-9aa7-44ed7cbb07fc spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:47:02Z" message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.580905ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:29:02Z" - latency: 2.163459ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 2.283511ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 2.336405ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 2.42477ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 2.487118ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 2.061564ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:23:02Z" - latency: 2.318948ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:22:02Z" - latency: 2.228285ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:21:02Z" - latency: 2.232723ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:20:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-network-check-target-ip-10-0-135-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26595" uid: 40575c0f-a5f6-4e93-b3da-ea45301f59e7 spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:47:02Z" message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.731073ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:29:02Z" - latency: 763.171µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 830.475µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 871.658µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 969.438µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 1.169351ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 1.506609ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:23:02Z" - latency: 775.068µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:22:02Z" - latency: 875.643µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:21:02Z" - latency: 869.495µs message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:20:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-81-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-81.us-west-2.compute.internal uid: 997a28d7-967a-4226-b593-88f8c9a74151 resourceVersion: "26381" uid: 8afdd4c6-5072-4700-aef9-bfd63720314c spec: sourcePod: network-check-source-6f78d59f99-k48q7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T03:46:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145867ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:28:02Z" - latency: 1.729165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:28:02Z" - latency: 958.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:27:02Z" - latency: 2.181419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:27:02Z" - latency: 972.74µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:26:02Z" - latency: 1.864281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:26:02Z" - latency: 894.256µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:25:02Z" - latency: 2.531355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:25:02Z" - latency: 682.996µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:24:02Z" - latency: 1.709411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:24:02Z" kind: List metadata: resourceVersion: ""