apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "17203" uid: 0638eab4-2c70-491e-bff8-878eb709e645 spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T15:39:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.3622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:30Z" - latency: 997.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:30Z" - latency: 1.963518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 826.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 974.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 970.042µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 959.173µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 862.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:30Z" - latency: 1.434147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:30Z" - latency: 937.597µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "16561" uid: 00acffbc-87b0-4bb1-9433-7a9d875ddbc4 spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:38:30Z" message: 'load-balancer-api-external: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.621037ms message: 'load-balancer-api-external: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 7.587285ms message: 'load-balancer-api-external: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:44:30Z" - latency: 5.911127ms message: 'load-balancer-api-external: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 6.724219ms message: 'load-balancer-api-external: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:43:30Z" - latency: 7.242478ms message: 'load-balancer-api-external: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 6.785453ms message: 'load-balancer-api-external: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:30Z" - latency: 4.610603ms message: 'load-balancer-api-external: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 6.2069ms message: 'load-balancer-api-external: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:41:30Z" - latency: 5.282328ms message: 'load-balancer-api-external: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 6.866606ms message: 'load-balancer-api-external: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:40:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "16560" uid: b284b58c-c9e2-4da0-a4de-87c0d688896d spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:38:30Z" message: 'load-balancer-api-internal: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.597116ms message: 'load-balancer-api-internal: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 7.655572ms message: 'load-balancer-api-internal: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:44:30Z" - latency: 6.082199ms message: 'load-balancer-api-internal: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 6.76985ms message: 'load-balancer-api-internal: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:43:30Z" - latency: 4.493589ms message: 'load-balancer-api-internal: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 6.763403ms message: 'load-balancer-api-internal: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:30Z" - latency: 5.921806ms message: 'load-balancer-api-internal: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 6.388916ms message: 'load-balancer-api-internal: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:41:30Z" - latency: 5.294459ms message: 'load-balancer-api-internal: tcp connection to ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 6.813313ms message: 'load-balancer-api-internal: resolved host name ac54a9af6c72a4886b627e96e6c1f4d8-7aee4026909a8398.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:40:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-network-check-target-ip-10-0-130-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "17200" uid: 63baf2c6-150f-4cda-a7fe-081d09080469 spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:39:30Z" message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.556896ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:30Z" - latency: 882.817µs message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:30Z" - latency: 2.238587ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 1.113341ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 861.626µs message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 1.14481ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 1.355705ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 1.033447ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:30Z" - latency: 1.028921ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:30Z" - latency: 1.037437ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-network-check-target-ip-10-0-137-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "17201" uid: 778c52aa-87f3-49ff-8775-803993625b0b spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:39:30Z" message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.417628ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:30Z" - latency: 2.435414ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:30Z" - latency: 2.262714ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 2.082376ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 1.996982ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 2.141485ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 2.202518ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 2.083778ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:30Z" - latency: 2.423962ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:30Z" - latency: 2.314688ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-network-check-target-ip-10-0-138-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "17202" uid: c3aa12f6-ad8c-4145-84ce-2f01c04d4013 spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:39:30Z" message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.397944ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:46:30Z" - latency: 2.394407ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:45:30Z" - latency: 2.980189ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 2.386632ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 2.587455ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 2.421568ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 2.495462ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 2.369795ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:30Z" - latency: 2.285463ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:30Z" - latency: 2.293572ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:32:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-131-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-131.ec2.internal uid: f73cc904-1f99-4d49-916e-f22611ec00bf resourceVersion: "16559" uid: e23afccc-66d2-4088-85e6-08f45cba5336 spec: sourcePod: network-check-source-869dcfcdcd-7dwvw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T15:38:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 812.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:44:30Z" - latency: 2.364505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:44:30Z" - latency: 1.062979ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:43:30Z" - latency: 1.774805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:43:30Z" - latency: 804.023µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:30Z" - latency: 1.899027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:30Z" - latency: 1.067664ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:30Z" - latency: 1.521178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:41:30Z" - latency: 824.762µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:30Z" - latency: 1.819182ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:40:30Z" kind: List metadata: resourceVersion: ""