apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61551" uid: a3d14e50-07fb-4c33-903c-125bbf71a2bd spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T18:19:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.795µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 840.796µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 1.132494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 1.303248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 986.063µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 858.155µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:49:59Z" - latency: 816.036µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:48:59Z" - latency: 978.268µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:47:59Z" - latency: 1.209149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:46:59Z" - latency: 1.137199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:45:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61552" uid: 3aead6dc-d9c1-4d25-853e-c6d01594d5c6 spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T18:18:59Z" message: 'load-balancer-api-external: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.345209ms message: 'load-balancer-api-external: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 7.556833ms message: 'load-balancer-api-external: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:54:59Z" - latency: 4.2957ms message: 'load-balancer-api-external: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 7.0975ms message: 'load-balancer-api-external: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:53:59Z" - latency: 4.596266ms message: 'load-balancer-api-external: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 7.305138ms message: 'load-balancer-api-external: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:52:59Z" - latency: 5.257898ms message: 'load-balancer-api-external: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 7.755407ms message: 'load-balancer-api-external: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:51:59Z" - latency: 4.631357ms message: 'load-balancer-api-external: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 6.4579ms message: 'load-balancer-api-external: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61553" uid: 4faa409f-fe1b-46a4-86d6-a93cec4c2565 spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T18:18:59Z" message: 'load-balancer-api-internal: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.279527ms message: 'load-balancer-api-internal: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 7.630238ms message: 'load-balancer-api-internal: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:54:59Z" - latency: 4.291536ms message: 'load-balancer-api-internal: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 7.141808ms message: 'load-balancer-api-internal: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:53:59Z" - latency: 5.893012ms message: 'load-balancer-api-internal: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 7.229206ms message: 'load-balancer-api-internal: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:52:59Z" - latency: 5.216417ms message: 'load-balancer-api-internal: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 7.837812ms message: 'load-balancer-api-internal: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:51:59Z" - latency: 3.868692ms message: 'load-balancer-api-internal: tcp connection to aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 6.510051ms message: 'load-balancer-api-internal: resolved host name aecbd51fee23b4ec29b893f101f3cd19-db4ba9987be6f1d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-network-check-target-ip-10-0-129-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61548" uid: 2ca81efa-f266-431a-987d-46638611c899 spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T18:19:59Z" message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.237835ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 2.178565ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 2.42836ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 2.338753ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 2.164539ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 2.218763ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:49:59Z" - latency: 2.07183ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:48:59Z" - latency: 2.066406ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:47:59Z" - latency: 2.468686ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:46:59Z" - latency: 2.466652ms message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:45:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-network-check-target-ip-10-0-131-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61549" uid: 6be3ec23-604f-47ad-b750-821edc03260b spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T18:19:59Z" message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.981232ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 1.575005ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 1.93761ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 1.863647ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 2.121389ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 1.964639ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:49:59Z" - latency: 1.800292ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:48:59Z" - latency: 2.026579ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:47:59Z" - latency: 1.717461ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:46:59Z" - latency: 2.059455ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:45:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-network-check-target-ip-10-0-136-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61547" uid: dbea5f94-c8fc-48f0-b6e5-c39b9eb52367 spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T18:19:59Z" message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.175µs message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 1.430521ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 861.473µs message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 1.051054ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 1.443605ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 1.330552ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:49:59Z" - latency: 911.99µs message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:48:59Z" - latency: 1.291787ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:47:59Z" - latency: 1.970402ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:46:59Z" - latency: 971.748µs message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:45:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-25-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-25.ec2.internal uid: 5d193538-296b-407e-8c43-fe48e6339fc7 resourceVersion: "61550" uid: 119105a8-187a-4392-990b-bce43b43600c spec: sourcePod: network-check-source-869dcfcdcd-vwp4s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T18:18:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.222379ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:54:59Z" - latency: 1.825411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:54:59Z" - latency: 875.626µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:53:59Z" - latency: 1.9838ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:53:59Z" - latency: 1.18621ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:52:59Z" - latency: 2.0913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:52:59Z" - latency: 846.758µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:51:59Z" - latency: 1.808387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:51:59Z" - latency: 928.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:50:59Z" - latency: 1.528438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:50:59Z" kind: List metadata: resourceVersion: ""