Teleport 6.2 Test Plan #6651

russjones · 2021-04-29T17:40:07Z

Manual Testing Plan

Below are the items that should be manually tested with each release of Teleport.
These tests should be run on both a fresh install of the version to be released
as well as an upgrade of the previous version of Teleport.

Combinations @fspmarshall @quinqu

For some manual testing, many combinations need to be tested. For example, for
interactive sessions the 12 combinations are below.

Teleport with multiple Kubernetes clusters @xacrimon @webvictim

Note: you can use GKE or EKS or minikube to run Kubernetes clusters.
Minikube is the only caveat - it's not reachable publicly so don't run a proxy there.

Helm charts

Migrations @tcsc @nklaassen

Migrate trusted clusters from 6.1.0 to 6.2.0
- Migrate auth server on main cluster, then rest of the servers on main cluster
  SSH should work for both main and old clusters
- Migrate auth server on remote cluster, then rest of the remote cluster
  SSH should work

Command Templates

When interacting with a cluster, the following command templates are useful:

OpenSSH

# when connecting to the recording proxy, `-o 'ForwardAgent yes'` is required.
ssh -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %[email protected] -s proxy:%h:%p" \
  node.example.com

# the above command only forwards the agent to the proxy, to forward the agent
# to the target node, `-o 'ForwardAgent yes'` needs to be passed twice.
ssh -o "ForwardAgent yes" \
  -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %[email protected] -s proxy:%h:%p" \
  node.example.com

# when connecting to a remote cluster using OpenSSH, the subsystem request is
# updated with the name of the remote cluster.
ssh -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %[email protected] -s proxy:%h:%[email protected]" \
  node.foo.com

Teleport

# when connecting to a OpenSSH node, remember `-p 22` needs to be passed.
tsh --proxy=proxy.example.com --user=<username> --insecure ssh -p 22 node.example.com

# an agent can be forwarded to the target node with `-A`
tsh --proxy=proxy.example.com --user=<username> --insecure ssh -A -p 22 node.example.com

# the --cluster flag is used to connect to a node in a remote cluster.
tsh --proxy=proxy.example.com --user=<username> --insecure ssh --cluster=foo.com -p 22 node.foo.com

Teleport Plugins @awly @Joerger

Test receiving a message via Teleport Slackbot
Test receiving a new Jira Ticket via Teleport Jira

WEB UI @kimlisa @alex-kovoy

Main

For main, test with admin role that has access to all resources.

Top Nav

Verify that cluster selector displays all (root + leaf) clusters
Verify that user name is displayed
Verify that user menu shows logout, help&support, and account settings (for local users)

Side Nav

Verify that each item has an icon
Verify that Collapse/Expand works and collapsed has icon >, and expand has icon v
Verify that it automatically expands and highlights the item on page refresh

Servers aka Nodes

Applications

Verify that clicking on Add Application button renders dialogue
- Verify input validation (prevent empty value and invalid url)
- Verify after input and clicking on Generate Script, bash command is rendered
- Verify clicking on Regenerate button regenerates token value in bash command

Databases

Verify that clicking on Add Database button renders dialogue for manual instructions:
- Verify selecting different options on Step 4 changes Step 5 commands

Active Sessions

Verify that "empty" state is handled
Verify that it displays the session when session is active
Verify that "Description", "Session ID", "Users", "Nodes" and "Duration" columns show correct values
Verify that "OPTIONS" button allows to join a session

Audit log

Verify that time range button is shown and works
Verify that clicking on Session Ended event icon, takes user to session player
Verify event detail dialogue renders when clicking on events details button
Verify searching by type, description, created works

Users

Verify that users are shown
Verify that creating a new user works
Verify that editing user roles works
Verify that removing a user works
Verify resetting a user's password works
Verify search by username, roles, and type works

Auth Connectors

Verify that creating OIDC/SAML/GITHUB connectors works
Verify that editing OIDC/SAML/GITHUB connectors works
Verify that error is shown when saving an invalid YAML
Verify that correct hint text is shown on the right side
Verify that encrypted SAML assertions work with an identity provider that supports it (Azure).

Auth Connectors Card Icons

Verify that GITHUB card has github icon
Verify that SAML card has SAML icon
Verify that OIDC card has OIDC icon
Verify when there are no connectors, empty state renders

Roles

Verify that roles are shown
Verify that "Create New Role" dialog works
Verify that deleting and editing works
Verify that error is shown when saving an invalid YAML
Verify that correct hint text is shown on the right side

Managed Clusters

Verify that it displays a list of clusters (root + leaf)
Verify that every menu item works: nodes, apps, audit events, session recordings.

Help & Support

Verify that all URLs work and correct (no 404)

Access Requests

Creating Access Rquests

Create a role with limited permissions (defined below as allow-roles). This role allows you to see the Role screen and ssh into all nodes.
Create another role with limited permissions (defined below as allow-users). This role session expires in 4 minutes, allows you to see Users screen, and denies access to all nodes.
Create another role with no permissions other than being able to create requests (defined below as default)
Create a user with role default assigned
Create a few requests under this user to test pending/approved/denied state.

kind: role
metadata:
  name: allow-roles
spec:
  allow:
    logins:
    - root
    node_labels:
      '*': '*'
    rules:
    - resources:
      - role
      verbs:
      - list
      - read
  options:
    max_session_ttl: 8h0m0s
version: v3

kind: role
metadata:
  name: allow-users
spec:
  allow:
    rules:
    - resources:
      - user
      verbs:
      - list
      - read
  deny:
    node_labels:
      '*': '*'
  options:
    max_session_ttl: 4m0s
version: v3

kind: role
metadata:
  name: default
spec:
  allow:
    request:
      roles:
      - allow-roles
      - allow-users
      suggested_reviewers:
      - random-user-1
      - random-user-2
  options:
    max_session_ttl: 8h0m0s
version: v3

Verify that creating a new request works
Verify that under requestable roles, only allow-roles and allow-users are listed
Verify input validation requires at least one role to be selected
Verify you can select/input/modify reviewers
Verify after creating, requests are listed in pending states
Verify you can't review own requests

Viewing & Approving/Denying Requests

Create a user with the role reviewer that allows you to review all requests, and delete them.

kind: role
version: v3
metadata:
  name: reviewer
spec:
  allow:
    review_requests:
      roles: ['*']

Verify you can view access request from request list
Verify there is list of reviewers you selected (empty list if none selected AND none wasn't defined in roles)
Verify threshold name is there (it will be default if thresholds weren't defined in role, or blank if not named)
Verify you can approve a request with message, and immediately see updated state with your review stamp (green checkmark) and message box
Verify you can deny a request, and immediately see updated state with your review stamp (red cross)
Verify deleting the denied request is removed from list

Assuming Approved Requests

Verify assume buttons are only present for approved request and for logged in user
Verify that assuming allow-roles allows you to see roles screen and ssh into nodes
Verify that after clicking on the assume button, it is disabled in both the list and in viewing
After assuming allow-roles, verify that assuming allow-users allows you to see users screen, and denies access to nodes
- Verify a switchback banner is rendered with roles assumed, and count down of when it expires
- Verify switching back goes back to your default static role
- Verify after re-assuming this role, the user is automatically logged out after the expiry is met (4 minutes)
Verify that after logging out (or getting logged out automatically) and relogging in, permissions are reset to default, and requests that are not expired and are approved are assumable again

Access Request Waiting Room

Strategy Reason

Create the following role:

kind: role
metadata:
  name: restrict
spec:
  allow:
    request:
      roles:
      - <some other role to assign user after approval>
  options:
    max_session_ttl: 8h0m0s
    request_access: reason
    request_prompt: <some custom prompt to show in reason dialogue>
version: v3

Verify after login, reason dialogue is rendered with prompt set to request_prompt setting
Verify after clicking send request, pending dialogue renders
Verify after approving a request, dashboard is rendered
Verify the correct role was assigned

Strategy Always

With the previous role you created from Strategy Reason, change request_access to always:

Verify after login, pending dialogue is rendered
Verify after approving a request, dashboard is rendered
Verify after denying a request, access denied dialogue is rendered

Strategy Optional

With the previous role you created from Strategy Reason, change request_access to optional:

Verify after login, dashboard is rendered
Verify a switchback banner is rendered with roles assumed, and count down of when it expires
- Verify switchback button says Switch Back and clicking goes back to the login screen

Account

Verify that Account screen is accessibly from the user menu for local users.
Verify that changing a local password works (OTP, U2F)

Terminal

Verify that top nav has a user menu (Main and Logout)
Verify that switching between tabs works on alt+[1...9]

Node List Tab

Verify that Cluster selector works (URL should change too)
Verify that Quick launcher input works
Verify that Quick launcher input handles input errors
Verify that "Connect" button shows a list of available logins
Verify that "Hostname", "Address" and "Labels" columns show the current values
Verify that "Search" by hostname, address, labels work
Verify that new tab is created when starting a session

Session Tab

Verify that session and browser tabs both show the title with login and node name
Verify that terminal resize works
- Install midnight commander on the node you ssh into: $ sudo apt-get install mc
- Run the program: $ mc
- Resize the terminal to see if panels resize with it
Verify that session tab shows/updates number of participants when a new user joins the session
Verify that tab automatically closes on "$ exit" command
Verify that SCP Upload works
Verify that SCP Upload handles invalid paths and network errors
Verify that SCP Download works
Verify that SCP Download handles invalid paths and network errors

Session Player

Verify that it can replay a session
Verify that when playing, scroller auto scrolls to bottom most content
Verify when resizing player to a small screen, scroller appears and is working
Verify that error message is displayed (enter a invalid SID in the URL)

Invite Form

Verify that input validates
Verify that invite works with 2FA disabled
Verify that invite works with OTP enabled
Verify that invite works with U2F enabled
Verify that error message is shown if an invite is expired/invalid

Login Form

Verify that input validates
Verify that login works with 2FA disabled
Verify that login works with OTP enabled
Verify that login works with U2F enabled
Verify that login works for Github/SAML/OIDC
Verify that account is locked after several unsuccessful attempts
Verify that redirect to original URL works after successful login

Multi-factor Authentication (mfa)

Create/modify teleport.yaml and set the following authentication settings under auth_service

authentication:
  type: local
  second_factor: optional
  require_session_mfa: yes
  u2f:
    app_id: https://example.com:443
    facets:
    - https://example.com:443
    - https://example.com
    - example.com:443
    - example.com

MFA create, login, password reset

Verify when creating a user, and setting password, required 2nd factor is totp (TODO: temporary hack, ideally want to allow user to select)
Verify at login page, there is a mfa dropdown menu (none, u2f, otp), and can login with otp
Verify at reset password page, there is the same dropdown to select your mfa, and can reset with otp

MFA require auth

Through the CLI, tsh login and register a u2f key with tsh mfa add (not supported in UI yet).

Using the same user as above:

Verify logging in with registered u2f key works
Verify connecting to a ssh node prompts you to tap your registered u2f key

RBAC

Create a role, with no allow.rules defined:

kind: role
metadata:
  name: test
spec:
  allow:
    app_labels:
      '*': '*'
    logins:
    - root
    node_labels:
      '*': '*'
  options:
    max_session_ttl: 8h0m0s
version: v3

Verify that a user has access only to: "Servers", "Applications", "Databases", "Kubernetes", "Active Sessions", "Access Requests" and "Manage Clusters"
Verify there is no Add Server button in Server view
Verify there is no Add Application button in Applications view
Verify only Nodes and Apps are listed under options button in Manage Clusters

Note: User has read/create access_request access to their own requests, despite resource settings

Add the following under spec.allow.rules to enable read access to the audit log:

  - resources:
      - event
      verbs:
      - list

Verify that the Audit Log and Session Recordings is accessible
Verify that playing a recorded session is denied

Add the following to enable read access to recorded sessions

  - resources:
      - session
      verbs:
      - read

Verify that a user can re-play a session (session.end)

Add the following to enable read access to the roles

- resources:
      - role
      verbs:
      - list
      - read

Verify that a user can see the roles
Verify that a user cannot reset password and create/delete/update a role

Add the following to enable read access to the auth connectors

- resources:
      - auth_connector
      verbs:
      - list
      - read

Verify that a user can see the list of auth connectors.
Verify that a user cannot create/delete/update the connectors

Add the following to enable read access to users

  - resources:
      - user
      verbs:
      - list
      - read

Verify that a user can access the "Users" screen
Verify that a user cannot create/delete/update a user

Add the following to enable read access to trusted clusters

  - resources:
      - trusted_cluster
      verbs:
      - list
      - read

Verify that a user can access the "Trust" screen
Verify that a user cannot create/delete/update a trusted cluster.

Performance/Soak Test @xacrimon @fspmarshall

Using tsh bench tool, perform the soak tests and benchmark tests on the following configurations:

Cluster with 10K nodes in normal (non-IOT) node mode with ETCD
Cluster with 10K nodes in normal (non-IOT) mode with DynamoDB
Cluster with 1K IOT nodes with ETCD
Cluster with 1K IOT nodes with DynamoDB
Cluster with 500 trusted clusters with ETCD
Cluster with 500 trusted clusters with DynamoDB

Soak Tests

Run 4hour soak test with a mix of interactive/non-interactive sessions:

tsh bench --duration=4h user@teleport-monster-6757d7b487-x226b ls
tsh bench -i --duration=4h user@teleport-monster-6757d7b487-x226b ps uax

Observe prometheus metrics for goroutines, open files, RAM, CPU, Timers and make sure there are no leaks

Verify that prometheus metrics are accurate.

Breaking load tests

Load system with tsh bench to the capacity and publish maximum numbers of concurrent sessions with interactive
and non interactive tsh bench loads.

Application Access @r0mant @smallinsky

Database Access @r0mant @smallinsky

The text was updated successfully, but these errors were encountered:

quinqu · 2021-05-14T22:33:57Z

When adding an OTP device with tsh mfa add and try to enter the code, teleport says the code must be 6 digits long and my input surely is. It still wont be accepted. Terminal output:

Choose device type [TOTP, U2F]: TOTP
Enter device name: tempdevice
Enter an OTP code from a *registered* device: 628304


Open your TOTP app and create a new manual entry with these fields:
  URL: <omitted> 
  Account name: <omitted>
  Secret key: <omitted>
  Issuer: <omitted> 
  Algorithm: SHA1
  Number of digits: 6
  Period: 30s

Once created, enter an OTP code generated by the app: 624072
TOTP code must be exactly 6 digits long, try again
Once created, enter an OTP code generated by the app: 624072
TOTP code must be exactly 6 digits long, try again
Once created, enter an OTP code generated by the app: 910046
TOTP code must be exactly 6 digits long, try again
Once created, enter an OTP code generated by the app: 426970
TOTP code must be exactly 6 digits long, try again
Once created, enter an OTP code generated by the app:

awly · 2021-05-17T16:59:02Z

@quinqu could you please file a bug for this and assign to me?
It's likely I introduced the problem in 6.2

Joerger · 2021-05-19T01:35:26Z

Updating a user with tctl create -f user.yaml breaks the audit log and session recordings tabs in the Web UI - #6935

tcsc · 2021-05-19T06:47:25Z

@webvictim - I've added a test matrix for the tsh tests here so we don't stomp on each other. Or on ourselves. Feel free to edit as necessary.

New	New (No Rec)	Upgraded	Upgraded (No Rec)
PASS	PASS	PASS	PASS	tsh ssh <regular-node>
PASS	PASS	PASS	PASS	tsh ssh <node-remote-cluster>
PASS	PASS	PASS	PASS	tsh ssh -A <regular-node>
PASS	PASS	PASS	PASS	tsh ssh -A <node-remote-cluster>
PASS	PASS	PASS	PASS	tsh ssh <regular-node> ls
PASS	PASS	PASS	PASS	tsh ssh <node-remote-cluster> ls
PASS	PASS	PASS	PASS	tsh join <regular-node>
PASS	PASS	PASS	PASS	tsh join <node-remote-cluster>
PASS	*PASS	PASS	*PASS	tsh play <regular-node>
PASS	*PASS	PASS	*PASS	tsh play <node-remote-cluster>
PASS	PASS	PASS	PASS	tsh scp <regular-node>
PASS	PASS	PASS	PASS	tsh scp <node-remote-cluster>
PASS	PASS	PASS	PASS	tsh ssh -L <regular-node>
PASS	PASS	PASS	PASS	tsh ssh -L <node-remote-cluster>
PASS	PASS	PASS	PASS	tsh ls
PASS	PASS	PASS	PASS	tsh clusters

= failed with ERROR: 0 not found, which I assume is the correct behaviour when recording is disabled

tcsc · 2021-05-19T07:30:15Z

Encountered #6938 while testing: Panic when using tctl with remote auth server

kimlisa · 2021-05-19T07:56:25Z

mfa related bug, where scp upload/download does not work in the web ui: #6939

r0mant · 2021-05-19T19:06:53Z

@Joerger @xacrimon Seeing #6935 as well which Brian reported above.

@xacrimon Looks like this file (dynamic.go) was a part of your RFD19 implementation, could this have caused it? Just need to add user.updated event to the switch probably.

xacrimon · 2021-05-19T19:28:15Z

@r0mant Resolved in #6949 and #6950 backport to v6.

fspmarshall · 2021-05-19T20:46:02Z

Changes introduced in #6731 break compatibility with older 6.X instances due to reliance on new GRPC methods (e.g. attempting to view audit events from UI of a 6.2 proxy results in unknown method GetEvents for service proto.AuthService error when dealing with a 6.1 auth server).

Teleport should fallback to using old event API if new one is not available.

cc: @xacrimon @kimlisa

xacrimon · 2021-05-19T21:05:57Z

@fspmarshall So this is a bit of an issue. The old events API does not support pagination but the IAuditLog interface expects it. Should we just ignore the new parameters introduced in RFD 19 and pretend pagination doesn't exist on fallback?

kimlisa · 2021-05-20T01:16:30Z

ui switchback bug (i am fixing): #6960
@xacrimon related to #6935, unknown event bug: #6959

fspmarshall · 2021-05-20T16:23:58Z

Should we just ignore the new parameters introduced in RFD 19 and pretend pagination doesn't exist on fallback?

@xacrimon Followed up in PR. Basically, I think we should pretend it doesn't exist when dealing with the first call (since that means we're getting the "first page", which is what the old API did), but we should return an error if startKey != "", since that means we're loading a subsequent page, which the old API can't do.

awly · 2021-05-20T21:32:46Z

@xacrimon @webvictim @fspmarshall @quinqu let me know if you're overloaded.
Some other folks are done with their testing so I could re-distribute remaining tasks if needed.

quinqu · 2021-05-20T21:38:24Z

@awly i could use some help on the U2F second factor tests as i do not have a U2F device.

awly · 2021-05-20T21:41:30Z

@quinqu will do 👍

awly · 2021-05-20T22:01:55Z

FYI everyone, if you find an issue while testing, please file a bug and put it into 6.2 milestone.
That way I can track all the remaining work and questions.

xacrimon · 2021-05-21T12:13:38Z

I have previously assumed DynamoDB tests were running but they have not been. I still need to hook these up and run them before I can say everything is correct. I will make another comment but please do not cut before I confirm that everything is indeed working @awly. @russjones I've also merged the API compat PR. #6990 will need to be merged as well, I will ping for reviews when it is ready.

webvictim · 2021-05-21T13:02:59Z

Ran into some weird tsh logout behaviour, detailed in #6992

Not sure if this is a blocker but I can't log out of all my clusters for some reason.

xacrimon · 2021-05-21T13:35:21Z

Okay. I have pinged reviews on #6990 and I sign off on everything working when it is merged. I’ve manually done some testing to make sure it works.

webvictim · 2021-05-21T18:44:41Z

Most Kubernetes tests are finished, just waiting on #6990 merge/backport (and rc.2 cut?) to verify the audit log entries:

awly · 2021-05-25T00:24:02Z

All issues are either resolved or not caused by 6.2.
Marking the testplan as done.

russjones · 2021-08-05T21:56:46Z

From @fspmarshall

6.2 - etcd - IoT

tsh bench --duration=30m root@loadtest-665c98bfb5-72w58 ls
* Requests originated: 17920
* Requests failed: 258
* Last error: connection closed
Histogram
Percentile Response Duration
---------- -----------------
25         4867 ms
50         6943 ms
75         9583 ms
90         14951 ms
95         20959 ms
99         40799 ms
100        65439 ms

tsh bench --interactive --duration=30m root@loadtest-665c98bfb5-9wk2b ps aux
* Requests originated: 17905
* Requests failed: 253
* Last error: connection error: desc = "transport: authentication handshake failed: EOF"
Histogram
Percentile Response Duration
---------- -----------------
25         4923 ms
50         7079 ms
75         9727 ms
90         15015 ms
95         20783 ms
99         41951 ms
100        64927 ms

6.2 - etcd - non-IoT

tsh bench --duration=30m root@loadtest-665c98bfb5-qcf82 ls
* Requests originated: 17983
* Requests failed: 23
* Last error: connection error: desc = "transport: authentication handshake failed: EOF"
Histogram
Percentile Response Duration
---------- -----------------
25         4719 ms
50         6567 ms
75         8703 ms
90         11143 ms
95         13439 ms
99         21263 ms
100        49183 ms

tsh bench --interactive --duration=30m root@loadtest-665c98bfb5-zfsrb ps aux
* Requests originated: 17970
* Requests failed: 17
* Last error: connection error: desc = "transport: authentication handshake failed: EOF"
Histogram
Percentile Response Duration
---------- -----------------
25         4655 ms
50         6391 ms
75         8327 ms
90         10703 ms
95         13079 ms
99         21759 ms
100        59423 ms

russjones added the test-plan A list of tasks required to ship a successful product release. label Apr 29, 2021

russjones added this to the 6.2 "Buffalo" milestone Apr 29, 2021

russjones assigned awly Apr 29, 2021

awly mentioned this issue May 4, 2021

Teleport 6.2 Release Plan #6734

Closed

19 tasks

russjones added the documentation label May 7, 2021

xacrimon mentioned this issue May 20, 2021

[branch/v6] Ensure API compatibility with auth servers older than v6.2 #6965

Merged

awly removed the documentation label May 24, 2021

awly closed this as completed May 25, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Teleport 6.2 Test Plan #6651

Teleport 6.2 Test Plan #6651

russjones commented Apr 29, 2021 •

edited by webvictim

Loading

quinqu commented May 14, 2021

awly commented May 17, 2021

Joerger commented May 19, 2021

tcsc commented May 19, 2021 •

edited

Loading

tcsc commented May 19, 2021

kimlisa commented May 19, 2021

r0mant commented May 19, 2021

xacrimon commented May 19, 2021

fspmarshall commented May 19, 2021

xacrimon commented May 19, 2021 •

edited

Loading

kimlisa commented May 20, 2021

fspmarshall commented May 20, 2021

awly commented May 20, 2021

quinqu commented May 20, 2021

awly commented May 20, 2021

awly commented May 20, 2021

xacrimon commented May 21, 2021 •

edited

Loading

webvictim commented May 21, 2021

xacrimon commented May 21, 2021 •

edited

Loading

webvictim commented May 21, 2021

awly commented May 25, 2021

russjones commented Aug 5, 2021

Teleport 6.2 Test Plan #6651

Teleport 6.2 Test Plan #6651

Comments

russjones commented Apr 29, 2021 • edited by webvictim Loading

Manual Testing Plan

Combinations @fspmarshall @quinqu

Teleport with multiple Kubernetes clusters @xacrimon @webvictim

Helm charts

Migrations @tcsc @nklaassen

Command Templates

OpenSSH

Teleport

Teleport Plugins @awly @Joerger

WEB UI @kimlisa @alex-kovoy

Main

Top Nav

Side Nav

Servers aka Nodes

Applications

Databases

Active Sessions

Audit log

Users

Auth Connectors

Auth Connectors Card Icons

Roles

Managed Clusters

Help & Support

Access Requests

Creating Access Rquests

Viewing & Approving/Denying Requests

Assuming Approved Requests

Access Request Waiting Room

Strategy Reason

Strategy Always

Strategy Optional

Account

Terminal

Node List Tab

Session Tab

Session Player

Invite Form

Login Form

Multi-factor Authentication (mfa)

MFA create, login, password reset

MFA require auth

RBAC

Performance/Soak Test @xacrimon @fspmarshall

Application Access @r0mant @smallinsky

Database Access @r0mant @smallinsky

quinqu commented May 14, 2021

awly commented May 17, 2021

Joerger commented May 19, 2021

tcsc commented May 19, 2021 • edited Loading

tcsc commented May 19, 2021

kimlisa commented May 19, 2021

r0mant commented May 19, 2021

xacrimon commented May 19, 2021

fspmarshall commented May 19, 2021

xacrimon commented May 19, 2021 • edited Loading

kimlisa commented May 20, 2021

fspmarshall commented May 20, 2021

awly commented May 20, 2021

quinqu commented May 20, 2021

awly commented May 20, 2021

awly commented May 20, 2021

xacrimon commented May 21, 2021 • edited Loading

webvictim commented May 21, 2021

xacrimon commented May 21, 2021 • edited Loading

webvictim commented May 21, 2021

awly commented May 25, 2021

russjones commented Aug 5, 2021

6.2 - etcd - IoT

6.2 - etcd - non-IoT

russjones commented Apr 29, 2021 •

edited by webvictim

Loading

tcsc commented May 19, 2021 •

edited

Loading

xacrimon commented May 19, 2021 •

edited

Loading

xacrimon commented May 21, 2021 •

edited

Loading

xacrimon commented May 21, 2021 •

edited

Loading