Thomas Johander LoPan455

If a remote server has password access disabled and relies on authorized SSH keys to manage user access, things can get tricky.

The scenario this gist will solve is:

1. Server A (10.0.1.20) has a user account, ubuntu, that we need to be able to use to login to it from a variety of hosts.
2. User A has access to a Server A (10.0.1.20) via SSH. Therfore User A's public key is present in Server A's 'authorized_keys' file.
3. User A's private key is present on a Bastion host that allows password logins.
4. User B needs to access Server A, and therefore needs her public key copied to Server A. Server A doesn't allow password logins, so we're stuck.

`https://kubernetes.io/docs/concepts/workloads/pods/ Pods are the smallest deployable units of computing that you can create and manage in Kubernetes.

A Pod (as in a pod of whales or pea pod) is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. A Pod's contents are always co-located and co-scheduled, and run in a shared context. A Pod models an application-specific "logical host": it contains one or more application containers which are relatively tightly coupled. In non-cloud contexts, applications executed on the same physical or virtual machine are analogous to cloud applications executed on the same logical host.

A pod might be analagous to a single VM that runs multiple services.

As well as application containers, a Pod can contain init containers that run during Pod startup. You can also inject ephemeral containers for debugging if your cluster offers this.

There is a file, /etc/cloud/cloud-init.d/99-installer.cfg that holds the defualt, "no sourece" user data. That will be used if you don't add the line below it that looks like: datasource=[NoCloud], or you edit the "no source" user-data to hold the stuff you want.

• Make sure you turn on the "QEMU Geust Agent" in either the UI or set on the VM via the CLI

You can create VMs from the command line like:

sudo qm clone 9990 404 --name ci-test-8
sudo qm set 404 --cicustom "user=snippets:snippets/user-data.yaml" --ipconfig0 "ip=dhcp" --agent enabled=1

Proxmox VE 6.x release includes a feature to add custom cloud-init configs. Unfortunately there is poor documentation, so I had to figure this out by adding pieces of information together.

The cloud-init files need to be stored in a snippet. This is not very well documented:

1. Go to Storage View -> Storage -> Add -> Directory
2. Give it an ID such as snippets, and specify any path on your host such as /snippets
3. Under Content choose Snippets and de-select Disk image (optional)
4. Upload (scp/rsync/whatever) your user-data, meta-data, network-config files to your proxmox server in /snippets/snippets/ (the directory should be there if you followed steps 1-3)

In the example below, I can't use a ParameterizedTypeReference because the compiler erases type information (maybe some additional research on that would be helpful) So you can't do ParameterizedTypeReference<List<Post>>().

In order to get around that, you have to hack this private function together:

fun getPosts(): Mono<PostList> =
        apiClient
            .get()
 .uri { builder -&gt; builder.path("/posts").build() }