apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "29824" uid: e3b090cd-4f6a-4983-970f-e58c54ba01c3 spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-07T20:03:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.077µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:10:06Z" - latency: 863.679µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:09:06Z" - latency: 867.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 908.002µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 968.749µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 939.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 840.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 886.592µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:03:06Z" - latency: 887.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:02:06Z" - latency: 891.263µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:01:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "28548" uid: 64207897-e5f8-4d16-9d03-8208d87656a8 spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T20:02:06Z" message: 'load-balancer-api-external: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.199845ms message: 'load-balancer-api-external: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 8.184202ms message: 'load-balancer-api-external: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:08:06Z" - latency: 6.549012ms message: 'load-balancer-api-external: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 9.502597ms message: 'load-balancer-api-external: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:07:06Z" - latency: 5.157278ms message: 'load-balancer-api-external: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 6.806391ms message: 'load-balancer-api-external: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:06:06Z" - latency: 5.856758ms message: 'load-balancer-api-external: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 9.67018ms message: 'load-balancer-api-external: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:05:06Z" - latency: 3.739278ms message: 'load-balancer-api-external: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 8.965656ms message: 'load-balancer-api-external: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:04:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "28549" uid: d7f9328d-1bd4-4e44-9fd4-1380f52b9dc5 spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T20:02:06Z" message: 'load-balancer-api-internal: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.555916ms message: 'load-balancer-api-internal: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 8.122729ms message: 'load-balancer-api-internal: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:08:06Z" - latency: 5.304957ms message: 'load-balancer-api-internal: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 9.560359ms message: 'load-balancer-api-internal: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:07:06Z" - latency: 5.221065ms message: 'load-balancer-api-internal: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 6.743818ms message: 'load-balancer-api-internal: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:06:06Z" - latency: 5.837589ms message: 'load-balancer-api-internal: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 9.603754ms message: 'load-balancer-api-internal: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:05:06Z" - latency: 16.733238ms message: 'load-balancer-api-internal: tcp connection to a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 8.932533ms message: 'load-balancer-api-internal: resolved host name a3d83f95bc8e84615a4d890bf49c35c7-dda84d63dd0c6971.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T20:04:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-network-check-target-ip-10-0-132-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "29821" uid: 035e9827-455f-42b7-ac11-fd36ceb0c2d4 spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T20:03:06Z" message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.269713ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:10:06Z" - latency: 843.333µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:09:06Z" - latency: 833.526µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 870.97µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 774.721µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 809.592µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 883.367µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 873.751µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:03:06Z" - latency: 873.31µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:02:06Z" - latency: 796.137µs message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:01:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-network-check-target-ip-10-0-139-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "29823" uid: 0bb8f620-d0c6-4fc3-bd92-80ea0f00d5ae spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-07T20:03:06Z" message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.166488ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:10:06Z" - latency: 2.125154ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:09:06Z" - latency: 1.970783ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 2.302573ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 2.258891ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 2.303094ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 2.07545ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 2.039238ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:03:06Z" - latency: 1.992816ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:02:06Z" - latency: 1.800575ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:01:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-network-check-target-ip-10-0-142-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "29822" uid: ac9b2383-048a-4888-b663-c7d738f6e747 spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T20:03:06Z" message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.927563ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:10:06Z" - latency: 2.429691ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:09:06Z" - latency: 1.916964ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 2.204713ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 2.218241ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 2.257217ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 2.416475ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 2.080029ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:03:06Z" - latency: 2.049125ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:02:06Z" - latency: 2.072873ms message: 'network-check-target-ip-10-0-142-65: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:01:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:56:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-6-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-6.ec2.internal uid: f0af034e-639a-4fc2-a54c-d2fd2ce823c5 resourceVersion: "28547" uid: e0de0455-cec4-4cf2-a142-f2f4825571d0 spec: sourcePod: network-check-source-dbd9cf844-68knb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-07T20:02:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.815µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:08:06Z" - latency: 2.150411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T20:08:06Z" - latency: 1.052095ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:07:06Z" - latency: 1.85243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T20:07:06Z" - latency: 917.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:06:06Z" - latency: 1.750212ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T20:06:06Z" - latency: 772.157µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:05:06Z" - latency: 1.705944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T20:05:06Z" - latency: 960.588µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T20:04:06Z" - latency: 1.850884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T20:04:06Z" kind: List metadata: resourceVersion: ""