We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hi
with values.yaml added with type below, I am able to deploy AWX on IBM Cloud Private (ICP), a Kubernetes cluster.
ICP comes with a helm catalog where I point to helm repo for demo with modified helm chart.
type: NodePort
would suggest adding a type in the values.yaml since awx/templates/service.yaml reference to it where it uses ClusterIP by default.
With above changes, once can specify NodePort, ClusterIP, LoadBalancer as value in the helm deployment.
The text was updated successfully, but these errors were encountered:
Hi type can be easily configured while running helm install and setting type as loadbalancer like this: --set service.type=LoadBalancer
Sorry, something went wrong.
No branches or pull requests
hi
with values.yaml added with type below, I am able to deploy AWX on IBM Cloud Private (ICP), a Kubernetes cluster.
ICP comes with a helm catalog where I point to helm repo for demo with modified helm chart.
type: NodePort
would suggest adding a type in the values.yaml since awx/templates/service.yaml reference to it where it uses ClusterIP by default.
With above changes, once can specify NodePort, ClusterIP, LoadBalancer as value in the helm deployment.
The text was updated successfully, but these errors were encountered: