apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "40092" uid: 231638db-1ac4-4aa5-8890-3b5aae5a5f2d spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T19:19:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.425402ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 1.583677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:07:52Z" - latency: 1.035821ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:06:52Z" - latency: 1.024761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:05:52Z" - latency: 857.771µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:04:52Z" - latency: 1.000638ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:03:52Z" - latency: 929.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:02:52Z" - latency: 995.708µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:01:52Z" - latency: 1.028504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:00:52Z" - latency: 1.068246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:59:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "42239" uid: 51e78970-168f-44b9-a84d-c5257e181888 spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T19:18:52Z" message: 'load-balancer-api-external: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.016944ms message: 'load-balancer-api-external: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:12:52Z" - latency: 8.02135ms message: 'load-balancer-api-external: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:12:52Z" - latency: 3.66721ms message: 'load-balancer-api-external: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:11:52Z" - latency: 9.159536ms message: 'load-balancer-api-external: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:11:52Z" - latency: 5.068065ms message: 'load-balancer-api-external: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:10:52Z" - latency: 9.123522ms message: 'load-balancer-api-external: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:10:52Z" - latency: 5.791524ms message: 'load-balancer-api-external: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:09:52Z" - latency: 9.199095ms message: 'load-balancer-api-external: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:09:52Z" - latency: 4.408131ms message: 'load-balancer-api-external: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 7.915045ms message: 'load-balancer-api-external: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:08:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "42238" uid: f2c2d350-08c7-414e-b06c-acd37b8c3a2f spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T19:18:52Z" message: 'load-balancer-api-internal: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.499471ms message: 'load-balancer-api-internal: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:12:52Z" - latency: 8.095041ms message: 'load-balancer-api-internal: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:12:52Z" - latency: 3.667671ms message: 'load-balancer-api-internal: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:11:52Z" - latency: 9.209497ms message: 'load-balancer-api-internal: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:11:52Z" - latency: 5.07935ms message: 'load-balancer-api-internal: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:10:52Z" - latency: 9.253826ms message: 'load-balancer-api-internal: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:10:52Z" - latency: 5.78459ms message: 'load-balancer-api-internal: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:09:52Z" - latency: 9.258878ms message: 'load-balancer-api-internal: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:09:52Z" - latency: 4.525636ms message: 'load-balancer-api-internal: tcp connection to ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 8.009493ms message: 'load-balancer-api-internal: resolved host name ac9248b27c3e8462480e461463ac9378-2ce9d3905b1e1365.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T20:08:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-network-check-target-ip-10-0-129-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "40091" uid: 6fde3d33-b7a9-4acf-93f5-44615df80f7c spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:19:52Z" message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.318475ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 2.081295ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:07:52Z" - latency: 2.089803ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:06:52Z" - latency: 2.592004ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:05:52Z" - latency: 2.045522ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:04:52Z" - latency: 2.358644ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:03:52Z" - latency: 2.152134ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:02:52Z" - latency: 2.240899ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:01:52Z" - latency: 2.055976ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:00:52Z" - latency: 2.4098ms message: 'network-check-target-ip-10-0-129-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:59:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-network-check-target-ip-10-0-129-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "40090" uid: 5577aea3-6989-4935-8260-25b5aa92e72b spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:19:52Z" message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.031869ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 2.305333ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:07:52Z" - latency: 1.999144ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:06:52Z" - latency: 1.960559ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:05:52Z" - latency: 1.840767ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:04:52Z" - latency: 1.985244ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:03:52Z" - latency: 2.148959ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:02:52Z" - latency: 2.013959ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:01:52Z" - latency: 1.8713ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:00:52Z" - latency: 1.845786ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:59:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-network-check-target-ip-10-0-131-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "40089" uid: bb17c347-57c7-4fe8-9456-07bfac63f11e spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:19:52Z" message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.279µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 1.139527ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:07:52Z" - latency: 1.329394ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:06:52Z" - latency: 766.13µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:05:52Z" - latency: 757.143µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:04:52Z" - latency: 899.016µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:03:52Z" - latency: 917.252µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:02:52Z" - latency: 1.171461ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:01:52Z" - latency: 784.645µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:00:52Z" - latency: 754.771µs message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:59:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:12:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-214.ec2.internal uid: daf4c006-2436-4f14-9415-071b592cf5df resourceVersion: "42237" uid: d9e38090-21b2-48d8-8ce6-1a4eda888913 spec: sourcePod: network-check-source-8894fc9bd-lh97m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T19:18:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.805µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:12:52Z" - latency: 1.68973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T20:12:52Z" - latency: 812.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:11:52Z" - latency: 1.659225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T20:11:52Z" - latency: 859.516µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:10:52Z" - latency: 1.660161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T20:10:52Z" - latency: 733.312µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:09:52Z" - latency: 1.62788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T20:09:52Z" - latency: 920.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T20:08:52Z" - latency: 1.571389ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T20:08:52Z" kind: List metadata: resourceVersion: ""