apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "114725" uid: defbdf9f-f8be-43bb-9793-11ffbbf88861 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:38:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.37µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:48:32Z" - latency: 1.343442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:47:32Z" - latency: 1.250145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:46:32Z" - latency: 1.236164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:45:32Z" - latency: 1.258864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:44:32Z" - latency: 1.368853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 1.325299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 860.167µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 6.334701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 9.151755ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "111636" uid: f13aa7bf-df4d-4ba7-b584-ecafe0c0de04 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:37:32Z" message: 'load-balancer-api-external: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.518559ms message: 'load-balancer-api-external: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 7.421713ms message: 'load-balancer-api-external: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:43:32Z" - latency: 57.648814ms message: 'load-balancer-api-external: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 6.945861ms message: 'load-balancer-api-external: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:42:32Z" - latency: 56.006322ms message: 'load-balancer-api-external: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 7.42378ms message: 'load-balancer-api-external: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:41:32Z" - latency: 55.211683ms message: 'load-balancer-api-external: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 12.685421ms message: 'load-balancer-api-external: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:40:32Z" - latency: 71.510726ms message: 'load-balancer-api-external: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - latency: 53.646728ms message: 'load-balancer-api-external: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:39:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "111638" uid: 4be9e9a6-1080-42ff-9a74-2a26bb41a273 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:37:32Z" message: 'load-balancer-api-internal: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.577514ms message: 'load-balancer-api-internal: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 7.323078ms message: 'load-balancer-api-internal: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:43:32Z" - latency: 50.461113ms message: 'load-balancer-api-internal: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 6.815099ms message: 'load-balancer-api-internal: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:42:32Z" - latency: 55.947734ms message: 'load-balancer-api-internal: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 7.366863ms message: 'load-balancer-api-internal: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:41:32Z" - latency: 55.165017ms message: 'load-balancer-api-internal: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 20.701509ms message: 'load-balancer-api-internal: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:40:32Z" - latency: 57.943671ms message: 'load-balancer-api-internal: tcp connection to a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - latency: 54.071984ms message: 'load-balancer-api-internal: resolved host name a37db1c6ee22f4efb81f40e9e9d69904-f845c31920a170ae.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:39:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-128-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "114724" uid: 889b7b2a-5f31-4198-a59b-deda4cb9ea81 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:38:32Z" message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.962674ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:48:32Z" - latency: 2.579642ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:47:32Z" - latency: 2.631503ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:46:32Z" - latency: 2.369548ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:45:32Z" - latency: 2.217408ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:44:32Z" - latency: 2.355149ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 2.351378ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 2.40399ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 5.351044ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 9.235024ms message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-135-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "114723" uid: 67777aff-fa4a-4ae2-9f18-5ee00df453b1 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:38:32Z" message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.67141ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:48:32Z" - latency: 2.036625ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:47:32Z" - latency: 1.993844ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:46:32Z" - latency: 1.803795ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:45:32Z" - latency: 2.028109ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:44:32Z" - latency: 2.05355ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 2.276612ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 1.967342ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 5.07055ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 21.487527ms message: 'network-check-target-ip-10-0-135-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "114722" uid: 4ca33a06-c6da-4c38-863e-7e112b1928f8 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:38:32Z" message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.527µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:48:32Z" - latency: 1.575309ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:47:32Z" - latency: 1.208297ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:46:32Z" - latency: 1.471763ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:45:32Z" - latency: 1.124124ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:44:32Z" - latency: 1.528865ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 1.426859ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 1.189758ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 7.500584ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 9.085451ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.us-west-2.compute.internal uid: 7b3baede-ac6f-40cf-bc3b-49997b58e0fb resourceVersion: "111633" uid: 71de7e31-e1ee-4139-8cbc-fcc910678291 spec: sourcePod: network-check-source-6f78d59f99-vmfmg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:37:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.238146ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:43:32Z" - latency: 2.148639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:43:32Z" - latency: 984.702µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:42:32Z" - latency: 1.941366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:42:32Z" - latency: 1.963586ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:32Z" - latency: 2.059286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:41:32Z" - latency: 4.766903ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:32Z" - latency: 8.815948ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:40:32Z" - latency: 10.881444ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:32Z" - latency: 20.317794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:39:32Z" kind: List metadata: resourceVersion: ""