apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "51298" uid: 4437e596-111a-4971-94f5-307550c50a94 spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T15:25:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 1.015742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 988.345µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 1.071204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 1.138743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:49:00Z" - latency: 1.316873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:00Z" - latency: 1.097497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:00Z" - latency: 1.675327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:00Z" - latency: 1.129409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:00Z" - latency: 870.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "52419" uid: 4cb57536-5bd8-477e-9237-a6011b96e30c spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T15:24:00Z" message: 'load-balancer-api-external: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.791385ms message: 'load-balancer-api-external: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:54:00Z" - latency: 9.373803ms message: 'load-balancer-api-external: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:54:00Z" - latency: 4.305607ms message: 'load-balancer-api-external: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 10.409521ms message: 'load-balancer-api-external: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:53:00Z" - latency: 11.408215ms message: 'load-balancer-api-external: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 7.012502ms message: 'load-balancer-api-external: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:52:00Z" - latency: 4.90913ms message: 'load-balancer-api-external: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 7.71961ms message: 'load-balancer-api-external: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:51:00Z" - latency: 4.037486ms message: 'load-balancer-api-external: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 8.195771ms message: 'load-balancer-api-external: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:50:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "52420" uid: dbca6500-b238-46f5-9fc3-436691bd2436 spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T15:24:00Z" message: 'load-balancer-api-internal: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.847418ms message: 'load-balancer-api-internal: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:54:00Z" - latency: 9.312617ms message: 'load-balancer-api-internal: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:54:00Z" - latency: 5.287189ms message: 'load-balancer-api-internal: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 10.387402ms message: 'load-balancer-api-internal: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:53:00Z" - latency: 13.490355ms message: 'load-balancer-api-internal: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 6.982016ms message: 'load-balancer-api-internal: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:52:00Z" - latency: 4.892029ms message: 'load-balancer-api-internal: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 7.630426ms message: 'load-balancer-api-internal: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:51:00Z" - latency: 4.035919ms message: 'load-balancer-api-internal: tcp connection to a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 8.217799ms message: 'load-balancer-api-internal: resolved host name a9dd29ab3440647fab6662f95444464d-79d34de2d1de2f38.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:50:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-134-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "51295" uid: 3946d94a-96c7-44f9-93ea-9e3448cb4e12 spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:25:00Z" message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.124332ms message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 876.226µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 850.155µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 890.208µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 920.245µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:49:00Z" - latency: 811.041µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:00Z" - latency: 976.889µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:00Z" - latency: 754.418µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:00Z" - latency: 1.272612ms message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:00Z" - latency: 804.132µs message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-136-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "51297" uid: cd4b7742-f216-4077-aa77-31f5701fedb2 spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:25:00Z" message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296974ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 2.284705ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 1.971242ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 2.229561ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 1.840384ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:49:00Z" - latency: 1.914803ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:00Z" - latency: 2.088822ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:00Z" - latency: 2.345702ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:00Z" - latency: 2.295248ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:00Z" - latency: 2.084953ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-140-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "51296" uid: 38b084c0-9fbc-4134-ae8c-36c5ba45d517 spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:25:00Z" message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.923792ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 1.726118ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 1.838028ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 1.817414ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 1.937643ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:49:00Z" - latency: 1.895347ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:00Z" - latency: 1.587026ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:00Z" - latency: 1.89233ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:00Z" - latency: 1.991218ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:00Z" - latency: 1.551818ms message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-200-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-200.ec2.internal uid: 711a5082-a18a-477b-b4ad-38ee85cd3e36 resourceVersion: "52418" uid: e19a9010-2d75-4f43-ad30-6b26c3f0286a spec: sourcePod: network-check-source-6947749cfc-9cmpt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T15:24:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.478µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:54:00Z" - latency: 1.717475ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:54:00Z" - latency: 1.096375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:53:00Z" - latency: 1.970532ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:53:00Z" - latency: 785.723µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:52:00Z" - latency: 1.643866ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:52:00Z" - latency: 1.020378ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:51:00Z" - latency: 2.150745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:51:00Z" - latency: 916.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:50:00Z" - latency: 1.798279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:50:00Z" kind: List metadata: resourceVersion: ""