Closed fifthpostulate closed 4 years ago
Hi @fifthpostulate
In order to not have to implement every Kubernetes feature in ContainerProxy, we decided to add a generic way of adding Kubernetes specific configuration to a ContainerProxy app. This feature is called kubernetes-pod-patches
and allows to patch the specification of the Pod before it is created by ContainerProxy.
More information about this feature can be found here (you have to scroll down a bit).
An example to change the ServiceAccount is included.
This should cover your use-case. Feel free to open an issue if you experience any issue with this feature.
The change is included in the just ShinyProxy 2.4.0
Again thanks for your contribution.
In the application configuration for Kubernetes backend users it would be useful to be able to assign a service account to the application pods. Something like this:
This would allow AWS EKS users to use Kubernetes service account to IAM role bindings to enable connectivity to Hive, Aurora, or any other platform dependencies.