apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "27769" uid: 5f4c838b-a0c3-4067-bce9-6c87c1e15c13 spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T20:56:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 774.457µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:03:54Z" - latency: 861.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:02:54Z" - latency: 775.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 1.171208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 903.364µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 887.962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 841.757µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 893.539µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:56:54Z" - latency: 1.342127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:55:54Z" - latency: 847.869µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "26561" uid: f5c3a414-905a-496a-8b96-dad1cb8fe697 spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T20:55:54Z" message: 'load-balancer-api-external: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.42212ms message: 'load-balancer-api-external: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 6.34604ms message: 'load-balancer-api-external: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T21:01:54Z" - latency: 4.004442ms message: 'load-balancer-api-external: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 6.386394ms message: 'load-balancer-api-external: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T21:00:54Z" - latency: 4.150897ms message: 'load-balancer-api-external: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 17.128561ms message: 'load-balancer-api-external: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T20:59:54Z" - latency: 4.439022ms message: 'load-balancer-api-external: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 6.862382ms message: 'load-balancer-api-external: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T20:58:54Z" - latency: 4.392107ms message: 'load-balancer-api-external: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 5.589484ms message: 'load-balancer-api-external: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T20:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "26562" uid: 91f2f927-2b7b-4b9c-a6ed-3a8ba4323a91 spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T20:55:54Z" message: 'load-balancer-api-internal: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.64166ms message: 'load-balancer-api-internal: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 6.405209ms message: 'load-balancer-api-internal: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T21:01:54Z" - latency: 3.948438ms message: 'load-balancer-api-internal: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 6.274361ms message: 'load-balancer-api-internal: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T21:00:54Z" - latency: 4.191197ms message: 'load-balancer-api-internal: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 17.032254ms message: 'load-balancer-api-internal: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T20:59:54Z" - latency: 4.500753ms message: 'load-balancer-api-internal: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 6.892499ms message: 'load-balancer-api-internal: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T20:58:54Z" - latency: 4.462896ms message: 'load-balancer-api-internal: tcp connection to aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 5.540831ms message: 'load-balancer-api-internal: resolved host name aa3d4f826af064136b9c4bb5337cfaf8-a595c5d6c5780cb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T20:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-network-check-target-ip-10-0-137-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "27767" uid: 7a697925-d9cc-492e-b8be-20000240b5da spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T20:56:54Z" message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.403294ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:03:54Z" - latency: 2.227696ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:02:54Z" - latency: 1.830716ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 2.02521ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 2.099828ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 2.382805ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 1.847723ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 2.195287ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:56:54Z" - latency: 2.272837ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:55:54Z" - latency: 2.113899ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-network-check-target-ip-10-0-137-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "27766" uid: 37c8b25c-b776-4907-a7fa-30f164ef6022 spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T20:56:54Z" message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088225ms message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:03:54Z" - latency: 807.191µs message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:02:54Z" - latency: 1.295089ms message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 626.848µs message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 852.202µs message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 759.825µs message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 843.739µs message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 820.702µs message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:56:54Z" - latency: 1.546732ms message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:55:54Z" - latency: 1.11806ms message: 'network-check-target-ip-10-0-137-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-network-check-target-ip-10-0-139-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "27768" uid: 58eb0741-4bed-47cc-83d9-98e70fc30e56 spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T20:56:54Z" message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.862252ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:03:54Z" - latency: 2.178502ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:02:54Z" - latency: 2.070046ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 2.006863ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 2.077849ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 1.979944ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 2.117224ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 2.096849ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:56:54Z" - latency: 1.982574ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:55:54Z" - latency: 2.15024ms message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T20:49:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-110.ec2.internal uid: f5ca19c6-e065-4194-a26a-f04864602890 resourceVersion: "26560" uid: 904e252d-ba4e-436e-ac1f-6c6f19856186 spec: sourcePod: network-check-source-8894fc9bd-z74x2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T20:55:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.239483ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:01:54Z" - latency: 1.669921ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T21:01:54Z" - latency: 847.353µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T21:00:54Z" - latency: 1.699129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T21:00:54Z" - latency: 1.261445ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:59:54Z" - latency: 1.633959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T20:59:54Z" - latency: 874.524µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:58:54Z" - latency: 1.727491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T20:58:54Z" - latency: 1.092922ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T20:57:54Z" - latency: 1.641903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T20:57:54Z" kind: List metadata: resourceVersion: ""