Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Custom vRouter settings¶
TechPreview
Depending on the Tungsten Fabric Operator API version in use, proceed with one of the following options:
To specify custom settings for the Tungsten Fabric vRouter nodes, for
example, to change the name of the tunnel network interface or enable
debug level logging on some subset of nodes, use the nodes settings in
the TFOperator custom resource.
For example, to enable debug level logging on a specific node or multiple nodes:
spec:
nodes:
<CUSTOMSPEC-NAME>:
labels:
name: <NODE-LABEL>
value: <NODE-LABEL-VALUE>
nodeVRouter:
enabled: true
envSettings:
agent:
env:
- name: LOG_LEVEL
value: SYS_DEBUG
To specify custom settings for the Tungsten Fabric vRouter nodes, for
example, to change the name of the tunnel network interface or enable
debug level logging on some subset of nodes, use the customSpecs
settings in the TFOperator custom resource.
For example, to enable debug level logging on a specific node or multiple nodes:
spec:
controllers:
tf-vrouter:
agent:
customSpecs:
- name: <CUSTOMSPEC-NAME>
label:
name: <NODE-LABEL>
value: <NODE-LABEL-VALUE>
containers:
- name: agent
env:
- name: LOG_LEVEL
value: SYS_DEBUG
Caution
The customspecs:name value must follow the RFC 1123
international format. Verify that the name of a DaemonSet object
is a valid DNS subdomain name.
The customSpecs parameter inherits all settings for the tf-vrouter
containers that are set on the spec:controllers:agent level and
overrides or adds additional parameters. The example configuration above
overrides the logging level from SYS_INFO, which is the default logging
level, to SYS_DEBUG.
For clusters with a multi-rack architecture, you may need to redefine the
gateway IP for the Tungsten Fabric vRouter nodes using the
VROUTER_GATEWAY parameter. For details, see Multi-rack architecture.