apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "70344" uid: b3d92671-4437-4605-bee7-f26581ec721c spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T15:06:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.858048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:41:11Z" - latency: 1.274125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:40:11Z" - latency: 1.035405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:39:11Z" - latency: 1.183832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:11Z" - latency: 1.322839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:11Z" - latency: 1.683398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:11Z" - latency: 1.323416ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:11Z" - latency: 1.294907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:11Z" - latency: 1.688805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:11Z" - latency: 946.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "83971" uid: a24e2c20-3372-4de1-b5b6-478f7bfe3437 spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:05:11Z" message: 'load-balancer-api-external: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.324006ms message: 'load-balancer-api-external: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:47:11Z" - latency: 7.447779ms message: 'load-balancer-api-external: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:47:11Z" - latency: 5.514546ms message: 'load-balancer-api-external: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:46:11Z" - latency: 7.909576ms message: 'load-balancer-api-external: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:46:11Z" - latency: 5.171772ms message: 'load-balancer-api-external: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:45:11Z" - latency: 7.198415ms message: 'load-balancer-api-external: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:45:11Z" - latency: 4.916702ms message: 'load-balancer-api-external: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:44:11Z" - latency: 6.803103ms message: 'load-balancer-api-external: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:44:11Z" - latency: 5.285406ms message: 'load-balancer-api-external: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:43:11Z" - latency: 7.345234ms message: 'load-balancer-api-external: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:43:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "83970" uid: 451468b5-5bac-4797-96a9-962a8642a0a7 spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:05:11Z" message: 'load-balancer-api-internal: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.291303ms message: 'load-balancer-api-internal: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:47:11Z" - latency: 7.479289ms message: 'load-balancer-api-internal: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:47:11Z" - latency: 6.25054ms message: 'load-balancer-api-internal: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:46:11Z" - latency: 7.855615ms message: 'load-balancer-api-internal: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:46:11Z" - latency: 4.819615ms message: 'load-balancer-api-internal: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:45:11Z" - latency: 7.283977ms message: 'load-balancer-api-internal: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:45:11Z" - latency: 4.988028ms message: 'load-balancer-api-internal: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:44:11Z" - latency: 6.695046ms message: 'load-balancer-api-internal: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:44:11Z" - latency: 5.577375ms message: 'load-balancer-api-internal: tcp connection to ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:43:11Z" - latency: 7.434811ms message: 'load-balancer-api-internal: resolved host name ac15901a883ba48ec8ecb24fb85e6e2e-babb7de756929901.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:43:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-129-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "70340" uid: bcb33458-8fda-4d44-a5d3-560432e43fc8 spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:06:11Z" message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.342202ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:41:11Z" - latency: 2.14736ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:40:11Z" - latency: 2.230552ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:39:11Z" - latency: 2.237386ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:11Z" - latency: 2.373637ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:11Z" - latency: 2.259728ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:11Z" - latency: 2.221445ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:11Z" - latency: 2.223083ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:11Z" - latency: 2.55803ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:11Z" - latency: 2.035687ms message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-137-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "70341" uid: df910393-d979-4840-86bb-a1925aa5d219 spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:06:11Z" message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.374412ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:41:11Z" - latency: 1.438753ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:40:11Z" - latency: 1.280973ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:39:11Z" - latency: 872.142µs message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:11Z" - latency: 1.223481ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:11Z" - latency: 1.851181ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:11Z" - latency: 1.550241ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:11Z" - latency: 914.85µs message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:11Z" - latency: 1.801474ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:11Z" - latency: 1.059921ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-139-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "70342" uid: a8456bd7-11dc-4144-80eb-70dd8387a41a spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:06:11Z" message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.481406ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:41:11Z" - latency: 2.273137ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:40:11Z" - latency: 2.028318ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:39:11Z" - latency: 1.994772ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:11Z" - latency: 2.208154ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:11Z" - latency: 2.419136ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:11Z" - latency: 2.613875ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:11Z" - latency: 2.741104ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:11Z" - latency: 3.041734ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:11Z" - latency: 2.023211ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:59:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: 2b975639-b1de-4f46-90fa-87ba89ba6c4d resourceVersion: "83969" uid: e5a442df-291a-40f4-b1ab-68ce26e1fddc spec: sourcePod: network-check-source-7d88cb55d8-nt4bv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T15:05:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.439µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:47:11Z" - latency: 1.958801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:47:11Z" - latency: 903.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:46:11Z" - latency: 2.732532ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:46:11Z" - latency: 919.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:45:11Z" - latency: 1.862295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:45:11Z" - latency: 1.155056ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:44:11Z" - latency: 1.86063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:44:11Z" - latency: 918.409µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:43:11Z" - latency: 1.723369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:43:11Z" kind: List metadata: resourceVersion: ""