apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60704" uid: 4bd51ea2-c298-4e86-9c7d-524f77d0e929 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T13:39:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.159656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 1.02658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 941.395µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 1.331824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 1.102061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 938.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:09:22Z" - latency: 1.18276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:08:22Z" - latency: 991.655µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:07:22Z" - latency: 888.969µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:06:22Z" - latency: 1.209521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:05:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60706" uid: 184e02e2-8290-4ac3-bfa9-d03fa3c60b43 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T13:38:22Z" message: 'load-balancer-api-external: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.269662ms message: 'load-balancer-api-external: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 7.525534ms message: 'load-balancer-api-external: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:14:22Z" - latency: 5.858902ms message: 'load-balancer-api-external: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 9.290939ms message: 'load-balancer-api-external: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:13:22Z" - latency: 3.388608ms message: 'load-balancer-api-external: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 6.941526ms message: 'load-balancer-api-external: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:12:22Z" - latency: 4.668677ms message: 'load-balancer-api-external: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 8.026955ms message: 'load-balancer-api-external: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:11:22Z" - latency: 3.666863ms message: 'load-balancer-api-external: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 8.936375ms message: 'load-balancer-api-external: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:10:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60705" uid: 99ecfd46-45b8-4e98-aa22-a9c591be6b70 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T13:38:22Z" message: 'load-balancer-api-internal: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.282117ms message: 'load-balancer-api-internal: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 7.451655ms message: 'load-balancer-api-internal: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:14:22Z" - latency: 3.157491ms message: 'load-balancer-api-internal: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 9.258437ms message: 'load-balancer-api-internal: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:13:22Z" - latency: 4.45253ms message: 'load-balancer-api-internal: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 6.886276ms message: 'load-balancer-api-internal: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:12:22Z" - latency: 3.412997ms message: 'load-balancer-api-internal: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 7.967503ms message: 'load-balancer-api-internal: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:11:22Z" - latency: 3.451723ms message: 'load-balancer-api-internal: tcp connection to af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 8.784435ms message: 'load-balancer-api-internal: resolved host name af2131cc9000a45c8a98ea5f3bc2aa25-bb3692d898b66665.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:10:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-network-check-target-ip-10-0-133-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60702" uid: c14993cd-8a87-4866-bb05-8b621d6e72d5 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T13:39:22Z" message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.612934ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 2.180993ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 2.503083ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 2.266711ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 2.477254ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 2.239272ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:09:22Z" - latency: 2.469623ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:08:22Z" - latency: 2.155868ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:07:22Z" - latency: 2.680189ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:06:22Z" - latency: 2.59644ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:05:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-network-check-target-ip-10-0-134-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60700" uid: c164886d-c130-4894-8eb3-9ebefa0cd642 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T13:39:22Z" message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012852ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 911.535µs message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 1.014377ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 1.624091ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 1.537392ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 943.037µs message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:09:22Z" - latency: 1.064966ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:08:22Z" - latency: 1.198716ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:07:22Z" - latency: 848.511µs message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:06:22Z" - latency: 1.393921ms message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:05:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-network-check-target-ip-10-0-142-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60703" uid: 51bcb8cf-7e2f-440f-ae1d-329c6333ba84 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T13:39:22Z" message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.597386ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 2.451897ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 2.52707ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 2.444271ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 2.449192ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 2.404739ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:09:22Z" - latency: 2.504113ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:08:22Z" - latency: 2.344306ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:07:22Z" - latency: 2.630254ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:06:22Z" - latency: 2.699911ms message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:05:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T13:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-240-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-240.ec2.internal uid: f0fbba30-8e35-416a-b4e7-aa7ad73485e9 resourceVersion: "60701" uid: e8251186-1bfa-4a3c-9e54-de4d5e1ad594 spec: sourcePod: network-check-source-989f8b8dc-q8hsn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T13:38:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.989µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:14:22Z" - latency: 2.032451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:14:22Z" - latency: 886.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:13:22Z" - latency: 1.841839ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:13:22Z" - latency: 877.643µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:12:22Z" - latency: 1.687522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:12:22Z" - latency: 949.004µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:11:22Z" - latency: 1.644723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:11:22Z" - latency: 1.237076ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:10:22Z" - latency: 1.852536ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:10:22Z" kind: List metadata: resourceVersion: ""