apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "50809" uid: d7a67b38-e0e9-41cf-aad3-4e1058c90aac spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T20:15:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.626µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 890.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 834.201µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 951.819µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 868.893µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:55Z" - latency: 1.268149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:55Z" - latency: 928.017µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:55Z" - latency: 1.209091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:55Z" - latency: 926.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:55Z" - latency: 849.283µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "51635" uid: cb9b7a49-637f-4852-89cd-9a4725e29bef spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:14:55Z" message: 'load-balancer-api-external: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.957218ms message: 'load-balancer-api-external: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:55Z" - latency: 7.065864ms message: 'load-balancer-api-external: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:44:55Z" - latency: 4.260696ms message: 'load-balancer-api-external: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 7.302124ms message: 'load-balancer-api-external: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:43:55Z" - latency: 4.883872ms message: 'load-balancer-api-external: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 6.141185ms message: 'load-balancer-api-external: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:42:55Z" - latency: 4.671286ms message: 'load-balancer-api-external: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 6.483299ms message: 'load-balancer-api-external: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:41:55Z" - latency: 6.299612ms message: 'load-balancer-api-external: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 9.302447ms message: 'load-balancer-api-external: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:40:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "51634" uid: 36f0b75f-93ea-44e7-a999-c21105960474 spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:14:55Z" message: 'load-balancer-api-internal: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.976359ms message: 'load-balancer-api-internal: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:55Z" - latency: 7.022236ms message: 'load-balancer-api-internal: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:44:55Z" - latency: 4.891177ms message: 'load-balancer-api-internal: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 7.401001ms message: 'load-balancer-api-internal: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:43:55Z" - latency: 6.596908ms message: 'load-balancer-api-internal: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 6.230717ms message: 'load-balancer-api-internal: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:42:55Z" - latency: 4.67648ms message: 'load-balancer-api-internal: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 6.528154ms message: 'load-balancer-api-internal: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:41:55Z" - latency: 6.306801ms message: 'load-balancer-api-internal: tcp connection to ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 9.267307ms message: 'load-balancer-api-internal: resolved host name ab9f98892658242508f171bd05a809f2-b2773de990c4921d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:40:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-130-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "50808" uid: 133bc7ec-9b22-4c21-ac2f-268baced54ab spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:15:55Z" message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.264913ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 1.039532ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 951.052µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 898.397µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 1.184244ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:55Z" - latency: 1.183083ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:55Z" - latency: 842.349µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:55Z" - latency: 1.2559ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:55Z" - latency: 1.475545ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:55Z" - latency: 1.097627ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-131-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "50806" uid: 906c201c-c4ab-4f60-9116-cf512315c7e8 spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:15:55Z" message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.217914ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 2.208783ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 2.124168ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 2.349296ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 2.162884ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:55Z" - latency: 2.24855ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:55Z" - latency: 2.113643ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:55Z" - latency: 2.128037ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:55Z" - latency: 2.31158ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:55Z" - latency: 1.75924ms message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-136-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "50807" uid: 96ba961c-b752-4584-ad7c-13038cdf24f0 spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:15:55Z" message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.196015ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 2.32303ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 15.581788ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 2.357813ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 2.075929ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:55Z" - latency: 2.265622ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:55Z" - latency: 2.07994ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:55Z" - latency: 2.498065ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:55Z" - latency: 2.410467ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:55Z" - latency: 2.325216ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.ec2.internal uid: ce336f17-44a9-44a7-a1fe-c189740ed966 resourceVersion: "51633" uid: 3f149b1b-4732-4eb9-b3b7-3da1f0fc0d0c spec: sourcePod: network-check-source-989f8b8dc-kgfjd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:14:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.323µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:55Z" - latency: 2.226385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:44:55Z" - latency: 935.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:55Z" - latency: 1.554301ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:43:55Z" - latency: 996.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:55Z" - latency: 2.043103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:42:55Z" - latency: 899.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:55Z" - latency: 1.662722ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:41:55Z" - latency: 831.017µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:55Z" - latency: 2.364931ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:40:55Z" kind: List metadata: resourceVersion: ""