apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15462" uid: 04ade798-b790-4185-ae74-86b465b069ca spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T15:28:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.203689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:28:43Z" - latency: 869.327µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 1.162867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 935.287µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 1.407883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 893.698µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 953.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15052" uid: b42bda2f-f0c3-4ae4-9a27-a29d00180d77 spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:27:43Z" message: 'load-balancer-api-external: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.987514ms message: 'load-balancer-api-external: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 7.563814ms message: 'load-balancer-api-external: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:27:43Z" - latency: 5.517245ms message: 'load-balancer-api-external: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 8.076062ms message: 'load-balancer-api-external: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:26:43Z" - latency: 4.491726ms message: 'load-balancer-api-external: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 7.533034ms message: 'load-balancer-api-external: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:25:43Z" - latency: 4.506703ms message: 'load-balancer-api-external: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 8.808425ms message: 'load-balancer-api-external: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:24:43Z" - latency: 5.249075ms message: 'load-balancer-api-external: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 13.816698ms message: 'load-balancer-api-external: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:23:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15051" uid: cf3cd025-c61f-4b43-b2cb-b011277b7de3 spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:27:43Z" message: 'load-balancer-api-internal: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.997116ms message: 'load-balancer-api-internal: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 7.471277ms message: 'load-balancer-api-internal: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:27:43Z" - latency: 5.571543ms message: 'load-balancer-api-internal: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 7.951112ms message: 'load-balancer-api-internal: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:26:43Z" - latency: 5.370287ms message: 'load-balancer-api-internal: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 7.451805ms message: 'load-balancer-api-internal: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:25:43Z" - latency: 4.542852ms message: 'load-balancer-api-internal: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 8.72154ms message: 'load-balancer-api-internal: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:24:43Z" - latency: 5.790615ms message: 'load-balancer-api-internal: tcp connection to abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 13.736923ms message: 'load-balancer-api-internal: resolved host name abdd304e472a6436eb90404035462ca1-bb100cc3675d20e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:23:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-133-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15460" uid: 3d3c280d-386b-4cf1-a0a7-527b0af0445e spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:28:43Z" message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.125293ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:28:43Z" - latency: 1.766854ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 1.829067ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 1.74207ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 1.971585ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 1.8888ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 2.403949ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-137-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15461" uid: d19a6a8b-28bb-419f-8018-ddf55c65ed29 spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:28:43Z" message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.237912ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:28:43Z" - latency: 2.038134ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 2.119846ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 1.95556ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 2.13333ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 2.049973ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 2.282245ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-142-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15459" uid: fe715acc-18af-4f11-ac29-8c5242886895 spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:28:43Z" message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.274µs message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:28:43Z" - latency: 834.052µs message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 954.66µs message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 762.516µs message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 818.74µs message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 814.944µs message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 1.669385ms message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-43-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-43.ec2.internal uid: 2f014579-cc8a-4309-928c-5f11827f2392 resourceVersion: "15050" uid: 9eb309b3-c3b8-4fd6-a5da-03fb12b3f403 spec: sourcePod: network-check-source-dbd9cf844-cdxwq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T15:27:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096283ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:27:43Z" - latency: 1.723939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:27:43Z" - latency: 886.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:26:43Z" - latency: 1.714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:26:43Z" - latency: 1.247755ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:25:43Z" - latency: 1.551147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:25:43Z" - latency: 850.264µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:24:43Z" - latency: 2.233451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:24:43Z" - latency: 801.687µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:23:43Z" - latency: 8.032927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:23:43Z" kind: List metadata: resourceVersion: ""