Skip to content

HTTP Server#

Management → HSHTTP Servers

The HTTPServer enables the JSON-RPC programmable interface on a node.

Support is currently limited to SR Linux.

HTTPS#

If the selected protocol is HTTPS instead of HTTP, the tlsProfile property must reference a valid TLS profile deployed on the node.

Dependencies#

Each HTTPServer resource targets either a ManagementRouter, a DefaultRouter, or a Router. While only one of the three is required, all three are listed as dependencies.

ManagementRouter#

If the HTTPServer is reachable through a ManagementRouter, the resource referenced by the router property must exist.

Management routers cannot be selected through label selectors.

DefaultRouter#

If the HTTPServer is reachable through a DefaultRouter, the resource referenced by the router property must exist.

Label selectors may be used to select multiple DefaultRouters.

Router#

If the HTTPServer is reachable through a Router, the resource referenced by the router property must exist.

Routers cannot be selected through label selectors.

Referenced resources#

The HTTPServer does not reference any other EDA resources.

Examples#

apiVersion: management.eda.nokia.com/v1
kind: HTTPServer
metadata:
  name: http-server
  namespace: eda
spec:
  enableAuthentication: true
  enabled: true
  protocol: HTTP
  router: init-base-mgmt-router
  routerKind: ManagementRouter

cat << 'EOF' | kubectl apply -f -
apiVersion: management.eda.nokia.com/v1
kind: HTTPServer
metadata:
  name: http-server
  namespace: eda
spec:
  enableAuthentication: true
  enabled: true
  protocol: HTTP
  router: init-base-mgmt-router
  routerKind: ManagementRouter
EOF

Custom Resource Definition#

To browse the Custom Resource Definition go to crd.eda.dev.

HTTPServer

management.eda.nokia.com / v1

SPEC

HTTPServerSpec defines the desired state of HTTPServer

  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #

STATUS

HTTPServerStatus defines the observed state of HTTPServer

  • #
  • #
  • #
  • #
  • #