apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50330" uid: 795bf2b6-c70f-4d3e-8bcf-71880f3f1f16 spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T15:08:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.064324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 1.114727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 1.119684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 1.212492ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 1.025127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 1.064936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:35Z" - latency: 736.736µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:35Z" - latency: 842.966µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:36:35Z" - latency: 877.015µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:35:35Z" - latency: 1.264578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50331" uid: 26172b6b-69bb-4676-b968-73209e50f3c9 spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T15:07:35Z" message: 'load-balancer-api-external: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.236785ms message: 'load-balancer-api-external: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 7.489096ms message: 'load-balancer-api-external: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:43:35Z" - latency: 4.947504ms message: 'load-balancer-api-external: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 8.313595ms message: 'load-balancer-api-external: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:42:35Z" - latency: 5.487472ms message: 'load-balancer-api-external: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 8.605735ms message: 'load-balancer-api-external: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:41:35Z" - latency: 4.36523ms message: 'load-balancer-api-external: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 8.275827ms message: 'load-balancer-api-external: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:40:35Z" - latency: 3.787707ms message: 'load-balancer-api-external: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 8.700333ms message: 'load-balancer-api-external: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:39:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50332" uid: e2f139da-2213-49f3-aecb-b4a1abfb34c7 spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T15:07:35Z" message: 'load-balancer-api-internal: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 12.750009ms message: 'load-balancer-api-internal: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 7.533209ms message: 'load-balancer-api-internal: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:43:35Z" - latency: 4.719681ms message: 'load-balancer-api-internal: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 8.341959ms message: 'load-balancer-api-internal: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:42:35Z" - latency: 5.438104ms message: 'load-balancer-api-internal: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 8.628203ms message: 'load-balancer-api-internal: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:41:35Z" - latency: 4.375906ms message: 'load-balancer-api-internal: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 8.239481ms message: 'load-balancer-api-internal: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:40:35Z" - latency: 3.80369ms message: 'load-balancer-api-internal: tcp connection to a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 8.80723ms message: 'load-balancer-api-internal: resolved host name a08721121c8b74b9c9250d90f915194d-7c835ebc808bc4d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:39:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-network-check-target-ip-10-0-133-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50325" uid: bc0a1591-1f67-457b-8515-c430653ed362 spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:08:35Z" message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041509ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 1.201812ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 821.705µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 804.838µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 885.185µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 920.264µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:35Z" - latency: 757.739µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:35Z" - latency: 1.330771ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:36:35Z" - latency: 1.185112ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:35:35Z" - latency: 1.226363ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-network-check-target-ip-10-0-134-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50327" uid: 56506ee4-04d5-4281-9707-7fef807822a8 spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:08:35Z" message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.238658ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 2.187986ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 2.202854ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 2.105356ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 1.969831ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 2.095537ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:35Z" - latency: 1.955031ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:35Z" - latency: 2.207552ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:36:35Z" - latency: 1.863046ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:35:35Z" - latency: 1.963664ms message: 'network-check-target-ip-10-0-134-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-network-check-target-ip-10-0-139-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50328" uid: 0fee4c10-4c16-4295-a6f0-167e636cd3ca spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:08:35Z" message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.015315ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 1.881538ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 1.86849ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 2.001756ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 1.840078ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 2.010501ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:35Z" - latency: 2.029509ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:35Z" - latency: 2.166289ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:36:35Z" - latency: 2.064987ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:35:35Z" - latency: 2.043015ms message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-52.ec2.internal uid: 7cacfe00-09f6-4877-a9be-0e05965ebd54 resourceVersion: "50326" uid: 5c441a20-eed0-48ba-94ef-2453786ea349 spec: sourcePod: network-check-source-6947749cfc-xr776 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T15:07:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:35Z" - latency: 1.978058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:43:35Z" - latency: 1.10852ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:35Z" - latency: 1.724611ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:42:35Z" - latency: 941.039µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:35Z" - latency: 1.718631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:41:35Z" - latency: 842.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:35Z" - latency: 1.939102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:40:35Z" - latency: 878.061µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:35Z" - latency: 1.805796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:39:35Z" kind: List metadata: resourceVersion: ""