apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "18460" uid: a23e29d7-c44a-45f1-9a12-8b6e9840200f spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T16:42:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.00706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 857.944µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:38Z" - latency: 873.37µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:38Z" - latency: 851.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:38Z" - latency: 812.27µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:38Z" - latency: 1.028804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:38Z" - latency: 970.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:38Z" - latency: 1.801968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:38Z" - latency: 1.141154ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:38Z" - latency: 973.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "20516" uid: e6b31f10-502e-4f0b-abb9-eb31e3678e70 spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:41:38Z" message: 'load-balancer-api-external: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.149055ms message: 'load-balancer-api-external: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:38Z" - latency: 6.752842ms message: 'load-balancer-api-external: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:53:38Z" - latency: 4.62163ms message: 'load-balancer-api-external: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:38Z" - latency: 6.347127ms message: 'load-balancer-api-external: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:52:38Z" - latency: 4.314961ms message: 'load-balancer-api-external: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:38Z" - latency: 6.365595ms message: 'load-balancer-api-external: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:51:38Z" - latency: 5.618979ms message: 'load-balancer-api-external: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:38Z" - latency: 7.931196ms message: 'load-balancer-api-external: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:50:38Z" - latency: 5.040893ms message: 'load-balancer-api-external: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 7.075314ms message: 'load-balancer-api-external: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:49:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "20515" uid: 428bd256-aeec-4521-a3de-2515184fa056 spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:41:38Z" message: 'load-balancer-api-internal: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.134646ms message: 'load-balancer-api-internal: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:38Z" - latency: 6.872279ms message: 'load-balancer-api-internal: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:53:38Z" - latency: 3.654272ms message: 'load-balancer-api-internal: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:38Z" - latency: 6.440903ms message: 'load-balancer-api-internal: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:52:38Z" - latency: 4.292067ms message: 'load-balancer-api-internal: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:38Z" - latency: 6.423885ms message: 'load-balancer-api-internal: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:51:38Z" - latency: 5.641956ms message: 'load-balancer-api-internal: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:38Z" - latency: 8.048574ms message: 'load-balancer-api-internal: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:50:38Z" - latency: 5.009025ms message: 'load-balancer-api-internal: tcp connection to ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 7.124933ms message: 'load-balancer-api-internal: resolved host name ac009b6034a4e4c8484a3ddaf807c196-e0a82886bcd37fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:49:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-ip-10-0-132-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "18457" uid: d74782bc-fb54-44f9-a54c-499af59c6acc spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:42:38Z" message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.073621ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 768.334µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:38Z" - latency: 717.737µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:38Z" - latency: 963.821µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:38Z" - latency: 768.456µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:38Z" - latency: 883.205µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:38Z" - latency: 953.064µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:38Z" - latency: 923.387µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:38Z" - latency: 881.343µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:38Z" - latency: 835.269µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-ip-10-0-135-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "18459" uid: ce62859c-53df-4e9d-afb4-df1576a97f86 spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:42:38Z" message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.044591ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 2.203689ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:38Z" - latency: 2.381864ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:38Z" - latency: 2.163455ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:38Z" - latency: 2.205878ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:38Z" - latency: 2.169264ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:38Z" - latency: 1.967441ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:38Z" - latency: 2.15047ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:38Z" - latency: 2.28793ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:38Z" - latency: 2.137737ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-ip-10-0-141-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "18458" uid: c0f8e4d3-9f51-4516-8c09-6b439daa2672 spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:42:38Z" message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.052514ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 1.886411ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:38Z" - latency: 2.016471ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:38Z" - latency: 2.138881ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:38Z" - latency: 1.944465ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:38Z" - latency: 2.165444ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:38Z" - latency: 2.141161ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:38Z" - latency: 2.173571ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:38Z" - latency: 2.1912ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:38Z" - latency: 2.167145ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 1ad0c0e5-b1cd-47ff-8a07-c473443d3bce resourceVersion: "20514" uid: 2e5f5a29-dc47-4607-b54e-807ca110e502 spec: sourcePod: network-check-source-8894fc9bd-nlj65 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T16:41:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 746.049µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:38Z" - latency: 1.682603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:53:38Z" - latency: 1.135438ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:38Z" - latency: 1.666722ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:52:38Z" - latency: 791.118µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:38Z" - latency: 1.656454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:51:38Z" - latency: 855.134µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:38Z" - latency: 1.589165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:50:38Z" - latency: 1.036422ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:38Z" - latency: 2.063538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:49:38Z" kind: List metadata: resourceVersion: ""