apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "40494" uid: 920d29d3-ccce-43a5-ba91-38bf646bb21a spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T02:24:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.474758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 1.154911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 1.271233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:36:55Z" - latency: 984.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:35:55Z" - latency: 986.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:34:55Z" - latency: 1.103644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:33:55Z" - latency: 2.033676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:32:55Z" - latency: 1.639968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:31:55Z" - latency: 941.681µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:30:55Z" - latency: 1.221504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:29:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "42093" uid: 23aea049-708b-4aef-9d89-9b102ce49876 spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:23:55Z" message: 'load-balancer-api-external: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.863715ms message: 'load-balancer-api-external: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:55Z" - latency: 7.444898ms message: 'load-balancer-api-external: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:41:55Z" - latency: 57.625012ms message: 'load-balancer-api-external: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:55Z" - latency: 7.644806ms message: 'load-balancer-api-external: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:40:55Z" - latency: 56.57376ms message: 'load-balancer-api-external: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:55Z" - latency: 7.482612ms message: 'load-balancer-api-external: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:39:55Z" - latency: 3.387683859s message: 'load-balancer-api-external: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 7.795757ms message: 'load-balancer-api-external: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:38:55Z" - latency: 60.128999ms message: 'load-balancer-api-external: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 6.974176ms message: 'load-balancer-api-external: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:37:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "42094" uid: 72c9c101-e430-4264-bb68-807d22d62d8d spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:23:55Z" message: 'load-balancer-api-internal: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 59.330957ms message: 'load-balancer-api-internal: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:55Z" - latency: 7.574561ms message: 'load-balancer-api-internal: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:41:55Z" - latency: 56.306376ms message: 'load-balancer-api-internal: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:55Z" - latency: 7.838375ms message: 'load-balancer-api-internal: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:40:55Z" - latency: 54.932899ms message: 'load-balancer-api-internal: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:55Z" - latency: 7.440987ms message: 'load-balancer-api-internal: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:39:55Z" - latency: 54.917164ms message: 'load-balancer-api-internal: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 7.850619ms message: 'load-balancer-api-internal: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:38:55Z" - latency: 59.524171ms message: 'load-balancer-api-internal: tcp connection to abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 7.064667ms message: 'load-balancer-api-internal: resolved host name abcb0b6ef32ad46c1ad0e3f88f14fa5a-de13e1ab1fc0a92b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:37:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-network-check-target-ip-10-0-129-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "40492" uid: 6b2b5fb3-9ff9-440f-a205-1cd371860757 spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:24:55Z" message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.696184ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 2.733513ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 3.153833ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:36:55Z" - latency: 2.28723ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:35:55Z" - latency: 2.418816ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:34:55Z" - latency: 2.234508ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:33:55Z" - latency: 2.788394ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:32:55Z" - latency: 2.62585ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:31:55Z" - latency: 2.649904ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:30:55Z" - latency: 2.992018ms message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:29:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-network-check-target-ip-10-0-137-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "40493" uid: 703f3e86-f69b-4bc0-914b-20c0c50600a1 spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:24:55Z" message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.747622ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 2.410692ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 2.480701ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:36:55Z" - latency: 2.549703ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:35:55Z" - latency: 1.981098ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:34:55Z" - latency: 2.482348ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:33:55Z" - latency: 2.705317ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:32:55Z" - latency: 2.856271ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:31:55Z" - latency: 2.140684ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:30:55Z" - latency: 2.27101ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:29:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-network-check-target-ip-10-0-141-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "40491" uid: 2a1f28b6-9715-4c3b-926f-1e661813f67b spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:24:55Z" message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.771546ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 1.354802ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 1.824843ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:36:55Z" - latency: 1.517033ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:35:55Z" - latency: 966.191µs message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:34:55Z" - latency: 1.292095ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:33:55Z" - latency: 1.373641ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:32:55Z" - latency: 1.200042ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:31:55Z" - latency: 2.110644ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:30:55Z" - latency: 1.05992ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:29:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-221-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-221.us-west-2.compute.internal uid: 14c39054-4839-4b87-959e-03b60c525321 resourceVersion: "42090" uid: 16a3e6e1-e311-44cb-9da6-16dd05c0dbeb spec: sourcePod: network-check-source-6f78d59f99-74tfv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T02:23:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.354133ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:55Z" - latency: 1.868545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:41:55Z" - latency: 1.009144ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:55Z" - latency: 1.936868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:40:55Z" - latency: 865.177µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:55Z" - latency: 2.314658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:39:55Z" - latency: 876.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:55Z" - latency: 2.776375ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:38:55Z" - latency: 1.094126ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:55Z" - latency: 2.026846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:37:55Z" kind: List metadata: resourceVersion: ""