apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "19811" uid: 1a4ff8a6-ec09-401f-b5ec-ac2ffd7e65cd spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T17:16:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 1.172311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 996.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:28:51Z" - latency: 1.932771ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:27:51Z" - latency: 1.002657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:26:51Z" - latency: 1.067709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:25:51Z" - latency: 2.642916ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:24:51Z" - latency: 1.08362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:23:51Z" - latency: 1.043735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:22:51Z" - latency: 1.051659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "20961" uid: 1718b115-5f61-4c29-bdba-0d117d24adb2 spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T17:15:51Z" message: 'load-balancer-api-external: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.796161ms message: 'load-balancer-api-external: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:33:51Z" - latency: 6.826854ms message: 'load-balancer-api-external: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:33:51Z" - latency: 4.465327ms message: 'load-balancer-api-external: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:32:51Z" - latency: 7.87244ms message: 'load-balancer-api-external: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:32:51Z" - latency: 5.049919ms message: 'load-balancer-api-external: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:31:51Z" - latency: 8.605866ms message: 'load-balancer-api-external: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:31:51Z" - latency: 5.216597ms message: 'load-balancer-api-external: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 8.626777ms message: 'load-balancer-api-external: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:30:51Z" - latency: 3.99343ms message: 'load-balancer-api-external: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 23.946886ms message: 'load-balancer-api-external: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:29:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "20960" uid: e4eea3aa-a77b-48bf-9255-cd9b2793b1d7 spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T17:15:51Z" message: 'load-balancer-api-internal: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.771262ms message: 'load-balancer-api-internal: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:33:51Z" - latency: 6.88504ms message: 'load-balancer-api-internal: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:33:51Z" - latency: 4.448598ms message: 'load-balancer-api-internal: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:32:51Z" - latency: 7.78287ms message: 'load-balancer-api-internal: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:32:51Z" - latency: 5.070981ms message: 'load-balancer-api-internal: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:31:51Z" - latency: 8.640712ms message: 'load-balancer-api-internal: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:31:51Z" - latency: 5.829068ms message: 'load-balancer-api-internal: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 8.659339ms message: 'load-balancer-api-internal: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:30:51Z" - latency: 3.982509ms message: 'load-balancer-api-internal: tcp connection to af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 23.889025ms message: 'load-balancer-api-internal: resolved host name af786770425464cf08a21269b9028457-f84e2a94d9ab0bbb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T17:29:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-ip-10-0-129-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "19808" uid: 87628540-0dee-4f68-9551-242133290860 spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T17:16:51Z" message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.411µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 795.735µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 789.964µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:28:51Z" - latency: 1.020092ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:27:51Z" - latency: 819.403µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:26:51Z" - latency: 728.559µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:25:51Z" - latency: 4.434798ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:24:51Z" - latency: 1.119974ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:23:51Z" - latency: 2.040592ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:22:51Z" - latency: 843.345µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-ip-10-0-136-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "19809" uid: a1f56b2b-5211-4f63-8689-b6980ab5c146 spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T17:16:51Z" message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.121787ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 2.200158ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 1.98632ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:28:51Z" - latency: 2.276104ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:27:51Z" - latency: 2.145295ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:26:51Z" - latency: 2.107129ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:25:51Z" - latency: 3.902435ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:24:51Z" - latency: 2.0586ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:23:51Z" - latency: 2.019831ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:22:51Z" - latency: 2.313195ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-ip-10-0-142-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "19810" uid: aec79ae2-dea0-431b-8432-e504032c2b78 spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T17:16:51Z" message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.253142ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 2.138379ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 2.144924ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:28:51Z" - latency: 2.319676ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:27:51Z" - latency: 2.303527ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:26:51Z" - latency: 2.049725ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:25:51Z" - latency: 4.158199ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:24:51Z" - latency: 2.206554ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:23:51Z" - latency: 2.118919ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:22:51Z" - latency: 2.202271ms message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T17:09:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d489f72e-27a6-4fa0-9563-0e9961f3abeb resourceVersion: "20959" uid: 7860352b-6a6c-450a-98ae-717a757f3282 spec: sourcePod: network-check-source-7f44b6dd87-gzk92 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T17:15:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 957.091µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:33:51Z" - latency: 1.793035ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T17:33:51Z" - latency: 872.316µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:32:51Z" - latency: 2.886328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T17:32:51Z" - latency: 770.498µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:31:51Z" - latency: 1.641989ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T17:31:51Z" - latency: 747.692µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:30:51Z" - latency: 1.821403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T17:30:51Z" - latency: 868.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T17:29:51Z" - latency: 17.251339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T17:29:51Z" kind: List metadata: resourceVersion: ""