apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "71442" uid: b4f5c6b0-8128-4a85-9cd9-122e2c9322c5 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T16:13:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.197665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:59Z" - latency: 1.093119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:59Z" - latency: 1.140159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:59Z" - latency: 849.28µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:59Z" - latency: 1.173319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:59Z" - latency: 1.210819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:59Z" - latency: 1.249003ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:59Z" - latency: 1.215044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:48:59Z" - latency: 978.787µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:47:59Z" - latency: 846.415µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "79518" uid: 251ffc79-80ac-4e57-908f-5793b1c43ec2 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T16:12:59Z" message: 'load-balancer-api-external: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.489457ms message: 'load-balancer-api-external: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T17:00:59Z" - latency: 7.386594ms message: 'load-balancer-api-external: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T17:00:59Z" - latency: 5.344638ms message: 'load-balancer-api-external: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:59:59Z" - latency: 9.360873ms message: 'load-balancer-api-external: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:59:59Z" - latency: 3.992952ms message: 'load-balancer-api-external: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:59Z" - latency: 9.889817ms message: 'load-balancer-api-external: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:58:59Z" - latency: 4.038464ms message: 'load-balancer-api-external: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:59Z" - latency: 10.437612ms message: 'load-balancer-api-external: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:57:59Z" - latency: 4.177572ms message: 'load-balancer-api-external: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:59Z" - latency: 7.972339ms message: 'load-balancer-api-external: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "79517" uid: 5d5fc7f9-0a38-4733-b45b-560f803b48e5 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T16:12:59Z" message: 'load-balancer-api-internal: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.556158ms message: 'load-balancer-api-internal: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T17:00:59Z" - latency: 7.338739ms message: 'load-balancer-api-internal: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T17:00:59Z" - latency: 5.362298ms message: 'load-balancer-api-internal: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:59:59Z" - latency: 9.30846ms message: 'load-balancer-api-internal: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:59:59Z" - latency: 4.867392ms message: 'load-balancer-api-internal: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:59Z" - latency: 9.839533ms message: 'load-balancer-api-internal: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:58:59Z" - latency: 4.038033ms message: 'load-balancer-api-internal: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:59Z" - latency: 10.494322ms message: 'load-balancer-api-internal: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:57:59Z" - latency: 4.140587ms message: 'load-balancer-api-internal: tcp connection to ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:59Z" - latency: 7.945274ms message: 'load-balancer-api-internal: resolved host name ae34a60fc101641b386206f2150c5393-3673f2de0244e2f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-network-check-target-ip-10-0-131-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "71440" uid: 6cf8448a-e302-4267-95fe-5e7aca15ad96 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T16:13:59Z" message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.242455ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:59Z" - latency: 2.449283ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:59Z" - latency: 2.219993ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:59Z" - latency: 2.338625ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:59Z" - latency: 2.365052ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:59Z" - latency: 2.356876ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:59Z" - latency: 2.576044ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:59Z" - latency: 2.252042ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:48:59Z" - latency: 2.361193ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:47:59Z" - latency: 2.42673ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-network-check-target-ip-10-0-132-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "71439" uid: 4add3b9b-049f-4d9e-81d2-c2927343e9a3 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T16:13:59Z" message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.783µs message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:59Z" - latency: 1.757583ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:59Z" - latency: 916.873µs message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:59Z" - latency: 914.337µs message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:59Z" - latency: 872.165µs message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:59Z" - latency: 1.472328ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:59Z" - latency: 907.685µs message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:59Z" - latency: 1.023116ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:48:59Z" - latency: 1.30107ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:47:59Z" - latency: 1.025533ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-network-check-target-ip-10-0-141-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "71441" uid: 694b7e9f-541f-4df2-bd12-6a44a3b83535 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T16:13:59Z" message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.228682ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:59Z" - latency: 2.437268ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:59Z" - latency: 2.209688ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:59Z" - latency: 2.354678ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:59Z" - latency: 2.25165ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:59Z" - latency: 2.239492ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:59Z" - latency: 2.119333ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:59Z" - latency: 1.84925ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:48:59Z" - latency: 1.919342ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:47:59Z" - latency: 1.8945ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-42-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-42.ec2.internal uid: e392e1c7-cc7a-4b50-8c1a-cd1a9a1ba4a6 resourceVersion: "79516" uid: ea29e9d9-6adc-41b4-b9ee-2f677cf90cf4 spec: sourcePod: network-check-source-65bdbbff45-krplv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T16:12:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.138373ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T17:00:59Z" - latency: 1.926221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T17:00:59Z" - latency: 909.315µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:59:59Z" - latency: 1.908816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:59:59Z" - latency: 917.886µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:59Z" - latency: 2.245773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:58:59Z" - latency: 1.072052ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:59Z" - latency: 1.72388ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:57:59Z" - latency: 900.706µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:59Z" - latency: 1.68714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:56:59Z" kind: List metadata: resourceVersion: ""