Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix AWS hosted cluster template networking issue (fixes #788) #810

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kylewuolle
Copy link
Contributor

@kylewuolle kylewuolle commented Dec 18, 2024

This PR adds the ability to set the management cluster name in the AWS hosted template. This is needed because of issue #788. Requires PR Mirantis/helm-charts#2 to be merged and the resulting helm chart to be published. An upstream PR for the change to the chart has been created : kubernetes/cloud-provider-aws#1085.

…ent cluster name which is required for networking to work with AWS. Also switched to using the forked version of the AWS cloud provider helm chart so we can support this.
Copy link
Collaborator

@a13x5 a13x5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor notes.
@kylewuolle did you research a possibility to pass managementClusterName automatically?
For example we could do in the same way we're passing credential values

@@ -55,6 +55,10 @@ spec:
- --cluster-cidr={{ first .Values.clusterNetwork.pods.cidrBlocks }}
- --allocate-node-cidrs=true
- --cluster-name={{ include "cluster.name" . }}
cloudConfig:
enabled: {{ ne .Values.managementClusterName "" }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to have just true here, since without it it won't work anyway

cloudConfig:
enabled: {{ ne .Values.managementClusterName "" }}
global:
KubernetesClusterID: {{ .Values.managementClusterName }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And then we can just have required if you want to have some guards on that value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

AWS subnet tagging causes hosted clusters to not allow load balancer to be exposed
2 participants