Master node | Minimum | Recommended |
---|---|---|
CPU | 4 cores | 16 cores |
RAM | 16GB | 64GB |
Worker nodes | Minimum | Recommended |
---|---|---|
CPU | 4 cores | 16 cores |
RAM | 16GB | 64GB |
nproc
.
https://anaconda.yourdomain.com/apps/001
and
https://anaconda.yourdomain.com/apps/002
, one app could access the cookies of the other, and JavaScript in one app could access the other app.
To prevent this potential security risk, Anaconda assigns deployments unique addresses such as
https://uuid001.anaconda.yourdomain.com
and
https://uuid002.anaconda.yourdomain.com
, where yourdomain.com
is replaced with your organization’s domain name, and uuid001
and uuid002
is replaced with dynamically generated universally unique identifiers (UUIDs), for example.
To facilitate this, Anaconda Enterprise requires the use of wildcard DNS entries that apply to a set of domain names such as *.anaconda.yourdomain.com
.
For example, if you are using the fully qualified domain name (FQDN) anaconda.yourdomain.com
with a master node IP address of 12.34.56.78
, the DNS entries would be as follows:
<node>
role=ae-master<node>
cluster_role=ae-master<node>
app_role=storage<node>
role=ae-worker<node>
cluster_role=ae-worker<ae5>.apps.<OCP>
[\*](#id1).<ae5>.apps.<OCP>
oc
:
main
and ui
, respectively.
gpu=true
label is applied to all GPU nodes.<node>
role=ae-master<node>
cluster_role=ae-master<node>
app_role=storage<node>
role=ae-worker<node>
cluster_role=ae-workervalues.yaml
will need to be customized with an FQDN and provisioner. Once done, run the following:
gpu=true
.