apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "54780" uid: b3326e65-d5b9-46bc-875d-31ac7f2dc650 spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T00:06:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 749.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 1.066112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 1.029086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 884.775µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 973.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:28Z" - latency: 943.781µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:28Z" - latency: 1.465786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:28Z" - latency: 932.962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:28Z" - latency: 1.108175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:28Z" - latency: 1.089085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "55675" uid: 3a7a012e-df68-4153-9678-f6e18f0101fd spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T00:05:28Z" message: 'load-balancer-api-external: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.07441ms message: 'load-balancer-api-external: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:35:28Z" - latency: 10.044422ms message: 'load-balancer-api-external: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:35:28Z" - latency: 5.740612ms message: 'load-balancer-api-external: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 14.053413ms message: 'load-balancer-api-external: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:34:28Z" - latency: 4.575597ms message: 'load-balancer-api-external: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 9.091191ms message: 'load-balancer-api-external: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:33:28Z" - latency: 4.921347ms message: 'load-balancer-api-external: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 16.191442ms message: 'load-balancer-api-external: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:32:28Z" - latency: 4.469767ms message: 'load-balancer-api-external: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 10.097483ms message: 'load-balancer-api-external: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:31:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "55676" uid: a19e17c3-e346-4158-979d-f9c391effe6d spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T00:05:28Z" message: 'load-balancer-api-internal: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.104132ms message: 'load-balancer-api-internal: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:35:28Z" - latency: 9.960338ms message: 'load-balancer-api-internal: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:35:28Z" - latency: 5.840878ms message: 'load-balancer-api-internal: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 13.964173ms message: 'load-balancer-api-internal: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:34:28Z" - latency: 4.563196ms message: 'load-balancer-api-internal: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 9.011766ms message: 'load-balancer-api-internal: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:33:28Z" - latency: 4.8327ms message: 'load-balancer-api-internal: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 16.115585ms message: 'load-balancer-api-internal: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:32:28Z" - latency: 4.491094ms message: 'load-balancer-api-internal: tcp connection to a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 10.154567ms message: 'load-balancer-api-internal: resolved host name a336fb9f21ca24e958673fbe5f4b96e8-165f48a177d060a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:31:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-129-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "54777" uid: 69575aac-b8d5-41ad-97fd-d00092b2515d spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:06:28Z" message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.075251ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 796.352µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 790.066µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 1.201352ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 1.369724ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:28Z" - latency: 881.067µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:28Z" - latency: 939.568µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:28Z" - latency: 1.265875ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:28Z" - latency: 789.542µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:28Z" - latency: 906.085µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-133-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "54779" uid: b0a6566a-8df5-4f2b-951e-f41c0d4f82fd spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:06:28Z" message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.627959ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 2.227237ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 2.341431ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 2.116177ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 2.614261ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:28Z" - latency: 2.375599ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:28Z" - latency: 2.360865ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:28Z" - latency: 2.585813ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:28Z" - latency: 2.712658ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:28Z" - latency: 2.24769ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-141-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "54778" uid: eacbafd8-708b-4f9d-94c3-d985c556fc8b spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:06:28Z" message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.176125ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 2.416205ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 2.274246ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 2.102806ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 2.70235ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:28Z" - latency: 2.550386ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:28Z" - latency: 2.469053ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:28Z" - latency: 2.498142ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:28Z" - latency: 2.494833ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:28Z" - latency: 2.383967ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: a0be246a-c3b8-40a0-a613-e5b25cbd8541 resourceVersion: "55674" uid: d969cea4-e9a8-4989-b8fb-7f3395f2a6b0 spec: sourcePod: network-check-source-989f8b8dc-tp5dt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T00:05:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06136ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:35:28Z" - latency: 1.778152ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:35:28Z" - latency: 796.744µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:28Z" - latency: 1.979468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:34:28Z" - latency: 1.151732ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:28Z" - latency: 1.649499ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:33:28Z" - latency: 829.799µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:28Z" - latency: 1.695983ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:32:28Z" - latency: 1.020314ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:28Z" - latency: 1.817379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:31:28Z" kind: List metadata: resourceVersion: ""