Merge branch 'master' into feature/cloud-dedicated-user-management-docs
commit
c0cf22c166
|
|
@ -52,7 +52,7 @@ stored in an InfluxDB database.
|
|||
|
||||
### Install prerequisites for Superset and Flight SQL
|
||||
|
||||
We recommend using **Docker and docker-compose** to run Superset.
|
||||
We recommend using **Docker and Docker Compose** to run Superset.
|
||||
To set up Superset to run in Docker containers with Flight SQL, follow these steps:
|
||||
|
||||
> [!Warning]
|
||||
|
|
@ -60,7 +60,7 @@ To set up Superset to run in Docker containers with Flight SQL, follow these ste
|
|||
> Windows and Docker, see the
|
||||
> [Superset documentation](https://superset.apache.org/docs/installation/docker-compose).
|
||||
|
||||
1. Follow the instructions to download and install Docker and docker-compose for your system:
|
||||
1. Follow the instructions to download and install Docker and Docker Compose for your system:
|
||||
|
||||
- **macOS**: [Install Docker for macOS](https://docs.docker.com/desktop/install/mac-install/)
|
||||
- **Linux**: [Install Docker for Linux](https://docs.docker.com/desktop/install/linux-install/)
|
||||
|
|
@ -154,7 +154,7 @@ pip3 install flightsql-dbapi
|
|||
3. Use the `docker-compose pull` command to fetch dependencies for the Docker containers.
|
||||
|
||||
```sh
|
||||
docker-compose -f docker-compose-non-dev.yml pull
|
||||
docker compose -f docker-compose-non-dev.yml pull
|
||||
```
|
||||
|
||||
The process might take several seconds to complete.
|
||||
|
|
@ -165,7 +165,7 @@ pip3 install flightsql-dbapi
|
|||
To start the containers and run Superset, enter the `docker-compose up` command and pass the `-f` flag with the setup file name:
|
||||
|
||||
```sh
|
||||
docker-compose -f docker-compose-non-dev.yml up
|
||||
docker compose -f docker-compose-non-dev.yml up
|
||||
```
|
||||
|
||||
This might take several seconds to complete.
|
||||
|
|
|
|||
|
|
@ -141,6 +141,84 @@ Before your license expires, your InfluxData sales representative will
|
|||
contact you about license renewal.
|
||||
You may also contact your sales representative at any time.
|
||||
|
||||
### Apply your renewed license
|
||||
|
||||
When you receive your renewed license file from InfluxData:
|
||||
|
||||
1. Use `kubectl` to apply the updated license:
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
||||
```sh
|
||||
kubectl apply --filename license.yml --namespace influxdb
|
||||
```
|
||||
|
||||
> [!Note]
|
||||
> You may see a warning about missing `kubectl.kubernetes.io/last-applied-configuration` annotation.
|
||||
> This warning is expected and can be safely ignored—the license will be applied successfully.
|
||||
|
||||
2. [Verify the license update](#verify-your-license) by checking that:
|
||||
- The `iox-license` secret is updated
|
||||
- Database pods remain in `Running` state
|
||||
- No license-related errors appear in pod logs
|
||||
|
||||
### License validation timing
|
||||
|
||||
InfluxDB Clustered validates licenses:
|
||||
- When pods start up
|
||||
- Periodically during operation (roughly once per hour)
|
||||
|
||||
After applying a renewed license, the system should automatically detect and use the new license during the next validation cycle.
|
||||
|
||||
### Troubleshooting license renewal
|
||||
|
||||
If you experience query failures with "no license found" errors after applying a renewed license:
|
||||
|
||||
1. **Check the license secret**:
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
||||
```sh
|
||||
kubectl get secret iox-license --namespace influxdb -o yaml
|
||||
```
|
||||
|
||||
Verify the secret was updated with the new license data.
|
||||
|
||||
2. **Check license controller logs**:
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
||||
```sh
|
||||
kubectl logs deployment/license-controller --namespace influxdb
|
||||
```
|
||||
|
||||
Look for successful license processing messages or any errors.
|
||||
|
||||
3. **Verify pod status**:
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
||||
```sh
|
||||
kubectl get pods -l app=iox --namespace influxdb
|
||||
```
|
||||
|
||||
Ensure all pods are in `Running` state and not crash-looping.
|
||||
|
||||
4. **If issues persist**, you may need to restart affected services:
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
||||
```sh
|
||||
# Scale down the querier service
|
||||
kubectl scale deployment iox-shared-querier --replicas=0 --namespace influxdb
|
||||
|
||||
# Wait for pods to terminate, then scale back up
|
||||
kubectl scale deployment iox-shared-querier --replicas=1 --namespace influxdb
|
||||
```
|
||||
|
||||
> [!Important]
|
||||
> Service restart should not be routinely necessary. If you consistently need to restart services after license renewal, contact InfluxData support.
|
||||
|
||||
---
|
||||
|
||||
## License enforcement
|
||||
|
|
|
|||
|
|
@ -1,14 +0,0 @@
|
|||
{
|
||||
"summary": {
|
||||
"total_checked": 79,
|
||||
"broken_count": 0,
|
||||
"success_rate": 100.0,
|
||||
"duration_ms": null
|
||||
},
|
||||
"broken_links": [],
|
||||
"metadata": {
|
||||
"timestamp": "2025-10-20T16:47:58.217901+00:00",
|
||||
"ci_mode": "Local",
|
||||
"version": "0.1.0"
|
||||
}
|
||||
}
|
||||
Loading…
Reference in New Issue