-
Notifications
You must be signed in to change notification settings - Fork 1
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
[VSSL-11995] VESSL_NGINX_ENABLED 추가 #75
Conversation
@@ -2,6 +2,7 @@ agent: | |||
accessToken: # required | |||
clusterName: | |||
providerType: on-premise # on-premise, aws, gcp, oci, azure | |||
nginxEnabled: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
value만 추가하는 것이 아니라 helm chart에 sub-chart로 nginx-ingress-controller를 설치하고 싶어요
+) 지금은 aron-onprem에서 설치하고 있을겁니다.
+) nginx-ingress-controller 추가 설정이 필요한 것으로 알고있습니다. 관련해서 @synthdnb 에게 여쭤보시지요
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vessl-nginx: | ||
enabled: true | ||
controller: | ||
ingressClass: | ||
name: "vessl-nginx" | ||
service: | ||
# This will create nodePort service on cluster biding port 80 and 443. | ||
# Set this to false if cluster already has other ingress controller, such as ingress-nginx | ||
create: false | ||
# enableSnippets must be true to run VESSL service in nodeport mode | ||
enableSnippets: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
No description provided.