apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "105493" uid: c70abb30-8624-451f-9dee-36b4588b6546 spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T00:13:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 851.239µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:41:21Z" - latency: 1.197974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:40:21Z" - latency: 1.541678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:39:21Z" - latency: 1.931597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:38:21Z" - latency: 914.955µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:37:21Z" - latency: 1.040419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 4.615745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 48.010973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 13.005898ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 6.386836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "92723" uid: 1a51c78e-4477-408f-bf14-c1cd5eced9af spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:12:21Z" message: 'load-balancer-api-external: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.785741ms message: 'load-balancer-api-external: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 7.758557ms message: 'load-balancer-api-external: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:36:21Z" - latency: 16.761728ms message: 'load-balancer-api-external: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 55.355155ms message: 'load-balancer-api-external: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:35:21Z" - latency: 20.657359ms message: 'load-balancer-api-external: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 109.439762ms message: 'load-balancer-api-external: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:34:21Z" - latency: 18.464505ms message: 'load-balancer-api-external: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 53.209266ms message: 'load-balancer-api-external: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:33:21Z" - latency: 28.656377ms message: 'load-balancer-api-external: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - latency: 14.354733ms message: 'load-balancer-api-external: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "92722" uid: b384a36c-cf60-4894-8ebf-37419f2177df spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:12:21Z" message: 'load-balancer-api-internal: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.814309ms message: 'load-balancer-api-internal: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 7.698779ms message: 'load-balancer-api-internal: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:36:21Z" - latency: 17.356672ms message: 'load-balancer-api-internal: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 49.767518ms message: 'load-balancer-api-internal: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:35:21Z" - latency: 20.269778ms message: 'load-balancer-api-internal: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 109.062214ms message: 'load-balancer-api-internal: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:34:21Z" - latency: 17.03676ms message: 'load-balancer-api-internal: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 52.730402ms message: 'load-balancer-api-internal: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:33:21Z" - latency: 19.60642ms message: 'load-balancer-api-internal: tcp connection to a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - latency: 17.700211ms message: 'load-balancer-api-internal: resolved host name a883217843c784754a9c94a5ff95cefd-0e67250544583792.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T00:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-network-check-target-ip-10-0-137-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "105490" uid: 616af918-bee3-4381-ba34-bc7c6448df16 spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:13:21Z" message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.99679ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:41:21Z" - latency: 2.503273ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:40:21Z" - latency: 8.894639ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:39:21Z" - latency: 2.74746ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:38:21Z" - latency: 2.737311ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:37:21Z" - latency: 2.629224ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 21.467398ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 47.884273ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 37.837991ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 9.853019ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-network-check-target-ip-10-0-138-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "105491" uid: f38942dd-c51a-414f-8c77-332dbc61e223 spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:13:21Z" message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.581566ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:41:21Z" - latency: 2.536426ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:40:21Z" - latency: 9.427519ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:39:21Z" - latency: 2.656688ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:38:21Z" - latency: 2.665633ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:37:21Z" - latency: 2.371626ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 13.254285ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 58.602735ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 12.125397ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 6.658397ms message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-network-check-target-ip-10-0-143-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "105489" uid: 530965c1-2d71-4558-9776-26b5c935b7d9 spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:13:21Z" message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.7356ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:41:21Z" - latency: 1.818978ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:40:21Z" - latency: 8.38077ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:39:21Z" - latency: 1.821992ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:38:21Z" - latency: 1.409424ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:37:21Z" - latency: 1.761056ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 20.944091ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 60.155817ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 12.452758ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 9.558262ms message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:06:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-120-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-120.ec2.internal uid: 74186ffd-f3fa-4b85-974a-411487dcb276 resourceVersion: "92720" uid: 436d58af-9faa-4188-bf75-263ab93ecaa6 spec: sourcePod: network-check-source-6f78d59f99-glf29 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T00:12:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.344238ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:36:21Z" - latency: 2.142111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T00:36:21Z" - latency: 21.756894ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:35:21Z" - latency: 20.666238ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T00:35:21Z" - latency: 5.927523ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:34:21Z" - latency: 67.298991ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T00:34:21Z" - latency: 14.918705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:33:21Z" - latency: 9.53492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T00:33:21Z" - latency: 3.208997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T00:32:21Z" - latency: 6.795079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T00:32:21Z" kind: List metadata: resourceVersion: ""