apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56249" uid: ef84cc4b-0f6e-4b77-ba39-a7c5ae14ef6d spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T21:13:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.313µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 973.827µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 1.316027ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 1.287099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 968.091µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 1.661462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:25Z" - latency: 1.000318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:25Z" - latency: 2.04551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:25Z" - latency: 1.016924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:25Z" - latency: 1.066644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56250" uid: df59aba4-5791-4698-8275-4bcb49cb8112 spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:12:25Z" message: 'load-balancer-api-external: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.393971ms message: 'load-balancer-api-external: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 7.786721ms message: 'load-balancer-api-external: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:48:25Z" - latency: 2.908313ms message: 'load-balancer-api-external: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 7.340525ms message: 'load-balancer-api-external: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:47:25Z" - latency: 4.567693ms message: 'load-balancer-api-external: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 7.483585ms message: 'load-balancer-api-external: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:46:25Z" - latency: 6.131558ms message: 'load-balancer-api-external: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 7.505032ms message: 'load-balancer-api-external: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:45:25Z" - latency: 5.059659ms message: 'load-balancer-api-external: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 7.180155ms message: 'load-balancer-api-external: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56251" uid: 0e34f9d8-c6e3-4f13-b7db-a8e3a3914cce spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:12:25Z" message: 'load-balancer-api-internal: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.313687ms message: 'load-balancer-api-internal: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 7.702091ms message: 'load-balancer-api-internal: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:48:25Z" - latency: 2.961866ms message: 'load-balancer-api-internal: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 7.249711ms message: 'load-balancer-api-internal: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:47:25Z" - latency: 4.551325ms message: 'load-balancer-api-internal: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 7.362304ms message: 'load-balancer-api-internal: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:46:25Z" - latency: 6.199074ms message: 'load-balancer-api-internal: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 7.42607ms message: 'load-balancer-api-internal: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:45:25Z" - latency: 5.076248ms message: 'load-balancer-api-internal: tcp connection to a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 7.073673ms message: 'load-balancer-api-internal: resolved host name a9c0189c76ffa414bbe64782f22ffef9-e324037f91a3c3d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-network-check-target-ip-10-0-130-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56245" uid: 1faa0250-1789-4924-b99e-f857f1ee7052 spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:13:25Z" message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.422µs message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 1.47179ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 886.871µs message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 1.101543ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 1.120195ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 882.877µs message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:25Z" - latency: 1.020943ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:25Z" - latency: 1.106962ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:25Z" - latency: 1.111525ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:25Z" - latency: 997.072µs message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-network-check-target-ip-10-0-130-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56246" uid: 5417d506-7bab-43e7-9876-dc0be3f0a964 spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:13:25Z" message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.941947ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 2.226335ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 2.184279ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 2.375209ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 2.235596ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 2.369069ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:25Z" - latency: 2.129198ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:25Z" - latency: 2.190117ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:25Z" - latency: 2.289606ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:25Z" - latency: 2.054302ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-network-check-target-ip-10-0-137-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56247" uid: b64218d3-6713-4f0c-bc64-f7df09917847 spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:13:25Z" message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.890501ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 2.513464ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 2.257044ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 2.549263ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 2.453232ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 2.183042ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:25Z" - latency: 2.320675ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:25Z" - latency: 2.300668ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:25Z" - latency: 2.342073ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:25Z" - latency: 2.317731ms message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:06:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-29-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-29.ec2.internal uid: 276911ee-b003-471a-bb6f-ad3da47e690b resourceVersion: "56248" uid: b7d2b04a-2fde-4847-aed5-8003fc602003 spec: sourcePod: network-check-source-869dcfcdcd-hb2sf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T21:12:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.793µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:25Z" - latency: 1.920346ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:48:25Z" - latency: 971.104µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:25Z" - latency: 1.786635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:47:25Z" - latency: 1.294612ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:25Z" - latency: 1.937533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:46:25Z" - latency: 1.316974ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:25Z" - latency: 2.200195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:45:25Z" - latency: 1.215678ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:25Z" - latency: 1.92155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:25Z" kind: List metadata: resourceVersion: ""