Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to use NodePort and LoadBalancer type for deployment #695

Open
manojkumargogula opened this issue Apr 18, 2024 · 1 comment
Open
Labels
good first issue Good for newcomers help wanted Extra attention is needed improvement

Comments

@manojkumargogula
Copy link

Hey i want to to use loadbalancer type for the services of temporal and temporal ui, how could i do that.

apiVersion: temporal.io/v1beta1
kind: TemporalCluster
metadata:
name: prod
namespace: demo
spec:
version: 1.22.7
numHistoryShards: 1
persistence:
defaultStore:
sql:
user: temporal
pluginName: mysql
databaseName: temporal
connectAddr: mysql.demo.svc.cluster.local:3306
connectProtocol: tcp
passwordSecretRef:
name: mysql-password
key: PASSWORD
visibilityStore:
sql:
user: temporal
pluginName: mysql
databaseName: temporal_visibility
connectAddr: mysql.demo.svc.cluster.local:3306
connectProtocol: tcp
passwordSecretRef:
name: mysql-password
key: PASSWORD
ui:
enabled: true
admintools:
enabled: true
metrics:
enabled: false

@alexandrevilain
Copy link
Owner

Hi! @manojkumargogula !

You're right, this is not supported for now.
Isn't an ingress a good solution for you ?

While waiting for this feature to be available, you can duplicate the ui service on your cluster.

@alexandrevilain alexandrevilain added help wanted Extra attention is needed good first issue Good for newcomers improvement labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed improvement
Projects
None yet
Development

No branches or pull requests

2 participants