Transition away from containerized `cloudflared` #1

New issue

Closed

opened 2024-03-28 04:38:35 +00:00 by marc · 1 comment

marc commented

2024-03-28 04:38:35 +00:00

Owner

Description

Using cloudflared in a container causes more problem than it solves, namely for networking.

Since rootless containers are used, networks can't be created, so we're bound to stash all the services under one large pod, which quickly becomes an antipattern once you've got unrelated services living together in the same namespace.

Definition of done

Containers should be moved out of the services pod into their own;
The bastion service should be removed, cloudflared should be run directly on the machine.

# Description Using `cloudflared` in a container causes more problem than it solves, namely for networking. Since rootless containers are used, networks can't be created, so we're bound to stash all the services under one large pod, which quickly becomes an antipattern once you've got unrelated services living together in the same namespace. # Definition of done - Containers should be moved out of the `services` pod into their own; - The `bastion` service should be removed, `cloudflared` should be run directly on the machine.

marc added this to the Development project 2024-03-28 04:39:11 +00:00

marc commented

2024-03-31 19:10:02 +00:00

Author

Owner

Done as of 9a068d849d

Done as of 9a068d849d46de61904cea6ee14288be332ef2d0

marc closed this issue

2024-03-31 19:10:04 +00:00

This repo is archived. You cannot comment on issues.

No labels

No milestone

No project

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: marc/spadinastan#1

No description provided.

Transition away from containerized cloudflared #1

Description

Definition of done

Transition away from containerized `cloudflared` #1