Back to Cilium

Protocol Documentation

api/v1/relay/README.md

1.19.34.4 KB
Original Source

Protocol Documentation

<a name="top"></a>

Table of Contents

<a name="relay_relay-proto"></a>

<p align="right"><a href="#top">Top</a></p>

relay/relay.proto

<a name="relay-NodeStatusEvent"></a>

NodeStatusEvent

NodeStatusEvent is a message sent by hubble-relay to inform clients about the state of a particular node.

FieldTypeLabelDescription
state_changeNodeStatestate_change contains the new node state
node_namesstringrepeatednode_names is the list of nodes for which the above state changes applies
messagestringmessage is an optional message attached to the state change (e.g. an error message). The message applies to all nodes in node_names.

<a name="relay-NodeState"></a>

NodeState

NameNumberDescription
UNKNOWN_NODE_STATE0UNKNOWN_NODE_STATE indicates that the state of this node is unknown.
NODE_CONNECTED1NODE_CONNECTED indicates that we have established a connection to this node. The client can expect to observe flows from this node.
NODE_UNAVAILABLE2NODE_UNAVAILABLE indicates that the connection to this node is currently unavailable. The client can expect to not see any flows from this node until either the connection is re-established or the node is gone.
NODE_GONE3NODE_GONE indicates that a node has been removed from the cluster. No reconnection attempts will be made.
NODE_ERROR4NODE_ERROR indicates that a node has reported an error while processing the request. No reconnection attempts will be made.

Scalar Value Types

.proto TypeNotesC++JavaPythonGoC#PHPRuby
<a name="double" /> doubledoubledoublefloatfloat64doublefloatFloat
<a name="float" /> floatfloatfloatfloatfloat32floatfloatFloat
<a name="int32" /> int32Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint32 instead.int32intintint32intintegerBignum or Fixnum (as required)
<a name="int64" /> int64Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint64 instead.int64longint/longint64longinteger/stringBignum
<a name="uint32" /> uint32Uses variable-length encoding.uint32intint/longuint32uintintegerBignum or Fixnum (as required)
<a name="uint64" /> uint64Uses variable-length encoding.uint64longint/longuint64ulonginteger/stringBignum or Fixnum (as required)
<a name="sint32" /> sint32Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int32s.int32intintint32intintegerBignum or Fixnum (as required)
<a name="sint64" /> sint64Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int64s.int64longint/longint64longinteger/stringBignum
<a name="fixed32" /> fixed32Always four bytes. More efficient than uint32 if values are often greater than 2^28.uint32intintuint32uintintegerBignum or Fixnum (as required)
<a name="fixed64" /> fixed64Always eight bytes. More efficient than uint64 if values are often greater than 2^56.uint64longint/longuint64ulonginteger/stringBignum
<a name="sfixed32" /> sfixed32Always four bytes.int32intintint32intintegerBignum or Fixnum (as required)
<a name="sfixed64" /> sfixed64Always eight bytes.int64longint/longint64longinteger/stringBignum
<a name="bool" /> boolboolbooleanbooleanboolboolbooleanTrueClass/FalseClass
<a name="string" /> stringA string must always contain UTF-8 encoded or 7-bit ASCII text.stringStringstr/unicodestringstringstringString (UTF-8)
<a name="bytes" /> bytesMay contain any arbitrary sequence of bytes.stringByteStringstr[]byteByteStringstringString (ASCII-8BIT)