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

ingress removed #87

Merged
merged 6 commits into from
Mar 15, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions devdocs/helm-chart.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@ The Helm chart for this driver includes the following features:

- A Deployment to create pods for your driver application
- A Service to expose your application internally and externally (with a NodePort)
- Ingress rule to expose your application externally with Ingress (Ingress controller required on Kubernetes cluster. By default, LM installs an Ingress controller for you)
- Configurable options for:
- Location and version of Docker image
- Number of replicas of the driver
Expand All @@ -13,7 +12,6 @@ The Helm chart for this driver includes the following features:
- Pod affinity/anti-affinity
- Node affinity/anti/affinity
- NodePort
- Ingress Host
- Necessary Deployment labels so logs from the driver may be viewed in the dashboard provided with LM (Kibana)

# Build Helm Chart
Expand Down
2 changes: 0 additions & 2 deletions docs/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,8 +98,6 @@ The following table lists configurable parameters of the chart:
| app.resources | Set requests and limits to CPU and memory resources | {} |
| service.type | Type of Service to be deployed | NodePort |
| service.nodePort | NodePort used to expose the service | 31684 |
| ingress.enabled | Flag to disable/enable creation of an Ingress rule for external access | true |
| ingress.host | Hostname on the Ingress rule | kubedriver.lm |

## Application Configuration

Expand Down
18 changes: 0 additions & 18 deletions helm/kubedriver/templates/ingress.yaml

This file was deleted.

8 changes: 0 additions & 8 deletions helm/kubedriver/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -137,11 +137,3 @@ service:
# Using NodePort allows access to the IPs through http://k8s-host:nodePort/
type: NodePort
nodePort: 31684

ingress:
enabled: true
## The host used to access the service externally i.e. http://<server.ingress.hostname>/
## If not making use of a DNS to resolve this host you must add this to the client hosts file with the K8s IP
## E.g.
## 10.220.1.2 kubedriver.lm
host: kubedriver.lm