apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:31:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "143957" uid: d5530a4c-2277-49cc-b1f7-ff31f1e7bfc7 spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T17:38:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.381849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:34:15Z" - latency: 1.32752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:33:15Z" - latency: 1.072152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:32:15Z" - latency: 1.599017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:15Z" - latency: 1.470756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:15Z" - latency: 1.167119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:15Z" - latency: 1.166313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:15Z" - latency: 1.164231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:15Z" - latency: 1.12927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:26:15Z" - latency: 1.342235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:25:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:31:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "141834" uid: c556e952-d866-4895-a198-fa3a24d9962f spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:37:15Z" message: 'load-balancer-api-external: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.528953ms message: 'load-balancer-api-external: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:15Z" - latency: 6.788524ms message: 'load-balancer-api-external: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:31:15Z" - latency: 15.543357ms message: 'load-balancer-api-external: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:15Z" - latency: 8.378076ms message: 'load-balancer-api-external: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:30:15Z" - latency: 14.197526ms message: 'load-balancer-api-external: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:15Z" - latency: 6.601002ms message: 'load-balancer-api-external: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:29:15Z" - latency: 14.511986ms message: 'load-balancer-api-external: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:15Z" - latency: 6.515075ms message: 'load-balancer-api-external: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:28:15Z" - latency: 14.354015ms message: 'load-balancer-api-external: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:15Z" - latency: 6.821694ms message: 'load-balancer-api-external: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:27:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:31:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "141833" uid: 561bdcbc-399b-4142-b45e-90b97f894280 spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:37:15Z" message: 'load-balancer-api-internal: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.554749ms message: 'load-balancer-api-internal: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:15Z" - latency: 7.026427ms message: 'load-balancer-api-internal: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:31:15Z" - latency: 13.899055ms message: 'load-balancer-api-internal: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:15Z" - latency: 8.461333ms message: 'load-balancer-api-internal: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:30:15Z" - latency: 16.055524ms message: 'load-balancer-api-internal: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:15Z" - latency: 6.707869ms message: 'load-balancer-api-internal: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:29:15Z" - latency: 15.65996ms message: 'load-balancer-api-internal: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:15Z" - latency: 6.58827ms message: 'load-balancer-api-internal: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:28:15Z" - latency: 14.216045ms message: 'load-balancer-api-internal: tcp connection to afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:15Z" - latency: 6.880447ms message: 'load-balancer-api-internal: resolved host name afd4fa48ebce84d46839d4698f22b62b-b4824c7bf6aceb51.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:27:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:31:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-network-check-target-ip-10-0-136-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "143954" uid: 2f8ceadb-2221-4b9d-b665-01ccb6452b68 spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:38:15Z" message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.313048ms message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:34:15Z" - latency: 968.614µs message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:33:15Z" - latency: 1.279362ms message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:32:15Z" - latency: 950.219µs message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:15Z" - latency: 1.00875ms message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:15Z" - latency: 791.066µs message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:15Z" - latency: 962.565µs message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:15Z" - latency: 907.571µs message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:15Z" - latency: 1.072433ms message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:26:15Z" - latency: 1.769391ms message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:25:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:11:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-network-check-target-ip-10-0-141-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "142842" uid: 1e448400-42be-4b40-84d0-e38da67eecc0 spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T18:18:18Z" message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.156001ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:32:18Z" - latency: 2.291069ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:18Z" - latency: 2.314276ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:18Z" - latency: 1.116109ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:18Z" - latency: 2.246599ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:18Z" - latency: 2.223941ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:18Z" - latency: 2.278683ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:26:18Z" - latency: 1.055625ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:25:18Z" - latency: 1.10203ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:24:18Z" - latency: 853.704µs message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:23:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:31:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-network-check-target-ip-10-0-142-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "143955" uid: ffcd6ed7-50fc-4eba-89db-e31aaf1e8a09 spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:38:15Z" message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.341067ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:34:15Z" - latency: 2.322727ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:33:15Z" - latency: 1.993501ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:32:15Z" - latency: 2.284911ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:15Z" - latency: 2.349306ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:15Z" - latency: 2.439455ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:15Z" - latency: 2.233591ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:15Z" - latency: 1.920023ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:15Z" - latency: 2.370292ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:26:15Z" - latency: 2.787791ms message: 'network-check-target-ip-10-0-142-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:25:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:31:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-153-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-153.ec2.internal uid: 14136a4c-77f9-448f-83df-b5641078bebb resourceVersion: "141831" uid: d51aaa3c-107d-4e2b-b53a-f24edde622f3 spec: sourcePod: network-check-source-6f78d59f99-5fvrw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T17:37:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.056748ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:31:15Z" - latency: 1.794695ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:31:15Z" - latency: 913.598µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:30:15Z" - latency: 1.984208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:30:15Z" - latency: 1.986233ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:29:15Z" - latency: 1.890624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:29:15Z" - latency: 1.037536ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:28:15Z" - latency: 1.61006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:28:15Z" - latency: 820.396µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:27:15Z" - latency: 1.851091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:27:15Z" kind: List metadata: resourceVersion: ""