Go to file
Dustin c48076b8f0 test: Adjust k8s roles for integration tests
Initially, I thought it was necessary to use a ClusterRole in order to
assign permissions in one namespace to a service account in another.  It
turns out, this is not necessary, as RoleBinding rules can refer to
subjects in any namespace.  Thus, we can limit the privileges of the
*dynk8s-provisioner* service account by only allowing it access to the
Secret and ConfigMap resources in the *kube-system* and *kube-public*
namespaces, respectively, plus the Secret resources in its own
namespace.
2022-10-11 21:08:49 -05:00
ci tests: Begin integration tests 2022-10-07 07:37:20 -05:00
src events: Delete Node on instance termination 2022-10-11 20:00:24 -05:00
terraform terraform: Begin AWS configuration 2022-09-27 12:58:51 -05:00
tests test: Adjust k8s roles for integration tests 2022-10-11 21:08:49 -05:00
.dockerignore ci: Begin Jenkins build pipeline 2022-09-10 10:30:54 -05:00
.editorconfig ci: Begin Jenkins build pipeline 2022-09-10 10:30:54 -05:00
.gitattributes Initial commit 2022-08-31 21:02:17 -05:00
.gitignore sns: Save messages to disk 2022-09-05 09:45:44 -05:00
Cargo.lock routes: Add kubeadm kubeconfig resource 2022-10-07 06:52:06 -05:00
Cargo.toml routes: Add kubeadm kubeconfig resource 2022-10-07 06:52:06 -05:00
Containerfile container: Rebase on Fedora 35 2022-09-11 13:17:54 -05:00
rustfmt.toml Initial commit 2022-08-31 21:02:17 -05:00