apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "21417" uid: fc4c82a0-241f-4932-a9f9-09c95aa1f5bf spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T15:35:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:49:19Z" - latency: 834.783µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:48:19Z" - latency: 1.03976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:47:19Z" - latency: 867.483µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 814.919µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 1.043612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 1.098381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 889.919µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 855.5µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:19Z" - latency: 957.719µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "20002" uid: cfe910db-83db-46c1-af4e-0106ae601bb5 spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:34:19Z" message: 'load-balancer-api-external: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.222066ms message: 'load-balancer-api-external: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 12.731906ms message: 'load-balancer-api-external: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:46:19Z" - latency: 4.886858ms message: 'load-balancer-api-external: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 8.534372ms message: 'load-balancer-api-external: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:45:19Z" - latency: 3.903017ms message: 'load-balancer-api-external: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 8.006563ms message: 'load-balancer-api-external: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:44:19Z" - latency: 4.847986ms message: 'load-balancer-api-external: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 8.58312ms message: 'load-balancer-api-external: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:43:19Z" - latency: 6.318407ms message: 'load-balancer-api-external: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 8.143553ms message: 'load-balancer-api-external: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "20003" uid: ed2591c1-e5bd-440e-a686-8fbfd10a11f2 spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:34:19Z" message: 'load-balancer-api-internal: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.373704ms message: 'load-balancer-api-internal: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 12.779674ms message: 'load-balancer-api-internal: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:46:19Z" - latency: 4.865428ms message: 'load-balancer-api-internal: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 8.646147ms message: 'load-balancer-api-internal: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:45:19Z" - latency: 6.269741ms message: 'load-balancer-api-internal: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 8.066212ms message: 'load-balancer-api-internal: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:44:19Z" - latency: 4.112785ms message: 'load-balancer-api-internal: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 8.697147ms message: 'load-balancer-api-internal: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:43:19Z" - latency: 9.238789ms message: 'load-balancer-api-internal: tcp connection to af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 8.244262ms message: 'load-balancer-api-internal: resolved host name af79b629f7445440baa6b41afb213226-46032d78989c3a48.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-132-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "21415" uid: 0ec6deb4-bce7-468d-9b88-31b4ae5e1621 spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:35:19Z" message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.730152ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:49:19Z" - latency: 1.75795ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:48:19Z" - latency: 1.582194ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:47:19Z" - latency: 1.755508ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 1.892514ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 1.735095ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 1.997837ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 1.886896ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 2.028121ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:19Z" - latency: 1.750137ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-133-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "21414" uid: 9026bc90-2074-4a94-a798-7c07c728d87a spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:35:19Z" message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 758.337µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:49:19Z" - latency: 1.333032ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:48:19Z" - latency: 1.262127ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:47:19Z" - latency: 916.088µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 905.979µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 789.63µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 680.855µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 868.284µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 1.091212ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:19Z" - latency: 916.261µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-133-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "21416" uid: 3f59d232-cd05-4277-ac8f-df3d795a4ab2 spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:35:19Z" message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.252977ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:49:19Z" - latency: 2.019067ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:48:19Z" - latency: 2.286891ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:47:19Z" - latency: 2.078859ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 1.983913ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 2.477989ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 2.228917ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 2.078949ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 2.413981ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:19Z" - latency: 2.409227ms message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:28:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: a4c7415a-2cfb-4a50-8f2b-855f92a921d5 resourceVersion: "20001" uid: 9a2eaef0-ab53-4caf-993a-825edfe20776 spec: sourcePod: network-check-source-869dcfcdcd-scnn4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T15:34:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.451µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:19Z" - latency: 1.679843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:46:19Z" - latency: 883.68µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:19Z" - latency: 1.89719ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:45:19Z" - latency: 1.181314ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:19Z" - latency: 1.612295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:44:19Z" - latency: 991.34µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:19Z" - latency: 1.641876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:43:19Z" - latency: 676.577µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:19Z" - latency: 1.834815ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:19Z" kind: List metadata: resourceVersion: ""