cluster: introduce Region.Cluser and m/{region}/k8s_token to store a cluster's token #42

Merged
karasz merged 3 commits from pr-amery-k8s_token into main 2024-03-19 17:44:48 +01:00
Owner

having this field distinguishes functional regions from primary regions. primary regions determine the kubernetes cluster while functional regions only DNS entrypoints

having this field distinguishes functional regions from primary regions. primary regions determine the kubernetes cluster while functional regions only DNS entrypoints
amery added 2 commits 2024-03-02 22:01:53 +01:00
amery requested review from karasz 2024-03-02 22:01:59 +01:00
amery added 1 commit 2024-03-02 22:30:46 +01:00
Author
Owner

reduced Zone.loadClusterToken complexity

reduced `Zone.loadClusterToken` complexity
amery added 1 commit 2024-03-02 22:35:10 +01:00
amery added 1 commit 2024-03-02 23:09:33 +01:00
karasz requested changes 2024-03-05 17:13:48 +01:00
@@ -221,0 +234,4 @@
return err
}
// first non-empty line
Owner

What happens if the token file has no non-empty lines?

What happens if the token file has no non-empty lines?
Author
Owner

it's marked as cluster but without token (yet)

my intention was to generate the token when installing the first member of such cluster

it's marked as cluster but without token (yet) my intention was to generate the token when installing the first member of such cluster
karasz marked this conversation as resolved
karasz approved these changes 2024-03-19 17:38:36 +01:00
karasz left a comment
Owner

+1

+1
amery added 3 commits 2024-03-19 17:43:02 +01:00
Author
Owner

rebased

rebased
karasz merged commit 3a2a20a611 into main 2024-03-19 17:44:48 +01:00
karasz deleted branch pr-amery-k8s_token 2024-03-19 17:47:11 +01:00
Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: amery/jpictl#42