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.

Sign up for GitHub

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

Jump to bottom

Update docs old env variables #1986

Merged
merged 1 commit into from
Apr 12, 2024
Merged

Update docs old env variables #1986

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 1 addition & 2 deletions docs/manual/warnings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,7 @@ The `podTemplate` field allows you to customize nearly every part of the pods th
* The `foundationdb` container will always have volume mounts with the names `data`, `dynamic-conf`, and `fdb-trace-logs`, which will be defined by the operator. You cannot define volume mounts with these names.
* The `foundationdb-kubernetes-sidecar` and `foundationdb-kubernetes-init` containers will always have volume mounts with the names `config-map` and `dynamic-conf`, which will be defined by the operator. You cannot define volume mounts with these names.
* The `foundationdb` container will always have environment variables with the names `FDB_CLUSTER_FILE` and `FDB_TLS_CA_FILE`. You can define custom values for these environment variables. If you do not define them, the operator will provide a value.
* The `foundationdb-kubernetes-sidecar` and `foundationdb-kubernetes-init` containers will always have environment variables with the names `SIDECAR_CONF_DIR`, `FDB_PUBLIC_IP`, `FDB_MACHINE_ID`, `FDB_ZONE_ID`, and `FDB_INSTANCE_ID`. You can define custom values for these environment variables. If you do not define them, the operator will provide a value.
* The `foundationdb-kubernetes-init` container will always have an environment variable with the names `COPY_ONCE`. You can define custom values for these environment variables. If you do not define them, the operator will provide a value.
* The `foundationdb-kubernetes-sidecar` and `foundationdb-kubernetes-init` containers will always have environment variables with the names `FDB_PUBLIC_IP`, `FDB_MACHINE_ID`, `FDB_ZONE_ID`, and `FDB_INSTANCE_ID`. You can define custom values for these environment variables. If you do not define them, the operator will provide a value.
* The `foundationdb-kubernetes-sidecar` container will always have environment variables with the names `FDB_TLS_VERIFY_PEERS` and `FDB_TLS_CA_FILE`. You can define custom values for these environment variables. If you do not define them, the operator will provide a value.
* If you specify the environment variable `ADDITIONAL_ENV_FILE` for the `foundationdb-kubernetes-sidecar` and `foundationdb-kubernetes-init` containers, its content will be sourced before any container command runs, and you can override or define there any other environment variable; this can be used for example to inject environment variables using a shared volume.
* The `foundationdb-kubernetes-sidecar` container will always have a readiness probe defined. If you do not define one, the operator will provide a default readiness probe.
Expand Down
Loading