apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "72143" uid: f8c296ad-1bf7-4b3d-b530-6b4caa93f170 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:31:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.304µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:12Z" - latency: 972.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:12Z" - latency: 1.070163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:12Z" - latency: 1.171218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:12Z" - latency: 1.369179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:12Z" - latency: 850.819µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:12Z" - latency: 1.248897ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:12Z" - latency: 897.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:12Z" - latency: 862.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:12Z" - latency: 1.203141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:04:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "69384" uid: 425a26d4-8314-40e0-8a6c-6b5a0ea30ab5 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:30:12Z" message: 'load-balancer-api-external: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.335768876s message: 'load-balancer-api-external: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:12Z" - latency: 8.238332ms message: 'load-balancer-api-external: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:12:12Z" - latency: 4.139729ms message: 'load-balancer-api-external: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:12Z" - latency: 8.46688ms message: 'load-balancer-api-external: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:11:12Z" - latency: 4.887289ms message: 'load-balancer-api-external: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:12Z" - latency: 8.384579ms message: 'load-balancer-api-external: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:10:12Z" - latency: 4.262171ms message: 'load-balancer-api-external: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:12Z" - latency: 8.91965ms message: 'load-balancer-api-external: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:09:12Z" - latency: 4.622429ms message: 'load-balancer-api-external: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:12Z" - latency: 7.389359ms message: 'load-balancer-api-external: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:08:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "69385" uid: e6245d45-f337-46de-bb1b-aec463ace7d2 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:30:12Z" message: 'load-balancer-api-internal: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.336293545s message: 'load-balancer-api-internal: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:12Z" - latency: 8.295257ms message: 'load-balancer-api-internal: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:12:12Z" - latency: 4.272862ms message: 'load-balancer-api-internal: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:12Z" - latency: 8.573262ms message: 'load-balancer-api-internal: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:11:12Z" - latency: 4.708836ms message: 'load-balancer-api-internal: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:12Z" - latency: 8.411083ms message: 'load-balancer-api-internal: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:10:12Z" - latency: 4.27034ms message: 'load-balancer-api-internal: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:12Z" - latency: 9.007721ms message: 'load-balancer-api-internal: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:09:12Z" - latency: 4.770449ms message: 'load-balancer-api-internal: tcp connection to a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:12Z" - latency: 7.437841ms message: 'load-balancer-api-internal: resolved host name a9625b2ca139d492684213f5799dca2a-c689789764f3c9f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:08:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-network-check-target-ip-10-0-128-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "72142" uid: 72fc3fc0-1ea0-4541-a17b-64eab5aba876 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:31:12Z" message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.341093ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:12Z" - latency: 2.135904ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:12Z" - latency: 2.324492ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:12Z" - latency: 2.27822ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:12Z" - latency: 2.405428ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:12Z" - latency: 2.214473ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:12Z" - latency: 2.097346ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:12Z" - latency: 2.153127ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:12Z" - latency: 2.391445ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:12Z" - latency: 2.29989ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:04:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:12:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-network-check-target-ip-10-0-131-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "71259" uid: 171e6f61-8922-4bc3-b3c7-228f1a8fd315 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: 10.132.0.4:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-network-check-target-ip-10-0-133-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "72141" uid: 02259ece-cf47-48a8-9786-35db55240795 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:31:12Z" message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133365ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:12Z" - latency: 2.013893ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:12Z" - latency: 2.063036ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:12Z" - latency: 2.414765ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:12Z" - latency: 1.9479ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:12Z" - latency: 1.747822ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:12Z" - latency: 2.403536ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:12Z" - latency: 2.094862ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:12Z" - latency: 2.172286ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:12Z" - latency: 2.423812ms message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:04:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-8.ec2.internal uid: 4e32f8df-a536-4256-8681-3c031d0f4ef6 resourceVersion: "69281" uid: 5245975c-39c4-4638-94ab-f977255246a0 spec: sourcePod: network-check-source-7d88cb55d8-wqszm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:30:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:12Z" - latency: 1.66453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:12:12Z" - latency: 1.077364ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:12Z" - latency: 2.032326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:11:12Z" - latency: 848.978µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:12Z" - latency: 1.790682ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:10:12Z" - latency: 961.142µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:12Z" - latency: 1.990957ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:09:12Z" - latency: 1.015297ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:12Z" - latency: 1.710381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:08:12Z" kind: List metadata: resourceVersion: ""