apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "54365" uid: 7ab4b353-f74a-4813-91b2-4eadf7b2f9d1 spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T21:39:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.27232ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 1.353463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 915.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 1.27959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 1.419116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:03:19Z" - latency: 1.248895ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:02:19Z" - latency: 1.656891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:01:19Z" - latency: 1.273471ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:00:19Z" - latency: 1.024862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:59:19Z" - latency: 1.151157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:58:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "55321" uid: 82312102-b8c0-4f2b-acfe-e39de4988faa spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:38:19Z" message: 'load-balancer-api-external: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.02784ms message: 'load-balancer-api-external: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:08:19Z" - latency: 7.373056ms message: 'load-balancer-api-external: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:08:19Z" - latency: 6.252111ms message: 'load-balancer-api-external: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 7.535867ms message: 'load-balancer-api-external: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:07:19Z" - latency: 5.958695ms message: 'load-balancer-api-external: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 7.112442ms message: 'load-balancer-api-external: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:06:19Z" - latency: 4.020851ms message: 'load-balancer-api-external: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 6.82808ms message: 'load-balancer-api-external: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:05:19Z" - latency: 4.476533ms message: 'load-balancer-api-external: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 6.927947ms message: 'load-balancer-api-external: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:04:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "55320" uid: 3f00a9b8-f5e3-4cbf-baa4-5d8f3c50f140 spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:38:19Z" message: 'load-balancer-api-internal: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.999387ms message: 'load-balancer-api-internal: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:08:19Z" - latency: 7.405163ms message: 'load-balancer-api-internal: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:08:19Z" - latency: 5.776238ms message: 'load-balancer-api-internal: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 7.519791ms message: 'load-balancer-api-internal: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:07:19Z" - latency: 4.047809ms message: 'load-balancer-api-internal: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 7.181943ms message: 'load-balancer-api-internal: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:06:19Z" - latency: 3.976273ms message: 'load-balancer-api-internal: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 6.868691ms message: 'load-balancer-api-internal: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:05:19Z" - latency: 4.436577ms message: 'load-balancer-api-internal: tcp connection to a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 7.006843ms message: 'load-balancer-api-internal: resolved host name a6d434655778546a1a436645e96419c6-d4a3c41fd08a02ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:04:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-ip-10-0-130-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "54362" uid: 00cf75ac-9e36-4c15-b9fc-3ce94afa1fed spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:39:19Z" message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.029463ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 891.824µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 1.026726ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 912.151µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 1.635488ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:03:19Z" - latency: 1.204941ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:02:19Z" - latency: 1.068197ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:01:19Z" - latency: 1.033845ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:00:19Z" - latency: 1.32689ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:59:19Z" - latency: 956.532µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:58:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-ip-10-0-130-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "54364" uid: d2d9e00f-932c-404a-ab37-2394bd2da275 spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:39:19Z" message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.30371ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 2.211552ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 2.115971ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 2.66909ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 2.673ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:03:19Z" - latency: 2.679106ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:02:19Z" - latency: 2.225114ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:01:19Z" - latency: 2.098182ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:00:19Z" - latency: 2.210498ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:59:19Z" - latency: 2.299721ms message: 'network-check-target-ip-10-0-130-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:58:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-ip-10-0-135-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "54363" uid: b119563f-4845-4060-91fe-b2fefac2da23 spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:39:19Z" message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369918ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 2.087063ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 2.037334ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 2.294585ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 2.292449ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:03:19Z" - latency: 2.299353ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:02:19Z" - latency: 2.266559ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:01:19Z" - latency: 2.166838ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:00:19Z" - latency: 2.131849ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:59:19Z" - latency: 2.024262ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:58:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:32:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 0e68c62e-659a-40de-8ebc-00df525c243f resourceVersion: "55317" uid: f7339bc9-d729-4f9d-9807-18dc1e11f22d spec: sourcePod: network-check-source-869dcfcdcd-hv4rg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T21:38:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.017949ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:08:19Z" - latency: 2.123315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:08:19Z" - latency: 976.768µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:07:19Z" - latency: 1.891858ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:07:19Z" - latency: 875.868µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:06:19Z" - latency: 2.129924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:06:19Z" - latency: 1.026598ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:05:19Z" - latency: 1.802696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:05:19Z" - latency: 1.119619ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:04:19Z" - latency: 2.021249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:04:19Z" kind: List metadata: resourceVersion: ""