apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55543" uid: c7dcb1ea-7974-40ac-8050-d7fe4fecf5b3 spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T22:20:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.424225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 1.293803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 1.30447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 844.521µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 1.034465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 1.458025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:50:21Z" - latency: 1.062546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:49:21Z" - latency: 1.41508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:48:21Z" - latency: 1.123498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:47:21Z" - latency: 1.090082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:46:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55544" uid: d85d6321-6775-4c80-b209-3b783c2da482 spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T22:19:21Z" message: 'load-balancer-api-external: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.616323ms message: 'load-balancer-api-external: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 7.485219ms message: 'load-balancer-api-external: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:55:21Z" - latency: 4.290036ms message: 'load-balancer-api-external: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 6.70469ms message: 'load-balancer-api-external: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:54:21Z" - latency: 5.985397ms message: 'load-balancer-api-external: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 9.352921ms message: 'load-balancer-api-external: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:53:21Z" - latency: 5.28794ms message: 'load-balancer-api-external: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 8.429553ms message: 'load-balancer-api-external: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:52:21Z" - latency: 5.330455ms message: 'load-balancer-api-external: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 7.600931ms message: 'load-balancer-api-external: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55545" uid: 630238d9-ed34-4e1b-abd1-d043fb0b1ba6 spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T22:19:21Z" message: 'load-balancer-api-internal: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.66905ms message: 'load-balancer-api-internal: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 7.42883ms message: 'load-balancer-api-internal: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:55:21Z" - latency: 4.269379ms message: 'load-balancer-api-internal: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 6.653394ms message: 'load-balancer-api-internal: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:54:21Z" - latency: 5.965998ms message: 'load-balancer-api-internal: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 9.410015ms message: 'load-balancer-api-internal: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:53:21Z" - latency: 5.234008ms message: 'load-balancer-api-internal: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 8.514824ms message: 'load-balancer-api-internal: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:52:21Z" - latency: 5.294545ms message: 'load-balancer-api-internal: tcp connection to af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 7.656673ms message: 'load-balancer-api-internal: resolved host name af117932e60d346f99d060911a936768-0b142891d121b604.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T22:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-network-check-target-ip-10-0-131-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55540" uid: 7676fc8e-760e-409b-bb36-ffd35cd88435 spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T22:20:21Z" message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.038084ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 947.26µs message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 912.665µs message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 1.109735ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 1.022636ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 1.12421ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:50:21Z" - latency: 1.011027ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:49:21Z" - latency: 1.06212ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:48:21Z" - latency: 908.177µs message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:47:21Z" - latency: 1.382459ms message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:46:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-network-check-target-ip-10-0-133-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55539" uid: 7b273889-c61f-4adc-b19f-d5614ddf9370 spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T22:20:21Z" message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.217069ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 2.298413ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 2.286192ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 2.096094ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 2.078963ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 2.23742ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:50:21Z" - latency: 2.172647ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:49:21Z" - latency: 2.493947ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:48:21Z" - latency: 2.168452ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:47:21Z" - latency: 2.143917ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:46:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-network-check-target-ip-10-0-143-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55541" uid: dc547e2d-6e9e-4fdc-8678-7e1111fe19fa spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T22:20:21Z" message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.310106ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 2.030338ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 2.08423ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 2.051749ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 2.009425ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 2.018912ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:50:21Z" - latency: 2.011377ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:49:21Z" - latency: 2.094103ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:48:21Z" - latency: 1.961641ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:47:21Z" - latency: 2.114399ms message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:46:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T22:13:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-45.ec2.internal uid: 707d5a6d-5d0e-4d57-89c1-4507c331aaa5 resourceVersion: "55542" uid: bb433bad-13f0-4262-9f60-515b5c8ed5b2 spec: sourcePod: network-check-source-869dcfcdcd-8vrr2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T22:19:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.239µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:55:21Z" - latency: 1.880784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T22:55:21Z" - latency: 1.169956ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:54:21Z" - latency: 1.677486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T22:54:21Z" - latency: 1.314639ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:53:21Z" - latency: 1.914294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T22:53:21Z" - latency: 1.405667ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:52:21Z" - latency: 1.811909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T22:52:21Z" - latency: 1.041327ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T22:51:21Z" - latency: 2.008458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T22:51:21Z" kind: List metadata: resourceVersion: ""