-
Updated
Dec 22, 2021 - Go
cluster-api
Here are 36 public repositories matching this topic...
/kind bug
What steps did you take and what happened:
when updating the AWSCluster.spec.additionalTags field tags are reconciled on all instances except for the bastion host.
What did you expect to happen:
updating tags in the spec should also reconcile on the bastion host
Environment:
- Cluster-api-provider-aws version: v0.6.4
- Kubernetes version: (use `kubec
-
Updated
Oct 17, 2021
-
Updated
Aug 6, 2021 - Python
-
Updated
Dec 20, 2021 - Go
It will be good to add information around how to assign ControlPlaneEndpoint IP in the getting started document -
We only state that CP Endpoint should be an IP in the subnet but not in the DHCP range. Refer to create workload cluster
-
Updated
Apr 5, 2021 - Go
-
Updated
Dec 20, 2021 - Go
-
Updated
Jul 23, 2021 - Go
-
Updated
Dec 1, 2019 - Go
-
Updated
Jun 28, 2019 - Go
-
Updated
Jun 30, 2019 - Go
-
Updated
Dec 22, 2020 - Shell
-
Updated
Dec 22, 2021 - Go
-
Updated
Dec 22, 2021 - Go
-
Updated
Dec 6, 2021 - Go
-
Updated
Oct 18, 2021 - Shell
-
Updated
Feb 12, 2020 - Shell
-
Updated
Dec 15, 2019 - Go
-
Updated
Jan 6, 2021 - Go
-
Updated
Dec 21, 2021 - Go
-
Updated
Nov 15, 2019
-
Updated
Jul 9, 2020 - Shell
-
Updated
Feb 15, 2020
-
Updated
Sep 28, 2020 - JavaScript
-
Updated
May 23, 2019 - Go
-
Updated
Dec 21, 2021 - Go
Improve this page
Add a description, image, and links to the cluster-api topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cluster-api topic, visit your repo's landing page and select "manage topics."


User Story
The
exposStragegyfield in theClusterresource is today mutable, but changing it for an existing cluster would lead to an interruption of the communication between Kubelet and OpenVPN client and the control plane.This problem is related to kubeconfig used by the Kubelet and the OpenVPN client config getting stale after the expose strategy change, and could be addressed by re