This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WITH payload_data (id, value) AS ( | |
VALUES (1, 'data1'), (2, 'data2'), (3, 'data3') | |
) | |
SELECT u.name, p.value | |
FROM users u | |
JOIN payload_data p ON u.id = p.id; | |
WITH payload_data AS ( | |
SELECT | |
json_extract(value, '$.id') as id, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. handle internal traffic? (i.e. previously admin services made calls out of k8s cluster, now it should be internal) | |
2. handle external traffic? (i.e. was identity service or identity scheduler in same network as DBs previously?) | |
2. How do we know what are the K8S objects to add? (StorageClass/ Persistent Volume/Persistent Volume claim?) | |
pod - unit of deployment | |
service - fixed endpoint for 1 or more pods | |
deployment - details on show should containers/pods be deployed, how many should be deployed, configuration | |
node - a machine/VM - IPs across all nodes are unique, talks through pod IPs |