apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "18605" uid: fc167500-064f-46ea-93b7-46400d432b2a spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T19:35:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.902µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 1.004559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:55Z" - latency: 969.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:55Z" - latency: 786.697µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:55Z" - latency: 914.253µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:55Z" - latency: 1.014918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:37:55Z" - latency: 977.453µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:36:55Z" - latency: 1.328325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:35:55Z" - latency: 881.105µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:34:55Z" - latency: 1.411083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "20739" uid: 80f577cc-6660-411e-920a-67235dd79905 spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T19:34:55Z" message: 'load-balancer-api-external: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.330213ms message: 'load-balancer-api-external: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:55Z" - latency: 11.609077ms message: 'load-balancer-api-external: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:46:55Z" - latency: 5.670599ms message: 'load-balancer-api-external: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:55Z" - latency: 7.723823ms message: 'load-balancer-api-external: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:45:55Z" - latency: 9.674596ms message: 'load-balancer-api-external: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:55Z" - latency: 6.152647ms message: 'load-balancer-api-external: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:44:55Z" - latency: 4.440627ms message: 'load-balancer-api-external: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:55Z" - latency: 6.926606ms message: 'load-balancer-api-external: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:43:55Z" - latency: 4.094133ms message: 'load-balancer-api-external: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 7.682641ms message: 'load-balancer-api-external: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:42:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "20738" uid: 1f76d7e5-eaf5-4395-94a4-e6d32c4bd9bb spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T19:34:55Z" message: 'load-balancer-api-internal: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.331664ms message: 'load-balancer-api-internal: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:55Z" - latency: 11.692975ms message: 'load-balancer-api-internal: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:46:55Z" - latency: 5.680878ms message: 'load-balancer-api-internal: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:55Z" - latency: 7.685631ms message: 'load-balancer-api-internal: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:45:55Z" - latency: 4.664127ms message: 'load-balancer-api-internal: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:55Z" - latency: 6.213752ms message: 'load-balancer-api-internal: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:44:55Z" - latency: 4.247573ms message: 'load-balancer-api-internal: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:55Z" - latency: 6.998802ms message: 'load-balancer-api-internal: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:43:55Z" - latency: 4.237687ms message: 'load-balancer-api-internal: tcp connection to a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 7.591146ms message: 'load-balancer-api-internal: resolved host name a282f2f5aed084919940164b071226c4-065524e91f99dafa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:42:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-131-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "18603" uid: 1f735179-7d45-4e1a-8100-ac171902a162 spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:35:55Z" message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.0871ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 2.112229ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:55Z" - latency: 2.284929ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:55Z" - latency: 1.830723ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:55Z" - latency: 2.20851ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:55Z" - latency: 2.40845ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:37:55Z" - latency: 2.155111ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:36:55Z" - latency: 2.729689ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:35:55Z" - latency: 2.179459ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:34:55Z" - latency: 2.389285ms message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-133-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "18604" uid: 2aa62ba8-658f-4412-a8d0-a4aa60144edd spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:35:55Z" message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296356ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 1.9388ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:55Z" - latency: 2.107806ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:55Z" - latency: 2.066287ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:55Z" - latency: 2.239051ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:55Z" - latency: 2.724489ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:37:55Z" - latency: 2.250183ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:36:55Z" - latency: 2.141113ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:35:55Z" - latency: 2.084411ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:34:55Z" - latency: 2.268981ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-138-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "18602" uid: a39bfc67-d939-425b-a9ad-0245eb916cd0 spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:35:55Z" message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.078µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 771.869µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:55Z" - latency: 886.732µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:55Z" - latency: 782.056µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:55Z" - latency: 1.033379ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:55Z" - latency: 908.787µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:37:55Z" - latency: 894.174µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:36:55Z" - latency: 863.115µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:35:55Z" - latency: 839.947µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:34:55Z" - latency: 1.511362ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:28:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: de9ec935-1ec7-4676-b736-dac733cc4cc5 resourceVersion: "20737" uid: b46046cb-608f-448f-824c-6333e9167f71 spec: sourcePod: network-check-source-8894fc9bd-dppdk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T19:34:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.917µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:55Z" - latency: 1.653073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:46:55Z" - latency: 792.626µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:55Z" - latency: 1.586265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:45:55Z" - latency: 822.37µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:55Z" - latency: 1.747371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:44:55Z" - latency: 968.701µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:55Z" - latency: 1.783798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:43:55Z" - latency: 917.904µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:55Z" - latency: 1.837129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:42:55Z" kind: List metadata: resourceVersion: ""