You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the deployment uses `nip.io` for ingress (no DNS setup required). To use your own domain, add `--set ingress.domain="your-domain"` to the helm command above.
109
+
110
+
For detailed instructions on custom domain setup and required DNS records, see [Custom Domain Configuration](INGRESS_AND_TLS_SETUP.md#custom-domain-configuration).
111
+
106
112
### OPTION 2: Install control plane with your existing grafana & prometheus to existing OKE cluster
107
113
108
114
If you already have Prometheus Postgateway and Grafana running, login to existing OKE cluster where you would like to install this:
--set backend.superuser.username="username for API & control plane e.g. admin" \
124
130
--set backend.superuser.email="your email" \
125
131
--set backend.superuser.password="access password for API & control plane" \
126
-
--set grafana.adminPassword="access password for grafana portal. User name is admin by default" \
127
-
132
+
--set grafana.adminPassword="access password for grafana portal. User name is admin by default"
128
133
```
129
134
135
+
**Optional: Custom Domain Configuration**
136
+
137
+
By default, the deployment uses `nip.io` for ingress (no DNS setup required). To use your own domain, add `--set ingress.domain="your-domain"` to the helm command above.
138
+
139
+
For detailed instructions on custom domain setup and required DNS records, see [Custom Domain Configuration](INGRESS_AND_TLS_SETUP.md#custom-domain-configuration).
140
+
130
141
## Verify for successful install
131
142
132
143
Once the installation is complete you should see the following pods in the "lens" namespace. If you don't please uninstall and reinstall or check the helm install events/logs.
Copy file name to clipboardExpand all lines: GETTING_STARTED_RM_DEPLOY.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,7 @@ The deployment automatically installs **ingress-nginx** and **cert-manager** for
59
59
- Configure parameters:
60
60
-**Create IAM Policy:** Enable if you wish to create the workload identity IAM policy for the backend service account.
61
61
-**IAM Policy Name:** Default is `corrino-lens-backend-workload-policy`
62
+
-**Ingress Domain:** (Optional) Custom domain for ingress. Leave empty to use `nip.io` wildcard DNS service (recommended for quick start, no DNS setup required). If you provide a custom domain, you must manually create DNS records. See [Custom Domain Configuration](INGRESS_AND_TLS_SETUP.md#custom-domain-configuration) for details.
62
63
-**Superuser Username:** Username for the OCI GPU Scanner Portal (default: `admin`)
63
64
-**Superuser Password:** Password for the OCI GPU Scanner Portal (default: `supersecret`) — **Recommended to change for production**
64
65
-**Superuser Email:** Email address for the superuser account (default: `[email protected]`)
@@ -75,7 +76,9 @@ Access the OKE cluster using the credentials created for the new OKE cluster.
75
76
After connecting with OKE cluster run the below command
76
77
```kubectl get ingress -n lens```
77
78
78
-
Copy the HOSTS details for all the applications deployed by lens. e.g. lens.129.80.43.138.nip.io
79
+
Copy the HOSTS details for all the applications deployed by lens. e.g. lens.129.80.43.138.nip.io
80
+
81
+
**Note:** If you configured a custom domain during deployment, you need to manually create DNS records. See [Custom Domain Configuration](INGRESS_AND_TLS_SETUP.md#custom-domain-configuration) for detailed instructions.
Copy file name to clipboardExpand all lines: INGRESS_AND_TLS_SETUP.md
+69Lines changed: 69 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,75 @@ kubectl get crd | grep cert-manager || echo "No cert-manager CRDs"
97
97
98
98
---
99
99
100
+
## Custom Domain Configuration
101
+
102
+
By default, OCI GPU Scanner uses `nip.io` for ingress, which is a wildcard DNS service that requires no manual DNS configuration. All URLs will be in the format `<service>.<LOADBALANCER_IP>.nip.io` (e.g., `lens.129.80.43.138.nip.io`).
103
+
104
+
### Using nip.io (Default - Recommended for Quick Start)
105
+
106
+
**No DNS configuration required!** The deployment automatically uses `nip.io`, which provides wildcard DNS resolution based on the LoadBalancer IP address.
107
+
108
+
**Helm installation:** No additional parameters needed - this is the default behavior.
109
+
110
+
**Resource Manager:** Leave the "Ingress Domain" field empty.
111
+
112
+
### Using a Custom Domain
113
+
114
+
If you prefer to use your own domain instead of `nip.io`, you can configure a custom domain during installation. However, you **must manually create DNS A records** in your DNS provider.
115
+
116
+
If you prefer to use `.oci-incubations.com` as your domain, contact [email protected] or [email protected] for adding DNS A records after deployment.
117
+
118
+
#### Step 1: Configure Custom Domain During Installation
0 commit comments