You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Helm/K8S implementation for our proof server is mainly thought for a usage along the eksctl configuration file in the repository. It forces the users to have deployed hardware with a special tag, r7iz.metal-32xl to know which instances/nodes to deploy the cluster pods.
As mentioned by @huitseekerin #228, we could move away from this nodeSelector behavior and instead leverage ressources configuration.
The text was updated successfully, but these errors were encountered:
The current Helm/K8S implementation for our proof server is mainly thought for a usage along the
eksctl
configuration file in the repository. It forces the users to have deployed hardware with a special tag,r7iz.metal-32xl
to know which instances/nodes to deploy the cluster pods.As mentioned by @huitseeker in #228, we could move away from this
nodeSelector
behavior and instead leverage ressources configuration.The text was updated successfully, but these errors were encountered: