apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "52230" uid: 5af27df1-1e24-45f5-a960-70333a56391e spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T21:17:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.305293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 1.126805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 1.057748ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 846.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 1.168855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:50Z" - latency: 965.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:50Z" - latency: 867.24µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:50Z" - latency: 1.397664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:38:50Z" - latency: 982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:37:50Z" - latency: 1.1632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:36:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "53179" uid: e4711eb2-d3c4-4da4-84df-4a54218f0d5f spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:16:50Z" message: 'load-balancer-api-external: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.908641ms message: 'load-balancer-api-external: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:50Z" - latency: 8.961257ms message: 'load-balancer-api-external: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:46:50Z" - latency: 5.833828ms message: 'load-balancer-api-external: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 7.613627ms message: 'load-balancer-api-external: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:45:50Z" - latency: 5.75498ms message: 'load-balancer-api-external: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 12.56411ms message: 'load-balancer-api-external: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:50Z" - latency: 4.754219ms message: 'load-balancer-api-external: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 7.631898ms message: 'load-balancer-api-external: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:50Z" - latency: 4.955006ms message: 'load-balancer-api-external: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 9.238423ms message: 'load-balancer-api-external: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "53180" uid: 530e1388-6ee3-48b5-8bcb-c0cc24de14e8 spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:16:50Z" message: 'load-balancer-api-internal: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.429258ms message: 'load-balancer-api-internal: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:50Z" - latency: 9.051958ms message: 'load-balancer-api-internal: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:46:50Z" - latency: 5.802865ms message: 'load-balancer-api-internal: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 7.661004ms message: 'load-balancer-api-internal: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:45:50Z" - latency: 5.751456ms message: 'load-balancer-api-internal: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 12.290668ms message: 'load-balancer-api-internal: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:50Z" - latency: 4.683091ms message: 'load-balancer-api-internal: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 7.516422ms message: 'load-balancer-api-internal: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:50Z" - latency: 4.968711ms message: 'load-balancer-api-internal: tcp connection to a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 9.260941ms message: 'load-balancer-api-internal: resolved host name a9ff363d7e297432a81353775c55a259-1da3544b1c3ef6fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-network-check-target-ip-10-0-128-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "52229" uid: 1567317a-513a-4968-8177-76f638282e5a spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:17:50Z" message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.152457ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 2.307862ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 2.033056ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 1.653772ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 2.26459ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:50Z" - latency: 1.92546ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:50Z" - latency: 1.913325ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:50Z" - latency: 1.797966ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:38:50Z" - latency: 1.785888ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:37:50Z" - latency: 1.71018ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:36:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-network-check-target-ip-10-0-129-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "52227" uid: 2aa2c712-9ab0-4841-aef2-bce4aaf57868 spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:17:50Z" message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.4µs message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 3.595453ms message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 1.041092ms message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 955.831µs message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 1.310042ms message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:50Z" - latency: 864.928µs message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:50Z" - latency: 1.203506ms message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:50Z" - latency: 956.505µs message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:38:50Z" - latency: 1.825459ms message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:37:50Z" - latency: 944.694µs message: 'network-check-target-ip-10-0-129-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:36:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-network-check-target-ip-10-0-143-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "52228" uid: bf5c2c02-ba17-442a-b2fb-8771e47fcfa4 spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:17:50Z" message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.404824ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 2.159873ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 2.183774ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 1.96995ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 2.071035ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:50Z" - latency: 1.944564ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:50Z" - latency: 2.439268ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:50Z" - latency: 2.305881ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:38:50Z" - latency: 2.22151ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:37:50Z" - latency: 2.513123ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:36:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-60-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-60.ec2.internal uid: d3663eef-c593-4c04-84af-e956a78b7a01 resourceVersion: "53178" uid: dd9a5425-d44a-4e13-857e-16b59b6ce0a4 spec: sourcePod: network-check-source-869dcfcdcd-j6r5j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T21:16:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:50Z" - latency: 2.637824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:46:50Z" - latency: 1.082919ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:50Z" - latency: 2.157298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:45:50Z" - latency: 827.338µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:50Z" - latency: 4.29992ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:50Z" - latency: 926.351µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:50Z" - latency: 1.920864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:50Z" - latency: 920.908µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:50Z" - latency: 2.406229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:50Z" kind: List metadata: resourceVersion: ""