apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61695" uid: 603fb238-24e3-4d1a-99ba-0f524b32d350 spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T22:10:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 1.0749ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 1.096239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 1.733979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 1.072445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 862.33µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:40:08Z" - latency: 963.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:39:08Z" - latency: 979.006µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:38:08Z" - latency: 942.176µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:08Z" - latency: 789.84µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61697" uid: cce3c0cd-2c61-4a68-8924-3fec5bdd6624 spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T22:09:08Z" message: 'load-balancer-api-external: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.912276ms message: 'load-balancer-api-external: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 8.714503ms message: 'load-balancer-api-external: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:45:08Z" - latency: 3.242159ms message: 'load-balancer-api-external: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 7.65434ms message: 'load-balancer-api-external: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:44:08Z" - latency: 5.370645ms message: 'load-balancer-api-external: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 7.503969ms message: 'load-balancer-api-external: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:43:08Z" - latency: 5.073519ms message: 'load-balancer-api-external: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 9.641983ms message: 'load-balancer-api-external: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:42:08Z" - latency: 5.823403ms message: 'load-balancer-api-external: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 7.719401ms message: 'load-balancer-api-external: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:41:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61696" uid: 8f7b74e1-4bcc-49c6-bf1c-60264f9f6b36 spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T22:09:08Z" message: 'load-balancer-api-internal: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.927333ms message: 'load-balancer-api-internal: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 8.662325ms message: 'load-balancer-api-internal: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:45:08Z" - latency: 3.228569ms message: 'load-balancer-api-internal: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 7.612467ms message: 'load-balancer-api-internal: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:44:08Z" - latency: 5.386584ms message: 'load-balancer-api-internal: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 7.575129ms message: 'load-balancer-api-internal: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:43:08Z" - latency: 3.806853ms message: 'load-balancer-api-internal: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 9.566926ms message: 'load-balancer-api-internal: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:42:08Z" - latency: 5.769198ms message: 'load-balancer-api-internal: tcp connection to af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 7.694075ms message: 'load-balancer-api-internal: resolved host name af0223a2986ef4d53bff0b736dbf4e45-a746fd2aaac09f7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:41:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-network-check-target-ip-10-0-132-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61690" uid: 7ce77b38-1b91-4b24-a89e-a0cb48ae60bd spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T22:10:08Z" message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 829.955µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 928.076µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 912.572µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 908.627µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 1.30474ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 877.776µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:40:08Z" - latency: 736.974µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:39:08Z" - latency: 789.783µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:38:08Z" - latency: 776.546µs message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:08Z" - latency: 1.316979ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-network-check-target-ip-10-0-133-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61694" uid: 45a172e2-93ec-425b-9f66-114add9c6c34 spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T22:10:08Z" message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.536434ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 2.323498ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 2.458833ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 2.413401ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 2.201546ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 2.460108ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:40:08Z" - latency: 2.271637ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:39:08Z" - latency: 2.902591ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:38:08Z" - latency: 2.154742ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:08Z" - latency: 2.477497ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-network-check-target-ip-10-0-143-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61691" uid: d1ea1b61-6d46-41dc-9fb9-5b0e8e606df0 spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T22:10:08Z" message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.149844ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 2.243987ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 2.295856ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 2.215554ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 2.244412ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 2.33154ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:40:08Z" - latency: 1.773767ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:39:08Z" - latency: 2.21612ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:38:08Z" - latency: 2.123505ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:08Z" - latency: 2.073544ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:03:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-128-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-128.ec2.internal uid: d9e277b3-01c0-4c4a-919f-f070824b9f40 resourceVersion: "61693" uid: 4e52e553-6130-4ef8-bc77-da57af2be191 spec: sourcePod: network-check-source-869dcfcdcd-gwtpb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T22:09:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.005µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:45:08Z" - latency: 2.081134ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:45:08Z" - latency: 840.318µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:44:08Z" - latency: 1.757486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:44:08Z" - latency: 1.013147ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:43:08Z" - latency: 1.660558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:43:08Z" - latency: 916.646µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:42:08Z" - latency: 2.405708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:42:08Z" - latency: 843.515µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:41:08Z" - latency: 1.781767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:41:08Z" kind: List metadata: resourceVersion: ""