Get most services out of the default interface #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ktsakalozos
force-pushed
the
feature/access
branch
2 times, most recently
from
df6cf5f
to
908b9f3
Compare
tvansteenburgh
suggested changes
Sep 11, 2018
README.md
Outdated
| @@ -13,7 +13,7 @@ snap install microk8s --classic --beta | |||
| ``` | |||
|
|
|||
| > At this time microk8s is an early beta, while this should be safe to install please beware. | |||
| > In order to install microk8s make sure port 8080 is not used. | |||
| > There are a few ports that need to be open for microk8s to install successfully. 8080 and 6443 are the most common ones. Please go though the [list of used ports](docs/ports.md) and the security implications involved in installing microk8s. | |||
docs/ports.md
Outdated
|
|
||
| For now microk8s is meant to be used for local development thus certain security issues are not addressed at this point. Here we present the ports and sockets each service uses as well as the default authorisation and authentication configuration. | ||
|
|
||
| Services can be placed in two groups based on the network interface they are bind to. Services binding to the localhost interface are only available from within the host and we take no action to protect them. Services binding to the default host interface are available from outside the host and thus we enforce some form of access restrictions. The ports used by both types of services need to be free so that microk8s starts successfully. |
There was a problem hiding this comment.
"interface they are bound to" or "interface they bind to"
docs/ports.md
Outdated
|
|
||
| Services can be placed in two groups based on the network interface they are bind to. Services binding to the localhost interface are only available from within the host and we take no action to protect them. Services binding to the default host interface are available from outside the host and thus we enforce some form of access restrictions. The ports used by both types of services need to be free so that microk8s starts successfully. | ||
|
|
||
| ### Services Binging to the Default Host Interface |
docs/ports.md
Outdated
| If you remove `--proxy-mode` from `/var/snap/microk8s/current/args/kube-proxy` and `sudo systemctl restart snap.microk8s.daemon-proxy` kube-proxy will stop exposing the cluster hosted services. | ||
|
|
||
|
|
||
| ### Services Binging to the localhost Interface |
docs/ports.md
Outdated
|
|
||
| ## Authentication and Authorization | ||
|
|
||
| Upon a new deployment microk8s creates a new CA, a signed server certificate and a service account key file. These files are stored under `/var/microk8s/current/certs`. Kubelet an the API server are aware of the same CA and so the signed server certificate is used by the API server to authenticate with kubelet (`--kubelet-client-certificate`). Clients talking to the secure port of the API server (`6443`) have to also be aware of the CA (`certificate-authority-data` in user kubeconfig). |
There was a problem hiding this comment.
Kubelet and the API server...
snapcraft.yaml.orig
Outdated
| @@ -0,0 +1,200 @@ | |||
| name: microk8s | |||
There was a problem hiding this comment.
Is this file (snapcraft.yaml.orig) supposed to be here?
ktsakalozos
force-pushed
the
feature/access
branch
from
908b9f3
to
0597630
Compare
Closed
|
Can we test this PR by running the following? Referencing comments in #110 I'm however getting this message: When inspected the changes are not included in the I would like to test this PR (preferably by running |
@nilbot The channel |
ktsakalozos
force-pushed
the
feature/access
branch
from
cc5e232
to
f130b85
Compare
|
Closing this in favor of #323 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ports still used on the default interface:
--proxy-mode=userspacefor compatibility reasons.If you remove
--proxy-modefrom/var/snap/microk8s/current/args/kube-proxyandsudo systemctl restart snap.microk8s.daemon-proxykube-proxy will stop exposing the cluster hosted services.