apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "75287" uid: a61af4fe-b44f-4f34-8491-19b3afc5f685 spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T22:19:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.331545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:01:56Z" - latency: 1.108338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 1.385921ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 880.365µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 1.112528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 971.183µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 1.153816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:55:56Z" - latency: 1.279418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:54:56Z" - latency: 916.632µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:53:56Z" - latency: 1.553751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "72680" uid: 29edaef4-5ec5-4a83-8133-508d7838753a spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T22:18:56Z" message: 'load-balancer-api-external: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.812246ms message: 'load-balancer-api-external: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 13.106261ms message: 'load-balancer-api-external: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T23:00:56Z" - latency: 4.314735ms message: 'load-balancer-api-external: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 7.128596ms message: 'load-balancer-api-external: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:59:56Z" - latency: 3.660163ms message: 'load-balancer-api-external: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 13.984475ms message: 'load-balancer-api-external: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:58:56Z" - latency: 4.433649ms message: 'load-balancer-api-external: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 10.024322ms message: 'load-balancer-api-external: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:57:56Z" - latency: 4.720881ms message: 'load-balancer-api-external: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 11.075362ms message: 'load-balancer-api-external: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:56:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "72681" uid: dad1c19b-4d3a-495c-ad4b-595b385ea84a spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T22:18:56Z" message: 'load-balancer-api-internal: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.9117ms message: 'load-balancer-api-internal: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 13.196908ms message: 'load-balancer-api-internal: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T23:00:56Z" - latency: 4.312098ms message: 'load-balancer-api-internal: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 7.28323ms message: 'load-balancer-api-internal: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:59:56Z" - latency: 4.928108ms message: 'load-balancer-api-internal: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 13.928228ms message: 'load-balancer-api-internal: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:58:56Z" - latency: 4.871477ms message: 'load-balancer-api-internal: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 10.232115ms message: 'load-balancer-api-internal: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:57:56Z" - latency: 4.246786ms message: 'load-balancer-api-internal: tcp connection to ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 11.126726ms message: 'load-balancer-api-internal: resolved host name ad6eec89356974465ba8babce45ee29d-e8d51532aa4955be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T22:56:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-129-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "75285" uid: ac880962-fe66-4538-8735-392e4b5e9334 spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T22:19:56Z" message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.167052ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:01:56Z" - latency: 2.178981ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 2.167131ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 1.883053ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 1.821728ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 2.114806ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 2.103173ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:55:56Z" - latency: 1.969228ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:54:56Z" - latency: 1.922611ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:53:56Z" - latency: 2.475844ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-141-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "75286" uid: a9e225be-4511-4b73-b7f8-9a08387c126c spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T22:19:56Z" message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.406705ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:01:56Z" - latency: 2.338367ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 2.482743ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 2.587531ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 1.932147ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 2.176558ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 2.393906ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:55:56Z" - latency: 2.337926ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:54:56Z" - latency: 2.326275ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:53:56Z" - latency: 2.380852ms message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-142-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "75283" uid: c663d956-0ceb-4413-9ad0-0bc992270cff spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T22:19:56Z" message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.446µs message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:01:56Z" - latency: 1.039579ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 1.469103ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 969.047µs message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 1.221173ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 1.057531ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 907.371µs message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:55:56Z" - latency: 919.242µs message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:54:56Z" - latency: 1.133622ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:53:56Z" - latency: 1.103412ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T22:12:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-132-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-132.ec2.internal uid: b58f9063-b52e-4cdb-9cda-92dd56645f4c resourceVersion: "72679" uid: a76f1667-e468-4873-a97c-4cf69c001afa spec: sourcePod: network-check-source-7d88cb55d8-bgl6d targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T22:18:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.123427ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T23:00:56Z" - latency: 1.857927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T23:00:56Z" - latency: 942.992µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:59:56Z" - latency: 1.788023ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T22:59:56Z" - latency: 911.593µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:58:56Z" - latency: 1.808542ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T22:58:56Z" - latency: 1.053656ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:57:56Z" - latency: 2.025006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T22:57:56Z" - latency: 1.159491ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T22:56:56Z" - latency: 2.198123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T22:56:56Z" kind: List metadata: resourceVersion: ""