Comments (19)
Hi, I would also be interested in this. I'm trying to put together a Kubeadm-based cluster on AWS at the moment and struggling to get the Cloud Provider integration to advance beyond my worker nodes being tainted with:
node.cloudprovider.kubernetes.io/uninitialized
Their hostnames are the EC2 DNS name:
$> hostname -f
ip-10-0-10-91.us-gov-west-1.compute.internal
My Kubeadm config files set the cloud provider to external
in four places
# Present in both KubeletConfiguration and InitConfiguration
nodeRegistration:
kubeletExtraArgs:
cloud-provider: external
# Present in ClusterConfiguration
apiServer:
extraArgs:
cloud-provider: external
# Present in ClusterConfiguration
controllerManager:
extraArgs:
cloud-provider: external
The EC2 instances as well as my route tables, subnets, etc are tagged with:
"kubernetes.io/cluster/${var.K8S_CLUSTER_NAME}" = "kubernetes.io/cluster/${var.K8S_CLUSTER_NAME}"
And my EC2 instances were launched with an instance profile with the IAM policies outlined in the README:
$> aws ec2 describe-instances --instance-ids INSTANCE.ID | jq '.Reservations[].Instances[].IamInstanceProfile[]'
"arn:aws-us-gov:iam::ACCOUNT.ID:instance-profile/PROFILE-NAME"
from cloud-provider-aws.
Got this squared away thanks to the help of @andrewsykim.
I had to make a few changes. First of all, if you look in the manifests directory on the root of the repo there is a DaemonSet and an RBAC schema. These both need to be deployed and operational on your cluster for your nodes to be initialized.
You'll notice that the DaemonSet doesn't have an image reference. This is because the AWS Cloud Controller Manager isn't officially publicly hosted yet. You'll need to build it yourself or use one on DockerHub. Here's the one I made from the newest commit from three days ago.
You might also notice that there is an --cloud-provider=aws
argument passed to the container despite being the external
provisioner. This is intentional.
Lastly, you'll need to ensure that all of your EC2 instances have this tag: KubernetesCluster = var.K8S_CLUSTER_NAME
where var.K8S_CLUSTER_NAME
is the name of your cluster.
from cloud-provider-aws.
Not that it's related to cloud-provider-aws
documentation but to your observation regarding the official docs on how and when the --cloud-provider
flag should be not used/used: kubernetes/website#20137
from cloud-provider-aws.
/assign
from cloud-provider-aws.
Looking for feedback on what the documentation site should look like #102
from cloud-provider-aws.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
from cloud-provider-aws.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
from cloud-provider-aws.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
from cloud-provider-aws.
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from cloud-provider-aws.
/reopen
/remove-lifecycle rotten
from cloud-provider-aws.
@andrewsykim: Reopened this issue.
In response to this:
/reopen
/remove-lifecycle rotten
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from cloud-provider-aws.
We have a docs site here https://cloud-provider-aws.sigs.k8s.io/ but we need help with content
from cloud-provider-aws.
/help wanted
from cloud-provider-aws.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
from cloud-provider-aws.
/remove-lifecycle stale
from cloud-provider-aws.
We are in the process of updating the docs and adding a new docs site. I'll keep this issue updated.
from cloud-provider-aws.
Follow progress here:
https://kubernetes.github.io/cloud-provider-aws/
Also the README has been updated: https://github.com/kubernetes/cloud-provider-aws/blob/master/README.md but ideally that information should be included in the home page of the docs site too.
from cloud-provider-aws.
/assign
from cloud-provider-aws.
Documentation will be available here going forward: https://cloud-provider-aws.sigs.k8s.io/
We will continue working on the docs, but I think we've made enough initial progress that I can close this issue. Please feel free to open specific issues if you feel certain areas are lacking documentation.
from cloud-provider-aws.
Related Issues (20)
- Dependency update tool Check fails in CLOMonitor HOT 5
- Release Automation for Primary Artifacts HOT 6
- Finding the ProviderID fails when using a custom domain in the dhcp options HOT 12
- /etc/eks/image-credential-provider/ecr-credential-provider HOT 1
- `service.beta.kubernetes.io/aws-load-balancer-healthcheck-timeout` is never applied HOT 5
- Publish the ecr-credential-provider as a container image HOT 8
- Newly autoscaled worker-nodes not added to the targets of Network Loadbalancer. HOT 5
- Please ignore (created by mistake) HOT 3
- Fork the tagging controller into generic node customization controller HOT 3
- TalosOSv1.5.5: AWS CCM can't find the instance via the API so it can't configure the nodes in peer region HOT 5
- Website does not have the correct trademark disclaimer HOT 7
- GitHub repository does not link to the project website url HOT 5
- AWS CCM DockerFile build for more than one platform HOT 11
- cloud-provider-aws does not Prefer CLI Arguments for Configuring Kubernetes HOT 7
- Improve documentation HOT 7
- GitHub releases for latest tags missing HOT 5
- NLB does not map to manual EndpointSlice HOT 6
- label nodes with the name of the autoscaling group they belong to (if they belong to one) HOT 13
- Multiple ENIs is confusing cloud-provider-aws controller HOT 5
- Karpenter does not terminate instances in Pending state HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cloud-provider-aws.