apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "172996" uid: c298ed7e-c699-4461-b483-8e52ea03b2e1 spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T08:42:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.769014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 940.908µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 900.158µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 1.228753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:24:14Z" - latency: 989.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:23:14Z" - latency: 1.213814ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:22:14Z" - latency: 916.7µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:21:14Z" - latency: 1.920414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:20:14Z" - latency: 9.072171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:19:14Z" - latency: 1.106918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:18:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "174464" uid: a68db35a-f2e9-471e-81ea-13ad9225185c spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T08:41:14Z" message: 'load-balancer-api-external: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.398524ms message: 'load-balancer-api-external: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:29:14Z" - latency: 6.856671ms message: 'load-balancer-api-external: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:29:14Z" - latency: 55.338975ms message: 'load-balancer-api-external: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:28:14Z" - latency: 81.536562ms message: 'load-balancer-api-external: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:28:14Z" - latency: 51.876169ms message: 'load-balancer-api-external: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 7.180058ms message: 'load-balancer-api-external: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:27:14Z" - latency: 59.057996ms message: 'load-balancer-api-external: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 7.049617ms message: 'load-balancer-api-external: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:26:14Z" - latency: 55.496955ms message: 'load-balancer-api-external: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 7.638693ms message: 'load-balancer-api-external: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:25:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "174462" uid: 984fadac-aee8-46d2-a0db-33a4f3dab080 spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T08:41:14Z" message: 'load-balancer-api-internal: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.644938ms message: 'load-balancer-api-internal: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:29:14Z" - latency: 6.742995ms message: 'load-balancer-api-internal: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:29:14Z" - latency: 61.539837ms message: 'load-balancer-api-internal: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:28:14Z" - latency: 75.453613ms message: 'load-balancer-api-internal: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:28:14Z" - latency: 56.392462ms message: 'load-balancer-api-internal: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 7.220752ms message: 'load-balancer-api-internal: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:27:14Z" - latency: 50.870492ms message: 'load-balancer-api-internal: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 6.958912ms message: 'load-balancer-api-internal: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:26:14Z" - latency: 55.763027ms message: 'load-balancer-api-internal: tcp connection to add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 7.691597ms message: 'load-balancer-api-internal: resolved host name add429111eabe43cbaa078b9d9be88e3-5ea30804d4267b82.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T10:25:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-ip-10-0-134-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "172993" uid: 0dc9ecff-08a0-425e-8d1b-28c6293c034d spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T08:42:14Z" message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.621075ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 2.450306ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 2.124263ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 2.230736ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:24:14Z" - latency: 2.544355ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:23:14Z" - latency: 2.439435ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:22:14Z" - latency: 2.190463ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:21:14Z" - latency: 4.109645ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:20:14Z" - latency: 5.000003ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:19:14Z" - latency: 2.478259ms message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:18:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-ip-10-0-143-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "172992" uid: 8a5fb1fe-a84e-40dd-8fd8-753a3fedabc2 spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T08:42:14Z" message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.620778ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 2.627071ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 2.502618ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 3.063596ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:24:14Z" - latency: 2.521132ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:23:14Z" - latency: 2.788924ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:22:14Z" - latency: 2.4662ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:21:14Z" - latency: 3.052429ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:20:14Z" - latency: 7.20708ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:19:14Z" - latency: 2.603903ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:18:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-ip-10-0-143-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "172991" uid: 40b76d8f-239b-4ef7-9902-480af63aa73d spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T08:42:14Z" message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.259µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 872.603µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 1.209467ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 945.091µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:24:14Z" - latency: 1.04965ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:23:14Z" - latency: 974.827µs message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:22:14Z" - latency: 1.315693ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:21:14Z" - latency: 2.53181ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:20:14Z" - latency: 4.407441ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:19:14Z" - latency: 1.349663ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:18:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T08:35:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-244-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-244.us-west-2.compute.internal uid: d3a88da2-88f5-449e-b536-fd96b19b09cc resourceVersion: "174460" uid: f7c6ec30-8e75-4d59-96f7-e60d0d1cf5a6 spec: sourcePod: network-check-source-6f78d59f99-twnmm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T08:41:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.074µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:29:14Z" - latency: 2.166299ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T10:29:14Z" - latency: 12.827307ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:28:14Z" - latency: 19.173774ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T10:28:14Z" - latency: 951.339µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:27:14Z" - latency: 2.030951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T10:27:14Z" - latency: 799.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:26:14Z" - latency: 1.972595ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T10:26:14Z" - latency: 812.482µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T10:25:14Z" - latency: 2.592722ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T10:25:14Z" kind: List metadata: resourceVersion: ""