• Kubernetes 集群中节点的 INTERNAL-IP 问题

    calendar Apr 8, 2020   ---   · 2 min read · Network Docker  ·
    Share on: linkedin copy
    Kubernetes 集群中节点的 INTERNAL-IP 问题
    用自己 Kubernetes 学习笔记(一) - 初上手 一文中的方法用 Vagrant 虚拟机安装的 Kubernetes 集群，部署应用什么的都没问题，然而却在用
    $ kubectl exec -it <pod-name> -- sh
    试图登陆 docker 容器时出问题了，总是报错说
    error: unable to upgrade connection: pod does not exist
    kubectl 登陆不了 docker 容器，而且  kubectl logs 也会报一样的错，必须到具体的工作节点上用 docker exec 或 docker logs 才能访问到该节点上的容器信息。

    这就不太对头，网上找了下原因，结果是因为节点间通信时选错了 IP 地址。

    比如三个 Vagrant 虚拟机分别是
    1. k8s-master (172.28.128.14)
    2. k8s-node1 (172.28.128.10)
    3. k8s-node2 (172.28.128.11)

    在 k8s-master 中初始集群时用的命令也是指定的 172.28.128.14 IP 地址 Read More

  • Using Network Link Conditioner in iOS 6

    calendar Jun 23, 2013   ---   · 3 min read · Network Mobile ios  ·
    Share on: linkedin copy
    来到芝加哥后好久没写博客了，有些文章本想翻译后介绍给大家，可如今越发没先前那翻译的意愿了，所以不妨直接贴出原文如下：

    I previously covered using Network Link Conditioner to test how your app does in less-than-ideal network scenarios. One of the inconveniences of using it is in order to test your app on a device, you have to take the extra steps to configure a proxy on your computer that your device can connect to over a wi-fi connection. Well, not anymore. With iOS 6, Apple has given us Network Link Conditioner right on the device.

    To get started with Network Link Conditioner, first your device must be set up as a developer device. If you haven’t done this yet, you’ll need to go to Xcode, open Organizer (Shift-Command-2), select your device, and click the button that says Use for Development to add the device your developer account. Once you’ve done that, you should be able to open Settings on your device and see a Developer menu near the bottom, just above the apps list. Tapping on that reveals some helpful settings, Network Link Conditioner Status obviously being the one relevant to our interests here. Read More