Joe Salisbury
@salisburyheavyindustries.com
vp engineering @giantswarm.io / ten of swords / he/him / linktr.ee/salisbury_joe
polished crystal
September 21, 2025 at 2:28 PM
polished crystal
a bug planet (fire red plus)
August 12, 2025 at 7:45 PM
a bug planet (fire red plus)
okay that's @giantswarm.io out for kubecon london see ya later alligator
April 4, 2025 at 12:46 PM
okay that's @giantswarm.io out for kubecon london see ya later alligator
emerald seaglass was fun
February 9, 2025 at 1:50 PM
emerald seaglass was fun
and we're talking to the kind cluster!
note: we haven't fucked with the kubeconfig or anything in between, this is all via the same endpoint
note: we haven't fucked with the kubeconfig or anything in between, this is all via the same endpoint
December 19, 2024 at 4:27 PM
and we're talking to the kind cluster!
note: we haven't fucked with the kubeconfig or anything in between, this is all via the same endpoint
note: we haven't fucked with the kubeconfig or anything in between, this is all via the same endpoint
so now if we switch to the testcluster workspace
December 19, 2024 at 4:26 PM
so now if we switch to the testcluster workspace
and we now have the cluster mounted in kcp blam!
December 19, 2024 at 4:26 PM
and we now have the cluster mounted in kcp blam!
our "operator" sees the new workspace, and starts setting up a kind cluster and the necessary resources (see the script for what it's doing) to then mount the kind cluster in kcp
December 19, 2024 at 4:25 PM
our "operator" sees the new workspace, and starts setting up a kind cluster and the necessary resources (see the script for what it's doing) to then mount the kind cluster in kcp
we switch to the "consumer" workspace, and create a new workspace
December 19, 2024 at 4:24 PM
we switch to the "consumer" workspace, and create a new workspace
this is what our workspace structure looks like to start with - :root:operators:mounts and :root:providers:mounts are used in the pr, so we didn't fuck with that, and :root:consumer is where we're gonna put our clusters
December 19, 2024 at 4:22 PM
this is what our workspace structure looks like to start with - :root:operators:mounts and :root:providers:mounts are used in the pr, so we didn't fuck with that, and :root:consumer is where we're gonna put our clusters
kcp has a workspace concept, where you can make arbitrary (nested) workspaces, and put resources in them. workspaces point to a "logical cluster", which is a separate prefix in etcd
so like, a workspace is an inode, and a logical cluster is a directory itself (i think? possibly???????)
so like, a workspace is an inode, and a logical cluster is a directory itself (i think? possibly???????)
December 19, 2024 at 4:17 PM
kcp has a workspace concept, where you can make arbitrary (nested) workspaces, and put resources in them. workspaces point to a "logical cluster", which is a separate prefix in etcd
so like, a workspace is an inode, and a logical cluster is a directory itself (i think? possibly???????)
so like, a workspace is an inode, and a logical cluster is a directory itself (i think? possibly???????)
e.g: this is me talking against a kcp server running locally - note that you can talk to it like it's kubernetes, but it doesn't have nodes and pods and stuff
December 19, 2024 at 4:11 PM
e.g: this is me talking against a kcp server running locally - note that you can talk to it like it's kubernetes, but it doesn't have nodes and pods and stuff
t t t t t t t t t a r g e t t t t t
November 16, 2024 at 5:45 PM
t t t t t t t t t a r g e t t t t t