apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "58645" uid: d3fe0392-3a8f-44f1-aa5e-f394826c88b3 spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T12:21:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.173473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:56:19Z" - latency: 979.274µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:55:19Z" - latency: 1.474419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:54:19Z" - latency: 911.946µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:53:19Z" - latency: 943.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:52:19Z" - latency: 1.151933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:51:19Z" - latency: 995.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:50:19Z" - latency: 958.756µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:49:19Z" - latency: 1.002409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:48:19Z" - latency: 1.063342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "64998" uid: 7174d6ae-c247-4f4f-8d2e-dba28cca7d5b spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T12:20:19Z" message: 'load-balancer-api-external: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.772613ms message: 'load-balancer-api-external: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:02:19Z" - latency: 9.015451ms message: 'load-balancer-api-external: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:02:19Z" - latency: 5.268668ms message: 'load-balancer-api-external: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:01:19Z" - latency: 7.819193ms message: 'load-balancer-api-external: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:01:19Z" - latency: 5.127329ms message: 'load-balancer-api-external: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:00:19Z" - latency: 8.25099ms message: 'load-balancer-api-external: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:00:19Z" - latency: 3.566344ms message: 'load-balancer-api-external: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:59:19Z" - latency: 6.868301ms message: 'load-balancer-api-external: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T12:59:19Z" - latency: 3.847845ms message: 'load-balancer-api-external: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:58:19Z" - latency: 7.354072ms message: 'load-balancer-api-external: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T12:58:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "64999" uid: 0c696996-697b-46f2-b9c0-e273f6bad861 spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T12:20:19Z" message: 'load-balancer-api-internal: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.773205ms message: 'load-balancer-api-internal: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:02:19Z" - latency: 8.982246ms message: 'load-balancer-api-internal: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:02:19Z" - latency: 5.499251ms message: 'load-balancer-api-internal: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:01:19Z" - latency: 7.851433ms message: 'load-balancer-api-internal: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:01:19Z" - latency: 5.142097ms message: 'load-balancer-api-internal: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:00:19Z" - latency: 8.157993ms message: 'load-balancer-api-internal: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:00:19Z" - latency: 3.551807ms message: 'load-balancer-api-internal: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:59:19Z" - latency: 6.792039ms message: 'load-balancer-api-internal: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T12:59:19Z" - latency: 3.872211ms message: 'load-balancer-api-internal: tcp connection to a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:58:19Z" - latency: 7.257486ms message: 'load-balancer-api-internal: resolved host name a68daf83198d14ae7a6c824cc97a8aaa-9da6bcf0860db144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T12:58:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-network-check-target-ip-10-0-135-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "58644" uid: c839fd82-e747-45a3-b927-a404b5745591 spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T12:21:19Z" message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.919276ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:56:19Z" - latency: 1.980192ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:55:19Z" - latency: 2.422023ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:54:19Z" - latency: 2.129077ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:53:19Z" - latency: 2.295314ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:52:19Z" - latency: 2.325732ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:51:19Z" - latency: 2.450567ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:50:19Z" - latency: 2.608448ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:49:19Z" - latency: 2.491018ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:48:19Z" - latency: 2.40719ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-network-check-target-ip-10-0-136-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "58641" uid: 12082996-95df-439f-bea1-32e86056c849 spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T12:21:19Z" message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.374922ms message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:56:19Z" - latency: 972.798µs message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:55:19Z" - latency: 1.675728ms message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:54:19Z" - latency: 974.279µs message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:53:19Z" - latency: 1.001488ms message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:52:19Z" - latency: 907.463µs message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:51:19Z" - latency: 1.117489ms message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:50:19Z" - latency: 1.133583ms message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:49:19Z" - latency: 924.377µs message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:48:19Z" - latency: 1.260014ms message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-network-check-target-ip-10-0-138-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "58642" uid: 04d13dfc-4d75-4a61-8cfd-4d15eee34674 spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T12:21:19Z" message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.917933ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:56:19Z" - latency: 2.086093ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:55:19Z" - latency: 2.500206ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:54:19Z" - latency: 2.370581ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:53:19Z" - latency: 2.278575ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:52:19Z" - latency: 2.257428ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:51:19Z" - latency: 2.287766ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:50:19Z" - latency: 2.319474ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:49:19Z" - latency: 2.24137ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:48:19Z" - latency: 2.467951ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:14:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-33-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-33.ec2.internal uid: ad17f42e-2a80-483f-b642-bc2052aadc34 resourceVersion: "64997" uid: 7867ebd6-38cb-47cc-9f0d-fde48f525b6a spec: sourcePod: network-check-source-7bc5b6bf85-hz8nf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T12:20:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.192322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:02:19Z" - latency: 1.710929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:02:19Z" - latency: 1.056218ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:01:19Z" - latency: 1.747905ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:01:19Z" - latency: 1.131552ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:00:19Z" - latency: 1.897757ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:00:19Z" - latency: 963.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:59:19Z" - latency: 1.831862ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T12:59:19Z" - latency: 954.039µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T12:58:19Z" - latency: 1.865482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T12:58:19Z" kind: List metadata: resourceVersion: ""