apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "56040" uid: 770860d0-4798-4f40-a8a6-6be35a28ff60 spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T19:19:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.791µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:47:08Z" - latency: 1.259356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:46:08Z" - latency: 1.517127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:08Z" - latency: 2.259599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:08Z" - latency: 1.064552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:08Z" - latency: 1.120896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 1.131297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 972.194µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 1.175145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 1.00912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "50504" uid: 44180127-0c0d-4f57-879e-eeaee020c82d spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:18:08Z" message: 'load-balancer-api-external: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.015536ms message: 'load-balancer-api-external: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 7.225366ms message: 'load-balancer-api-external: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:08Z" - latency: 5.555339ms message: 'load-balancer-api-external: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 10.215772ms message: 'load-balancer-api-external: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:08Z" - latency: 4.956417ms message: 'load-balancer-api-external: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 7.859345ms message: 'load-balancer-api-external: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:40:08Z" - latency: 4.644416ms message: 'load-balancer-api-external: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 7.394067ms message: 'load-balancer-api-external: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:39:08Z" - latency: 5.634138ms message: 'load-balancer-api-external: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - latency: 7.441666ms message: 'load-balancer-api-external: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:38:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "50505" uid: 68fb2900-ec2c-4b37-bbe3-1c1ad78ddfa0 spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:18:08Z" message: 'load-balancer-api-internal: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.16084ms message: 'load-balancer-api-internal: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 7.169954ms message: 'load-balancer-api-internal: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:08Z" - latency: 5.568772ms message: 'load-balancer-api-internal: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 10.131367ms message: 'load-balancer-api-internal: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:08Z" - latency: 5.027182ms message: 'load-balancer-api-internal: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 7.807615ms message: 'load-balancer-api-internal: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:40:08Z" - latency: 4.625937ms message: 'load-balancer-api-internal: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 7.322761ms message: 'load-balancer-api-internal: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:39:08Z" - latency: 6.404765ms message: 'load-balancer-api-internal: tcp connection to a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - latency: 7.388707ms message: 'load-balancer-api-internal: resolved host name a15da50651b2a4ec7af13fe7018d0896-6e749b1a1be3f4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:38:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-network-check-target-ip-10-0-132-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "56039" uid: 0cfb4793-add0-45fe-98c6-0c379950d224 spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:19:08Z" message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.811484ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:47:08Z" - latency: 2.59312ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:46:08Z" - latency: 2.574002ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:08Z" - latency: 3.180473ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:08Z" - latency: 2.257881ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:08Z" - latency: 2.562976ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 2.303855ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 1.968901ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 2.216652ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 2.415017ms message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-network-check-target-ip-10-0-135-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "56037" uid: 18b067f4-7bb4-4100-8ad4-ba022ff804fd spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:19:08Z" message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091919ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:47:08Z" - latency: 1.092438ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:46:08Z" - latency: 1.63379ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:08Z" - latency: 1.241965ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:08Z" - latency: 899.58µs message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:08Z" - latency: 1.221577ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 1.310595ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 1.592699ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 1.278295ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 1.020815ms message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-network-check-target-ip-10-0-139-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "56038" uid: 0d8db8a1-2148-4e0a-9ffd-1672b64d7666 spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:19:08Z" message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426295ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:47:08Z" - latency: 2.570071ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:46:08Z" - latency: 3.014866ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:08Z" - latency: 2.796094ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:08Z" - latency: 2.24116ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:08Z" - latency: 2.258016ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 2.347552ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 2.350018ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 2.354943ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 2.490857ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-73.ec2.internal uid: be2117b3-e65c-4c64-8eef-6bd2c20b9338 resourceVersion: "50503" uid: f55d0bfd-419e-4473-8e60-e4558b7299fb spec: sourcePod: network-check-source-869dcfcdcd-vbjz9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T19:18:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.304µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:08Z" - latency: 1.852249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:08Z" - latency: 1.130789ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:08Z" - latency: 2.032799ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:08Z" - latency: 1.014735ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:08Z" - latency: 2.34695ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:40:08Z" - latency: 999.213µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:08Z" - latency: 1.955181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:39:08Z" - latency: 875.357µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:08Z" - latency: 1.746085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:38:08Z" kind: List metadata: resourceVersion: ""