apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32843" uid: afebb4cf-07cf-46fd-a740-08310ce38a16 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:31:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.818µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 900.389µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 921.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 788.542µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 1.177568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 909.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:01:22Z" - latency: 1.402817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:00:22Z" - latency: 1.211625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:59:22Z" - latency: 1.045055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:58:22Z" - latency: 1.041259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32845" uid: 0906844e-b65b-470e-a99e-392baaf54570 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:30:22Z" message: 'load-balancer-api-external: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.796819ms message: 'load-balancer-api-external: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 7.237023ms message: 'load-balancer-api-external: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:06:22Z" - latency: 4.411099ms message: 'load-balancer-api-external: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 6.684905ms message: 'load-balancer-api-external: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:05:22Z" - latency: 4.000975ms message: 'load-balancer-api-external: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 9.144464ms message: 'load-balancer-api-external: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:04:22Z" - latency: 4.966554ms message: 'load-balancer-api-external: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 7.875426ms message: 'load-balancer-api-external: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:03:22Z" - latency: 4.10952ms message: 'load-balancer-api-external: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 7.835792ms message: 'load-balancer-api-external: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:02:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32844" uid: 4a9d4dca-7efe-4c19-87b5-5305d5959cc8 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:30:22Z" message: 'load-balancer-api-internal: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.152829ms message: 'load-balancer-api-internal: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 7.212066ms message: 'load-balancer-api-internal: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:06:22Z" - latency: 4.471379ms message: 'load-balancer-api-internal: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 6.606375ms message: 'load-balancer-api-internal: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:05:22Z" - latency: 4.246385ms message: 'load-balancer-api-internal: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 9.10031ms message: 'load-balancer-api-internal: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:04:22Z" - latency: 4.998105ms message: 'load-balancer-api-internal: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 7.816694ms message: 'load-balancer-api-internal: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:03:22Z" - latency: 4.127027ms message: 'load-balancer-api-internal: tcp connection to a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 7.783236ms message: 'load-balancer-api-internal: resolved host name a421b2ff391464237abd502e9a364dd5-7cf6d3960b8eff3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:02:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-network-check-target-ip-10-0-128-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32839" uid: f93a6d0e-0b89-4063-bed0-0573db003d65 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:31:22Z" message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.008908ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 1.380586ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 869.692µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 863.001µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 801.313µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 946.13µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:01:22Z" - latency: 995.79µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:00:22Z" - latency: 835.058µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:59:22Z" - latency: 839.898µs message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:58:22Z" - latency: 1.120268ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-network-check-target-ip-10-0-132-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32841" uid: 112238ab-a8ab-4636-98f7-c4041756c0b9 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:31:22Z" message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.121746ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 2.110262ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 2.30439ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 2.142677ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 2.382194ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 2.137391ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:01:22Z" - latency: 2.22765ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:00:22Z" - latency: 2.298326ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:59:22Z" - latency: 2.377669ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:58:22Z" - latency: 2.164577ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-network-check-target-ip-10-0-142-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32840" uid: 1f28b187-17cb-452d-ae52-c56873648868 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:31:22Z" message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.206595ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 2.136022ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 2.404992ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 1.943136ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 2.305351ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 2.175488ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:01:22Z" - latency: 2.083583ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:00:22Z" - latency: 2.051278ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:59:22Z" - latency: 2.296104ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:58:22Z" - latency: 2.227301ms message: 'network-check-target-ip-10-0-142-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:24:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-21-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-21.ec2.internal uid: 0c494a45-3531-4e93-adb5-63c321e808cc resourceVersion: "32842" uid: 90b75173-c43b-455d-ab6c-3a0835d272d8 spec: sourcePod: network-check-source-8894fc9bd-mctfb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:30:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.159109ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:22Z" - latency: 1.977666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:06:22Z" - latency: 1.060376ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:22Z" - latency: 1.871169ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:05:22Z" - latency: 960.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:22Z" - latency: 1.516435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:04:22Z" - latency: 1.243714ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:22Z" - latency: 1.559736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:03:22Z" - latency: 761.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:02:22Z" - latency: 1.601067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:02:22Z" kind: List metadata: resourceVersion: ""