apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "25244" uid: 1a7d8064-b27d-4909-82da-fdf29b891bfb spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T03:45:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.812µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:45:57Z" - latency: 928.241µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 1.030273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 1.618312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 1.023109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 967.584µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 949.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:39:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "24239" uid: c1772014-ac58-4ac6-b3e1-d12dc5667e8f spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T03:44:57Z" message: 'load-balancer-api-external: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.777055ms message: 'load-balancer-api-external: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 6.485277ms message: 'load-balancer-api-external: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:44:57Z" - latency: 4.612331ms message: 'load-balancer-api-external: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 6.789366ms message: 'load-balancer-api-external: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:43:57Z" - latency: 5.035531ms message: 'load-balancer-api-external: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 6.849029ms message: 'load-balancer-api-external: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:42:57Z" - latency: 3.616732ms message: 'load-balancer-api-external: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 7.415108ms message: 'load-balancer-api-external: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:41:57Z" - latency: 3.754832ms message: 'load-balancer-api-external: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 6.912276ms message: 'load-balancer-api-external: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:40:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "24240" uid: 0f5030b6-3eb2-44d2-becf-8eda5d710073 spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T03:44:57Z" message: 'load-balancer-api-internal: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.730296ms message: 'load-balancer-api-internal: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 6.536594ms message: 'load-balancer-api-internal: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:44:57Z" - latency: 4.820296ms message: 'load-balancer-api-internal: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 6.688811ms message: 'load-balancer-api-internal: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:43:57Z" - latency: 3.736795ms message: 'load-balancer-api-internal: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 6.877307ms message: 'load-balancer-api-internal: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:42:57Z" - latency: 4.787704ms message: 'load-balancer-api-internal: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 7.315759ms message: 'load-balancer-api-internal: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:41:57Z" - latency: 4.946085ms message: 'load-balancer-api-internal: tcp connection to aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 6.830833ms message: 'load-balancer-api-internal: resolved host name aa8e31172e95343219ad30bea02b3658-eb7de7b880ec4e22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:40:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-network-check-target-ip-10-0-134-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "25241" uid: ff89fdb0-0c81-4f67-b19f-89ee3e9daad2 spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T03:45:57Z" message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.13µs message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:45:57Z" - latency: 782.277µs message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 976.261µs message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 865.85µs message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 968.324µs message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 1.135212ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 1.515501ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:39:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-network-check-target-ip-10-0-136-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "25243" uid: 2b67d40e-b051-4691-af67-5d20f4ccd416 spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T03:45:57Z" message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.698364ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:45:57Z" - latency: 2.085366ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 2.380296ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 2.033941ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 2.189615ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 2.402262ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 2.393414ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:39:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-network-check-target-ip-10-0-142-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "25242" uid: 1e6718b6-774a-4d25-9577-a9e6409d35f4 spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T03:45:57Z" message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.136942ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:45:57Z" - latency: 1.912415ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 2.207765ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 2.344817ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 2.090532ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 2.372326ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 2.869453ms message: 'network-check-target-ip-10-0-142-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:39:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-80-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-80.ec2.internal uid: 084ab7ff-d8d4-407e-b50b-21261ca3b89b resourceVersion: "24238" uid: 87c92203-b8d4-4505-8749-7af643d281f8 spec: sourcePod: network-check-source-7cbc45fddc-z8cfh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T03:44:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.246567ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:44:57Z" - latency: 1.689837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:44:57Z" - latency: 890.041µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:43:57Z" - latency: 1.704256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:43:57Z" - latency: 884.939µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:42:57Z" - latency: 1.702068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:42:57Z" - latency: 980.788µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:41:57Z" - latency: 1.768376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:41:57Z" - latency: 790.383µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:40:57Z" - latency: 1.850623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:40:57Z" kind: List metadata: resourceVersion: ""