apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "54288" uid: 6da37680-8bc8-4589-a4c7-b79a55f52ead spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T17:18:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 832.217µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 914.825µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 1.443166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 3.266248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:42:12Z" - latency: 799.869µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:41:12Z" - latency: 1.131794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:40:12Z" - latency: 851.67µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:39:12Z" - latency: 1.20902ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:38:12Z" - latency: 1.415594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:37:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "55324" uid: b7332e83-b8ef-40c9-8e4c-096e39677fd2 spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T17:17:12Z" message: 'load-balancer-api-external: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.131008ms message: 'load-balancer-api-external: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:47:12Z" - latency: 7.888912ms message: 'load-balancer-api-external: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:47:12Z" - latency: 6.038696ms message: 'load-balancer-api-external: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 9.333031ms message: 'load-balancer-api-external: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:46:12Z" - latency: 4.886743ms message: 'load-balancer-api-external: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 8.546583ms message: 'load-balancer-api-external: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:45:12Z" - latency: 4.886381ms message: 'load-balancer-api-external: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 6.594225ms message: 'load-balancer-api-external: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:44:12Z" - latency: 4.761903ms message: 'load-balancer-api-external: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 8.410939ms message: 'load-balancer-api-external: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:43:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "55325" uid: 3d728e26-335e-4b51-bc63-8b56afc5a4e6 spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T17:17:12Z" message: 'load-balancer-api-internal: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.129156ms message: 'load-balancer-api-internal: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:47:12Z" - latency: 7.965027ms message: 'load-balancer-api-internal: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:47:12Z" - latency: 5.958031ms message: 'load-balancer-api-internal: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 9.346815ms message: 'load-balancer-api-internal: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:46:12Z" - latency: 4.868457ms message: 'load-balancer-api-internal: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 8.479333ms message: 'load-balancer-api-internal: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:45:12Z" - latency: 4.948274ms message: 'load-balancer-api-internal: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 6.798251ms message: 'load-balancer-api-internal: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:44:12Z" - latency: 4.416944ms message: 'load-balancer-api-internal: tcp connection to a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 8.394023ms message: 'load-balancer-api-internal: resolved host name a27d38acbc8d7479e8d90028197de7f1-e46d8e0d467e974e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T17:43:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-ip-10-0-133-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "54285" uid: 1f5e120e-263a-4c0b-ac04-9cc9281543bb spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:18:12Z" message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.732µs message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 883.077µs message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 1.170885ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 898.016µs message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 3.920214ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:42:12Z" - latency: 1.035661ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:41:12Z" - latency: 1.598261ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:40:12Z" - latency: 772.879µs message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:39:12Z" - latency: 1.068189ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:38:12Z" - latency: 1.099719ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:37:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-ip-10-0-140-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "54287" uid: 933b286d-ce27-4075-a2f6-710c1ca23bd2 spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:18:12Z" message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.122933ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 2.507181ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 2.363819ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 2.5131ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 2.651594ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:42:12Z" - latency: 2.366332ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:41:12Z" - latency: 2.889423ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:40:12Z" - latency: 2.496306ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:39:12Z" - latency: 2.602277ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:38:12Z" - latency: 2.259761ms message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:37:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-ip-10-0-142-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "54286" uid: 8e8e0bf9-42fc-465d-9b9e-23738a0a2c31 spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:18:12Z" message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.884903ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 2.478263ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 2.205097ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 2.19826ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 4.915287ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:42:12Z" - latency: 2.392773ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:41:12Z" - latency: 2.799016ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:40:12Z" - latency: 2.332736ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:39:12Z" - latency: 2.222032ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:38:12Z" - latency: 2.27916ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:37:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:11:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: 791ad969-42bc-4888-ba47-98341f399b25 resourceVersion: "55322" uid: b8775d94-9ad7-4eb2-b1c8-b03ee8f44937 spec: sourcePod: network-check-source-989f8b8dc-7fpsc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T17:17:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.182µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:47:12Z" - latency: 1.663108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T17:47:12Z" - latency: 1.016217ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:46:12Z" - latency: 1.802879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T17:46:12Z" - latency: 812.493µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:45:12Z" - latency: 1.712133ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T17:45:12Z" - latency: 960.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:44:12Z" - latency: 1.973927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T17:44:12Z" - latency: 958.196µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T17:43:12Z" - latency: 1.717692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T17:43:12Z" kind: List metadata: resourceVersion: ""