apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "19771" uid: b7ebde32-d333-4ca7-82d0-41ea1e5fd013 spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T11:15:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 1.192685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 939.025µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:27:14Z" - latency: 790.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:26:14Z" - latency: 1.017425ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:25:14Z" - latency: 883.441µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:24:14Z" - latency: 949.061µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:23:14Z" - latency: 1.128087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:22:14Z" - latency: 1.678691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:21:14Z" - latency: 818.415µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:20:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "20918" uid: ded93ff9-39cd-475b-aaa5-bf3f6c140258 spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T11:14:14Z" message: 'load-balancer-api-external: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.983393ms message: 'load-balancer-api-external: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:32:14Z" - latency: 7.741408ms message: 'load-balancer-api-external: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:32:14Z" - latency: 3.728789ms message: 'load-balancer-api-external: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:31:14Z" - latency: 7.926954ms message: 'load-balancer-api-external: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:31:14Z" - latency: 5.912382ms message: 'load-balancer-api-external: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:30:14Z" - latency: 8.332712ms message: 'load-balancer-api-external: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:30:14Z" - latency: 5.666088ms message: 'load-balancer-api-external: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 7.831873ms message: 'load-balancer-api-external: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:29:14Z" - latency: 4.23516ms message: 'load-balancer-api-external: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 7.640541ms message: 'load-balancer-api-external: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:28:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "20919" uid: dd7e5664-d594-4635-9388-55b9ca0617e9 spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T11:14:14Z" message: 'load-balancer-api-internal: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.116338ms message: 'load-balancer-api-internal: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:32:14Z" - latency: 7.67285ms message: 'load-balancer-api-internal: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:32:14Z" - latency: 3.771069ms message: 'load-balancer-api-internal: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:31:14Z" - latency: 7.861414ms message: 'load-balancer-api-internal: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:31:14Z" - latency: 5.883817ms message: 'load-balancer-api-internal: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:30:14Z" - latency: 8.392262ms message: 'load-balancer-api-internal: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:30:14Z" - latency: 5.655846ms message: 'load-balancer-api-internal: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 7.795477ms message: 'load-balancer-api-internal: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:29:14Z" - latency: 4.303782ms message: 'load-balancer-api-internal: tcp connection to a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 7.621801ms message: 'load-balancer-api-internal: resolved host name a5a9473fbbcd74e23bfc6a910b887ee1-9c3d4e0a4105ca29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T11:28:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-ip-10-0-130-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "19769" uid: 6b81eaaf-717a-4413-a1e7-b9c8a986bbb4 spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T11:15:14Z" message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.746014ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 2.223897ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 2.126421ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:27:14Z" - latency: 1.892836ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:26:14Z" - latency: 2.038014ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:25:14Z" - latency: 2.098177ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:24:14Z" - latency: 2.228867ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:23:14Z" - latency: 2.162283ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:22:14Z" - latency: 2.272917ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:21:14Z" - latency: 1.791368ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:20:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-ip-10-0-133-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "19770" uid: 15cf3fc6-f03a-4cdd-8a03-3f367f2e1a7a spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T11:15:14Z" message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.013968ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 2.140588ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 1.948248ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:27:14Z" - latency: 2.059909ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:26:14Z" - latency: 1.988638ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:25:14Z" - latency: 2.402039ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:24:14Z" - latency: 2.387976ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:23:14Z" - latency: 2.377746ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:22:14Z" - latency: 2.037153ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:21:14Z" - latency: 2.10165ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:20:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-ip-10-0-135-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "19768" uid: 2bb08a0d-84f7-460e-a59e-5a03115e762b spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T11:15:14Z" message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.567µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 1.282814ms message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 810.442µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:27:14Z" - latency: 793.062µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:26:14Z" - latency: 772.132µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:25:14Z" - latency: 908.585µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:24:14Z" - latency: 1.240331ms message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:23:14Z" - latency: 1.022895ms message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:22:14Z" - latency: 881.871µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:21:14Z" - latency: 710.835µs message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:20:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T11:08:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-148-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-148.ec2.internal uid: 8a0031e2-3000-4a06-9ebf-d93b507df9fa resourceVersion: "20917" uid: 1fec3390-ec6e-4786-9df4-b05e6b8025ee spec: sourcePod: network-check-source-7f44b6dd87-dp9sg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T11:14:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 735.988µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:32:14Z" - latency: 1.688214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T11:32:14Z" - latency: 1.011745ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:31:14Z" - latency: 1.662664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T11:31:14Z" - latency: 758.933µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:30:14Z" - latency: 1.719743ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T11:30:14Z" - latency: 863.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:29:14Z" - latency: 1.843401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T11:29:14Z" - latency: 1.126282ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T11:28:14Z" - latency: 1.647865ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T11:28:14Z" kind: List metadata: resourceVersion: ""