apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "45607" uid: 9829d0b7-0668-47ec-8856-84386e041f60 spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-13T01:24:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 1.06272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 996.175µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 1.166375ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:42:10Z" - latency: 1.472407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:41:10Z" - latency: 1.059146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:40:10Z" - latency: 980.443µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:39:10Z" - latency: 871.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:38:10Z" - latency: 981.334µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:37:10Z" - latency: 1.376999ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:36:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "47664" uid: 3e6bfe00-fc49-4410-9d4d-af36c64c2b22 spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T01:23:10Z" message: 'load-balancer-api-external: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.835769ms message: 'load-balancer-api-external: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:47:10Z" - latency: 9.648165ms message: 'load-balancer-api-external: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:47:10Z" - latency: 4.627661ms message: 'load-balancer-api-external: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:46:10Z" - latency: 8.015214ms message: 'load-balancer-api-external: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:46:10Z" - latency: 7.353181ms message: 'load-balancer-api-external: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 9.0324ms message: 'load-balancer-api-external: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:45:10Z" - latency: 4.11668ms message: 'load-balancer-api-external: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 8.173236ms message: 'load-balancer-api-external: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:44:10Z" - latency: 4.381271ms message: 'load-balancer-api-external: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 11.260889ms message: 'load-balancer-api-external: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:43:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "47665" uid: 56785a69-d636-4ea5-aeb0-98744336c176 spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T01:23:10Z" message: 'load-balancer-api-internal: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.848087ms message: 'load-balancer-api-internal: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:47:10Z" - latency: 9.725352ms message: 'load-balancer-api-internal: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:47:10Z" - latency: 4.656345ms message: 'load-balancer-api-internal: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:46:10Z" - latency: 7.972507ms message: 'load-balancer-api-internal: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:46:10Z" - latency: 7.319206ms message: 'load-balancer-api-internal: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 9.060018ms message: 'load-balancer-api-internal: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:45:10Z" - latency: 4.079245ms message: 'load-balancer-api-internal: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 8.248891ms message: 'load-balancer-api-internal: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:44:10Z" - latency: 4.336646ms message: 'load-balancer-api-internal: tcp connection to a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 11.306018ms message: 'load-balancer-api-internal: resolved host name a9c8e7dae206e447d96c54e0a3145ef0-95734489634decdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:43:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-network-check-target-ip-10-0-136-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "45606" uid: 31a40bf5-deef-48ec-afd2-e04a75358e03 spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T01:24:10Z" message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.477862ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 2.396644ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 2.337051ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 2.32048ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:42:10Z" - latency: 2.370478ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:41:10Z" - latency: 2.430826ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:40:10Z" - latency: 2.558013ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:39:10Z" - latency: 2.06787ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:38:10Z" - latency: 2.354471ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:37:10Z" - latency: 2.567644ms message: 'network-check-target-ip-10-0-136-115: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:36:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-network-check-target-ip-10-0-140-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "45604" uid: c972abfd-7b00-4bb8-bb6e-9ce44e464eed spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T01:24:10Z" message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.325458ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 1.338056ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 958.335µs message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 850.899µs message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:42:10Z" - latency: 946.834µs message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:41:10Z" - latency: 1.567264ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:40:10Z" - latency: 898.959µs message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:39:10Z" - latency: 806.333µs message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:38:10Z" - latency: 886.399µs message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:37:10Z" - latency: 1.534405ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:36:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-network-check-target-ip-10-0-143-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "45605" uid: 0f9cb1e0-f06b-4aab-9348-84b0eb43bbd2 spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-13T01:24:10Z" message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.137461ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 2.479306ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 2.383999ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 2.496631ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:42:10Z" - latency: 2.743041ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:41:10Z" - latency: 2.251206ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:40:10Z" - latency: 2.485709ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:39:10Z" - latency: 2.160139ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:38:10Z" - latency: 2.673266ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:37:10Z" - latency: 2.5724ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:36:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:17:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-236-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-236.ec2.internal uid: 631b4178-4fb3-4590-ab0b-8748ee263f8f resourceVersion: "47663" uid: 2c1d0df1-e6e1-459c-bf14-8285d168c592 spec: sourcePod: network-check-source-6947749cfc-9skm6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-13T01:23:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.779µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:47:10Z" - latency: 1.804941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:47:10Z" - latency: 1.021766ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:46:10Z" - latency: 1.811241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:46:10Z" - latency: 1.151031ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:45:10Z" - latency: 2.185561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:45:10Z" - latency: 834.367µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:44:10Z" - latency: 1.953574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:44:10Z" - latency: 865.591µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:43:10Z" - latency: 1.660029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:43:10Z" kind: List metadata: resourceVersion: ""