apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "23748" uid: e28f5d4c-5a7a-4602-9c68-585be7290963 spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T18:40:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.33066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:54:40Z" - latency: 1.074382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:53:40Z" - latency: 1.402498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:52:40Z" - latency: 931.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 1.137909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 997.649µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 1.002473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 1.004851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 977.888µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:46:40Z" - latency: 1.037728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:45:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "22338" uid: 45892972-b821-46da-974a-c75082860fcc spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:39:40Z" message: 'load-balancer-api-external: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.921257ms message: 'load-balancer-api-external: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 7.782875ms message: 'load-balancer-api-external: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:51:40Z" - latency: 6.336067ms message: 'load-balancer-api-external: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 9.779051ms message: 'load-balancer-api-external: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:50:40Z" - latency: 4.88916ms message: 'load-balancer-api-external: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 8.938572ms message: 'load-balancer-api-external: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:49:40Z" - latency: 4.099757ms message: 'load-balancer-api-external: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 9.754669ms message: 'load-balancer-api-external: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:48:40Z" - latency: 5.800557ms message: 'load-balancer-api-external: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 8.759988ms message: 'load-balancer-api-external: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:47:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "22337" uid: 56494333-ec9f-4452-a5ee-00a7b5616d0a spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:39:40Z" message: 'load-balancer-api-internal: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.881891ms message: 'load-balancer-api-internal: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 7.819463ms message: 'load-balancer-api-internal: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:51:40Z" - latency: 5.026874ms message: 'load-balancer-api-internal: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 9.733767ms message: 'load-balancer-api-internal: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:50:40Z" - latency: 4.941289ms message: 'load-balancer-api-internal: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 8.840687ms message: 'load-balancer-api-internal: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:49:40Z" - latency: 3.8163ms message: 'load-balancer-api-internal: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 9.537071ms message: 'load-balancer-api-internal: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:48:40Z" - latency: 5.845233ms message: 'load-balancer-api-internal: tcp connection to af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 8.701299ms message: 'load-balancer-api-internal: resolved host name af27b5abf781045c693343efb0015547-7e83ff8c11c1e09a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:47:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-network-check-target-ip-10-0-130-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "23747" uid: e6ca6062-c531-4d84-b1f4-5cae9a0c4916 spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:40:40Z" message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.739405ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:54:40Z" - latency: 2.435904ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:53:40Z" - latency: 2.767928ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:52:40Z" - latency: 2.5683ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 2.520488ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 2.431753ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 1.84211ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 2.556725ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 2.512804ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:46:40Z" - latency: 3.21234ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:45:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-network-check-target-ip-10-0-134-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "23746" uid: 8babda76-f4d8-4a27-b0e9-57c1f715b785 spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:40:40Z" message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.449945ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:54:40Z" - latency: 1.20106ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:53:40Z" - latency: 1.51554ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:52:40Z" - latency: 945.452µs message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 954.972µs message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 1.088171ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 968.428µs message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 893.075µs message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 1.587207ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:46:40Z" - latency: 954.74µs message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:45:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-network-check-target-ip-10-0-138-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "23745" uid: ac787faf-da8a-48d6-bdd9-2d806ad875d2 spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:40:40Z" message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.386131ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:54:40Z" - latency: 2.446455ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:53:40Z" - latency: 2.871341ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:52:40Z" - latency: 2.183868ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 2.301374ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 2.296303ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 2.44385ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 2.488875ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 2.397998ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:46:40Z" - latency: 2.319624ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:45:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-202.ec2.internal uid: 3b0bb4c0-29a4-411f-b258-461d4678f158 resourceVersion: "22335" uid: c7b0fb58-c0e4-4322-af02-a2b180bdd8dd spec: sourcePod: network-check-source-7cbc45fddc-6fv49 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T18:39:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.174µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:51:40Z" - latency: 1.774927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:51:40Z" - latency: 857.012µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:50:40Z" - latency: 1.779574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:50:40Z" - latency: 1.32989ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:49:40Z" - latency: 1.906711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:49:40Z" - latency: 1.00895ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:48:40Z" - latency: 2.591168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:48:40Z" - latency: 1.639094ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:47:40Z" - latency: 1.958469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:47:40Z" kind: List metadata: resourceVersion: ""