apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "25892" uid: 7db6e516-234d-4c54-b2d1-ef9e71e06622 spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T21:26:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.795µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 960.288µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 998.417µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 1.177593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:44:40Z" - latency: 871.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:43:40Z" - latency: 1.002246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:42:40Z" - latency: 1.208525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:41:40Z" - latency: 927.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:40:40Z" - latency: 899.312µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:39:40Z" - latency: 935.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:38:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "26840" uid: 1d55f7e5-da21-4b98-8d1a-5ff01798c2a7 spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T21:25:40Z" message: 'load-balancer-api-external: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.110228ms message: 'load-balancer-api-external: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:49:40Z" - latency: 8.338307ms message: 'load-balancer-api-external: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:49:40Z" - latency: 5.105746ms message: 'load-balancer-api-external: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:48:40Z" - latency: 8.267318ms message: 'load-balancer-api-external: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:48:40Z" - latency: 4.951487ms message: 'load-balancer-api-external: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 7.805218ms message: 'load-balancer-api-external: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:47:40Z" - latency: 4.263127ms message: 'load-balancer-api-external: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 8.351464ms message: 'load-balancer-api-external: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:46:40Z" - latency: 4.859952ms message: 'load-balancer-api-external: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 6.594408ms message: 'load-balancer-api-external: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:45:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "26839" uid: 3a9c2ca7-7585-415b-b22a-a1a3404411b0 spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T21:25:40Z" message: 'load-balancer-api-internal: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.716672ms message: 'load-balancer-api-internal: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:49:40Z" - latency: 8.426051ms message: 'load-balancer-api-internal: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:49:40Z" - latency: 5.122561ms message: 'load-balancer-api-internal: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:48:40Z" - latency: 8.323734ms message: 'load-balancer-api-internal: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:48:40Z" - latency: 4.925883ms message: 'load-balancer-api-internal: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 7.682561ms message: 'load-balancer-api-internal: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:47:40Z" - latency: 4.30618ms message: 'load-balancer-api-internal: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 8.294537ms message: 'load-balancer-api-internal: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:46:40Z" - latency: 4.873466ms message: 'load-balancer-api-internal: tcp connection to a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 6.642583ms message: 'load-balancer-api-internal: resolved host name a08a505f1ebcb456fb5e338eefbc1e28-9d3503e2f7a3a6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:45:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-network-check-target-ip-10-0-136-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "25891" uid: 640d24a4-50b5-4dff-8e7e-51d7d6c90416 spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:26:40Z" message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.329133ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 2.262277ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 1.859256ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 2.262464ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:44:40Z" - latency: 2.080486ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:43:40Z" - latency: 2.03406ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:42:40Z" - latency: 2.621054ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:41:40Z" - latency: 2.202754ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:40:40Z" - latency: 2.51473ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:39:40Z" - latency: 2.340352ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:38:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-network-check-target-ip-10-0-136-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "25890" uid: 2db56fbb-6738-48d3-a53e-57726abd0a4e spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:26:40Z" message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.367367ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 2.298229ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 2.169493ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 2.283358ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:44:40Z" - latency: 2.298595ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:43:40Z" - latency: 2.232517ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:42:40Z" - latency: 2.656199ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:41:40Z" - latency: 2.702174ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:40:40Z" - latency: 2.252933ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:39:40Z" - latency: 2.790326ms message: 'network-check-target-ip-10-0-136-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:38:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-network-check-target-ip-10-0-138-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "25889" uid: 55ad8076-064e-4ecc-b9b0-10de0aeda0ff spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:26:40Z" message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 820.298µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 851.098µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 828.935µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 1.295625ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:44:40Z" - latency: 732.879µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:43:40Z" - latency: 896.361µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:42:40Z" - latency: 853.868µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:41:40Z" - latency: 960.276µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:40:40Z" - latency: 1.099941ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:39:40Z" - latency: 931.081µs message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:38:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-234.ec2.internal uid: 4d0b63df-4d48-44d3-be8f-1cd0c0fb3381 resourceVersion: "26838" uid: ee43919d-6884-4c61-8384-5ff7679d4595 spec: sourcePod: network-check-source-7d88cb55d8-mq8gd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T21:25:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.763µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:49:40Z" - latency: 2.118191ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:49:40Z" - latency: 754.701µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:48:40Z" - latency: 1.666468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:48:40Z" - latency: 845.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:47:40Z" - latency: 1.662659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:47:40Z" - latency: 703.361µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:46:40Z" - latency: 1.539519ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:46:40Z" - latency: 1.143941ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:45:40Z" - latency: 1.677627ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:45:40Z" kind: List metadata: resourceVersion: ""