apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "43188" uid: c41b60a4-6575-4e00-b07b-60487da58651 spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T15:43:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.76µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 902.28µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 1.151378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 1.02478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:14Z" - latency: 1.135061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:14Z" - latency: 1.075152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:59:14Z" - latency: 967.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:58:14Z" - latency: 875.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:57:14Z" - latency: 1.031744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:56:14Z" - latency: 1.063264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "45667" uid: aeacc4b3-d46e-4153-b2ab-fe5ac6d899bf spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T15:42:14Z" message: 'load-balancer-api-external: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.801042ms message: 'load-balancer-api-external: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:14Z" - latency: 6.77811ms message: 'load-balancer-api-external: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:06:14Z" - latency: 4.124396ms message: 'load-balancer-api-external: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:14Z" - latency: 6.662892ms message: 'load-balancer-api-external: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:05:14Z" - latency: 3.616627ms message: 'load-balancer-api-external: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 13.744708ms message: 'load-balancer-api-external: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:04:14Z" - latency: 3.688972ms message: 'load-balancer-api-external: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 6.962572ms message: 'load-balancer-api-external: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:03:14Z" - latency: 5.75444ms message: 'load-balancer-api-external: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 7.081362ms message: 'load-balancer-api-external: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "45666" uid: 4ecf67e8-2de1-4fcf-9b32-41d284d344e2 spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T15:42:14Z" message: 'load-balancer-api-internal: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.663891ms message: 'load-balancer-api-internal: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:14Z" - latency: 6.89331ms message: 'load-balancer-api-internal: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:06:14Z" - latency: 4.465385ms message: 'load-balancer-api-internal: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:14Z" - latency: 6.687457ms message: 'load-balancer-api-internal: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:05:14Z" - latency: 3.607197ms message: 'load-balancer-api-internal: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 13.768491ms message: 'load-balancer-api-internal: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:04:14Z" - latency: 3.555622ms message: 'load-balancer-api-internal: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 6.923051ms message: 'load-balancer-api-internal: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:03:14Z" - latency: 4.231876ms message: 'load-balancer-api-internal: tcp connection to a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 7.124949ms message: 'load-balancer-api-internal: resolved host name a26f35d3e346545fe843d616f8496ba2-efad3beb5f1f5e0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-132-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "43185" uid: 035e40cc-33e9-418c-93c5-b18b16d8ce27 spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:43:14Z" message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.218µs message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 1.286712ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 1.188335ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 1.0611ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:14Z" - latency: 1.149089ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:14Z" - latency: 891.807µs message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:59:14Z" - latency: 1.122325ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:58:14Z" - latency: 850.568µs message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:57:14Z" - latency: 1.077712ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:56:14Z" - latency: 918.938µs message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-135-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "43187" uid: fd50dffe-fa5d-4ece-8e44-866e07f5a573 spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:43:14Z" message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.319564ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 1.971393ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 2.150957ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 2.153594ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:14Z" - latency: 2.078106ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:14Z" - latency: 2.093874ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:59:14Z" - latency: 2.543455ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:58:14Z" - latency: 2.060005ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:57:14Z" - latency: 2.371273ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:56:14Z" - latency: 2.143375ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-141-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "43186" uid: 51d4c0d5-c90f-465e-a722-57ef00d3c9fe spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:43:14Z" message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.261734ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 2.254377ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 2.254872ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 2.358321ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:14Z" - latency: 2.315662ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:14Z" - latency: 2.263554ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:59:14Z" - latency: 2.320805ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:58:14Z" - latency: 2.285697ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:57:14Z" - latency: 2.187803ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:56:14Z" - latency: 2.067325ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:36:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: 6e30f49f-fb75-454d-92db-4823e737a5a1 resourceVersion: "45665" uid: 8853a32b-358b-498d-9d8d-5b62bc2ad6ea spec: sourcePod: network-check-source-7f44b6dd87-ddn7l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T15:42:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 777.786µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:14Z" - latency: 1.576652ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:06:14Z" - latency: 1.081574ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:14Z" - latency: 1.926335ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:05:14Z" - latency: 868.476µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:14Z" - latency: 1.76896ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:04:14Z" - latency: 804.395µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:14Z" - latency: 1.956832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:03:14Z" - latency: 910.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:14Z" - latency: 2.345704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:02:14Z" kind: List metadata: resourceVersion: ""