apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "24125" uid: d46f856b-6da6-45e6-bb04-25e19dd05f8f spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T21:08:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.229684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:08:49Z" - latency: 1.067435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:07:49Z" - latency: 923.007µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:06:49Z" - latency: 870.198µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:05:49Z" - latency: 1.019722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:04:49Z" - latency: 1.181186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:03:49Z" - latency: 1.0218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:02:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "28360" uid: d6ed60e4-796d-4e56-84f9-d58c3182fbef spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T21:07:49Z" message: 'load-balancer-api-external: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.22838ms message: 'load-balancer-api-external: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:49Z" - latency: 9.201147ms message: 'load-balancer-api-external: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:13:49Z" - latency: 4.418913ms message: 'load-balancer-api-external: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:12:49Z" - latency: 8.265297ms message: 'load-balancer-api-external: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:12:49Z" - latency: 4.171981ms message: 'load-balancer-api-external: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:11:49Z" - latency: 8.133465ms message: 'load-balancer-api-external: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:11:49Z" - latency: 3.98861ms message: 'load-balancer-api-external: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:10:49Z" - latency: 8.293055ms message: 'load-balancer-api-external: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:10:49Z" - latency: 3.382671ms message: 'load-balancer-api-external: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:09:49Z" - latency: 8.539519ms message: 'load-balancer-api-external: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:09:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "28359" uid: 5c7f8302-e2ca-4ef4-a6af-4991129a11f9 spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T21:07:49Z" message: 'load-balancer-api-internal: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.505383ms message: 'load-balancer-api-internal: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:49Z" - latency: 9.284518ms message: 'load-balancer-api-internal: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:13:49Z" - latency: 4.160778ms message: 'load-balancer-api-internal: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:12:49Z" - latency: 8.187244ms message: 'load-balancer-api-internal: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:12:49Z" - latency: 3.555956ms message: 'load-balancer-api-internal: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:11:49Z" - latency: 8.072674ms message: 'load-balancer-api-internal: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:11:49Z" - latency: 4.00342ms message: 'load-balancer-api-internal: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:10:49Z" - latency: 8.197108ms message: 'load-balancer-api-internal: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:10:49Z" - latency: 3.351212ms message: 'load-balancer-api-internal: tcp connection to a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:09:49Z" - latency: 8.595043ms message: 'load-balancer-api-internal: resolved host name a90276aa583294f3bb79b51c87e569a8-c0e70d89714c55b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:09:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-130-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "24123" uid: d3fd6f33-1172-4e24-98f6-a575cd38f54d spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T21:08:49Z" message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.871421ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:08:49Z" - latency: 2.559663ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:07:49Z" - latency: 2.127529ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:06:49Z" - latency: 1.901197ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:05:49Z" - latency: 1.904383ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:04:49Z" - latency: 1.874426ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:03:49Z" - latency: 1.990744ms message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:02:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-134-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "24124" uid: 68b1cba8-770f-4a9f-98a0-adcb9ebe1ce8 spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T21:08:49Z" message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.454942ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:08:49Z" - latency: 2.343808ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:07:49Z" - latency: 2.531821ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:06:49Z" - latency: 2.239064ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:05:49Z" - latency: 2.269903ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:04:49Z" - latency: 2.311813ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:03:49Z" - latency: 2.244382ms message: 'network-check-target-ip-10-0-134-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:02:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-135-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "24122" uid: f06b1a8e-faf8-4789-a3dd-95fe15e971ca spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T21:08:49Z" message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.811µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:08:49Z" - latency: 1.155869ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:07:49Z" - latency: 977.855µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:06:49Z" - latency: 1.442284ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:05:49Z" - latency: 853.599µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:04:49Z" - latency: 1.39276ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:03:49Z" - latency: 1.19182ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:02:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:01:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: 6942b628-c624-4b31-97e9-dae6b221eb50 resourceVersion: "28358" uid: b0980333-5913-4199-a005-02c285f6edfc spec: sourcePod: network-check-source-dbd9cf844-k2trv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T21:07:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 723.133µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:49Z" - latency: 1.685403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:13:49Z" - latency: 831.7µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:12:49Z" - latency: 1.643201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:12:49Z" - latency: 965.05µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:11:49Z" - latency: 1.9482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:11:49Z" - latency: 810.296µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:10:49Z" - latency: 1.854113ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:10:49Z" - latency: 888.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:09:49Z" - latency: 1.963179ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:09:49Z" kind: List metadata: resourceVersion: ""