apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "23659" uid: d5cb80e2-2b62-459f-9d17-a4323607b27f spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T07:42:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.057418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:03:34Z" - latency: 909.683µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:02:34Z" - latency: 875.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:01:34Z" - latency: 1.040091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:00:34Z" - latency: 1.058444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 911.317µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 971.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 763.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 1.371908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 779.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:54:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "22020" uid: 6ac198e3-841b-47ae-a55f-2861637010ca spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T07:41:34Z" message: 'load-balancer-api-external: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.570636ms message: 'load-balancer-api-external: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 7.577121ms message: 'load-balancer-api-external: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:59:34Z" - latency: 4.076459ms message: 'load-balancer-api-external: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 7.566627ms message: 'load-balancer-api-external: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:58:34Z" - latency: 4.363493ms message: 'load-balancer-api-external: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 6.792253ms message: 'load-balancer-api-external: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:57:34Z" - latency: 4.09467ms message: 'load-balancer-api-external: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 7.188221ms message: 'load-balancer-api-external: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:56:34Z" - latency: 4.26696ms message: 'load-balancer-api-external: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 8.720417ms message: 'load-balancer-api-external: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:55:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "22019" uid: 836431b2-5f19-45ba-8545-eaac90187d8e spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T07:41:34Z" message: 'load-balancer-api-internal: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.518854ms message: 'load-balancer-api-internal: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 7.663442ms message: 'load-balancer-api-internal: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:59:34Z" - latency: 4.090131ms message: 'load-balancer-api-internal: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 7.637649ms message: 'load-balancer-api-internal: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:58:34Z" - latency: 4.394629ms message: 'load-balancer-api-internal: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 6.74391ms message: 'load-balancer-api-internal: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:57:34Z" - latency: 4.566979ms message: 'load-balancer-api-internal: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 7.217196ms message: 'load-balancer-api-internal: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:56:34Z" - latency: 4.26016ms message: 'load-balancer-api-internal: tcp connection to a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 8.678391ms message: 'load-balancer-api-internal: resolved host name a36f49428cde240a48b1c23644997efc-15ded68eb0975b94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T07:55:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-ip-10-0-136-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "23656" uid: 31d336e3-427d-45b6-b91b-e98f4a3d6d19 spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T07:42:34Z" message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 769.856µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:03:34Z" - latency: 829.316µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:02:34Z" - latency: 1.166573ms message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:01:34Z" - latency: 856.699µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:00:34Z" - latency: 799.094µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 744.117µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 926.67µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 836.893µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 768.143µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 779.035µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:54:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-ip-10-0-141-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "23658" uid: 5da35a9a-b741-4370-ac94-4b95b0e250ec spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T07:42:34Z" message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.071024ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:03:34Z" - latency: 2.200836ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:02:34Z" - latency: 2.014163ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:01:34Z" - latency: 2.07047ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:00:34Z" - latency: 2.245716ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 2.650258ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 2.23752ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 2.103738ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 2.634843ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 2.093453ms message: 'network-check-target-ip-10-0-141-221: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:54:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-ip-10-0-142-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "23657" uid: 14cd77fe-2ad0-42eb-878f-af1e36500fb0 spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T07:42:34Z" message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.068576ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:03:34Z" - latency: 1.686272ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:02:34Z" - latency: 2.111639ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:01:34Z" - latency: 1.980758ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T08:00:34Z" - latency: 2.335164ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 1.808898ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 1.873554ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 1.863152ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 1.81316ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 1.841061ms message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:54:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T07:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: 6b3b3f5b-75ec-46c7-84b2-f216ffccf1bd resourceVersion: "22018" uid: db4168e2-b400-4ec5-aa15-a0bcf2a97dc7 spec: sourcePod: network-check-source-6f8b768455-qhcvg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T07:41:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.69µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:59:34Z" - latency: 1.941643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T07:59:34Z" - latency: 877.883µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:58:34Z" - latency: 1.779074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T07:58:34Z" - latency: 798.343µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:57:34Z" - latency: 1.634064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T07:57:34Z" - latency: 961.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:56:34Z" - latency: 1.595693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T07:56:34Z" - latency: 783.299µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T07:55:34Z" - latency: 2.078762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T07:55:34Z" kind: List metadata: resourceVersion: ""