apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "33021" uid: ab3ce2c6-fe17-48c6-8d6f-c8693e3bb197 spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:40:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.187864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 870.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 943.979µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:54Z" - latency: 1.349568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:54Z" - latency: 1.071814ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:54Z" - latency: 1.276079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:54Z" - latency: 807.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:54Z" - latency: 902.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:54Z" - latency: 1.130393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:54Z" - latency: 1.405581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "35665" uid: ee5e0d03-98fa-4e5e-a841-2459f444ae85 spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:39:54Z" message: 'load-balancer-api-external: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.186001ms message: 'load-balancer-api-external: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:54Z" - latency: 7.000704ms message: 'load-balancer-api-external: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:57:54Z" - latency: 4.491255ms message: 'load-balancer-api-external: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:54Z" - latency: 6.702727ms message: 'load-balancer-api-external: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:56:54Z" - latency: 3.764699ms message: 'load-balancer-api-external: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:54Z" - latency: 14.070409ms message: 'load-balancer-api-external: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:55:54Z" - latency: 5.644508ms message: 'load-balancer-api-external: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 7.134389ms message: 'load-balancer-api-external: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:54:54Z" - latency: 3.537901ms message: 'load-balancer-api-external: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 7.029205ms message: 'load-balancer-api-external: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:53:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "35664" uid: a5923909-c601-4473-ab8e-bf8cfd5c0d9d spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:39:54Z" message: 'load-balancer-api-internal: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.474902ms message: 'load-balancer-api-internal: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:54Z" - latency: 6.806536ms message: 'load-balancer-api-internal: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:57:54Z" - latency: 4.476845ms message: 'load-balancer-api-internal: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:54Z" - latency: 6.764727ms message: 'load-balancer-api-internal: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:56:54Z" - latency: 3.695448ms message: 'load-balancer-api-internal: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:54Z" - latency: 13.911338ms message: 'load-balancer-api-internal: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:55:54Z" - latency: 5.646583ms message: 'load-balancer-api-internal: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 7.074665ms message: 'load-balancer-api-internal: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:54:54Z" - latency: 4.58794ms message: 'load-balancer-api-internal: tcp connection to adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 6.993953ms message: 'load-balancer-api-internal: resolved host name adee4e4003ab94f9c95a4bae513c269f-3057e16137d708b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:53:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-network-check-target-ip-10-0-135-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "33019" uid: 0cbd7788-7190-4c8e-922e-a0a922fe1d4e spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:40:54Z" message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.370338ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 1.930665ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 1.893893ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:54Z" - latency: 1.903157ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:54Z" - latency: 1.899486ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:54Z" - latency: 2.347866ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:54Z" - latency: 1.780695ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:54Z" - latency: 1.617126ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:54Z" - latency: 1.985735ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:54Z" - latency: 1.818839ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-network-check-target-ip-10-0-137-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "33018" uid: efe53ca9-7293-4499-bd52-07eff9882982 spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:40:54Z" message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.386238ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 1.190056ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 1.435096ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:54Z" - latency: 1.725128ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:54Z" - latency: 792.266µs message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:54Z" - latency: 1.655716ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:54Z" - latency: 762.647µs message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:54Z" - latency: 826.778µs message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:54Z" - latency: 879.303µs message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:54Z" - latency: 823.587µs message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-network-check-target-ip-10-0-140-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "33020" uid: 068da921-6b47-456b-97cb-9e2d0cbfa785 spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:40:54Z" message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.417336ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 2.665622ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 2.51469ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:54Z" - latency: 2.323119ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:54Z" - latency: 1.987678ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:54Z" - latency: 2.423221ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:54Z" - latency: 2.084849ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:54Z" - latency: 2.254489ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:54Z" - latency: 2.174821ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:54Z" - latency: 1.968003ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:33:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-47.ec2.internal uid: 03e31754-b4f4-489b-a1a7-7cebd8ab9f92 resourceVersion: "35663" uid: 6df93681-e640-4463-827e-e0e3f1214feb spec: sourcePod: network-check-source-7b678d77c7-jxkbj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:39:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.219µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:54Z" - latency: 1.617381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:57:54Z" - latency: 807.475µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:54Z" - latency: 1.797758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:56:54Z" - latency: 947.744µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:54Z" - latency: 2.056521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:55:54Z" - latency: 810.82µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:54Z" - latency: 1.647531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:54:54Z" - latency: 914.455µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:54Z" - latency: 1.900016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:53:54Z" kind: List metadata: resourceVersion: ""