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
We can rearrange how we accept service definitions from values yaml to have more flexibility The new solution should allow us to:
Current:
services: https: servicePort: 9999 containerPort: 9999 ingressPort: 443 dataService: true clusterbind: servicePort: 7600 containerPort: 7600 clusterService: true clusterfail: servicePort: 7700 containerPort: 7700 clusterService: true clusterExternalDNSHostname:
Proposed:
services: data: annotations: {} https: servicePort: 9999 containerPort: 9999 ingressPort: 443 cluster: annotations: {} clusterbind: servicePort: 7600 containerPort: 7600 clusterService: true clusterfail: servicePort: 7700 containerPort: 7700 clusterService: true loadbalancer: annotations: {}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We can rearrange how we accept service definitions from values yaml to have more flexibility
The new solution should allow us to:
Current:
Proposed:
The text was updated successfully, but these errors were encountered: