apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62687" uid: 6817063d-acf0-4387-aa23-bb78e40f2504 spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T12:12:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.794295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 929.852µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 1.141958ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 1.025628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 875.248µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 945.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:42:28Z" - latency: 1.37575ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:41:28Z" - latency: 1.175134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:40:28Z" - latency: 1.119873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:39:28Z" - latency: 903.185µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:38:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62688" uid: 2c6a80b9-5c74-4371-9d7e-4ce127f1ab57 spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T12:11:28Z" message: 'load-balancer-api-external: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.285533ms message: 'load-balancer-api-external: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 7.916481ms message: 'load-balancer-api-external: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:47:28Z" - latency: 5.340659ms message: 'load-balancer-api-external: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 8.570722ms message: 'load-balancer-api-external: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:46:28Z" - latency: 4.091998ms message: 'load-balancer-api-external: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 8.970858ms message: 'load-balancer-api-external: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:45:28Z" - latency: 5.472518ms message: 'load-balancer-api-external: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 9.586082ms message: 'load-balancer-api-external: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:44:28Z" - latency: 4.904048ms message: 'load-balancer-api-external: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 8.703717ms message: 'load-balancer-api-external: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:43:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62689" uid: 31b240b0-7e5e-4648-8153-908c5bd5544a spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T12:11:28Z" message: 'load-balancer-api-internal: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.020018ms message: 'load-balancer-api-internal: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 7.928157ms message: 'load-balancer-api-internal: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:47:28Z" - latency: 5.389159ms message: 'load-balancer-api-internal: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 8.603628ms message: 'load-balancer-api-internal: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:46:28Z" - latency: 5.382649ms message: 'load-balancer-api-internal: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 8.992567ms message: 'load-balancer-api-internal: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:45:28Z" - latency: 5.796755ms message: 'load-balancer-api-internal: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 9.608351ms message: 'load-balancer-api-internal: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:44:28Z" - latency: 5.593897ms message: 'load-balancer-api-internal: tcp connection to a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 8.783063ms message: 'load-balancer-api-internal: resolved host name a998952c3f4dd4f76b613662753a34fe-00884c729f07596b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:43:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-132-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62684" uid: 3befb18c-510d-498f-b053-78c5d6a0a3cb spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T12:12:28Z" message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.467564ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 2.168223ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 2.238751ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 2.242846ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 2.075023ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 2.252052ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:42:28Z" - latency: 2.200958ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:41:28Z" - latency: 2.125211ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:40:28Z" - latency: 2.266157ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:39:28Z" - latency: 2.185736ms message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:38:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-138-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62683" uid: 7e69fc37-fb92-448c-bbcf-95acdc1cd28a spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T12:12:28Z" message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.293473ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 1.501428ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 891.733µs message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 1.483759ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 901.633µs message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 1.16291ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:42:28Z" - latency: 1.213216ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:41:28Z" - latency: 1.199332ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:40:28Z" - latency: 1.702618ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:39:28Z" - latency: 875.236µs message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:38:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-143-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62686" uid: 40fd5fbe-6282-48fd-9647-5f07120e1dbd spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T12:12:28Z" message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.690932ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 2.351129ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 2.254544ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 2.338192ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 2.115683ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 1.992015ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:42:28Z" - latency: 2.088161ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:41:28Z" - latency: 2.530051ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:40:28Z" - latency: 2.509847ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:39:28Z" - latency: 2.115231ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:38:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:05:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-35.ec2.internal uid: 1989ef5e-f8a9-47cb-b056-7f72f4603f9c resourceVersion: "62685" uid: ed31d87e-2452-4e04-8576-0553f8a33ee6 spec: sourcePod: network-check-source-7bc5b6bf85-46s4z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T12:11:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.549µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:47:28Z" - latency: 2.555824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:47:28Z" - latency: 1.039055ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:46:28Z" - latency: 2.11048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:46:28Z" - latency: 1.108522ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:45:28Z" - latency: 2.19493ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:45:28Z" - latency: 1.012365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:44:28Z" - latency: 2.101532ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:44:28Z" - latency: 1.076467ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:43:28Z" - latency: 2.087601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:43:28Z" kind: List metadata: resourceVersion: ""