apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "53691" uid: dc8239a4-adfa-4eec-9555-95925d267b3f spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T11:20:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.034173ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 899.902µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 863.832µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 1.491382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 1.221644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:44:59Z" - latency: 842.204µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:43:59Z" - latency: 1.509254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:42:59Z" - latency: 942.647µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:41:59Z" - latency: 855.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:40:59Z" - latency: 937.198µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "54738" uid: 265b1c3e-a675-4f79-8994-2eb24d7fbdd3 spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T11:19:59Z" message: 'load-balancer-api-external: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.514774ms message: 'load-balancer-api-external: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:59Z" - latency: 7.04902ms message: 'load-balancer-api-external: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:49:59Z" - latency: 6.259556ms message: 'load-balancer-api-external: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 8.008063ms message: 'load-balancer-api-external: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:48:59Z" - latency: 4.343682ms message: 'load-balancer-api-external: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 10.375888ms message: 'load-balancer-api-external: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:47:59Z" - latency: 6.263913ms message: 'load-balancer-api-external: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 6.826544ms message: 'load-balancer-api-external: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:46:59Z" - latency: 3.89322ms message: 'load-balancer-api-external: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 7.180459ms message: 'load-balancer-api-external: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:45:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "54739" uid: 95001408-e9af-47ab-98f2-8d032d0f803b spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T11:19:59Z" message: 'load-balancer-api-internal: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.506157ms message: 'load-balancer-api-internal: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:59Z" - latency: 6.972564ms message: 'load-balancer-api-internal: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:49:59Z" - latency: 3.997923ms message: 'load-balancer-api-internal: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 7.951149ms message: 'load-balancer-api-internal: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:48:59Z" - latency: 5.960043ms message: 'load-balancer-api-internal: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 10.40445ms message: 'load-balancer-api-internal: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:47:59Z" - latency: 3.897246ms message: 'load-balancer-api-internal: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 6.856719ms message: 'load-balancer-api-internal: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:46:59Z" - latency: 3.895797ms message: 'load-balancer-api-internal: tcp connection to a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 7.241977ms message: 'load-balancer-api-internal: resolved host name a660f4a278f6347cc8c2df3380f0f458-68daa2d478af1759.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:45:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-network-check-target-ip-10-0-136-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "53688" uid: 68f48a28-f16e-41f4-89c9-61b595b0fd9d spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:20:59Z" message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.818207ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 1.958184ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 1.824611ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 2.069757ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 1.940462ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:44:59Z" - latency: 1.831377ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:43:59Z" - latency: 2.009745ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:42:59Z" - latency: 1.874223ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:41:59Z" - latency: 1.435066ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:40:59Z" - latency: 2.077202ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-network-check-target-ip-10-0-137-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "53689" uid: 941f42dc-1b21-4c42-97a1-87fde644b822 spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:20:59Z" message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.176472ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 2.186268ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 1.88011ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 2.129629ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 2.140542ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:44:59Z" - latency: 1.98425ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:43:59Z" - latency: 2.327433ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:42:59Z" - latency: 1.823424ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:41:59Z" - latency: 1.944212ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:40:59Z" - latency: 2.32399ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-network-check-target-ip-10-0-142-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "53687" uid: 076eb192-4128-4374-af3d-b596f613bf9b spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:20:59Z" message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.891µs message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 1.56274ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 1.229816ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 1.78725ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 940.321µs message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:44:59Z" - latency: 1.110235ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:43:59Z" - latency: 1.153697ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:42:59Z" - latency: 1.367941ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:41:59Z" - latency: 1.237178ms message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:40:59Z" - latency: 990.118µs message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:13:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-39.ec2.internal uid: 075d6d6e-817c-4272-baba-6117a12932b5 resourceVersion: "54737" uid: 7f456834-9463-47b2-89cd-a9ed28d7ee15 spec: sourcePod: network-check-source-989f8b8dc-r6v22 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T11:19:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:59Z" - latency: 1.897944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:49:59Z" - latency: 902.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:59Z" - latency: 1.649121ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:48:59Z" - latency: 967.864µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:59Z" - latency: 2.410733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:47:59Z" - latency: 788.546µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:59Z" - latency: 1.786285ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:46:59Z" - latency: 912.208µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:59Z" - latency: 1.710737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:45:59Z" kind: List metadata: resourceVersion: ""