apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "78700" uid: 00c509ed-9b41-4fa7-8126-08739d51ce0b spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-01T00:48:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:37:07Z" - latency: 1.40933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:36:07Z" - latency: 898.321µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 1.210592ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 1.066294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 1.188003ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 1.133184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 1.196268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:30:07Z" - latency: 894.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:29:07Z" - latency: 1.118585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:28:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "76828" uid: d745ff24-10fd-41aa-8062-15c0d7b25ea8 spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-01T00:47:07Z" message: 'load-balancer-api-external: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.215427ms message: 'load-balancer-api-external: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 8.799457ms message: 'load-balancer-api-external: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:35:07Z" - latency: 5.524561ms message: 'load-balancer-api-external: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 8.56469ms message: 'load-balancer-api-external: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:34:07Z" - latency: 3.534066ms message: 'load-balancer-api-external: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 7.971365ms message: 'load-balancer-api-external: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:33:07Z" - latency: 5.373909ms message: 'load-balancer-api-external: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 10.583763ms message: 'load-balancer-api-external: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:32:07Z" - latency: 4.802514ms message: 'load-balancer-api-external: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 7.917876ms message: 'load-balancer-api-external: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:31:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "76829" uid: 997c9fa2-9942-4cca-9589-4dae4fb9a64b spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-01T00:47:07Z" message: 'load-balancer-api-internal: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.42932ms message: 'load-balancer-api-internal: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 8.688218ms message: 'load-balancer-api-internal: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:35:07Z" - latency: 5.906996ms message: 'load-balancer-api-internal: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 8.404149ms message: 'load-balancer-api-internal: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:34:07Z" - latency: 3.440659ms message: 'load-balancer-api-internal: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 7.815094ms message: 'load-balancer-api-internal: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:33:07Z" - latency: 5.345707ms message: 'load-balancer-api-internal: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 10.485546ms message: 'load-balancer-api-internal: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:32:07Z" - latency: 4.790294ms message: 'load-balancer-api-internal: tcp connection to aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 7.845783ms message: 'load-balancer-api-internal: resolved host name aa990e09f045d4706ac45e8ebd866d3b-70580a907f5d765e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:31:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-network-check-target-ip-10-0-137-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "78698" uid: 72a91949-d8aa-4d29-a278-4ff8f2e46854 spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-01T00:48:07Z" message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 853.919µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:37:07Z" - latency: 1.310408ms message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:36:07Z" - latency: 986.727µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 974.561µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 1.331756ms message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 972.571µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 781.456µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 868.355µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:30:07Z" - latency: 1.308287ms message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:29:07Z" - latency: 939.302µs message: 'network-check-target-ip-10-0-137-42: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:28:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-network-check-target-ip-10-0-138-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "78697" uid: dc6651fa-6506-489b-9d26-f15b0934a7d9 spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-01T00:48:07Z" message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.003603ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:37:07Z" - latency: 2.297603ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:36:07Z" - latency: 1.951302ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 2.122798ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 1.752879ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 2.119848ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 2.053408ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 2.144444ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:30:07Z" - latency: 1.703092ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:29:07Z" - latency: 2.083709ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:28:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-network-check-target-ip-10-0-141-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "78699" uid: 00577420-17e0-4fa7-9432-bde0f337aafa spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-01T00:48:07Z" message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.236134ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:37:07Z" - latency: 2.244931ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:36:07Z" - latency: 2.062978ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 2.218029ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 2.273713ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 2.388071ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 2.606688ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 2.249624ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:30:07Z" - latency: 2.218214ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:29:07Z" - latency: 2.049108ms message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:28:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:41:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-42-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-42.ec2.internal uid: cfc66d75-321b-4107-b346-e8bd527d8bdf resourceVersion: "76826" uid: d1a5fbf9-ae2d-4f4e-8b13-6aa13b684a59 spec: sourcePod: network-check-source-65bdbbff45-jfpj5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-01T00:47:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.459µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:35:07Z" - latency: 2.005356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:35:07Z" - latency: 851.568µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:34:07Z" - latency: 1.786572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:34:07Z" - latency: 838.52µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:33:07Z" - latency: 1.77699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:33:07Z" - latency: 859.474µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:32:07Z" - latency: 1.737481ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:32:07Z" - latency: 852.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:31:07Z" - latency: 1.629977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:31:07Z" kind: List metadata: resourceVersion: ""