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.

Sign up for GitHub

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

CASMTRIAGE-7577: Update to add cray-spire-jwks #5593

Merged
merged 2 commits into from
Dec 18, 2024
Merged

CASMTRIAGE-7577: Update to add cray-spire-jwks #5593

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6496dea
CASMTRIAGE-7577: Update to add cray-spire-jwks
ndavidson-hpe Dec 9, 2024
b5e1db9
Update example to better reflect real life
ndavidson-hpe Dec 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion ...ations/power_management/Power_On_and_Start_the_Management_Kubernetes_Cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,7 +330,7 @@ Some systems are configured with lazy mounts that do not have this requirement f

To resolve the space issue, see [Troubleshoot Ceph OSDs Reporting Full](../utility_storage/Troubleshoot_Ceph_OSDs_Reporting_Full.md).

1. (`ncn-m001#`) Check that `spire` pods have started.
1. (`ncn-m001#`) Check that `spire` and `cray-spire` pods have started.

Monitor the status of the `spire-jwks` pods to ensure they restart and enter the `Running` state.

Expand All @@ -341,6 +341,9 @@ Some systems are configured with lazy mounts that do not have this requirement f
Example output:

```text
cray-spire-jwks-57bbb4f5c7-57j5k 2/3 CrashLoopBackOff 9 23h 10.44.0.31 ncn-w002 <none> <none>
cray-spire-jwks-57bbb4f5c7-crb2m 2/3 CrashLoopBackOff 9 23h 10.36.0.34 ncn-w003 <none> <none>
cray-spire-jwks-57bbb4f5c7-lq9ar 2/3 CrashLoopBackOff 9 23h 10.39.0.5 ncn-w001 <none> <none>
spire-jwks-6b97457548-gc7td 2/3 CrashLoopBackOff 9 23h 10.44.0.117 ncn-w002 <none> <none>
spire-jwks-6b97457548-jd7bd 2/3 CrashLoopBackOff 9 23h 10.36.0.123 ncn-w003 <none> <none>
spire-jwks-6b97457548-lvqmf 2/3 CrashLoopBackOff 9 23h 10.39.0.79 ncn-w001 <none> <none>
Expand All @@ -352,6 +355,12 @@ Some systems are configured with lazy mounts that do not have this requirement f
kubectl rollout restart -n spire deployment spire-jwks
```

1. (`ncn-m001#`) If the `cray-spire-jwks` pods indicate `CrashLoopBackOff`, then restart the Cray Spire deployment.

```bash
kubectl rollout restart -n spire deployment cray-spire-jwks
```

1. (`ncn-m001#`) Rejoin Spire on the worker and master NCNs, to avoid issues with Spire tokens.

```bash
Expand Down
Loading