apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "22347" uid: e1f3c1e0-f026-497e-9504-b53f9d954fbe spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T22:01:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:35Z" - latency: 1.119748ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:35Z" - latency: 970.857µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:35Z" - latency: 1.016031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 1.866856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 1.105607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 999.756µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 973.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 1.271517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:35Z" - latency: 1.168297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "20838" uid: d0bebe60-d43c-43a1-bf5d-512af0491238 spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T22:00:35Z" message: 'load-balancer-api-external: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.56793ms message: 'load-balancer-api-external: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 13.192335ms message: 'load-balancer-api-external: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:12:35Z" - latency: 4.303993ms message: 'load-balancer-api-external: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 11.379943ms message: 'load-balancer-api-external: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:11:35Z" - latency: 5.237134ms message: 'load-balancer-api-external: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 11.483341ms message: 'load-balancer-api-external: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:10:35Z" - latency: 5.23837ms message: 'load-balancer-api-external: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 8.674273ms message: 'load-balancer-api-external: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:09:35Z" - latency: 5.464499ms message: 'load-balancer-api-external: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 9.84563ms message: 'load-balancer-api-external: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:08:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "20839" uid: 75ba7c44-bef7-40c0-a0df-49cf0952beb9 spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T22:00:35Z" message: 'load-balancer-api-internal: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.559361ms message: 'load-balancer-api-internal: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 13.226473ms message: 'load-balancer-api-internal: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:12:35Z" - latency: 4.26557ms message: 'load-balancer-api-internal: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 11.389667ms message: 'load-balancer-api-internal: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:11:35Z" - latency: 5.524172ms message: 'load-balancer-api-internal: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 11.517947ms message: 'load-balancer-api-internal: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:10:35Z" - latency: 5.218174ms message: 'load-balancer-api-internal: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 8.73211ms message: 'load-balancer-api-internal: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:09:35Z" - latency: 5.454954ms message: 'load-balancer-api-internal: tcp connection to a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 9.814255ms message: 'load-balancer-api-internal: resolved host name a7d0c24b888ad427bbffc1bf16e1bde5-668c73d646848c03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:08:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-network-check-target-ip-10-0-137-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "22344" uid: ba0cee4f-da10-41f4-9887-735d4d71711b spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:01:35Z" message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270279ms message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:35Z" - latency: 884.002µs message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:35Z" - latency: 791.562µs message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:35Z" - latency: 942.813µs message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 1.213152ms message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 899.442µs message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 957.544µs message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 967.71µs message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 1.45891ms message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:35Z" - latency: 1.180311ms message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-network-check-target-ip-10-0-137-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "22346" uid: 765ba27d-9009-407e-8c6a-de60cd39bfaa spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:01:35Z" message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.084245ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:35Z" - latency: 2.12753ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:35Z" - latency: 2.253565ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:35Z" - latency: 2.019643ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 2.120016ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 1.916442ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 1.897745ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 2.038512ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 2.116676ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:35Z" - latency: 1.951151ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-network-check-target-ip-10-0-139-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "22345" uid: 05650f29-0b6a-4192-8220-844e6bc6b814 spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:01:35Z" message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.15326ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:35Z" - latency: 1.756992ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:35Z" - latency: 1.983425ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:35Z" - latency: 1.646045ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 2.463318ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 1.881841ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 1.84201ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 2.088658ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 2.051335ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:35Z" - latency: 2.019139ms message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-177.ec2.internal uid: a0947177-163d-411c-b396-34eaeed4c841 resourceVersion: "20837" uid: 97f060ee-ed3f-418e-a0f7-07d4ad111e61 spec: sourcePod: network-check-source-7bc5b6bf85-sbs8l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T22:00:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 796.736µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:35Z" - latency: 1.744489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:12:35Z" - latency: 987.565µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:35Z" - latency: 1.938568ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:11:35Z" - latency: 686.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:35Z" - latency: 1.729343ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:10:35Z" - latency: 1.046468ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:35Z" - latency: 1.893514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:09:35Z" - latency: 809.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:35Z" - latency: 2.465094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:08:35Z" kind: List metadata: resourceVersion: ""