AWS Integrator Charm

AWS no longer supports an in-tree cloud-provider in 1.27

Bug #2013090 reported by Adam Dyess
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AWS Cloud Provider Charm
Fix Released
High
Adam Dyess
AWS Cloud Provider Charm 1.27
AWS Integrator Charm
Fix Released
High
Adam Dyess
AWS Integrator Charm 1.27
Charmed Kubernetes Bundles
Fix Released
High
Adam Dyess
Charmed Kubernetes Bundles 1.27
Kubernetes Control Plane Charm
Fix Released
High
Adam Dyess
Kubernetes Control Plane Charm 1.27

Bug Description

As of this PR [0], AWS no longer supports the legacy AWS cloud provider in-tree, and deployment to integrate with AWS components must use the out-of-tree provider [1]. A new charm must be developed to
* deploy and manage that new component
* update any IAM/security policy requirements
* share missing data over relation to enable the deployment
* appropriately configure the worker/control-plane without disturbing previous deployments

[0]: https://github.com/kubernetes/kubernetes/pull/115838
[1]: https://github.com/kubernetes/cloud-provider-aws/

Adam Dyess (addyess)
Changed in charm-aws-integrator:
milestone: none → 1.27
assignee: nobody → Adam Dyess (addyess)
importance: Undecided → High
status: New → In Progress
status: In Progress → New
status: New → In Progress
Changed in charm-aws-cloud-provider:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Adam Dyess (addyess)
milestone: none → 1.27
Revision history for this message
Adam Dyess (addyess) wrote :

* iam policy adjustments [0]
  * aws-integrator needs to add a new iam policy to workers
  * aws-integrator needs to add a new iam policy to control-planes
  * These policies include duplicates that are already applied, and likely the list needs to be pared down quite a bit to better fit the flow of aws-integrator's request based permissions

* kubernetes-control-plane is ALREADY tagging workers/control-planes with a cluster-tag
  * use the kube-control relation to expose cluster-tag to cloud-provider charm
  * update the kube-control relation to expose cluster-cidr to the cloud-provider charm

aws-integrator relation to kubernetes-worker/control-plane needs to
  * prevent --cloud-provider="aws" when not kube_version < (1, 27, 0)
  * kubelet needs extra argument --hostname-override=${get_node_name()} in kubernetes_common.py

[0]: https://cloud-provider-aws.sigs.k8s.io/prerequisites/

Changed in charm-kubernetes-master:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Adam Dyess (addyess)
milestone: none → 1.27
Revision history for this message
Adam Dyess (addyess) wrote (last edit ):

PRs:

https://github.com/charmed-kubernetes/layer-kubernetes-common/pull/45
https://github.com/juju-solutions/interface-aws-integration/pull/15
https://github.com/juju-solutions/charm-aws-integrator/pull/48
https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/pull/278
https://github.com/charmed-kubernetes/charm-aws-cloud-provider/pull/1
https://github.com/charmed-kubernetes/jenkins/pull/1250

George Kraft (cynerva)
summary: - AWS no longer supports an in-tree cloud-provider in 1.26
+ AWS no longer supports an in-tree cloud-provider in 1.27
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

Overlay PR for the bundle repo:
https://github.com/charmed-kubernetes/bundle/pull/876

Changed in charmed-kubernetes-bundles:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Adam Dyess (addyess)
milestone: none → 1.27
Kevin W Monroe (kwmonroe)
Changed in charmed-kubernetes-bundles:
status: In Progress → Fix Committed
Kevin W Monroe (kwmonroe)
Changed in charm-aws-integrator:
status: In Progress → Fix Committed
Changed in charm-kubernetes-master:
status: In Progress → Fix Committed
Adam Dyess (addyess)
Changed in charm-aws-cloud-provider:
status: In Progress → Fix Committed
Kevin W Monroe (kwmonroe)
Changed in charm-aws-cloud-provider:
status: Fix Committed → Fix Released
Changed in charm-aws-integrator:
status: Fix Committed → Fix Released
Changed in charmed-kubernetes-bundles:
status: Fix Committed → Fix Released
Changed in charm-kubernetes-master:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.