Closed lynnemorrison closed 2 days ago
@grs, this is a first attempt for adding a command to check the token in kubernets. I would appreciate if you could look through this and give me feedback on what you like and don't like and I'll update. I'll next start on adding this command to podman.
@grs Fixed your comments and added token status command output for podman.
Output when creating a claim and cert tokens:
Claim Token:
$ skupper token status ~/token1.txt Token was generated by local site with id: 69f74348-9c4c-4845-82d2-c59382418456
Token Name: 5473f3a0-21db-11ef-a72f-0800275c9d9f path: /home/lynne/token1.txt type: claim version: cb0a702 namespace: west claims made: 1 claims remaining: 0 Warning: token has expired, expiration time: 2024-06-03 15:13:57 -0400 EDT
Cert Token:
$ skupper token status ~/tokencrt.txt Token was generated by local site with id: 69f74348-9c4c-4845-82d2-c59382418456
Token Name: tokencrt path: /home/lynne/tokencrt.txt type: cert version: cb0a702 CA: Token matches skupper-site-server hostname: 10.98.40.44 found in SANs list Issuer: skupper-site-ca for both
Skupper-site-server Secret details: AuthorityKeyId: [4 94 8 23 106 216 202 130 101 115 255 186 150 81 195 198 155 242 221 111] DNS: [skupper-router.west skupper-router.west.svc.cluster.local 10.98.40.44] IP: [10.98.40.44] Issuer: CN=skupper-site-ca Created: 2024-06-03 14:56:42 -0400 EDT
Token Secret details: AuthorityKeyId: [4 94 8 23 106 216 202 130 101 115 255 186 150 81 195 198 155 242 221 111] Issuer: CN=skupper-site-ca
@grs Any chance of this getting merged in?
@ssorj any comments on this before we merge?
Add a skupper token status command to display details of the token/secrets and automates some checking when connections issues occur.
fixes #710