apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31754" uid: 6a419098-7cff-48aa-8532-75b0aaf62da6 spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T14:35:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.827µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 969.479µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 899.763µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 1.132153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 1.403602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 1.142366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:08Z" - latency: 973.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:08Z" - latency: 1.212275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:08Z" - latency: 996.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:08Z" - latency: 931.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31756" uid: 16f5b746-9bc6-4f79-9798-07904314791e spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T14:34:08Z" message: 'load-balancer-api-external: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.565102ms message: 'load-balancer-api-external: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 8.737754ms message: 'load-balancer-api-external: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:10:08Z" - latency: 4.326746ms message: 'load-balancer-api-external: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 8.657577ms message: 'load-balancer-api-external: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:09:08Z" - latency: 5.374326ms message: 'load-balancer-api-external: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 8.250481ms message: 'load-balancer-api-external: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:08:08Z" - latency: 6.065718ms message: 'load-balancer-api-external: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 9.619133ms message: 'load-balancer-api-external: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:07:08Z" - latency: 4.268677ms message: 'load-balancer-api-external: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 9.424761ms message: 'load-balancer-api-external: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:06:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31755" uid: 9157ffee-ef1c-4f11-b190-1c27cf62fd3c spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T14:34:08Z" message: 'load-balancer-api-internal: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.39756ms message: 'load-balancer-api-internal: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 8.80372ms message: 'load-balancer-api-internal: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:10:08Z" - latency: 3.786592ms message: 'load-balancer-api-internal: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 8.611703ms message: 'load-balancer-api-internal: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:09:08Z" - latency: 5.323693ms message: 'load-balancer-api-internal: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 8.379372ms message: 'load-balancer-api-internal: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:08:08Z" - latency: 6.102328ms message: 'load-balancer-api-internal: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 9.689365ms message: 'load-balancer-api-internal: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:07:08Z" - latency: 5.870562ms message: 'load-balancer-api-internal: tcp connection to acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 9.353108ms message: 'load-balancer-api-internal: resolved host name acde13fdfad1246a2b32627736c53cc4-e89cd257566aeea3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:06:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-129-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31752" uid: 5ecd9027-2ac9-49fd-91a9-e2b7fa600c1b spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T14:35:08Z" message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222573ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 2.269708ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 2.386694ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 2.663395ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 2.217411ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 2.553042ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:08Z" - latency: 1.98607ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:08Z" - latency: 2.376853ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:08Z" - latency: 2.203438ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:08Z" - latency: 2.655865ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-129-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31751" uid: 702cec54-18cf-4923-8182-fc786014308f spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T14:35:08Z" message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.187802ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 2.228848ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 2.007374ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 2.090434ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 2.143814ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 2.539484ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:08Z" - latency: 2.210661ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:08Z" - latency: 2.386272ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:08Z" - latency: 2.029429ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:08Z" - latency: 2.537079ms message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-131-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31750" uid: 8b63b674-8f93-49e0-a3dc-1173269a3cfc spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T14:35:08Z" message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.325µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 996.17µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 1.314341ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 1.033932ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 1.297476ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 718.411µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:08Z" - latency: 1.030873ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:08Z" - latency: 1.629051ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:08Z" - latency: 807.259µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:08Z" - latency: 1.335297ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:28:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: 65bea2e9-13a7-494a-86f7-eab88e0f2d43 resourceVersion: "31753" uid: ae5873aa-44ed-4487-94de-72cadad7c34c spec: sourcePod: network-check-source-8894fc9bd-qttrj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T14:34:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044503ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:10:08Z" - latency: 1.621488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:10:08Z" - latency: 676.54µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:09:08Z" - latency: 1.663831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:09:08Z" - latency: 866.138µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:08:08Z" - latency: 1.59735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:08:08Z" - latency: 954.216µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:07:08Z" - latency: 1.721231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:07:08Z" - latency: 787.519µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:06:08Z" - latency: 1.603404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:06:08Z" kind: List metadata: resourceVersion: ""