Comments (16)
from cloud-provider-aws.
What would be the recommended way to install this cloud-provider?
We are expected to apply a static example bunch of yaml files? They're still referencing version 1.27.1. What is the correct way to install the latest? Use this directory and do a bunch of sed commands for the latest?
Why not support the helm chart as the installation mechanism like the EBS CSI driver is doing? https://github.com/kubernetes-sigs/aws-ebs-csi-driver/releases
I hate to be blunt, but it's bad enough that the documentation for this CRITICAL project is severely lacking, but now a stable installation mechanism isn't even provided?
I REALLY wish AWS would chime in and take over this project so it has proper support instead of just expecting everyone to use EKS.
from cloud-provider-aws.
@et304383 can you please share where / how exactly you are using this chart?
We are managing our own K8s control plane for over 40 clusters, and obviously have to install this controller to support 1.27+
So far, this is how script to install:
helm repo add aws-cloud-controller-manager https://kubernetes.github.io/cloud-provider-aws
helm repo update
helm pull aws-cloud-controller-manager/aws-cloud-controller-manager --version 0.0.8 --untar
cd aws-cloud-controller-manager
cluster_cidr=$(grep cluster-cidr /etc/kubernetes/manifests/kube-controller-manager.yaml | cut -d = -f2)
cluster_name=$(grep cluster-name /etc/kubernetes/manifests/kube-controller-manager.yaml | cut -d = -f2)
yq -i '.args += ["--allocate-node-cidrs=false", "--configure-cloud-routes=false", "--cluster-cidr='$cluster_cidr'", "--cluster-name='$cluster_name'"]' values.yaml
export KUBECONFIG=/etc/kubernetes/admin.conf
helm upgrade --install -n kube-system aws-cloud-controller-manager .
You can see we already have to edit the values file to specify cluster cidr and cluster name (which there is zero documentation for, mind you), so adding another update to change the image version is just another line of code.
from cloud-provider-aws.
This issue is currently awaiting triage.
If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
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-sigs/prow repository.
from cloud-provider-aws.
from cloud-provider-aws.
/triage accepted
from cloud-provider-aws.
@kmala: The label triage/accepted
cannot be applied. Only GitHub organization members can add the label.
In response to this:
/triage accepted
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-sigs/prow repository.
from cloud-provider-aws.
I think it's worth keeping around, it has a decent number of users (including Rancher: https://github.com/rancher/rke1-docs). Can we switch the values.yaml
to use a latest
tag/something low maintenance instead?
from cloud-provider-aws.
@cartermckinnon we don't have a CI job to verify it does work .. so can't guarantee the functionality
from cloud-provider-aws.
What would be the recommended way to install this cloud-provider?
from cloud-provider-aws.
What would be the recommended way to install this cloud-provider?
from cloud-provider-aws.
@et304383 can you please share where / how exactly you are using this chart?
from cloud-provider-aws.
We have been managing k8s cluster on ec2 instances with cloud-provider=external then installing this aws cloud-provider. We leverage the helm-controller inside k3s/rke2 to bootstrap the cluster with this cloud-provider.
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
name: cloud-provider-aws
namespace: kube-system
spec:
chart: https://github.com/kubernetes/cloud-provider-aws/releases/download/helm-chart-aws-cloud-controller-manager-0.0.7/aws-cloud-controller-manager-0.0.7.tgz
targetNamespace: kube-system
bootstrap: true
valuesContent: |-
args:
- --v=2
- --cloud-provider=aws
- --controllers=cloud-node,cloud-node-lifecycle,service,-route
- '--cloud-config=/tmp/cloud-provider-config'
nodeSelector:
node-role.kubernetes.io/control-plane: "true"
tolerations:
- effect: NoSchedule
key: ""
operator: Exists
- effect: NoExecute
key: ""
operator: Exists
extraVolumes:
- hostPath:
path: /var/lib/rancher/rke2/etc/config-files/cloud-provider-config
type: File
name: cloud-provider-config
extraVolumeMounts:
- mountPath: /tmp/cloud-provider-config
name: cloud-provider-config
from cloud-provider-aws.
We are managing multiple cluster. We need cloud provider helm chart to install for kubernetes cluster to work. We have automated process for upgrading and testing clusters so it is easier to use helm chart values to update , rather that manually updating in a yaml file. if something goes wrong in testing , it could be rolled back easily using helm.
I think its better to keep the helm chart.
from cloud-provider-aws.
Currently using helm chart for self managed clusters
from cloud-provider-aws.
We're using it for self-managed clusters as well, specifying the tag in a values.yaml.
from cloud-provider-aws.
Related Issues (20)
- 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 6
- 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 11
- Multiple ENIs is confusing cloud-provider-aws controller HOT 5
- Karpenter does not terminate instances in Pending state HOT 5
- DeviceIndex is not respected when processing multiple network interfaces on a node HOT 3
- Service controller doesn't populate TargetGroups HOT 2
- aws cloud controller manager is unable to manage the nodes in cluster HOT 5
- Switch to aws-sdk-go-v2 vendored library HOT 6
- Support Region for DescribeInstance Call HOT 4
- Invalid format for AWS instance () HOT 2
- Add network topology information to nodes HOT 1
- switch to aws-sdk-go-v2 as v1 is going away HOT 4
- Container images missing for newer releases HOT 6
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.