This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
feat: initial support for amazon-vpc-cni-k8s #1463
Merged
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
k8s-ci-robot
added
cncf-cla: yes
Codecov Report
@@ Coverage Diff @@
## master #1463 +/- ##
==========================================
- Coverage 38.1% 37.88% -0.22%
==========================================
Files 74 75 +1
Lines 4559 4593 +34
==========================================
+ Hits 1737 1740 +3
- Misses 2580 2611 +31
Partials 242 242
Continue to review full report at Codecov.
|
mumoshu
force-pushed
the
amazon-vpc-cni-k8s
branch
from
73d3b68
to
9902c92
Compare
k8s-ci-robot
added
size/XXL
mumoshu
force-pushed
the
amazon-vpc-cni-k8s
branch
from
f1a6e44
to
3dac0ff
Compare
Add the below configuration to your `cluster.yaml` and then `amazon-vpc-cni-k8s` is installed as a daemonset for assigning VPC private IP addresses to your K8S pods.
```yaml
kubernetes:
networking:
amazonVPC:
enabled: true
```
Controller nodes have a k8s manifest file for installing amazon-vpc-cni-k8s daemonset. It adds an init container to copy all the cni binaries bundled to the hyperkube image. Otherwise amazon-vpc-cni-k8s doesn't work due to missing the `loopback` cni bin.
kubelet on worker and controller nodes now have appropriate `--node-ip` and `--max-pods` settings to make amazon-vpc-cni-k8s reliably work.
This is one of prerequisites towards the EKS support.
ref kubernetes-retired#1434
Just because it is the latest release and I've used it for testing in combination with the initial amazon-vpc-cni-k8s support.
The extraneous `}` in a line for installing the dashboard has been preventing the `install-kube-system` script from succeeding. This fixes that.
mumoshu
force-pushed
the
amazon-vpc-cni-k8s
branch
from
3dac0ff
to
5dad6f8
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add the below configuration to your
cluster.yamland thenamazon-vpc-cni-k8sis installed as a daemonset for assigning VPC private IP addresses to your K8S pods.Controller nodes have a k8s manifest file for installing amazon-vpc-cni-k8s daemonset. It adds an init container to copy all the cni binaries bundled to the hyperkube image. Otherwise amazon-vpc-cni-k8s doesn't work due to missing the
loopbackcni bin.kubelet on worker and controller nodes now have appropriate
--node-ipand--max-podssettings to make amazon-vpc-cni-k8s reliably work.This is one of prerequisites towards the EKS support.
TODOs:
--max-podsshould be set to an appropriately computed value as per https://github.com/aws/amazon-vpc-cni-k8s#setup--cni-conf-dir=/etc/cni/net.dby defaut. kube-aws uses/etc/kubernets/cni/net.dso amazon-vpc-cni-k8s should be configured accordingly.ref #1434