apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "46294" uid: cee9c44b-bd11-46cb-9a49-fe3c80f15580 spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T04:39:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.082µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 928.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 1.092267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 2.180737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:57:38Z" - latency: 3.796246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:56:38Z" - latency: 1.952499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:55:38Z" - latency: 1.018424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:54:38Z" - latency: 988.476µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:53:38Z" - latency: 1.321849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:52:38Z" - latency: 1.676378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "48682" uid: a84ed1e2-4052-44f8-ac74-b30ba7780db0 spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T04:38:38Z" message: 'load-balancer-api-external: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.243287ms message: 'load-balancer-api-external: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:02:38Z" - latency: 7.908504ms message: 'load-balancer-api-external: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T05:02:38Z" - latency: 4.29776ms message: 'load-balancer-api-external: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:01:38Z" - latency: 6.626652ms message: 'load-balancer-api-external: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T05:01:38Z" - latency: 4.697825ms message: 'load-balancer-api-external: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 7.365344ms message: 'load-balancer-api-external: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T05:00:38Z" - latency: 6.678335ms message: 'load-balancer-api-external: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 9.104724ms message: 'load-balancer-api-external: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T04:59:38Z" - latency: 3.893858ms message: 'load-balancer-api-external: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 7.608165ms message: 'load-balancer-api-external: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T04:58:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "48683" uid: 8429931f-a83a-47bc-921a-956b1011c740 spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T04:38:38Z" message: 'load-balancer-api-internal: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.704577ms message: 'load-balancer-api-internal: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:02:38Z" - latency: 7.879118ms message: 'load-balancer-api-internal: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T05:02:38Z" - latency: 4.242216ms message: 'load-balancer-api-internal: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:01:38Z" - latency: 6.665562ms message: 'load-balancer-api-internal: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T05:01:38Z" - latency: 4.694925ms message: 'load-balancer-api-internal: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 7.351898ms message: 'load-balancer-api-internal: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T05:00:38Z" - latency: 6.608324ms message: 'load-balancer-api-internal: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 9.24923ms message: 'load-balancer-api-internal: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T04:59:38Z" - latency: 3.961143ms message: 'load-balancer-api-internal: tcp connection to a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 7.54753ms message: 'load-balancer-api-internal: resolved host name a5dafd976098b40f58f290e68ed32473-7d05cf24b87fba13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T04:58:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-network-check-target-ip-10-0-136-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "46291" uid: 8c0c9969-87dc-47ee-951f-d563da3cdead spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T04:39:38Z" message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.515748ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 964.888µs message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 925.647µs message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 3.668211ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:57:38Z" - latency: 1.406925ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:56:38Z" - latency: 1.516477ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:55:38Z" - latency: 1.616526ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:54:38Z" - latency: 977.26µs message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:53:38Z" - latency: 2.234636ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:52:38Z" - latency: 1.034789ms message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-network-check-target-ip-10-0-139-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "46293" uid: 3a649047-b651-4f96-9f12-60e7e1fb320f spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T04:39:38Z" message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.444773ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 2.920894ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 2.319577ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 2.895333ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:57:38Z" - latency: 4.676837ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:56:38Z" - latency: 2.554299ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:55:38Z" - latency: 2.2554ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:54:38Z" - latency: 2.49432ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:53:38Z" - latency: 2.360073ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:52:38Z" - latency: 2.229523ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-network-check-target-ip-10-0-140-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "46292" uid: eee0a9f5-261a-4b66-9e9c-7ce91525ebd2 spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T04:39:38Z" message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.520621ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 3.441739ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 2.328906ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 3.227724ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:57:38Z" - latency: 4.089991ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:56:38Z" - latency: 2.569763ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:55:38Z" - latency: 2.540595ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:54:38Z" - latency: 2.472024ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:53:38Z" - latency: 3.23837ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:52:38Z" - latency: 2.8918ms message: 'network-check-target-ip-10-0-140-86: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T04:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-236-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-236.ec2.internal uid: c00dc54d-70ae-4346-a8e2-3972ad14d238 resourceVersion: "48680" uid: 0d0992f9-1db5-4531-894d-13b5f0575699 spec: sourcePod: network-check-source-6947749cfc-n2j57 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T04:38:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.675µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:02:38Z" - latency: 2.768613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T05:02:38Z" - latency: 933.483µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:01:38Z" - latency: 2.216539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T05:01:38Z" - latency: 1.269291ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T05:00:38Z" - latency: 1.841957ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T05:00:38Z" - latency: 981.328µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:59:38Z" - latency: 3.656328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T04:59:38Z" - latency: 916.035µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T04:58:38Z" - latency: 2.531341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T04:58:38Z" kind: List metadata: resourceVersion: ""