apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "43498" uid: 100f9816-c227-4aa1-9f77-74e376d3dd8a spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T22:31:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.579µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 1.175376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 1.604384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 711.219µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:16Z" - latency: 1.408631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:48:16Z" - latency: 1.000967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:47:16Z" - latency: 1.242388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:46:16Z" - latency: 753.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:45:16Z" - latency: 844.852µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:44:16Z" - latency: 1.406062ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "45657" uid: 5e551a88-ecf2-4b1f-837b-d7d2b636a1c6 spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T22:30:16Z" message: 'load-balancer-api-external: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.131936ms message: 'load-balancer-api-external: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:16Z" - latency: 7.034218ms message: 'load-balancer-api-external: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:54:16Z" - latency: 4.318796ms message: 'load-balancer-api-external: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:16Z" - latency: 6.83034ms message: 'load-balancer-api-external: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:53:16Z" - latency: 3.73869ms message: 'load-balancer-api-external: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 6.722791ms message: 'load-balancer-api-external: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:52:16Z" - latency: 3.52437ms message: 'load-balancer-api-external: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 7.504704ms message: 'load-balancer-api-external: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:51:16Z" - latency: 5.863739ms message: 'load-balancer-api-external: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 7.292883ms message: 'load-balancer-api-external: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:50:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "45658" uid: e812d5ac-4c9c-40eb-8d06-041eea055d94 spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T22:30:16Z" message: 'load-balancer-api-internal: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.201536ms message: 'load-balancer-api-internal: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:16Z" - latency: 7.003004ms message: 'load-balancer-api-internal: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:54:16Z" - latency: 4.290732ms message: 'load-balancer-api-internal: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:16Z" - latency: 6.871502ms message: 'load-balancer-api-internal: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:53:16Z" - latency: 3.752275ms message: 'load-balancer-api-internal: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 6.731383ms message: 'load-balancer-api-internal: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:52:16Z" - latency: 4.34569ms message: 'load-balancer-api-internal: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 7.464822ms message: 'load-balancer-api-internal: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:51:16Z" - latency: 5.899369ms message: 'load-balancer-api-internal: tcp connection to a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 7.232841ms message: 'load-balancer-api-internal: resolved host name a381e9cf0e29a4d4ebe5b37d3185d6b2-454f47b24fbfc7ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:50:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-network-check-target-ip-10-0-130-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "43495" uid: b2e6b392-5a5f-4b6e-8aad-ba303e802b31 spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:31:16Z" message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.088µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 1.570845ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 962.896µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 1.596728ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:16Z" - latency: 991.892µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:48:16Z" - latency: 877.636µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:47:16Z" - latency: 986.969µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:46:16Z" - latency: 853.173µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:45:16Z" - latency: 784.397µs message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:44:16Z" - latency: 1.240961ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-network-check-target-ip-10-0-134-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "43497" uid: da633630-c488-4deb-be88-23c9cbc85f4c spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:31:16Z" message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.377445ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 2.706116ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 2.393413ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 2.283132ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:16Z" - latency: 2.390039ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:48:16Z" - latency: 2.261756ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:47:16Z" - latency: 2.164138ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:46:16Z" - latency: 1.906246ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:45:16Z" - latency: 1.961507ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:44:16Z" - latency: 2.552682ms message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-network-check-target-ip-10-0-135-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "43496" uid: 1347d799-b398-4f02-84cd-4d19de5f8e31 spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:31:16Z" message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.270432ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 2.652754ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 2.447825ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 1.998476ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:16Z" - latency: 2.419541ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:48:16Z" - latency: 2.262486ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:47:16Z" - latency: 2.762702ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:46:16Z" - latency: 2.154811ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:45:16Z" - latency: 2.411264ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:44:16Z" - latency: 2.463795ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:24:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-232-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-232.ec2.internal uid: e59495db-7837-40fa-aac5-39e677c61644 resourceVersion: "45656" uid: eff9e882-2207-4768-9108-5cd28c4592b8 spec: sourcePod: network-check-source-6947749cfc-cgclp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T22:30:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.078µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:16Z" - latency: 1.844475ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:54:16Z" - latency: 776.528µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:16Z" - latency: 1.789592ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:53:16Z" - latency: 1.283431ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:16Z" - latency: 1.840075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:52:16Z" - latency: 1.09199ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:16Z" - latency: 1.80996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:51:16Z" - latency: 785.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:16Z" - latency: 1.886657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:50:16Z" kind: List metadata: resourceVersion: ""