Skip to main content

TerminalSpec

Description

TerminalSpec defines the desired state of Terminal


TermDesc field

Kind: TermDesc
Data Type: Struct
Optional: False


Applications field of tag applications

A map of optional Applications to be running as sidecars in the Terminal Pod. The key is the name of the Application, and the value is the ContainerDefinition. The key should always start with the prefix "app-" to avoid conflicts with the other containers. These Applications would have the same networking configuration as the Terminal, hence enjoying the 4G/5G connectivity.

Kind: Map of string to ContainerDefinition
Tag: applications
Manager Tag: applications
Data Type: Map
Optional: True


Slice field of tag slice

Slice of Terminal object.

Kind: TermSlice
Tag: slice
Data Type: Struct
Optional: False


TargetCores field of tag target-cores

TargetCores that the UE should be registered to.

Tag: target-cores
Manager Tag: -
Data Type: Slice
List Type: set
Optional: False


PreferredAccess field of tag preferred-access

PreferredAccess is the preferred AN the UE should be connected to, mainly used for scheduling.

Kind: *./api/v1.FullTag
Tag: preferred-access
Manager Tag: preferred-access
Data Type: Pointer
Optional: True


Identity field of tag identity

Identity of the UE.

Tag: identity
Manager Tag: identity
Data Type: Struct
Optional: False


IMS field of tag ims

IMS information of the UE.

Kind: *./api/v1.TermIMS
Tag: ims
Manager Tag: ims
Data Type: Pointer
Optional: True


Radio field of tag radio

Radio aspects of the UE configuration.

Kind: TermRadio
Tag: radio
Manager Tag: radio
Data Type: Struct
Optional: False


ReadinessCheck field of tag readiness-check

ReadinessCheck method for checking readiness of the UE.

Kind: *./api/v1.ReadinessCheck
Tag: readiness-check
Manager Tag: readiness-check
Data Type: Pointer
Optional: True