apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "54483" uid: e94b71f9-7bdf-4b73-aebd-02ee64de2b22 spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T01:11:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 1.110148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 1.565997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 964.332µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 836.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:35:19Z" - latency: 1.158179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:34:19Z" - latency: 1.059951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:33:19Z" - latency: 1.198319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:32:19Z" - latency: 874.238µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:31:19Z" - latency: 1.177706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:30:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "55268" uid: 148315f7-f605-4bde-915e-10f1eb4dd55e spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T01:10:19Z" message: 'load-balancer-api-external: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.088261ms message: 'load-balancer-api-external: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:40:19Z" - latency: 6.218834ms message: 'load-balancer-api-external: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:40:19Z" - latency: 4.727654ms message: 'load-balancer-api-external: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 7.879432ms message: 'load-balancer-api-external: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:39:19Z" - latency: 5.412353ms message: 'load-balancer-api-external: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 7.226938ms message: 'load-balancer-api-external: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:38:19Z" - latency: 4.843236ms message: 'load-balancer-api-external: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 8.458911ms message: 'load-balancer-api-external: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:37:19Z" - latency: 5.38081ms message: 'load-balancer-api-external: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 7.51513ms message: 'load-balancer-api-external: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "55267" uid: 402bb8e7-3d41-4ad0-9854-f2443e404d18 spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T01:10:19Z" message: 'load-balancer-api-internal: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.036477ms message: 'load-balancer-api-internal: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:40:19Z" - latency: 6.29219ms message: 'load-balancer-api-internal: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:40:19Z" - latency: 4.711044ms message: 'load-balancer-api-internal: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 7.839996ms message: 'load-balancer-api-internal: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:39:19Z" - latency: 5.473073ms message: 'load-balancer-api-internal: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 7.284496ms message: 'load-balancer-api-internal: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:38:19Z" - latency: 4.86297ms message: 'load-balancer-api-internal: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 8.376668ms message: 'load-balancer-api-internal: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:37:19Z" - latency: 5.321898ms message: 'load-balancer-api-internal: tcp connection to adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 7.555696ms message: 'load-balancer-api-internal: resolved host name adf308b41021b4e2c851af0278c3ae36-3e4af8bb7aeb9f0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T01:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-network-check-target-ip-10-0-130-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "54481" uid: b418cbab-1669-4c16-b40d-6db7b45de88e spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T01:11:19Z" message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.973652ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 2.023895ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 1.933681ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 2.167009ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 2.091321ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:35:19Z" - latency: 2.106305ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:34:19Z" - latency: 2.389514ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:33:19Z" - latency: 2.178032ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:32:19Z" - latency: 1.773436ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:31:19Z" - latency: 2.220844ms message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:30:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-network-check-target-ip-10-0-142-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "54482" uid: 2e677410-b9d1-4ad6-9375-a865632a2aef spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T01:11:19Z" message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323844ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 2.103317ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 2.343809ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 2.272481ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 2.192354ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:35:19Z" - latency: 2.294357ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:34:19Z" - latency: 2.311796ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:33:19Z" - latency: 2.126166ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:32:19Z" - latency: 2.056562ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:31:19Z" - latency: 2.324471ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:30:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-network-check-target-ip-10-0-142-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "54480" uid: dd538c59-9d7a-4ab1-9422-5f713e533102 spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T01:11:19Z" message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.043094ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 1.218879ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 1.57774ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 1.095369ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 1.420319ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:35:19Z" - latency: 905.227µs message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:34:19Z" - latency: 1.047402ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:33:19Z" - latency: 1.105682ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:32:19Z" - latency: 840.932µs message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:31:19Z" - latency: 960.293µs message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:30:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T01:04:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-55.ec2.internal uid: a79dfd7d-0028-4627-be69-bfc6d4a5eee1 resourceVersion: "55266" uid: 9ade67eb-d6b1-45b1-822b-1271dd205ff0 spec: sourcePod: network-check-source-989f8b8dc-rxrgz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T01:10:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.12µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:40:19Z" - latency: 1.873399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T01:40:19Z" - latency: 932.351µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:39:19Z" - latency: 1.974702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T01:39:19Z" - latency: 845.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:38:19Z" - latency: 2.031817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T01:38:19Z" - latency: 1.083255ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:37:19Z" - latency: 1.731439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T01:37:19Z" - latency: 1.035759ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T01:36:19Z" - latency: 1.846972ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T01:36:19Z" kind: List metadata: resourceVersion: ""