apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16860" uid: bd2551a1-ffb6-4a5b-b4d6-85f8f2813b2e spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T15:12:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.64µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:59Z" - latency: 1.215879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:59Z" - latency: 899.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 1.162772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 841.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 766.211µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 802.903µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 921.801µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:59Z" - latency: 1.085032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:59Z" - latency: 814.696µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16130" uid: 1b668a19-0764-40f0-8740-eb922ac2b996 spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:11:59Z" message: 'load-balancer-api-external: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.653509ms message: 'load-balancer-api-external: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 9.024812ms message: 'load-balancer-api-external: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:17:59Z" - latency: 4.7184ms message: 'load-balancer-api-external: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 8.381559ms message: 'load-balancer-api-external: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:16:59Z" - latency: 4.579047ms message: 'load-balancer-api-external: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 8.086384ms message: 'load-balancer-api-external: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:15:59Z" - latency: 4.12541ms message: 'load-balancer-api-external: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 10.578378ms message: 'load-balancer-api-external: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:14:59Z" - latency: 5.459454ms message: 'load-balancer-api-external: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 8.342534ms message: 'load-balancer-api-external: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16129" uid: ab23b645-925c-43f1-855e-2e5337481b2a spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:11:59Z" message: 'load-balancer-api-internal: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.668552ms message: 'load-balancer-api-internal: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 9.067284ms message: 'load-balancer-api-internal: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:17:59Z" - latency: 3.840831ms message: 'load-balancer-api-internal: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 8.421791ms message: 'load-balancer-api-internal: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:16:59Z" - latency: 4.590266ms message: 'load-balancer-api-internal: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 8.15983ms message: 'load-balancer-api-internal: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:15:59Z" - latency: 4.9663ms message: 'load-balancer-api-internal: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 10.629753ms message: 'load-balancer-api-internal: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:14:59Z" - latency: 5.4114ms message: 'load-balancer-api-internal: tcp connection to a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 8.55051ms message: 'load-balancer-api-internal: resolved host name a488bd082d5ba40e29ea8aae1632550f-ee27b11807859dd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-network-check-target-ip-10-0-130-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16858" uid: a227ea45-901e-4b13-a820-02aea478e6bf spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:12:59Z" message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.150559ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:59Z" - latency: 2.069648ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:59Z" - latency: 2.067509ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 2.337997ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 2.464777ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 2.299655ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 2.262193ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 2.233337ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:59Z" - latency: 2.427858ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:59Z" - latency: 2.095064ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-network-check-target-ip-10-0-130-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16857" uid: 704e48d4-8a91-4d30-bc54-e5585662b954 spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:12:59Z" message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.413µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:59Z" - latency: 1.275935ms message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:59Z" - latency: 952.367µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 797.454µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 769.809µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 748.491µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 903.172µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 1.391558ms message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:59Z" - latency: 1.399274ms message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:59Z" - latency: 938.029µs message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-network-check-target-ip-10-0-140-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16859" uid: ac8ed032-cb5e-4dbf-a763-952ffd5b98b3 spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:12:59Z" message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.246751ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:59Z" - latency: 2.167696ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:59Z" - latency: 2.113835ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 2.176025ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 2.632776ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 2.485835ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 2.395571ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 2.540759ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:59Z" - latency: 2.078981ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:59Z" - latency: 2.205947ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-24.ec2.internal uid: 4fea437f-ff80-4f7e-abf1-3b2215e301a3 resourceVersion: "16128" uid: 5682602b-7694-41b0-988c-1f1c8ca753e8 spec: sourcePod: network-check-source-7d88cb55d8-6b68s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T15:11:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:59Z" - latency: 1.579751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:17:59Z" - latency: 833.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:59Z" - latency: 1.671208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:16:59Z" - latency: 912.219µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:59Z" - latency: 1.796795ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:15:59Z" - latency: 856.407µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:59Z" - latency: 1.730121ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:14:59Z" - latency: 765.551µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:59Z" - latency: 1.60775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:13:59Z" kind: List metadata: resourceVersion: ""