apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "53364" uid: 83666a91-e656-457c-89db-851da20d5403 spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T21:44:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 998.013µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 1.48567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 1.359677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 1.438011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 886.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:08:13Z" - latency: 1.229938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:07:13Z" - latency: 1.268705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:06:13Z" - latency: 848.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:05:13Z" - latency: 1.144547ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:04:13Z" - latency: 1.190064ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:03:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "54258" uid: 716bc01d-0dc0-4fdf-bc2b-1b807a4105b9 spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T21:43:13Z" message: 'load-balancer-api-external: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.545899ms message: 'load-balancer-api-external: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:13:13Z" - latency: 13.306975ms message: 'load-balancer-api-external: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:13:13Z" - latency: 5.111085ms message: 'load-balancer-api-external: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 9.293896ms message: 'load-balancer-api-external: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:12:13Z" - latency: 4.362304ms message: 'load-balancer-api-external: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 6.97983ms message: 'load-balancer-api-external: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:11:13Z" - latency: 4.429035ms message: 'load-balancer-api-external: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 7.592018ms message: 'load-balancer-api-external: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:10:13Z" - latency: 3.973425ms message: 'load-balancer-api-external: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 9.145558ms message: 'load-balancer-api-external: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:09:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "54259" uid: dbce0de7-a9e8-4aca-8a4f-947fbc41b119 spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T21:43:13Z" message: 'load-balancer-api-internal: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.710197ms message: 'load-balancer-api-internal: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:13:13Z" - latency: 13.330194ms message: 'load-balancer-api-internal: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:13:13Z" - latency: 5.110161ms message: 'load-balancer-api-internal: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 9.325596ms message: 'load-balancer-api-internal: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:12:13Z" - latency: 3.884407ms message: 'load-balancer-api-internal: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 6.854185ms message: 'load-balancer-api-internal: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:11:13Z" - latency: 5.278052ms message: 'load-balancer-api-internal: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 7.661083ms message: 'load-balancer-api-internal: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:10:13Z" - latency: 3.964817ms message: 'load-balancer-api-internal: tcp connection to a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 9.040205ms message: 'load-balancer-api-internal: resolved host name a4d3147a7cc384c0b8cc5ef9435c6047-d77f3a9807353bc6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:09:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-network-check-target-ip-10-0-130-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "53363" uid: 8cd367b7-492c-4525-8a2c-18a712420e1d spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T21:44:13Z" message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.407105ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 2.147203ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 2.422288ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 2.357814ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 2.3037ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:08:13Z" - latency: 2.155741ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:07:13Z" - latency: 2.1864ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:06:13Z" - latency: 2.395919ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:05:13Z" - latency: 2.29604ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:04:13Z" - latency: 2.654662ms message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:03:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-network-check-target-ip-10-0-131-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "53362" uid: be180259-caf6-40e2-9d07-27e0122ab695 spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T21:44:13Z" message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.852145ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 2.051205ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 2.06867ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 1.873133ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 2.029705ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:08:13Z" - latency: 2.048802ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:07:13Z" - latency: 2.064893ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:06:13Z" - latency: 2.147366ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:05:13Z" - latency: 2.072334ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:04:13Z" - latency: 2.60748ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:03:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-network-check-target-ip-10-0-136-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "53361" uid: 2e7a4d76-26f0-457f-bee0-d7e794e1a789 spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T21:44:13Z" message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.373µs message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 851.14µs message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 896.501µs message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 1.519706ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 1.027184ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:08:13Z" - latency: 908.628µs message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:07:13Z" - latency: 914.121µs message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:06:13Z" - latency: 1.674227ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:05:13Z" - latency: 962.767µs message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:04:13Z" - latency: 1.039512ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:03:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:37:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-11-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-11.ec2.internal uid: 752b2739-9dfb-4314-9374-a44b0172422a resourceVersion: "54257" uid: 715978d7-3a8c-4025-936a-77d2557fb3ec spec: sourcePod: network-check-source-989f8b8dc-zp4tr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T21:43:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.225µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:13:13Z" - latency: 2.13684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:13:13Z" - latency: 941.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:12:13Z" - latency: 2.242174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:12:13Z" - latency: 958.684µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:11:13Z" - latency: 2.019492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:11:13Z" - latency: 1.021325ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:10:13Z" - latency: 1.806249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:10:13Z" - latency: 1.029554ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:09:13Z" - latency: 2.390813ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:09:13Z" kind: List metadata: resourceVersion: ""