Documentation for updating vSphere credentials #8717
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
eks-distro-bot
added
the
size/S
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8717 +/- ##
==========================================
+ Coverage 73.55% 73.56% +0.01%
==========================================
Files 578 578
Lines 36580 36610 +30
==========================================
+ Hits 26905 26931 +26
+ Misses 7955 7953 -2
- Partials 1720 1726 +6 ☔ View full report in Codecov by Sentry. |
2ez4szliu
force-pushed
the
vsphere-credential-update
branch
from
3808b52
to
ad16808
Compare
| 2. Only update Secret `vsphere-credentials` under `eksa-system` namespace then trigger a full EKS-A CAPI cluster upgrade by modifying the cluster spec: | ||
| - Update `EKSA_VSPHERE_PASSWORD` environment variable to the new password and get the base64 encoded string of the password using `echo -n "<YOUR_PASSWORD>" | base64` | ||
| - Update secret `vsphere-credentials` under `eksa-system` namespace - Update `password`, `passwordCP`, `passwordCSI` field under data and in `kubectl.kubernetes.io/last-applied-configuration` if annotation exists. | ||
| - Modify cluster spec file and run `eksctl anywhere upgrade cluster -f <cluster-config-file>` to trigger a full cluster upgrade. This will automatically apply the new credentials to all related secrets. |
There was a problem hiding this comment.
Can we specify a few fields a customer can upgrade to enable full CAPI cluster upgrade as an example?
There was a problem hiding this comment.
Thanks Pankti, added some examples
2ez4szliu
force-pushed
the
vsphere-credential-update
branch
from
ad16808
to
a8e439b
Compare
2ez4szliu
force-pushed
the
vsphere-credential-update
branch
from
a8e439b
to
5fd37d4
Compare
*Issue #, if available: #6468
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.