apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "44095" uid: 22157bc2-1f65-4f1a-b7d6-65828c743ef2 spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T13:15:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.092436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 1.224151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 836.044µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 1.066315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:33:56Z" - latency: 1.230421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:32:56Z" - latency: 1.662136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:31:56Z" - latency: 918.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:30:56Z" - latency: 1.335671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:29:56Z" - latency: 1.747345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:28:56Z" - latency: 1.279821ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "46202" uid: 764766fc-1b45-466f-b055-8ed771fec766 spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T13:14:56Z" message: 'load-balancer-api-external: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.482245ms message: 'load-balancer-api-external: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:38:56Z" - latency: 8.117051ms message: 'load-balancer-api-external: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:38:56Z" - latency: 5.038208ms message: 'load-balancer-api-external: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:37:56Z" - latency: 8.746703ms message: 'load-balancer-api-external: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:37:56Z" - latency: 10.510647ms message: 'load-balancer-api-external: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 8.800753ms message: 'load-balancer-api-external: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:36:56Z" - latency: 5.35996ms message: 'load-balancer-api-external: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 7.942388ms message: 'load-balancer-api-external: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:35:56Z" - latency: 4.286406ms message: 'load-balancer-api-external: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 12.51358ms message: 'load-balancer-api-external: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:34:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "46203" uid: c1b10858-b13c-435b-9856-281b05d7aecd spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T13:14:56Z" message: 'load-balancer-api-internal: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.452775ms message: 'load-balancer-api-internal: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:38:56Z" - latency: 8.013005ms message: 'load-balancer-api-internal: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:38:56Z" - latency: 3.944917ms message: 'load-balancer-api-internal: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:37:56Z" - latency: 8.818809ms message: 'load-balancer-api-internal: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:37:56Z" - latency: 16.978207ms message: 'load-balancer-api-internal: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 8.918427ms message: 'load-balancer-api-internal: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:36:56Z" - latency: 5.324931ms message: 'load-balancer-api-internal: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 8.006057ms message: 'load-balancer-api-internal: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:35:56Z" - latency: 4.506713ms message: 'load-balancer-api-internal: tcp connection to a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 12.564491ms message: 'load-balancer-api-internal: resolved host name a61405394392a4f619713a4081a2d4f6-6089a0a027a9da76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:34:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-ip-10-0-128-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "44093" uid: dca8979c-cfe0-4f35-b4bf-4c86042bfd98 spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:15:56Z" message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.198479ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 2.001744ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 2.542016ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 2.56729ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:33:56Z" - latency: 2.191503ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:32:56Z" - latency: 2.474492ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:31:56Z" - latency: 2.429716ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:30:56Z" - latency: 2.314254ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:29:56Z" - latency: 2.659223ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:28:56Z" - latency: 2.249404ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-ip-10-0-129-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "44094" uid: b3462694-1b82-421b-97b9-0ce7b15bf362 spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:15:56Z" message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.271382ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 2.661046ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 2.591558ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 1.778279ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:33:56Z" - latency: 1.984473ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:32:56Z" - latency: 2.179652ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:31:56Z" - latency: 2.472824ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:30:56Z" - latency: 2.256141ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:29:56Z" - latency: 2.504264ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:28:56Z" - latency: 2.560873ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-ip-10-0-140-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "44092" uid: 9996dd51-5520-423c-ae9f-2f8bd07a2225 spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:15:56Z" message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.211697ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 852.638µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 1.581415ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 823.233µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:33:56Z" - latency: 1.405173ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:32:56Z" - latency: 920.582µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:31:56Z" - latency: 1.02401ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:30:56Z" - latency: 1.443701ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:29:56Z" - latency: 1.914654ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:28:56Z" - latency: 876.943µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:27:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:08:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 15ce2b1d-4921-426f-b78b-041a1f99c5b6 resourceVersion: "46201" uid: 7d3f5735-48f4-43a3-9326-728732dfe55e spec: sourcePod: network-check-source-dbd9cf844-5fg6q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T13:14:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.399219ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:38:56Z" - latency: 1.54338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:38:56Z" - latency: 840.903µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:37:56Z" - latency: 2.088625ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:37:56Z" - latency: 744.343µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:36:56Z" - latency: 2.039851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:36:56Z" - latency: 1.097623ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:35:56Z" - latency: 1.592146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:35:56Z" - latency: 712.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:34:56Z" - latency: 2.015833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:34:56Z" kind: List metadata: resourceVersion: ""