apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "139263" uid: 41b303ed-80a8-4b61-b568-e9791de9a969 spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T19:38:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.72631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:37Z" - latency: 1.138759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:37Z" - latency: 1.14099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:32:37Z" - latency: 992.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:31:37Z" - latency: 1.481623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:30:37Z" - latency: 1.238788ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:29:37Z" - latency: 1.256904ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:28:37Z" - latency: 1.390112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:27:37Z" - latency: 1.457548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:26:37Z" - latency: 1.238081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:25:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "143417" uid: 4528b22c-b03a-4370-8cd7-722e7d9ceed2 spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:37:37Z" message: 'load-balancer-api-external: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.793467ms message: 'load-balancer-api-external: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:37:37Z" - latency: 6.797253ms message: 'load-balancer-api-external: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:37:37Z" - latency: 6.698405ms message: 'load-balancer-api-external: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:36:37Z" - latency: 7.543285ms message: 'load-balancer-api-external: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:36:37Z" - latency: 6.602194ms message: 'load-balancer-api-external: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:35:37Z" - latency: 6.862321ms message: 'load-balancer-api-external: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:35:37Z" - latency: 4.752407ms message: 'load-balancer-api-external: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:37Z" - latency: 7.255128ms message: 'load-balancer-api-external: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:34:37Z" - latency: 4.874354ms message: 'load-balancer-api-external: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:37Z" - latency: 7.129418ms message: 'load-balancer-api-external: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "143418" uid: 0e85cb7c-87ab-4905-a6af-36a01fc62afb spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:37:37Z" message: 'load-balancer-api-internal: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.778412ms message: 'load-balancer-api-internal: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:37:37Z" - latency: 6.75513ms message: 'load-balancer-api-internal: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:37:37Z" - latency: 6.409912ms message: 'load-balancer-api-internal: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:36:37Z" - latency: 7.478689ms message: 'load-balancer-api-internal: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:36:37Z" - latency: 6.595479ms message: 'load-balancer-api-internal: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:35:37Z" - latency: 6.837314ms message: 'load-balancer-api-internal: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:35:37Z" - latency: 8.019333ms message: 'load-balancer-api-internal: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:37Z" - latency: 7.234067ms message: 'load-balancer-api-internal: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:34:37Z" - latency: 6.580266ms message: 'load-balancer-api-internal: tcp connection to af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:37Z" - latency: 7.104837ms message: 'load-balancer-api-internal: resolved host name af8413d880a654734978d43b2e4628fb-5097b7c7c1477187.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-138-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "139261" uid: 01fae28f-700a-48c3-8834-3a6ff8fe3f03 spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:38:37Z" message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.726µs message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:37Z" - latency: 1.239012ms message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:37Z" - latency: 1.13602ms message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:32:37Z" - latency: 943.841µs message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:31:37Z" - latency: 1.051137ms message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:30:37Z" - latency: 968.762µs message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:29:37Z" - latency: 1.018121ms message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:28:37Z" - latency: 1.675721ms message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:27:37Z" - latency: 1.14232ms message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:26:37Z" - latency: 827.408µs message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:25:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:10:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-139-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "143798" uid: 413f1f55-1170-41b9-b443-bdba69a1db71 spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:17:19Z" message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.284788ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:38:19Z" - latency: 2.366056ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:37:19Z" - latency: 3.074658ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:36:19Z" - latency: 2.455626ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:35:19Z" - latency: 2.420623ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:19Z" - latency: 2.282383ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:19Z" - latency: 2.066718ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:32:19Z" - latency: 2.311615ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:31:19Z" - latency: 2.032036ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:30:19Z" - latency: 2.235656ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:29:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-141-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "139262" uid: f18eb8f5-a77f-407f-9556-596719c4a25b spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:38:37Z" message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.252434ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:37Z" - latency: 2.262872ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:37Z" - latency: 2.194393ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:32:37Z" - latency: 2.121462ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:31:37Z" - latency: 2.125196ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:30:37Z" - latency: 2.31868ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:29:37Z" - latency: 2.234284ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:28:37Z" - latency: 2.57879ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:27:37Z" - latency: 2.272276ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:26:37Z" - latency: 2.295195ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:25:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-61-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-61.us-east-2.compute.internal uid: 4d5e048c-e2a7-479b-96f5-c471bfa178ce resourceVersion: "143416" uid: 397b0231-a474-414a-850c-44ebb25d580c spec: sourcePod: network-check-source-6f78d59f99-j6dm5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T19:37:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.814µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:37:37Z" - latency: 2.158096ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:37:37Z" - latency: 1.03389ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:36:37Z" - latency: 2.022885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:36:37Z" - latency: 2.402622ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:35:37Z" - latency: 1.812259ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:35:37Z" - latency: 2.292396ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:34:37Z" - latency: 2.085531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:34:37Z" - latency: 2.163984ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:33:37Z" - latency: 1.908097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:33:37Z" kind: List metadata: resourceVersion: ""