Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no api-proxy visible with kubeadm and minor tweaks #170

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

no api-proxy visible with kubeadm and minor tweaks #170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions websrc/source/documents/tutorials/networking-kubernetes-16.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -333,7 +333,7 @@ kube-proxy-kq3nb 1/1 Running 0 24m
kube-scheduler-kubeadm-master 1/1 Running 0 23m
```

You should see contiv-netmaster, contiv-netplugin, contiv-etcd and contiv-api-proxy nodes in `Running` status. A small number of initial restarts are normal while all the pods startup, but you should not see an increasing number here.
You should see contiv-netmaster, contiv-netplugin, and contiv-etcd nodes in `Running` status (and contiv-api-proxy if deployed with kubespray). A small number of initial restarts are normal while all the pods startup, but you should not see a continuous increasing number of restarts.

`netctl` is a utility to create, update, read and modify Contiv objects. It is a CLI wrapper on top of REST interface.

Expand Down Expand Up @@ -398,14 +398,15 @@ eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
```

In the above output, you'll see the following interfaces:
In the above output for the VM, you'll see the following interfaces:

- `docker0` interface corresponds to the linux bridge and its associated
subnet `172.17.0.1/16`. This is created by the docker daemon automatically, and
is the default network containers would belong to when an override network
is not specified.
- `eth0` in this VM is the management interface, on which we ssh into the VM
- `eth1` in this VM is the interface that connects to an external network (if needed)
- `eth2` in this VM is the interface that carries vxlan and control (e.g. etcd) traffic
subnet `172.17.0.1/16`. This is created by the docker daemon automatically,
and containers belong to this network unless an override network is
specified.
- `eth0` is the management interface, on which we ssh into the VM
- `eth1` is the interface that connects to an external network (if needed)
- `eth2` is the interface that carries vxlan and control (e.g. etcd) traffic

```
[vagrant@kubeadm-master ~]$ ifconfig contivh0
Expand Down Expand Up @@ -1026,4 +1027,4 @@ cd cluster && vagrant destroy -f
### Improvements or Comments
This tutorial was developed by Contiv engineers. Thank you for trying out this tutorial.
Please file a GitHub issue if you see an issue with the tutorial, or if you prefer
improving some text, feel free to send a pull request.
improving some text, feel free to send a pull request.