apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132549" uid: 669ba045-a764-41b9-8bc7-724901be720e spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T12:36:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:23Z" - latency: 1.559744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 1.24147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 1.450038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 970.165µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 825.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 2.790762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:23Z" - latency: 2.074652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:11:23Z" - latency: 1.327425ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:10:23Z" - latency: 1.008959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:09:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132017" uid: feca14a5-cb0d-41b8-b2bb-e2a9389d6a0c spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T12:35:23Z" message: 'load-balancer-api-external: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.653797ms message: 'load-balancer-api-external: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 7.258782ms message: 'load-balancer-api-external: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:17:23Z" - latency: 5.940911ms message: 'load-balancer-api-external: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 7.055862ms message: 'load-balancer-api-external: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:16:23Z" - latency: 6.191253ms message: 'load-balancer-api-external: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 7.290344ms message: 'load-balancer-api-external: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:15:23Z" - latency: 5.347471ms message: 'load-balancer-api-external: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 6.538259ms message: 'load-balancer-api-external: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:14:23Z" - latency: 5.670127ms message: 'load-balancer-api-external: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 7.798882ms message: 'load-balancer-api-external: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:13:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132018" uid: 13d558f4-a76d-4266-b80b-c48f7f8ac05d spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T12:35:23Z" message: 'load-balancer-api-internal: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.725385ms message: 'load-balancer-api-internal: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 7.234315ms message: 'load-balancer-api-internal: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:17:23Z" - latency: 5.913638ms message: 'load-balancer-api-internal: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 7.091211ms message: 'load-balancer-api-internal: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:16:23Z" - latency: 6.300555ms message: 'load-balancer-api-internal: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 7.353199ms message: 'load-balancer-api-internal: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:15:23Z" - latency: 5.515091ms message: 'load-balancer-api-internal: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 6.56337ms message: 'load-balancer-api-internal: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:14:23Z" - latency: 5.676641ms message: 'load-balancer-api-internal: tcp connection to aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 7.727479ms message: 'load-balancer-api-internal: resolved host name aa2133d1650bd41e088a42584786b3bd-f71f89299a4320f8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:13:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-network-check-target-ip-10-0-130-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132546" uid: 371dbfad-9fc5-47a8-bfe8-0b096f2c261c spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:36:23Z" message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.383µs message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:23Z" - latency: 991.383µs message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 907.213µs message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 1.598651ms message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 1.214575ms message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 985.275µs message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 3.258764ms message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:23Z" - latency: 1.045212ms message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:11:23Z" - latency: 1.141038ms message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:10:23Z" - latency: 1.092983ms message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:09:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-network-check-target-ip-10-0-140-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132548" uid: 4f93fd55-07c7-43b6-b23f-827a2b6ec078 spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:36:23Z" message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.27345ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:23Z" - latency: 2.464574ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 2.589498ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 2.279635ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 2.71166ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 2.519851ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 2.980124ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:23Z" - latency: 2.605577ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:11:23Z" - latency: 2.531219ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:10:23Z" - latency: 2.535703ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:09:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-network-check-target-ip-10-0-142-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132547" uid: c7cc12c9-194b-4ae0-ac7a-ca970934dee7 spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:36:23Z" message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.973546ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:23Z" - latency: 1.956004ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 2.28185ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 2.260609ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 1.970448ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 2.164797ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 3.846615ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:23Z" - latency: 2.546302ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:11:23Z" - latency: 2.363456ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:10:23Z" - latency: 2.194333ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:09:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:29:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-190-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-190.us-east-2.compute.internal uid: 60fa7f06-bda2-4e9d-9497-f2faf3fca635 resourceVersion: "132016" uid: cd480ae0-3b72-4bd9-ad8d-c724d3ce9cd6 spec: sourcePod: network-check-source-6f78d59f99-m9xxh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T12:35:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 984.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:23Z" - latency: 2.055053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:17:23Z" - latency: 1.147479ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:23Z" - latency: 1.988463ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:16:23Z" - latency: 999.382µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:23Z" - latency: 2.621794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:15:23Z" - latency: 1.066436ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:23Z" - latency: 1.881195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:14:23Z" - latency: 1.066087ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:23Z" - latency: 2.980124ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:13:23Z" kind: List metadata: resourceVersion: ""