search

Twingate / kubernetes-operator

Twingate Kubernetes Operator allows configuring Twingate using Kubernetes assets - OSS
https://www.twingate.com
Mozilla Public License 2.0
23 stars 2 forks source link

Get remote network name/ID from k8s secret #122

Open blakemorgan opened 9 months ago

blakemorgan commented 9 months ago

What is missing?

Currently, we have to hard code the remoteNetworkName or remoteNetworkId. It would be nice if we could fetch this from a existing k8s secret like we can with the Twingate API key.

Why do we need it?

The way our automation works, it's easier to fetch dynamic values from a resources that already exists on the cluster rather than set it as a value in a Helm chart. If we were able to fetch the remote network name/ID from a k8s secret, we could hydrate the cluster with that information dynamically before deploying any Helm applications to it. That would allow us to use the same values.yaml file for each cluster with different remote network rather than create a file for each cluster.

Additionally, it may be nice to have twingateOperator just read it all its settings from a pre-existing ConfigMap, but that's irrelevant to our use case.

Environment

Anything else we need to know?:

linear[bot] commented 9 months ago

OSS-5 Get remote network name/ID from k8s secret

github-actions[bot] commented 6 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.