apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60847" uid: 57d1fde2-a12f-41c0-b183-4d151524c307 spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-11T23:41:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.130824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 1.099427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 1.087119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 847.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 1.353815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 1.060356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:11:07Z" - latency: 1.07538ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:10:07Z" - latency: 942.339µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:09:07Z" - latency: 1.063306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:08:07Z" - latency: 971.174µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:07:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60848" uid: 0e33fe44-e305-4a28-afe9-4898bc7eb193 spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T23:40:07Z" message: 'load-balancer-api-external: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.452614ms message: 'load-balancer-api-external: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 8.678549ms message: 'load-balancer-api-external: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:16:07Z" - latency: 4.691118ms message: 'load-balancer-api-external: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 11.739783ms message: 'load-balancer-api-external: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:15:07Z" - latency: 4.259517ms message: 'load-balancer-api-external: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 8.938805ms message: 'load-balancer-api-external: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:14:07Z" - latency: 5.038152ms message: 'load-balancer-api-external: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 8.123711ms message: 'load-balancer-api-external: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:13:07Z" - latency: 3.891293ms message: 'load-balancer-api-external: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 9.12853ms message: 'load-balancer-api-external: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:12:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60849" uid: 2630e149-455d-47ff-bb12-a537f7304532 spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T23:40:07Z" message: 'load-balancer-api-internal: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.882889ms message: 'load-balancer-api-internal: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 8.579546ms message: 'load-balancer-api-internal: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:16:07Z" - latency: 4.601427ms message: 'load-balancer-api-internal: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 11.785091ms message: 'load-balancer-api-internal: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:15:07Z" - latency: 4.575442ms message: 'load-balancer-api-internal: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 8.831241ms message: 'load-balancer-api-internal: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:14:07Z" - latency: 5.072952ms message: 'load-balancer-api-internal: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 8.070717ms message: 'load-balancer-api-internal: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:13:07Z" - latency: 4.197123ms message: 'load-balancer-api-internal: tcp connection to a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 9.003319ms message: 'load-balancer-api-internal: resolved host name a426ed1727ccd41c6a59ed78a5d3ab83-ddc19ae8cc7e823f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T00:12:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-network-check-target-ip-10-0-136-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60844" uid: 22e396a9-d1ed-442e-b195-d41843bc9bb7 spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-11T23:41:07Z" message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.054015ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 2.459544ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 2.242844ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 2.044099ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 2.513075ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 2.198596ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:11:07Z" - latency: 2.09894ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:10:07Z" - latency: 2.193221ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:09:07Z" - latency: 1.880488ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:08:07Z" - latency: 2.297973ms message: 'network-check-target-ip-10-0-136-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:07:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-network-check-target-ip-10-0-137-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60843" uid: 642f83f6-7384-446a-9cd1-4f2dcd7e85ba spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-11T23:41:07Z" message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.928µs message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 1.104776ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 825.924µs message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 875.069µs message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 1.082264ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 1.138971ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:11:07Z" - latency: 885.695µs message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:10:07Z" - latency: 1.180762ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:09:07Z" - latency: 1.265889ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:08:07Z" - latency: 1.09012ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:07:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-network-check-target-ip-10-0-140-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60845" uid: 4066fc32-283f-410e-8a91-58b564a7f102 spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-11T23:41:07Z" message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.330357ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 2.124652ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 2.201475ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 2.177997ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 2.359304ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 2.019919ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:11:07Z" - latency: 2.316192ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:10:07Z" - latency: 2.130493ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:09:07Z" - latency: 1.873238ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:08:07Z" - latency: 2.198609ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:07:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T23:34:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-251-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-251.ec2.internal uid: 52ca3bdf-9db2-40ab-95dd-f45146545a4f resourceVersion: "60846" uid: d4a6ced5-3e4a-455c-9385-d53e98efa9e9 spec: sourcePod: network-check-source-869dcfcdcd-w2hcg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-11T23:40:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.390177ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:16:07Z" - latency: 1.684874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T00:16:07Z" - latency: 842.016µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:15:07Z" - latency: 1.720001ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T00:15:07Z" - latency: 1.207555ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:14:07Z" - latency: 1.707845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T00:14:07Z" - latency: 870.441µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:13:07Z" - latency: 1.768509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T00:13:07Z" - latency: 1.080053ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T00:12:07Z" - latency: 1.757979ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T00:12:07Z" kind: List metadata: resourceVersion: ""