apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "52973" uid: 994dcc49-c2a7-47d0-bb09-89bc00937215 spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T00:14:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:42:21Z" - latency: 961.444µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:41:21Z" - latency: 890.325µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:40:21Z" - latency: 1.156959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:39:21Z" - latency: 1.192286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:38:21Z" - latency: 1.38314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 768.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 891.09µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 1.076536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 981.793µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "47609" uid: 4d7714b9-1a02-4c9e-8d5d-7822d8093523 spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T00:13:21Z" message: 'load-balancer-api-external: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.379198ms message: 'load-balancer-api-external: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 8.078937ms message: 'load-balancer-api-external: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:37:21Z" - latency: 5.862015ms message: 'load-balancer-api-external: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 7.000343ms message: 'load-balancer-api-external: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:36:21Z" - latency: 6.904155ms message: 'load-balancer-api-external: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 6.802159ms message: 'load-balancer-api-external: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:35:21Z" - latency: 3.34006ms message: 'load-balancer-api-external: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 6.675571ms message: 'load-balancer-api-external: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:34:21Z" - latency: 5.574759ms message: 'load-balancer-api-external: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - latency: 7.082462ms message: 'load-balancer-api-external: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "47608" uid: 335e46e8-2243-4201-81b7-0befef85dcd4 spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T00:13:21Z" message: 'load-balancer-api-internal: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.411163ms message: 'load-balancer-api-internal: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 8.143277ms message: 'load-balancer-api-internal: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:37:21Z" - latency: 5.929633ms message: 'load-balancer-api-internal: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 7.026644ms message: 'load-balancer-api-internal: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:36:21Z" - latency: 6.93932ms message: 'load-balancer-api-internal: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 6.864821ms message: 'load-balancer-api-internal: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:35:21Z" - latency: 3.310179ms message: 'load-balancer-api-internal: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 6.695889ms message: 'load-balancer-api-internal: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:34:21Z" - latency: 5.642421ms message: 'load-balancer-api-internal: tcp connection to a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - latency: 6.998752ms message: 'load-balancer-api-internal: resolved host name a9689e8961400496e84af0c932113374-aa1dc942a330c70d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T00:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-137-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "52970" uid: b21e598e-e51b-469d-a27b-c460aa7d9bab spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T00:14:21Z" message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108767ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:42:21Z" - latency: 2.168475ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:41:21Z" - latency: 1.786986ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:40:21Z" - latency: 1.977795ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:39:21Z" - latency: 2.344879ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:38:21Z" - latency: 2.170895ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 2.04448ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 2.201337ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 2.195745ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 2.314948ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-138-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "52969" uid: 60ec65f5-fff5-4b68-b857-a1ef34def3e5 spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T00:14:21Z" message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.943µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:42:21Z" - latency: 861.345µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:41:21Z" - latency: 840.632µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:40:21Z" - latency: 853.543µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:39:21Z" - latency: 841.236µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:38:21Z" - latency: 1.455991ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 1.221899ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 925.209µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 812.714µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 860.871µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-139-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "52971" uid: 8db927cf-6737-4f13-8c2a-83f66e59775f spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T00:14:21Z" message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.782656ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:42:21Z" - latency: 1.800434ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:41:21Z" - latency: 1.734684ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:40:21Z" - latency: 1.785602ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:39:21Z" - latency: 1.783572ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:38:21Z" - latency: 2.057364ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 1.705903ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 1.889518ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 1.792607ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 1.946524ms message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T00:07:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: c63995c6-8284-4385-9c89-09b88fe751c7 resourceVersion: "47607" uid: 15e4b3f4-faf0-46f1-a0dd-e5b73314d5c7 spec: sourcePod: network-check-source-dbd9cf844-8krf9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T00:13:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.116µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:37:21Z" - latency: 2.167563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T00:37:21Z" - latency: 759.245µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:36:21Z" - latency: 1.601231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T00:36:21Z" - latency: 882.175µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:35:21Z" - latency: 2.000205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T00:35:21Z" - latency: 812.14µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:34:21Z" - latency: 1.717356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T00:34:21Z" - latency: 705.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T00:33:21Z" - latency: 2.142505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T00:33:21Z" kind: List metadata: resourceVersion: ""